Bulk Rename Utility lets you set rules separately, select the exact items to be affected, and preview the results in a New Name column. The workflow below focuses on bulk rename subfolders without changing unrelated files.
Example: before and after
These filenames are examples to explain the transformation; they are not test results from your files.
| Before | After (illustrative) |
|---|---|
Photos/Day1/IMG1.jpg | Photos/Day1/Trip1.jpg |
How to do it step by step
- Step 1. Make a backup of the top-level tree.
- Step 2. Enable recursive scanning.
- Step 3. Filter to files rather than folders.
- Step 4. Review preview across multiple subdirectories.
Why this workflow works
The rule and selection work together: the rule changes eligible filenames, while the selection limits which files receive the change. Always inspect the New Name column and confirm the directory before choosing Rename. For repetitive work, save verified settings as a favourite, but review them again on each new batch.
How to verify the results
Compare the original and proposed filenames side by side, check that each target name is unique in its directory, and confirm file extensions match the actual file types. After applying the rule, open a sample file in its usual Windows application and check any shortcuts or scripts that use the old path.
Frequently asked questions
How do I subfolders in Bulk Rename Utility?
Enable the subfolder option to apply filename rules to nested directories while preserving folder structure.
What should I check before applying this batch?
Compare the New Name preview for every selected file, check for duplicates and verify extensions. Recursion can affect far more files than the first visible folder.
Does changing a filename also change its contents?
No. A standard filename rename changes the name or path, not the document, photo, audio, or video data. Changing an extension also does not convert a file format.
Related Windows renaming guides
For release details, licensing and implementation-specific controls, consult the documentation and source list. Always use a small test directory before a large batch.