Skip to content

Vision OCR 1.10.0 — scans come out smaller than they went in

Choose a tag to compare

@charlesapetersen charlesapetersen released this 12 Aug 17:32
· 560 commits to main since this release

Files that used to come out bigger now come out smaller. Some scans grew when this app processed them — one book went from 16 MB to 156 MB, more than nine times its original size, and it was not alone. Across the whole 232-document test library the output was 1,039 MB against 1,198 MB going in; it is now 792 MB.

The cause was a page of dense small type being mistaken for a photograph. One of the three things the app looks at is how much ink is on a page, and a broadsheet of eight-point classifieds is a great deal of ink — so those pages were given a photographic layer on top of the sharp black-and-white one, carrying nothing the sharp version did not already have. Heavy ink now has to be corroborated by real photographic tone. Actual pictures were checked page by page at full size and are unaffected.

One honest caveat, found straight after release. Across the library the recognised text changed by −0.05%, and most documents gained. But one book lost 2.7% of its text, concentrated on about a dozen pages — and the cause turned out not to be the change above. On some high-resolution scans Vision recovers less text than it would at a lower rendering resolution, and Automatic leaves that choice to the recogniser. Pages that moved to black-and-white met that behaviour more often than they used to.

Correction (1.10.1). This note originally advised setting Page DPI to 300 for very high-resolution scans. Measured properly afterwards — 52 documents, 4,140 pages — Automatic recovers more text than any fixed value, and 300 makes more than half of those documents worse. That advice is withdrawn. Leave Page DPI on Automatic.

A written record of every batch. The results pane always lost its record when the window closed. Each finished run now leaves a report in ~/Library/Logs/VisionOCR: every input, where its output went, what happened to it, the settings that produced it, how long it took. For an overnight run over material that may not be re-scannable, that is the difference between "something failed last night" and knowing which document and why. On by default; Settings ▸ Behaviour has a Show Reports button. Your password is never written into it.

Retry just the files that failed. Four failures out of seventy-eight used to mean finding those four and dragging them in again. The results pane now offers Retry N Failed.

The language list comes from your Mac. An unrecognised BCP-47 code does not quietly do nothing — it fails every file in the batch. There is now an Add menu listing what this Mac actually supports, and a warning naming any code that will fail before you start.

Most importantly: "Fast" supports far fewer languages than the normal recogniser — six against thirty on macOS 26.6. Turning it on with Japanese, Russian, Chinese, Korean, Arabic or twenty others selected turned a working setup into a run where nothing succeeded, with no indication why. It says so now, the moment you tick the box.


232 of 232 documents through the full-corpus gate, 34.1 million characters recovered, no failures. 758 checks in the suite.

Installing. Vision OCR is signed but not notarized, so the first launch is blocked. Open it once, then go to System Settings ▸ Privacy & Security and click Open Anyway. Requires macOS 13 or later on Apple silicon. Nothing else to install.