Renaming Scanned PDFs When the Filenames Tell You Nothing
This is the scenario that pattern-based tools simply cannot solve, and it's worth calling out on its own, because it's the exact question that keeps showing up on forums like r/DataHoarder: "I have 300 scanned PDFs named Scan001 through Scan300, and I have no idea what's in any of them. How do I rename them based on what they actually say?"
The answer is content-aware OCR renaming, because the filename was never the source of truth here, the document content is. There is no rule you can write that turns "Scan0043" into "2019rentalagreementsmith" without something actually reading page one of that PDF.
A few things worth knowing before you run a big batch of scans through OCR renaming:
Scan quality matters more than volume. A crisp 300 DPI scan reads reliably; a dark, angled phone photo of a document might not extract cleanly.
Mixed document types are fine in one batch. You don't need to pre-sort invoices from contracts before uploading, the AI identifies document type as part of the read.
This isn't a metadata reader. It's reading the visible content on the page, not EXIF data, GPS tags, or a "date taken" field. If you're trying to rename photos by when they were shot, that's a different (and unsupported) use case here.
Review before you trust it at scale. For a batch of 200+ scans, spend two minutes checking the first 15-20 suggested names before approving the rest. That catches systematic issues (like an unusual document layout) before they run through the whole folder.
If your entire workflow is document-type-specific, invoices only, or contracts only, there are pages built around exactly that content-extraction mechanism, linked below, that go deeper into what fields get pulled and how.
Which Method Should You Actually Use?
If you're renaming a folder of files where you already know what each one is (you're just cleaning up naming conventions), Method 1 costs you nothing and takes a few minutes. If you're renaming files where the name is meaningless and the content is the only clue, no free tool solves that, you need something that reads the document. That's the whole reason content-aware renaming exists.
Most people land somewhere in between: a folder that's mostly known files with a chunk of unidentified scans mixed in. In that case, it's reasonable to pattern-rename the files you already understand and run the unidentified scans through content-aware OCR separately.
Related Situations This Page Doesn't Cover in Depth
Setting up a folder that renames new PDFs automatically as they arrive, without you running a batch each time, see the guide on automatic PDF renaming with watched folders.
The exact fields renamer.ai's OCR extracts from different document types (invoice number, vendor, contract parties) and how the extraction actually works, covered in renaming files based on content and auto-renaming PDFs based on content.
Bulk-renaming files that aren't PDFs, or mixed file types generally, see bulk rename files.
Doing this specifically on a Mac, including Finder-native options, see renaming multiple files at once on Mac.
For the full picture of every bulk and automated renaming approach renamer.ai supports, start at the bulk rename software hub.
Start With the Files That Actually Need It
If your PDFs already make sense to you and just need consistent naming, grab a free pattern-based tool and you're done in a few minutes. If you're staring down a folder of scans that could be anything, that's the exact problem we built renamer.ai's OCR renaming to solve. Try it on your next batch and see what's actually inside those files.
