You have a PDF open. You press Ctrl+F, type a word you can plainly see on the screen, and the search finds nothing. Or you try to select a line of text and instead get a blue box over the whole page.
Nothing is broken. That PDF does not contain text at all — it contains a photograph of text. This guide explains the difference, what OCR does about it, and how much of it you can realistically expect to work.
The format allows both, and they look identical on screen.
| Born-digital PDF | Scanned PDF | |
|---|---|---|
| Where it comes from | Exported from Word, LibreOffice, a browser's Print-to-PDF, an accounting system | A flatbed scanner, an office multifunction machine, or a phone camera |
| What is inside | Actual character codes plus font information | One image per page, nothing else |
| Ctrl+F | Works | Finds nothing |
| Select and copy | Works | Selects the image |
| Typical size | Small — tens of kilobytes per page | Large — often several megabytes per page |
A third case trips people up: a born-digital PDF that was printed and then scanned. It began life as real text, but the text was thrown away the moment it hit paper. What you have now is a scan, and it needs the same treatment as any other scan.
OCR — optical character recognition — looks at the pixels of a page image and works out which letters they represent. It finds regions that look like text, splits them into lines and then into individual characters, compares each shape against a trained model, and outputs its best guess as real text.
Two things follow from this, and they explain most of what frustrates people about OCR:
OCR quality is decided almost entirely before you run it — by the image you feed in.
Open your PDF, then use the Convert bar. Three routes exist depending on what you want out.
Extracts the text and shows it in an editable box you can correct and copy. If the PDF is born-digital, this pulls the existing text layer directly — that is exact, instant, and unlimited, because no recognition is involved. If it is a scan, recognition runs on the page images.
Produces a new file that looks identical to the original but has an invisible text layer added, so Ctrl+F and text selection work. If you feed it a PDF that already has a text layer, it will tell you so rather than doing redundant work. This is the option you want for filing and archiving, because the visual document is preserved exactly.
Gives you an editable document. For born-digital PDFs this is free and unlimited, and it is text-accurate — but understand what that means: you get the words, not a pixel-perfect rebuild of the layout. Complex formatting, multi-column layouts and precise table structure will need fixing by hand. Any tool promising a perfect layout conversion is overselling.
| Symptom | Likely cause | What to do |
|---|---|---|
| Output is meaningless characters | Resolution too low, or page badly skewed | Rescan at higher resolution; straighten before recognition |
| Most words right, numbers wrong | Digit and letter shapes are genuinely ambiguous | Proofread numeric fields by hand — always, on anything official |
| Text jumbled out of order | Multi-column or table layout | Expected. Recognition recovers characters, not reading order |
| Handwriting not recognised | Print-trained OCR | No fix. Type it manually |
| "Already searchable" message | The PDF is born-digital | Nothing needed — Ctrl+F already works |
| Searchable PDF slightly misaligned selection | Word boxes are positioned approximately | Cosmetic only. Search and copy still work correctly |
| Very slow on a long document | Recognition is computation-heavy and runs on your device | Process in smaller batches; keep the tab in the foreground |
Most online OCR services upload your pages to their servers. Pennary runs recognition locally in your browser instead. It is slower than a data centre — that is the honest trade — but the document never leaves your machine, which matters when the thing you are digitising is a contract, a medical record, an identity document or official correspondence.