Batch Renaming on Mac: Your Options at a Glance
Four practical routes, in rough order of how much setup they need:
You already know how to select a few files in Finder and rename them one at a time. That's fine for three files. It falls apart at thirty. It's not even an option once you're renaming across folders on a schedule. Mac has real batch renaming tools built in, plus a few third-party and AI options worth knowing. Here's the full lineup: Finder's own dialog, an Automator workflow, a Terminal command, and a content-aware option that reads the file before it names anything.
Four practical routes, in rough order of how much setup they need:
Options 1 through 3 work with the filename you already have. Option 4 is different. It can look inside a scanned or photographed document and name it based on what's written there.
If you're not sure which route fits, ask one question first. Do your files already carry a usable pattern in the name? Or would you have to open each one to know what it actually is? That answer sorts you into the first three methods, or the fourth, faster than any feature comparison can.
You already know how to get to this dialog: select your files, right-click, choose "Rename [n] Items…" What matters is what's inside - three tabs, each solving a different renaming problem.
Trade-off: zero install. Format mode's live preview means you see the result before committing, too. It still can't read what's inside a PDF or a photo, though. Every one of these three tabs operates purely on the existing filename.
Automator turns a renaming sequence into something reusable. Set it up once as a Quick Action, and it appears in your right-click menu on any folder of files going forward.
Building one: open Automator, choose "Quick Action" as the document type. Set "Workflow receives current" to files or folders. Drag in the "Rename Finder Items" action from the library. Configure it: add date, add text, or replace text, the same three modes Finder's dialog offers, just saved as a repeatable step. Save it. It's now live in Finder's right-click menu, under Quick Actions.
Trade-off: the setup takes a few minutes the first time. After that, renaming a new batch takes one right-click instead of reopening a dialog. Automator still works from the filename only. It has no ability to read a document's content, no matter how the workflow is configured.
For anyone who'd rather type a command than click through a dialog, Terminal offers two routes. There's the built-in mv command in a loop. There's also the more batch-friendly rename utility from Homebrew.
Installing and using rename for a quick batch swap:
brew install rename
rename 's/Draft/Final/' *.docx
The first line installs the utility, a one-time step. The second line swaps "Draft" for "Final" across every .docx file in the current folder. It's noticeably friendlier for batch work than looping mv calls one at a time. Looping mv is the plain built-in alternative, if you'd rather skip installing anything.
Trade-off: faster than clicking through Finder's dialog, once you know the syntax. It composes well, too, if you already use the command line for other Mac tasks. Homebrew needs to be installed first, though. That's an extra step, compared to Finder or Automator, both already on your Mac.
Beyond what Apple ships, dedicated Mac renaming apps add pattern-matching features Finder doesn't have. Think regex support, batch metadata editing, more numbering formats. NameChanger and similar apps live here. They're worth a look if Finder's three tabs don't cover your pattern.
A separate category solves a different problem entirely: content-aware renaming. Say a folder holds scanned client intake forms from a business like Thistlewood Realty Group. Each one gets dropped in by a shared scanner as Registered_Copy.pdf, Registered_Copy (2).pdf, and so on. No pattern tool can pull a client's name or a signing date out of a filename that never held that information. Not on Mac, not anywhere. A tool like renamer.ai reads the actual page instead, using OCR and AI vision. It writes a name from what it finds inside: client name, form type, date signed.
Trade-off: third-party pattern tools add real flexibility over Finder for structured batches. Content-aware tools solve a different problem: files with no usable pattern at all. That comes with an upload step a local Finder or Terminal rename doesn't require.
| Method | Speed | Technical Skill | Content-Aware? | Best For |
|---|---|---|---|---|
| Finder Rename Dialog | Fast | None | No | Quick batches with a shared pattern |
| Automator | Medium setup, fast after | Low | No | Repeating the same rename job often |
| Terminal (mv / rename) | Fast (once installed) | Medium-High | No | Command-line users, complex patterns |
| Third-Party & AI Apps | Medium (per batch) | Low | Yes (AI apps only) | Scanned or photographed documents |
Finder's Rename dialog is genuinely good at what it does: reshaping a name you already have. It cannot open the file it's renaming. That's true across all three of its tabs. It's true of Automator and Terminal, too. Every method above transforms the string in the filename field. None of them ever touch the content sitting behind it.
Picture a scanned batch from a practice like Calloway Veterinary Clinic. Forty vaccination records get scanned in one afternoon. Each one lands in the folder as Copy 2.pdf, Copy 3.pdf, and up. Finder's Format tab can turn that into Record_1.pdf, Record_2.pdf in a few clicks. It still can't tell you which pet, which owner, or which vaccination date each file actually holds. That information was never in the filename to begin with. It's written on the scanned page itself.
Content-aware renaming is the piece that closes this gap. Instead of restructuring an existing name, it opens the document and reads the page. Then it writes a filename from the pet's name, the visit date, and the record type it finds there. For a clinic, a law office, or any Mac team that scans paperwork often, that's a real difference. It's the gap between a folder that's technically renamed and one that's actually searchable. Pair it with Finder or Automator for the files that already have a usable pattern. Neither approach replaces the other.
Finder, Automator, and Terminal cover most Mac batch-renaming jobs where your files already carry a usable pattern. Sometimes they don't. When the files are scanned forms or photographed documents with nothing but a generic camera or scanner name attached, the complete bulk rename software from renamer.ai reads the content directly. It names the file from what it actually finds.
Yes. Folders can be renamed the same way as files through the same dialog. Format mode's counter and date options are most useful when applied to a batch of files, though, rather than a single folder.
Cmd+Z, right after running the Quick Action, reverses it in most cases. Automator's Rename Finder Items action registers as a standard Finder operation, which is why undo works. Testing on a small sample folder first is still safer than relying on undo across a large batch.
You type two commands: one to install it, one to run it against your files. Beyond that, no scripting knowledge is required. Basic substitution patterns still help you write more precise renames, though.
Third-party and AI renaming apps are the category for this. Look for one that explicitly lists OCR or AI vision, not just pattern matching, in its feature list - that's the difference between an app that reshapes a name and one that reads the document first.
Yes, by building a Folder Action instead of a Quick Action. A Folder Action watches a specific folder. It runs your rename workflow automatically whenever a new file lands there, without you triggering it by hand.
No. Renaming only changes the display name and the name stored in the file system. The file's content, its iCloud sync status, and its location all stay the same. That's true whether you rename it through Finder, Automator, Terminal, or a content-aware app.
Your files are kept private and secure.
View our Privacy Policy for more information.