Undo & Rename History

The first question everyone asks before pointing an AI at 500 files: what if it gets something wrong? The answer is built into NameQuick's core: every rename is recorded, every rename is reversible, and nothing about your files changes except the name.

---

Every rename is recorded#

The Recent Renames panel keeps a running history of everything NameQuick has done. For each file you see the original name, the new name, when it happened, and the outcome — including whether a name was adjusted (for example shortened) and why. Renames from watch folders are listed right alongside manual batches, so automated work is just as inspectable as work you triggered yourself.

Undo any rename#

Hover over any successful rename in the history and click Undo — the file gets its original name back, and the entry shows the reverted state with the generated name struck through. Changed your mind again? Redo re-applies the generated name. For batches, revert as many files as you need; NameQuick handles them safely one at a time, so name collisions can't corrupt anything along the way.

If a file has been moved or deleted outside NameQuick since the rename, its history entry is greyed out — NameQuick won't guess at files it can no longer see.

What never changes#

• Creation and modification dates are never touched — not by renaming, not by undoing. Sort order, backups, and "date taken" workflows stay intact.
• File contents are never modified. NameQuick changes names and (if you use Rules or Organize) locations — the bytes inside your files are read, never written.
• Extensions are protected. Generated names can't silently change a file's type.

What about moved files?#

Undo restores names. If a Rule also moved a file, undoing the rename doesn't move it back — your folder structure is yours to manage, and silently relocating files would be its own kind of mess. The history shows where every file ended up, so nothing is ever lost. (Organize, coming soon, goes further: its batch moves come with one-click whole-batch undo.)

---

Try it on something unimportant#

The fastest way to trust the safety net is to use it: rename a handful of throwaway files, then undo them all. That round-trip — rename, inspect, revert — is exactly the workflow review mode gives you on every batch if you'd rather approve names before they're applied at all.