Somewhere in every hard drive there is a folder of photos named IMG_4021.jpg, IMG_4022.jpg, straight from a camera that does not care how unreadable it is. Renaming twenty of those by hand is tedious but survivable. At two hundred, you start making mistakes, and by four hundred you have files with three different naming patterns and no idea which one is right.
Ahuange Renamer is how I handle that job now. You describe the renaming as a stack of rules, the tool shows you the final name of every file before anything touches the disk, and if the result is wrong there is a one-click undo. This guide covers the rule types, a full session from folder to finished batch, and the safety design underneath.
Why rules beat manual renaming
Manual renaming fails in a specific, repeatable way: you type the first few names carefully, then get faster and sloppier, and somewhere around file thirty the pattern drifts. And even if you stay perfect, there is no record of what the old names were.
Rules remove both problems. A rule applies identically to every file in the selection, so the pattern cannot drift. The preview table shows every old name next to its new name, so nothing is a surprise. And the undo history means a bad decision costs one click, not an afternoon.
The five rule types
Steps stack into a pipeline of up to five, applied in order. Ten built-in presets for photos, documents and downloads give you a working starting point that you can then adjust.
- Add puts text at the start or end of every name: dates, project prefixes, version markers like
_v2, or sequential numbers. - Replace finds text and swaps it. Renaming every
IMGprefix toPhoto, or stripping the%20clutter that web downloads pick up, is one step. - Change case forces lowercase, uppercase or title case across the batch, which settles folders that mix
REPORT.DOCXwithreport.docx. - Remove characters deletes at a position or range: camera counter digits, brackets, trailing spaces.
- Rebuild rearranges the name from its parts and can renumber the selection; numbering stays continuous even when the filter skips files.
A complete renaming session
1. Load the folder
Pick the folder and the scan starts immediately. Big folders stream in as they are found, so a folder with tens of thousands of files does not leave you looking at an empty window.
2. Filter and select
Narrow the list by name and tick exactly which files take part. The selection order is respected, so when Rebuild numbers your files, the numbers run without gaps.
3. Stack the rules
For a camera folder I would run: Replace IMG- with the shoot date, Change case to lowercase, then Add the project name as a suffix. Three steps, each still editable after stacking, and the presets get you most of the way there before you touch anything.
4. Read the preview
The preview table is where the session is actually won. It updates as you type, highlights the changed characters, and warns about two things that matter: two files heading for the same name, and characters Windows does not allow in file names. Nothing has been written to disk yet, so mistakes here cost nothing.
5. Run it, or undo it
Rename Files executes in two phases: everything first moves to unique temporary names, then into place. That ordering matters more than it sounds. It is what lets swap-style renames (file A taking file B’s old name and vice versa) work correctly, and it means an existing file is never silently overwritten. If the result is wrong anyway, one click reverts the whole batch, and the history timeline keeps the last 20 batches available even after restarting the app.
Recipes worth keeping
| Goal | Pipeline |
|---|---|
| Photos sorted by real capture date | EXIF rename (falls back to file modified time) + Add an event prefix |
| Web downloads cleaned up | Replace or Remove the %20 junk + Change case to lowercase |
| Document versions | Add a _v2 suffix + Replace the old project code |
| Mixed-case archives normalized | Change case to title case + Rebuild with separators |
| A reviewable record before committing | Export the preview as CSV: every original name paired with its new name |
That last row is the one I would point nervous users at. Before a large batch, the CSV gives you the complete old-to-new mapping as a file you can keep, check, or use to reverse the rename yourself.
When a batch goes wrong
The two-phase execution is the part I would not ship without. Renames run through temporary names, so a failure stops cleanly instead of leaving half a folder renamed, and a name collision fails that file instead of replacing whatever held the name first. Conflict detection also flags those collisions in the preview, long before execution. Long paths past Windows’ 260-character limit go through the mechanism automatically, because deep folder trees are exactly where renames tend to die halfway.
The tool itself is a single portable file under 3 MB, small enough for a USB stick, with everything running locally. Your file names stay on your machine.
The short version
Batch renaming goes wrong when it is quick, careless and irreversible. This makes it slow enough to see what will happen, careful enough to refuse overwrites, and reversible when you still get it wrong. That combination is the whole point.
Ahuange Renamer is free to download. Try it on a copy of a real folder first; the preview and the CSV export will tell you within a minute whether the rules do what you meant.