Batch Rename
Learn how to use Batch Rename for one-time cleanup work with clear statuses, safe review before Apply, and predictable write timing.
Batch Rename
Batch Rename lays out the review flow clearly. You import files, let RenamerX generate suggestions, inspect the results, and then decide what should change on disk.
Use it for:
- One-time cleanup projects.
- Template validation.
- Mixed or messy folders that need human review before any write happens.
What the Batch Rename workspace gives you
At the top of the workspace, you can:
- Choose a template.
- Add files or folders.
- Set an optional target folder.
- Search the current workspace.
- Filter by status.
Inside the list workspace, you can:
- Review status changes.
- Compare original and suggested names.
- Edit suggestions manually.
- Retry failed items.
- Ignore items that should stay out of the batch for now.
- Apply or undo selected items.
Folder imports are recursive.
Recommended workflow
1. Choose a template first
The template defines which fields matter and how the final filename is built. RenamerX expects that decision before import.
2. Import files or folders
After import, RenamerX skips unsupported or temporary items, adds supported files to the current workspace, and queues them automatically.
3. Wait for suggestions
You do not need to manually start every file. Imported items flow into processing automatically.
4. Review the workspace
Typical review actions include:
- Opening the preview.
- Comparing original and suggested names.
- Editing a suggestion.
- Retrying failures.
- Ignoring edge cases.
5. Apply only what you trust
If you set a target folder, RenamerX resolves the destination during apply. If you leave target empty, apply renames in place.
6. Undo if the outcome is wrong
Undo is available for applied items because RenamerX keeps track of original and current paths.

Status reference
| Status | Meaning in Batch Rename | Typical next action |
|---|---|---|
| Pending | The item is waiting in the queue. | Wait, or stop the pending work if needed. |
| Extracting | RenamerX is reading the file and generating fields. | Wait for completion. |
| Suggested | A suggestion is ready and nothing has been written yet. | Review, edit, apply, ignore, or retry later. |
| Applied | The filesystem change already happened. | Leave it, or undo it. |
| Failed | Generation or apply failed. | Inspect the error, then retry or ignore. |
| Cancelled | A queued job was stopped before finishing. | Requeue only if you still want the suggestion. |
| Ignored | You intentionally excluded the item from the current flow. | Leave it ignored, or retry it later if you want to process it again. |
What changes on disk, and what does not
| Batch action | Writes to disk? | Notes |
|---|---|---|
| Import | No | Creates workspace records only. |
| Suggestion generation | No | Updates metadata and suggested names in the workspace. |
| Manual name edit | No | Changes the suggestion only. |
| Apply | Yes | Renames, and optionally moves, files one item at a time. |
| Undo | Yes | Restores original path and name when possible. |
| Clear Batch Workspace | No | Deletes Batch workspace records, including the undo history those records carry. It does not restore files on disk. |
Important behavior details
Apply runs item by item
If one item fails during apply, other items can still succeed. Review the failed subset separately instead of assuming the whole batch was rolled back.
Target folder decisions only matter at apply time
Choosing a target folder does not move anything during import, extraction, or review. The move happens only when you apply.
Temporary files are skipped on intake
RenamerX does not try to process partial downloads or other temporary files too early.
Typical misconceptions
"Import already changed my files"
Import only adds files to the current workspace and queues processing.
"Clear Batch Workspace is the same as Undo"
Clear deletes the Batch workspace records. Undo restores files that were already changed on disk.
"A suggestion means the file has already been renamed"
Suggested means ready for review. Applied means written to disk.
Recommended rollout pattern
Batch Rename is a good place to review a template on a small set of files. If your work is continuous, you can also refine the same template in Watch Folders with Review First before enabling Auto Apply.