This is a specialized form of the “Tab-Delimited File List Format” which deals gracefully with multiple files that share the same unique name but are located in different folders.

In the normal tab-delimited file list format, if you have several files with the same “current name” (ie. the name in the first column), Better Rename has no way of working out which line refers to which file. In order to enable it to do so, you need to use not only the “current name” of the file but a the full POSIX path to the file in the first column.

This will look something like this:

/Users/frankrei/Documents/My file The New Name

/Users/frankrei/Documents/My Document The New Document

  1. The absolute POSIX compatible path to the old file
  2. The new name

Better Rename changes the name of the file specified by the full path to the new name specified in the second column.

Make sure that you put the absolute file path to the file or folder you want to rename into the first column in POSIX format. An absolute file path describes how you get from the “root” of the file system to an individual file or folder. Every file and folder has a unique absolute file path.

Understanding file paths is essential to getting this feature to work, so you might want to find out more about them at Wikipedia.

The second column needs to have only the new file name in it; not a path!

You can create the file list by hand, or you can let Better Rename help you with the task by using the Save File List… feature.

The Ignore case (tab-delimited file lists only) checkbox of the action allows the case of the path name to be ignored (e.g. /Users/smith/ = /users/smith/) for use with case insensitive file systems.

Important! There is one entirely unintuitive detail about how macOS handles file names that contain a slash or a colon that you need to know about.

Because POSIX uses the forward slash / as the path separator and the Finder uses the colon : for the same purpose, macOS does some “clever” translation between both symbols, e.g.

Say you have a file called My file name with a /, in the POSIX part, the slash will be replaced by a colon:

/Users/frankrei/Documents/My file with a :

Forward slashes must be replaced by a colon in the POSIX path, but they are fine in the “new name” part. You may not however have any colons in the new name.

Also, you may not mix full paths with simple current file names in the same file list. The first column must either contain only full POSIX paths or simple file names.

Can't find what you are looking for?

A short description of what you did, what you expected and what happened instead is usually all we need.