Finder fixes and how-tos

When Finder refuses a new name

Updated 2026-10-30 · 4 min read

Finder's message usually names the cause, and each cause has a different fix. Match your message to the list below, then use Terminal's mv if you want the exact system error.

Match the message to the cause

To rename, select the item and press Return, or Control-click it and choose Rename. If that fails, read the wording of the alert. These are the messages Finder itself contains:

What Finder says	Cause
The name “x” is already taken.	Another item in that folder has the name
You don’t have permission to rename the item “x”.	No write access to the folder
The item “x” can’t be renamed.	Locked, read-only, or protected
The name “x” can’t be used. Try using a name with fewer characters, or with no punctuation marks.	A character or length the volume rejects
“x” can’t be renamed right now because another operation is in progress	A copy, move or Trash empty is still running

Each cause has its own section below. If there is no alert and the name just snaps back, go to the Terminal section.

The name is already taken

Finder compares names without regard to case on a default APFS disk, so Report.pdf and report.pdf count as the same name. In a test, mv -n refused to rename bar.txt to FOO.txt because foo.txt was already there. Pick a different name, or move the other item out of the folder first.

If the alert also names an extension, the clash is with an item that has the same name and that extension.

The file is locked

Select the file and choose File > Get Info. Under General, clear the Locked checkbox, then rename. Finder's own advice for locked items is the same: choose File > Get Info, deselect Locked, and try again.

To see whether Terminal agrees, list the flags. A locked file shows uchg:

ls -lO ~/Desktop/Report.pdf

In a test, renaming a locked file with mv failed with Operation not permitted.

You can't write to the folder

Renaming changes the folder's list of names, so it needs write access to the folder, not just to the file. With write access removed from a test folder, mv printed Permission denied. Select the folder, choose File > Get Info, and open Sharing & Permissions. If your account shows Read only, click the lock at the bottom of the window (macOS may ask for an administrator password), then choose Read & Write from the pop-up menu next to your name. Do this for your own folders, not for system ones. The wider story is in how Mac file permissions work.

The disk is read-only

Finder reports a read-only location with “This location is read-only.” Typical sources are a disk image mounted read-only, a drive that was mounted read-only after an error, a network share you only have view rights on, and a Windows-formatted NTFS drive. Apple says a Mac might be able to read from NTFS but not write to it, so check Format in the drive's Get Info window. Copy the file to your Mac, rename it there, and copy it back if the drive allows writing.

Items on the Mac's own system volume are also read-only by design; Terminal reports Read-only file system or Operation not permitted there. Don't try to rename those.

The name itself is the problem

• A very long name is refused: Finder says “The name “x” can’t be used because it’s too long”, and mv reported File name too long for a 300-character name.
• A name that starts with a dot hides the file. Finder warns you and offers Use Dot. If you accept, the file disappears from view.
• Changing the extension prompts you: “Are you sure you want to change the extension from “.txt” to “.md”?” The buttons name both, for example Keep .txt and Use .md.
• Some extensions are required by Finder and can't be removed or changed.
• Punctuation that a network share or Windows-formatted drive rejects produces the “can’t be used” alert. See which characters filenames can contain.

An app has the file open, or iCloud is mid-sync

On a Mac, renaming a file that another program has open normally works. A test file held open by a shell was renamed without complaint. Finder does warn before renaming an application while it is running. Some apps still lock their documents, so close the file in the app and try again.

An item in iCloud Drive that is still uploading or downloading may refuse a rename until the transfer ends. Wait for the progress indicator next to it to clear, then try again.

Get the real error from Terminal

Type mv -v , drag the file in from Finder, then type the new name:

mv -vn ~/Desktop/Report.pdf ~/Desktop/Report-final.pdf

-v prints what happened and -n refuses to overwrite. Without -n, mv replaces an existing file with no warning. If it fails, the last words of the error say which cause applies: Operation not permitted (locked or protected), Permission denied (folder permissions), Read-only file system, or File name too long.

After the rename

Once the rename goes through, typing the new name into Everywhere shows the file under it, with its folder. Inside ~/Library/Application Support, Caches and a few other places that aren't watched live, the new name can wait for the next scan, and Desktop, Documents and Downloads are included only once Everywhere has Full Disk Access.

Common questions

Why can't I rename a file on my Mac?

The usual causes are a locked file, no write permission on the folder, a read-only disk, or a name already used in that folder. Finder's alert wording tells you which.

Why does Mac say the name is already taken?

Another item in the same folder has that name. On a default APFS disk, names that differ only in capitals count as the same, so Photo.jpg clashes with photo.jpg.

How do I rename a file in Terminal on a Mac?

Use mv -vn old.txt new.txt. It prints what it did and refuses to overwrite an existing file. If it fails, the error text names the cause.

Why can't I rename a file on an external drive?

The drive may be read-only, such as an NTFS disk, or you may lack write permission on it. Check the format and permissions in File > Get Info.