Because recognition happens locally, nothing is transmitted and the tool works offline once loaded, which suits classrooms as well as any document you would rather not upload. A first run downloads the engine and language pack, so do that while connected. Quality follows the scan: straight, clean pages recognize well; skewed or faded ones benefit from Clean scanned PDF first (run it before OCR, since cleanup rebuilds pages as images). A searchable text layer is also what screen readers need, which the Accessibility check will confirm. Spot-check names and numbers against the page.
How it works
- Open Bindery in Chrome and drop the scan into OCR
- Choose the language and searchable-PDF or plain-text output
- Download and test with Ctrl+F in Chrome’s viewer
Questions people ask
Is this the same as opening the PDF with Google Docs?
No. Docs OCR runs on Google’s servers after the file is uploaded to Drive and returns a document. Bindery keeps the file on the Chromebook, keeps every page pixel-identical, and adds an invisible text layer to the PDF itself so it stays a PDF that any viewer can search.
How long does a scan take on a Chromebook?
Roughly a few seconds per page on a typical model, running in a background worker you can cancel. The first use downloads the engine and the language pack once; after that OCR works offline, and the daily free allowance is ten completed jobs.
Which languages are available?
Eleven: English, Spanish, French, German, Portuguese, Italian, Arabic, Simplified Chinese, Japanese, Russian and Hindi. Pick the document’s language before running — the engine uses the pack to resolve ambiguous shapes, and the wrong pack costs accuracy. Each pack loads once from Bindery.