| Quick Facts | |
|---|---|
| Recommended scan resolution for reliable OCR | 300 dpi (dots per inch) |
| Typical vendor-claimed character-level OCR accuracy on clean printed text | 97 to 99 percent |
| Field-emission SEM resolution | under 2 nanometers |
| Aberration-corrected TEM resolution | under 1 angstrom (about 0.1 nanometer) |
| Typical TEM specimen thickness | under 100 nanometers |
What OCR scanning actually means
OCR stands for optical character recognition — software that converts a scanned image of text into editable, searchable digital characters, acting as the translation layer between a picture of a page and a document a computer can actually read.
Shopping for a specific model? See our best scanners picks — 10 models compared on the specs that decide it.
Every scanner, whether it is a flatbed next to a printer or the camera inside a banking app, does one job: it photographs a page and hands back a picture. That picture is just colored dots to a computer, no different structurally than a photo of a parking lot. The OCR scanner meaning kicks in at the next step, when software looks at those dots and decides which ones form the letter g versus a smudge of toner.
That is the whole trick behind optical character recognition: pattern recognition applied to letterforms instead of faces or road signs. Early systems in the 1970s matched pixels against a fixed set of font templates, one glyph at a time. Modern OCR scanning engines lean on machine learning models trained on millions of text samples instead, which is why they now handle dozens of fonts and several alphabets without needing a hand-built template for every one.
How does OCR work, step by step
OCR runs a scanned image through four stages — preprocessing, segmentation, character matching, and post-processing — before any of it turns into text you can read.
The pipeline starts with preprocessing, where software straightens a crooked page (deskewing), strips out flecks of dust (despeckling), and converts the image to stark black and white (binarization) so letters stand out from the background. Skip this step on a page scanned at an angle and the recognition engine mangles half the lines that follow.
Next comes segmentation, where the software carves the page into lines, then words, then individual characters. Each isolated shape gets compared against a reference library, either through matrix matching, a literal pixel-by-pixel overlay against known letterforms, or feature extraction, which breaks a shape into loops, lines, and intersections and scores how closely it fits each candidate letter.
The last stage, post-processing, is where dictionaries and language rules clean up the raw guesses. If the engine reads 'ho use' instead of 'house', a language model nudges it toward the real word. This is also where accuracy claims get slippery: a character-level accuracy of 99 percent still leaves room for a meaningfully higher word-level error rate, since one wrong letter ruins an otherwise correct word.
How scanners work before OCR ever sees the page
A scanner's hardware only captures an image — a sensor records reflected light off the page as pixels; OCR is a separate software step layered on top of that image, sometimes built in, sometimes not.
Inside most modern document scanners sits a CIS (contact image sensor) or, in older and higher-end units, a CCD array behind a lens. As the sensor bar or the paper itself moves past it, the scanner records brightness values line by line and stitches them into a digital image, the same basic idea as a photocopier but stopping short of printing anything back out.
An auto document feeder adds speed by pulling multiple pages through that sensor path without anyone lifting a lid each time, which is the main thing separating a general answer to how do scanners work from what an office actually needs at tax time. None of that hardware knows what a word is; it only knows brightness and position. If the goal is a machine built specifically around fast, accurate paper capture rather than a general-purpose flatbed, our document scanner guide compares current sheet-fed and flatbed models by feed speed and page capacity.
OCR sits downstream of all that, either baked into the scanner's bundled software or run separately in a desktop program or phone app. Scanners with OCR capability typically run the recognition step automatically the moment a scan finishes, saving a searchable PDF instead of a flat picture, which is worth confirming before assuming a machine does this by default, since plenty of budget units only ever capture images.
Can OCR read handwriting?
Yes, with real limits — OCR handles printed text extremely well and handwriting far less reliably, especially connected cursive, because neighboring letterforms blur together with too little separate shape information to tell apart cleanly.
Standard OCR engines were built and trained on printed fonts, so a typed invoice or a book page performs close to the software's advertised ceiling. Hand a scanner a page of cursive notes instead and accuracy drops noticeably, because cursive letters share strokes with their neighbors. The engine is guessing at where one letter ends and the next begins, not just at what shape each one is.
The technology aimed specifically at this problem goes by a different name: intelligent character recognition, or ICR, trained on handwriting samples rather than font templates. It does reasonably well on neat block printing inside a structured field, like a form with a box for each letter, and considerably worse on freeform cursive scrawled across a blank page.
This is exactly the gap that receipt- and expense-focused scanners try to close, since a receipt mixes a printed total with a handwritten tip or note. Neat has built its product line around extracting that kind of mixed data into a digital filing system rather than leaving a reader with a flat image, and our Neat scanner guide covers how the current lineup handles that specific job.
Why the word scanning means five different things
Outside of document capture, 'scanning' also describes retail barcode readers, a Java input class, electron microscopy, and a speed-reading technique — none of which involve OCR at all.
Ask how do scanners at stores work and the answer is in completely different territory: a checkout barcode scanner shines a laser or LED across a printed barcode and reads the pattern of wide and narrow stripes, translating those widths into a product number. No letterforms, no OCR pipeline, just a lookup against a price database.
Programmers run into the word too. In Java, the Scanner class has nothing to do with paper; it is a built-in tool for reading input from a keyboard, a file, or a string, one token at a time. Anyone asking how do scanners work in Java is almost always debugging code, not troubleshooting hardware.
Scientists split the word differently again. A scanning electron microscope builds an image by sweeping a focused beam across a sample's surface and reading the electrons that bounce back, resolving detail down to under 2 nanometers on a good field-emission model. A transmission electron microscope instead fires electrons through an ultra-thin specimen, usually under 100 nanometers thick, and can resolve under 1 angstrom on aberration-corrected instruments. A scanning vs transmission electron microscope comparison really comes down to reflected electrons versus electrons passed all the way through the sample.
Reading strategy borrows the word as well. Scanning vs skimming describes two opposite habits: skimming skips through a page to get the general idea, while scanning hunts for one specific fact, like a date or a total, without reading everything around it. The scanning vs skimming reading distinction matters for standardized tests and workplace reports alike, since there is rarely time to read every line closely. None of that overlaps with scanning jobs, a phrase job boards use for roles built around digitizing paper archives, where OCR does the actual recognition work behind a human operator feeding pages into a machine all day.
Why does my scanner not work, and how that wrecks OCR results
Most OCR failures start at the hardware step — a skewed page, a smudged scan bed, or a scanner Windows 11 no longer recognizes will all hand OCR a bad image before recognition even begins.
A scanner that suddenly will not connect is almost always a driver problem, not a hardware failure. Windows 11 sometimes drops or fails to carry over the TWAIN or WIA driver a scanner needs during a feature update, which is the most common reason people search why does my scanner not work with windows 11 specifically. Reinstalling the current driver straight from the manufacturer's site, instead of relying on whatever generic driver Windows substitutes, resolves the majority of these cases.
Outside of Windows 11 specifically, why does my scanner not work covers a wider list: a loose USB cable, a glass bed smudged enough to introduce noise into every scan, or a unit that has simply aged out of manufacturer driver support. None of those are OCR problems yet on their own; they turn into OCR problems the moment recognition software tries to read a crooked, speckled, or half-blank page and guesses wrong as a result.
If troubleshooting turns into 'this machine is done,' that is a fair moment to stop patching an old scanner and compare what is currently available. Our best scanners guide breaks down current models by scan speed, feed capacity, and price tier, so the comparison is against what actually exists now rather than a memory of an older lineup.
