The batch rename feature allows you to rename multiple files at once using regex patterns and destination templates with special macros.
The destination pattern supports the following macros:
\0 - The entire original filename\1 to \9 - Regex capture groups from the pattern match\d - Index number (1, 2, 3, etc.)file1.txt, file2.txt, file3.txt(.*)backup_\1backup_file1.txt, backup_file2.txt, backup_file3.txtdocument.txt, readme.txt, notes.txt(.*)\.txt\1.mddocument.md, readme.md, notes.mdphoto.jpg, image.jpg, picture.jpg(.*)\.(jpg)\1_\d.\2photo_1.jpg, image_2.jpg, picture_3.jpg2023-01-15_report.pdf, 2023-02-20_summary.pdf(\d{4})-(\d{2})-(\d{2})_(.*)\4_\1\2\3report_20230115.pdf, summary_20230220.pdfThe dialog shows a real-time preview of the rename operation:
OK - Rename will succeedUNCHANGED - No change neededCONFLICT! - Target filename already existsINVALID! - Invalid filename (contains illegal characters)Some characters can be written two ways that look identical on screen — が as
one character, or as か plus a voiced-sound mark. Files written the second way
come from HFS+ disks, network shares, archives, and from Finder itself.
XeFM treats the two spellings as the same text, so a search pattern typed at an IME finds a file however it happens to be stored, and two files whose new names differ only in spelling are reported as a conflict instead of one silently replacing the other.
A renamed file is written back in the single-character spelling. Finder uses the other one, so on macOS a name XeFM renames may end up spelled differently from the same name renamed in Finder. The file is the same file either way and both spellings open it; the difference matters only on disks and cloud storage that compare names byte for byte, which is why XeFM keeps one spelling everywhere. Files the rename does not touch are left exactly as they are.