Renamo

The problem

Nobody ever renames ten files.

Renaming ten files is a chore. Renaming four hundred is a job you postpone until it becomes urgent, and then you do it fast, by hand, one selection at a time. That is where a shoot loses its numbering.

The batch rename built into your system does find and replace, and a counter. Anything past that, a date pulled out of the filename, an accent stripped, a suffix moved to the front, and you are back to typing. Worse, you find out it went wrong once every name has already changed.

The answer

See the new name before it exists.

Renamo builds each new name from independent rules that you stack in any order: add, remove, replace, insert, date and time, numbering, extension. Every rule shows its effect on every file, live, before a single item is written to disk.

Name collisions are caught in the preview rather than discovered afterwards. And when a batch turns out wrong anyway, one click puts every name back.

How it works

Two phases, so nothing collides.

A rename that runs in a single pass can trip over itself: file B needs the name that file A has not released yet. Renamo renames in two phases, through temporary names, so a batch that reorders or swaps names completes without a conflict.

The whole operation is recorded as one batch. The undo restores the exact previous state of every item, not an approximation of it.

What is in it

The rest of the toolbox.