How to rename hundreds of photos in seconds
Photographers, designers, and content creators: stop wasting hours in Explorer. Here's the fastest workflow.
Coming back from a shoot with 800 photos named IMG_4521.JPG through IMG_5320.JPG is the moment most photographers either curse and renamne in Lightroom for an hour, or just give up and leave them as-is. Both are bad. Here’s a faster way.
Why camera-default names are awful
Cameras name files by an internal counter. IMG_4521.JPG tells you nothing about:
- What the shoot was (wedding? product? trip?)
- When it happened (the file date is unreliable after editing)
- Whose camera (a problem when two photographers shot the same event)
- Where it sits in the sequence (counter resets, gaps from deleted files)
Worse, when you import into Lightroom or Capture One a year later, the catalog inherits this nonsense and you spend 10 minutes searching for “the third shot from the cake-cutting.”
The 5-minute renaming workflow
Pick one convention and apply it to everything from a given shoot. The convention I’d recommend for most photographers:
YYYY-MM-DD_event_NNN.ext
2026-04-26_smith-wedding_001.jpg
That’s date-first (so folders sort chronologically), event slug (so a search for “smith” finds them all), then a 3-digit counter (so they sort correctly past 99).
Five steps in any decent batch renamer:
- Drop the folder of camera-named photos into the tool.
- Set “Ignore existing name” — we don’t care what the camera called them.
- New name:
2026-04-26_smith-wedding - Numbering:
001, 002, 003…at the end. - Lowercase, keep the
.jpgextension.
Hit export. 800 photos renamed in under 30 seconds.
Why a browser tool beats Lightroom for renaming
Lightroom’s batch rename works fine — once you’re already in Lightroom. But:
- It modifies your catalog, which means a missed undo means rebuilding metadata.
- It’s slow on big batches (thousands of files).
- You can’t easily preview the new names side-by-side before committing.
- You need Lightroom installed and licensed.
A standalone batch renamer like Namyfixer gives you a dry-run preview, side-by-side originals vs new names, collision detection, and a ZIP export — without touching your catalog. You import the renamed files into Lightroom afterwards if you want.
And critically: your photos never upload anywhere. The whole thing happens in your browser, locally.
Edge cases to watch for
A few traps that bite photographers specifically:
Sequence numbers across sub-folders
If you shoot two days and end up with Day1/ (300 photos) and Day2/ (250 photos), naive renaming restarts the counter at 001 in each folder. You probably want a continuous sequence: 001 → 550. Drop both folders into the same batch — most tools (including Namyfixer) treat them as one stream and number them globally.
Sidecar files (.xmp, .dng, .raw)
If you shoot RAW + JPEG, you have paired files: IMG_4521.NEF and IMG_4521.JPG. Renaming them independently breaks the pairing. Either:
- Rename only the JPEGs and re-export RAW from your editor with matching names, or
- Use a tool that detects pairs (Lightroom does; most batch renamers don’t).
For sidecar-aware renaming, RAW + XMP pairs from Capture One, etc., the safest move is to do it inside your editor.
Two cameras, one event
If you and a second shooter both use Canon, your IMG_4521 collides with theirs. Always include a photographer initial in the filename for multi-shooter events:
2026-04-26_smith-wedding_fr_001.jpg ← Florian's camera
2026-04-26_smith-wedding_jl_001.jpg ← Julie's camera
Namyfixer’s collision detector flags any duplicate names before export, so you can’t accidentally overwrite.
The math: how much time you save
Manual renaming in Explorer or Finder: ~5 seconds per file with focused work. For 800 photos, that’s ~67 minutes — and you’ll lose attention halfway and make mistakes.
Lightroom batch rename: 5-10 minutes including catalog updates.
Browser batch renamer: 30-60 seconds, including dropping the folder and previewing.
Across a year of weekly shoots, you save dozens of hours that you can spend editing or, you know, sleeping.
What about HEIC, RAW, and weird formats?
Doesn’t matter. A good batch renamer just changes filenames — it doesn’t decode images. So IMG_4521.HEIC, IMG_4521.NEF, IMG_4521.CR3, IMG_4521.ARW all work the same. The file content is untouched; only the filename changes.
If you’re working with truly weird formats (TIFF stacks, multi-page PSDs), the renamer doesn’t care — it sees them as opaque bytes.
TL;DR
- Date-first ISO format + event slug + 3-digit counter = fewer regrets.
- Browser tools beat Lightroom for pure renaming: faster, no catalog risk, no install.
- Watch for: sub-folder sequencing, RAW+JPEG pairs, multi-photographer collisions.
- Real talk: 30 seconds of batch renaming saves you an hour per shoot.
Try it on your last shoot: open Namyfixer and drop the folder.