Nobody searches the web for “batch OCR” because of one file. You’re here because a folder landed on you. Maybe it was a discovery production, a client’s year of receipts, a decade of board minutes, or a filing cabinet someone finally fed through the office scanner. Processing those one at a time through an app window is a day of clicking. These are your real options for doing the whole folder in one go, free ones included.
What “batch OCR” needs to actually mean
A useful batch tool has to do four things. It must process every PDF in a folder without per-file interaction; write a real searchable text layer into each output (not just show text on screen); leave your originals intact in case anything goes wrong at scale; and keep the output organized so you can tell processed from unprocessed. Judge every option below against those four.
Option 1. Adobe Acrobat Pro batch actions
Acrobat Pro can OCR multiple files via its Action Wizard. You build an action that runs Recognize Text, point it at a folder, and let it churn. It works, and the OCR quality is good.
The friction is that you’re configuring an enterprise feature, which means creating an action, setting output options, and watching a progress dialog inside Acrobat. And it’s all inside a subscription suite that costs hundreds of dollars a year. If your firm already pays for Acrobat, this is a perfectly good answer; set the action up once and reuse it. If you’d be subscribing just for this, it’s a lot of rent for one chore. (More in the Mac OCR roundup.)
Option 2. ABBYY FineReader’s batch processing
FineReader handles multi-file jobs well and offers deep control over recognition languages, output formats, and image cleanup. It’s the strongest choice when the batch job is conversion, meaning hundreds of scans that need to become editable Word or Excel files with layout preserved. For plain “make these searchable,” you’re still importing into an app, configuring a job, and exporting, all under subscription pricing.
Option 3. The command line (free, for the technical)
The open-source route is ocrmypdf, a well-regarded command-line tool that adds text layers to PDFs and can be scripted over a folder with a shell loop. It’s free, local, and genuinely good.
The honest catch is that it’s a developer tool. You’ll install it through a package manager (typically Homebrew, with its dependency chain), work in Terminal, and debug the occasional cryptic failure on odd PDFs. If you’re comfortable there, this is the best free batch answer on the platform and we’ll happily recommend it. If “open Terminal” already sounds like the chore you were trying to avoid, it isn’t for you.
Option 4. Cloud batch services
Some web services accept multiple files or a ZIP. The usual upload concerns of confidentiality, retention, and jurisdiction are all covered in the no-cloud guide, and batch makes each of them worse, because you’re no longer sending one document to an unknown server. You’re sending the whole folder. For client files, patient records, or anything sensitive, uploading in bulk is the same problem at scale.
Option 5. Right-click the folder (our answer)
RightClickOCR treats batch as the default case, not a premium feature, because the folder problem is the problem it was built to solve:
- In Finder, right-click the folder of scanned PDFs.
- Choose Make Searchable (OCR).
- Every PDF inside is processed. Each gets its own “Name (Searchable).pdf” written beside the original; non-PDFs are ignored. You can open the app to watch activity, but you don’t have to. It finishes either way.
Measured against the four requirements, it holds up. There is no per-file interaction beyond the one right-click. Each output carries a real embedded text layer, so ⌘F and Spotlight work on every file. Originals are never modified, and at batch scale that is the safety property that matters most, because a bug in a tool that edits in place could damage hundreds of files, while a tool that only ever writes new copies can’t. And the output sits beside each source file with an unambiguous suffix.
Everything runs on-device via Apple’s Vision framework, which means a folder of confidential files never touches a network. Crooked pages get deskewed automatically, which bulk-scanned archives always need. There is a one-time macOS setup toggle first, covered in the walkthrough. For the behavioral details, see how batch behaves.
Batch strategy tips (whatever tool you use)
- Test on a copy of five files first. Check the output quality before committing an afternoon of processing.
- Keep originals and outputs together. Side-by-side copies with a clear suffix beat a separate “OCR output” folder you’ll misplace.
- Expect imperfection on terrible scans. OCR accuracy tracks scan quality; a 1980s fax will yield rougher text than a clean 300-dpi scan. The point of batch is that even imperfect text makes documents findable.
- Make it a habit, not a project. Once the backlog is done, OCR new scans as they arrive. With a right-click workflow, it’s five seconds per drop-off.
How long will a big batch take?
On-device recognition is fast, and a clean page takes on the order of seconds on modern Apple silicon. A batch, though, is still pages times seconds. A 400-document production will take a while; the useful mental model is “start it, go do something else.” Because RightClickOCR writes each searchable copy as it finishes, results appear progressively in the folder. And because it never touches the originals, an interrupted batch costs you nothing. Your originals are untouched, so you can safely run it again. Spotlight begins indexing the finished copies immediately, so the first documents are searchable before the last ones are done.