Why Can’t I Rename a File?

When macOS refuses to rename a file, A Better Finder Rename reports:

You may not have sufficient access privileges to rename the file, the file may be on a read-only medium, an incompatible external drive or unsupported remote file system or it may be locked.

The message covers every case in which the operating system turns the rename down. Work through the list below.

The file is locked

Select the file in the Finder, choose File › Get Info and untick Locked in the General section. The Finder can lock several files at once if you select them all before opening the Info window.

You do not have permission

In the same Info window, check the Sharing & Permissions section. You need Read & Write access to the file and to the folder that contains it, because renaming changes the folder’s directory listing. Files copied from another user account or restored from an old disk often have the wrong owner.

The file is in use

Some applications keep their documents open and refuse to let them be renamed, or rename them back. Quit the application that has the file open and try again. This is common with files that are currently being downloaded or synchronised.

The file is in iCloud Drive or another cloud folder

Files that are only in the cloud and not downloaded to the Mac cannot be renamed until they are downloaded. Cloud services may also impose their own name rules, e.g. no trailing dots or spaces, and revert names that break them.

The volume is read-only

Optical discs, locked disk images, camera cards with the write-protect switch set and some network shares are read-only. By default A Better Finder Rename does not even add such files to the list; the Allow files on read-only volumes option in the Settings window lets you add them for preview only.

The file is part of macOS or an application

macOS protects its own files and the contents of application bundles. Renaming inside /System, /Library or an application’s package is refused by the system and is best left alone.

External drives, memory cards and network file systems

Drives formatted for Windows (exFAT, NTFS with third-party drivers), NAS devices with their own file systems and memory cards sometimes refuse names that macOS allows, or fail for no visible reason. Try another rename mechanism in the Settings window, or copy the files to the Mac first, rename them there and copy them back.

The new name is not allowed

A name cannot contain a colon (:) and the Finder shows a slash (/) in a name as a colon, see the POSIX path format. Names starting with a dot are hidden. Very long names fail on some file systems; most allow 255 characters per name.

Still stuck?

If a rename fails for a reason that is not listed here, choose Help › Contact the Developer and describe what happened. The Log debug information to console setting records more detail for support.