Rename files and folders in a batch, directly from Raycast.
| Command | Acts on |
|---|---|
| Rename File(s) — rename the selected files in a batch. | Files |
| Replace in File Names — replace characters in the names of the selected files. | Files |
| Rename Folder(s) — rename the selected folders in a batch. | Folders |
| Replace in Folder Names — replace characters in the names of the selected folders. | Folders |
| Advanced Batch Rename — rename using a rule-based engine that chains find & replace, case transforms, prefixes, suffixes, and numbering. | Your choice — see below |
| Rename History — view recent rename operations and undo them. | — |
Each rename command targets exactly one kind of Finder item, so a batch never touches something you did not mean to rename.
.pages/.key documents, and similar) are directories on disk, so they count as folders here even though Finder shows them as files.Changed behaviour: the file commands used to rename whatever was selected, folders included. They no longer do. To rename folders, use Rename Folder(s) or Replace in Folder Names; to rename files and folders together in one pass, use Advanced Batch Rename with Apply to set to Files & Folders.
Advanced Batch Rename carries an Apply to dropdown in its search bar with three values:
The preview list is the working set: it shows exactly what will be renamed, and updates as you change the scope. Toasts and the history entry follow the scope too — N files, N folders, or N items. If the current scope matches nothing in the selection, the rename is blocked with a message instead of quietly doing nothing.
Every command records successful renames to a local history (the 25 most recent operations) and opens Rename History after a successful batch, so you can review — or undo — what just happened. Open it any time to:
Undo is careful about files that changed since the rename: a file that has been moved or deleted, replaced by a different file, or whose original name is taken again, is skipped rather than failing the whole batch — it is marked with the reason and can be retried once the conflict is resolved. Undo verifies the file's identity (not just its path), so it never moves a file the rename didn't produce.
History is stored locally in Raycast and never leaves your machine.