When bulk renaming refuses to work

To batch rename in Finder, select every file you want to change, Control-click one of them, and choose Rename. A panel titled Rename Finder Items opens with a pop-up menu offering three modes: Replace Text, Add Text, and Format. Pick one, fill in the fields, check the example name at the bottom of the panel, and click Rename. If the result is wrong, press Command-Z straight away and the whole batch reverts in one step. That covers most jobs. The rest of this guide is about the jobs it does not cover: which mode fits which task, how to chain several passes without wrecking names, why a rename sometimes runs and changes nothing, and where Finder stops being the right tool.

The three modes, side by side

Apple's own description of the panel is short. As of 8 October 2026 the Mac User Guide page "Rename files, folders, and disks on Mac" lists the same three choices for every macOS version from Catalina onward, so the steps below apply whether the machine runs Sonoma, Sequoia, Tahoe or macOS 27.

Mode	What it changes	Typical job	Keeps the extension
Replace Text	Every match of the Find text	Fix a typo, swap a client code, strip "copy"	Only if the extension does not match the Find text
Add Text	Inserts text before or after the current name	Add a date prefix or a version suffix	Yes, "after name" goes before the extension
Format	Replaces the whole name with a pattern plus a number or date	Number photos, standardise a delivery set	Yes

Replace Text is the most precise of the three. It only touches files that contain the Find string, so it is safe to select a whole folder and let it skip the files that do not match. Leaving the "Replace with" field empty deletes the matched text, which is the quickest way to remove a word such as "final" or "draft" from forty names at once.

Add Text never removes anything. It is the right choice when the existing names carry information worth keeping and only need a common prefix or suffix. Because "after name" inserts the text before the extension, invoice.pdf becomes invoice_v2.pdf, not invoice.pdf_v2.

Format throws the old name away. It builds a new one from a Custom Format field plus a number or a date. This is the mode for camera files, scans and screenshots, where the original names carry nothing useful. It is also the mode most likely to produce a result that cannot be undone later in any meaningful sense, because once the original names are gone and the undo history is cleared, nothing records what each file used to be called.

Format mode in detail

Format has three name formats in its first pop-up menu: Name and Index, Name and Counter, and Name and Date. Next to it, a Where menu sets whether the number or date goes after the name or before it. Below that are the Custom Format field, where the fixed part of the name goes, and the "Start numbers at" field.

The difference between Index and Counter matters more than it looks. Index produces plain numbers (1, 2, 3 and onward), while Counter pads them with zeros to five digits. Plain numbers sort badly once a set passes nine files: in a list sorted as text, photo10 lands between photo1 and photo2. Finder itself sorts numbers naturally, so the problem stays hidden on the Mac and only appears when the files reach a web uploader, a print shop's system or a script that sorts them as strings. If the files are leaving the Mac, Counter is the safer choice.

Name and Date stamps the current date and time, not the date each file was created. That catches people who expect it to read the capture date from photos. Finder has no option to read EXIF data during a rename, so a set of photos taken over three days will all receive the same timestamp from the moment the Rename button was clicked.

The order in which files receive their numbers follows the order Finder is showing them in. Sort the window by Date Created, or by Name, before opening the panel, and the numbering follows that sort. Sorting after the rename is too late.

Apple's guide also lists names that should not be changed at all: application folders, the Library folder and other items that came with the system, the home folder, and filename extensions. The batch panel does not stop a selection that includes them, so it is worth checking the status bar item count and the selection before clicking Rename.

Running more than one pass

Real naming schemes rarely fit a single mode. A delivery folder might need the old client code replaced, a project prefix added, and a version suffix appended. That takes three passes, and the order decides whether the result is clean.

A sequence that holds up in practice:

1. Replace Text first. Clean the existing names while they are still recognisable. Removing "copy", stray spaces or a wrong code is easiest before anything else is attached.
2. Format second, if needed. If the plan is to renumber, do it now, because Format discards everything that came before.
3. Add Text last. Prefixes and suffixes go on after the base names are final, so a later Replace pass does not accidentally match text inside them.

Each pass is a separate undo step. Command-Z after the third pass restores the result of the second, not the original names. Undo is also tied to the Finder session: once Finder relaunches, or other file operations push the rename off the undo stack, the old names are gone. For anything larger than a few dozen files, duplicating the folder before the first pass costs a few seconds and removes the risk entirely.

Spaces deserve a deliberate decision. Finder accepts them, but any file that will later be handled from a command line, a URL or a build tool is easier to work with if spaces become hyphens or underscores. A Replace Text pass with a single space in Find and an underscore in "Replace with" does the whole folder at once.

When the rename refuses to work

When the panel misbehaves, the symptom points to the cause.

There is no Rename item in the menu. The batch panel only appears with more than one item selected. With a single file, Control-click offers an inline rename instead, which looks almost identical in the menu. Turn on View > Show Status Bar and confirm the selection count before looking further.

The panel runs, but nothing changes. Check whether the files are locked. Select them, press Command+Option+I to open one Inspector window for the whole selection, and look for the Locked checkbox. Locked files accept neither renaming nor deletion. Attachments saved from Mail, files restored from backups and output from some design applications arrive locked more often than expected.

The file is writable but still refuses. Renaming needs write permission on the folder, not on the file. A name is an entry in the parent folder's listing. Select the enclosing folder, press Command+I, and read Sharing & Permissions at the bottom. Read only there is the answer, even when the file itself shows Read & Write.

Every file on one drive fails. Open Get Info on the drive and read the Format line. A Windows NT File System volume is mounted read only by macOS, and no permission setting changes that. Copy the files to the Mac, rename them, and copy them back.

Most files rename and a few do not. This is usually cloud storage. Files in iCloud Drive that have been offloaded exist only as placeholders until they are downloaded. Control-click the folder, choose Download Now, wait for the cloud icons to clear, and run the rename again.

The rename is refused instantly. Apple's guide states the rule plainly: a name cannot include a colon or start with a period, and some apps reject a slash. A time such as 10:30 in Add Text hits this at once. Duplicate results stop the operation too: if a Replace pass would turn two files into the same name, Finder refuses rather than overwrite.

When Finder is the wrong tool

Finder's panel has no preview of the full list, no regular expressions, no way to read metadata such as a photo's capture date, and no saved presets. When a job needs one of those, there are three other routes.

Terminal. For a pattern Finder cannot express, a short shell loop does it. Changing upper-case extensions in the current folder, for example:

for f in *.JPG; do mv -n "$f" "${f%.JPG}.jpg"; done

The -n flag stops mv from overwriting an existing file, which is the shell equivalent of Finder's refusal on duplicates. The drawback is that the folder in the Terminal window and the folder in Finder are two different things, so a cd into the wrong place renames the wrong files. A file manager that keeps a terminal tied to the folder on screen removes that mismatch; the features page shows how that layout works.

Dedicated renamers. Two are named most often in search results. Renamer 7 requires macOS 15 Sequoia or later, runs on Windows 10 and later as well, and can rename from a CSV file. Advanced Renamer runs on Windows and macOS, supports renaming from MP3 tags and video metadata, and can undo a complete batch. Its commercial license is per user, does not expire, and covers versions 3.xx and 4.xx. Both details were checked on each vendor's own site on 8 October 2026. Either is worth the install if renaming is a weekly job.

Suggested names in macOS 27. On Macs that support Apple Intelligence, Apple's guide describes a Suggest File Names setting under Finder > Settings, which proposes names when creating or renaming documents. It works on single documents rather than batches, so it does not replace the Rename panel, but it removes the need for some of the clean-up passes in the first place.

Picking the route for the job

The choice comes down to what the old names are worth and how often the job repeats.

If the old names carry meaning and the change is the same for every file, Finder's Replace Text or Add Text is enough. If the old names carry nothing, Format with Counter is enough, provided the window is sorted first. If the new name depends on something inside each file, such as a date or a tag, Finder cannot do it, and a dedicated renamer or a script is the right tool. If the same job comes back every week, a saved preset in a dedicated app or a saved script pays off quickly.

For people who already spend the day in a terminal, the third route is often the fastest one, as long as the terminal is looking at the same folder as the file list. The comparison page sets out how a file manager with a built-in terminal differs from running Finder and Terminal side by side.

What to change first

Before the next large rename, duplicate the folder, sort the window the way the numbering should run, and use Counter rather than Index for anything leaving the Mac. If the job keeps needing patterns Finder cannot express, try running the rename from a terminal tied to the folder on screen in Atriens.