Before renaming 200 photographs, run the intended rule on a copy of six. Include one filename that should stay as it is and one that already occupies a proposed destination. Check whether the rule keeps the existing extension and where it would try to put the collision.
Save a map of the proposed paths outside the folder before running the batch. After the rename, update the map with the paths the tool actually produced. You can use that record after closing the preview.
Put a collision in the test set
Suppose the client asks you to replace draft- with approved-. In a disposable folder, put draft-lobby.jpg, draft-stairs.jpg, approved-lobby.jpg and notes.txt. Turning draft-lobby.jpg into approved-lobby.jpg would collide with an existing item even if you selected only the two drafts. Use a distinct target such as approved-lobby-v2.jpg after checking that the two files represent different revisions.
| Original relative path | Proposed relative path | Result |
|---|---|---|
draft-lobby.jpg |
approved-lobby.jpg |
Change the rule or assign a unique target |
draft-stairs.jpg |
approved-stairs.jpg |
Ready if the name is free |
notes.txt |
notes.txt |
Leave outside the batch |
Check target names against both the other proposed names and any files left out of the selection. On a folder headed to another machine, look for pairs of targets that differ only in capitalization. If two directories can contain the same basename, keep their relative paths in the mapping.
Preview with your file manager
PowerRename is part of PowerToys on Windows. It shows original and proposed names beside each other. Set the match scope to filename only if you want to preserve extensions, and confirm whether subfolder contents are included. Windows Explorer's Undo Rename can reverse the last change, so validate the first small batch before doing other file operations.
Finder's bulk rename command offers text replacement, text addition and a naming format. Check exactly which items you have selected and try the same option on the copied files. Leave filename extensions in place unless you are intentionally changing how an app recognizes a file.
Keep the undo usable a week later
Save the original and actual new paths of every successful rename. If you need to reverse the job and a name is now occupied, put the restored file in a separate holding folder while you compare the contents. A blanket inverse rule can pick up new files created since the first rename. Keep a checked copy of the original folder until the renamed files have been used in their destination tools.
Make the sample include everything the rule could touch
Put copies from a few folders into a disposable version of the tree. If a batch will include photos, sidecar files and notes, include an example of each. Give the test files distinct contents you can recognise. If the client says to replace the initial word “draft,” include another filename with “draft” in the middle. This catches a replace rule that treats several positions alike. Check whether you intended to affect names in subfolders or only the items you selected.
Look at the extension separately in the preview. A name that ends in a familiar suffix can have more than one dot. The app may show only part of it in ordinary view. Open the file information or enable the view that displays the actual filename before choosing what the tool can change. In a photo delivery, a JPEG and a text sidecar can need matching names with different extensions. Keep both extensions and test the pair after applying the naming rule.
For several directories, record the complete relative path. “Cover.jpg” under a folder for drafts differs from an identically named file in approved exports. If the receiving system brings both paths into a single folder, include that final layout in your collision check. Look for differences in case or punctuation that the destination treats the same. The Mac-to-Windows filename check has examples of those rules.
Use the preview as a set of proposed moves
Review which target is assigned to each file, then check what already exists at every destination. A collision can come from another proposed move or a file that the rename tool never selected. In the sample, leaving the approved lobby file out of the tool does not make its path available. Add a suffix that identifies the different version or revise the rule for both. If two outputs would be unique only by capitalization, choose names that remain distinct in the actual destination.
| Observation | Adjustment before running |
|---|---|
| A filename changes even though it lacks the intended prefix | Narrow the match to the part of the name you intend to use. |
| Two files reach the same proposed name | Give them distinct destinations and check the occupied paths. |
| A sidecar file no longer matches its photo | Apply a coordinated mapping while retaining both extensions. |
| A folder or an unexpected extension appears in the preview | Narrow the selection and repeat the test on the copied tree. |
Use the actual destination to check the preview. If the items will be shared, open one renamed sample with the destination program. An image editor can remember the original path or track a sidecar by basename. A short visual test catches problems that sorting the file names will miss.
Make a fallback independent of the immediate undo
Start with a copy of the source or another verified fallback you can reach. Preserve the old and proposed paths in a small table, adding the actual result from the first batch. To reverse a rename later, verify the current file and exact intended old path before using that map. If another file occupies the original name, preserve both copies and decide where they belong. Avoid applying a broad inverse search against a folder containing new work.
For an interrupted operation, check off which source files moved and which are still present. Inspect the failed item before running the batch again. A repeat with the same rule can affect a different set once some names have already changed. Use the map to identify the remaining files and complete the small batch before proceeding. Open one renamed file and its sidecar or link after the final check. Preserve the source copy until the receiving application has used the file under its new path.


