How to Rename Multiple Files at Once

Quick Answer: 5 Ways to Rename Multiple Files at Once

If you just want the short version:

Methods 1 to 3 are free and already on your machine. Method 4 adds power, but you install something new. Method 5 solves a different problem: what to do when the files all look identical from the outside, and the real pattern is inside the document, not in the order you saved them.

Method 1: Windows File Explorer (Select + F2)

This is the one most Windows users find by accident, usually while trying to rename one file and hitting Ctrl+click too many times.

Steps:

Honest trade-off: this is the fastest method here for plain sequential numbering. Five seconds, no install, no learning curve. But it's dumb about content. It doesn't know file #4 is the March invoice and file #7 is April's. Every file gets the same base name plus a counter. Sort your files in the right order first, or you'll rename them wrong in the right order.

Method 2: Mac Finder (Batch Rename)

macOS has had a real batch-rename tool built into Finder since 2016. It's more capable than Windows' F2 trick right out of the box.

Steps:

Honest trade-off: Finder's batch rename beats Explorer's on flexibility. You get find-and-replace and control over counter placement, no install needed. But it still can't look inside a PDF or a photo. It renames based on where a file sits in your selection, not what's written on the page.

Method 3: PowerShell / Command Line

If you're comfortable with a terminal, one line of PowerShell can rename a whole folder based on almost any rule you describe.

Get-ChildItem *.pdf | Rename-Item -NewName { $_.Name -replace 'Scan_','Invoice_' }

That line finds every PDF in the folder and swaps "Scan_" for "Invoice_" in each name. PowerShell (and shell scripting on Mac and Linux) can do much more than this: loops, conditions, pulling names from a CSV file. But that's a scripting project on its own, not a quick tutorial. Scripted, rule-based renaming across many folders deserves its own guide, not one paragraph here.

Honest trade-off: real power, but a real learning curve too. One wrong regex can rename files in a way that's hard to undo. Not the first stop for a quick, one-off cleanup.

Method 4: Third-Party Bulk Rename Tools

Between "type a name and hit F2" and "write a script" sits a category of rule-based bulk renaming tools: Bulk Rename Utility on Windows, Renamer or NameChanger on Mac, and others. These add a simple interface on top of pattern matching. Find-and-replace across hundreds of files. Insert dates or counters at any position. Strip or add prefixes. Change case. Preview every result before you commit.

Honest trade-off: more flexible than your OS's built-in tools, friendlier than a script. But you're installing another app, and every one of these tools works the same way underneath: matching a pattern or a position in the filename. None of them open the file and read what's inside. If your files already share some naming quirk you can target with a rule, this is a solid middle ground. If they're a pile of scans with no shared pattern at all, a rule can't find something that isn't there.

Method Comparison Table

When Filenames Aren't Enough: Renaming by What's Inside the File

Here's the problem none of the four methods above actually solve. You scan a stack of invoices at the office. Your scanner spits out Scan_001.pdf, all the way to Scan_063.pdf. Every method above can rename that pattern: strip "Scan_," add a prefix, whatever you like. But the result is still generic. You'd get Invoice_001.pdf through Invoice_063.pdf, which tells you nothing about which invoice is which. The vendor name, the invoice number, the date - that information sits inside the PDF, not in the filename. None of the pattern-based tools above can read it.

This is a different kind of renaming problem: content-aware renaming. Instead of matching a pattern in the existing name, the tool opens the file, reads the page with OCR, and writes a new name from what it finds. A tool like renamer.ai works this way. Point it at that folder of 63 scans, and it reads each invoice and proposes names like Brightway-Supplies-Invoice-4471-2026-03-14.pdf instead of Invoice_014.pdf. The same idea applies past invoices too: contracts named by the other party, photos named by what's actually in them. The naming decision comes from the document's content, not its spot in a folder. For document-heavy renaming at this scale, see our guide to bulk rename software for documents.

Honest trade-off: content-aware renaming is slower per file than a bulk pattern rename. It only pays off when your filenames genuinely don't carry the information you need: scanner output, camera photos, downloaded contracts. If your files already have usable names and just need a tweak, methods 1 to 4 are faster and simpler. Use pattern-based renaming when the pattern already lives in the name. Use content-aware renaming when the pattern only lives inside the document.

Once your files have names you can actually search for, the rest of the job gets easier. Searching, sorting, and handing a folder off to someone else all stop requiring a memory of what Scan_014.pdf was supposed to be.