Rename Photos by Capture Date in ExifToolGui

Camera file names such as IMG_4832 tell you nothing and collide between cameras. Names built from the capture date sort chronologically in any program, survive moves between folders, and make two cameras’ files interleave in true order. ExifToolGui V6.3.12, Frank Bijnen’s maintained fork of Bogdan Hrastnik’s GUI for Phil Harvey’s ExifTool, includes renaming from DateTime in its Modify menu, and ExifTool itself is documented as renaming files and organising them by date or other metadata.

Renaming trusts the stored capture date completely, so this guide starts there: a wrong DateTimeOriginal produces confidently wrong names. Fix dates first with changing DateTimeOriginal or shifting EXIF time, then rename. More workflows are in the Tutorials hub; the program is on the download page.

Fix and Verify Dates Before Any Renaming

Sort the folder by DateTimeOriginal in the file list and scan for outliers: a file dated years away from its neighbours, or a run of files stamped with a camera’s factory default date, will be renamed into the wrong place in the sequence. Correct those files first, individually or by an offset shift, and re-check the sorted order until the timeline looks true.

Pay special attention to merged sets. Two cameras with two different clock errors produce a merged folder whose files interleave wrongly even though each camera’s internal order looks fine. Align both cameras to true time before renaming the combined set, or the new names will bake the misalignment in permanently.

Choose the Modify Menu Renaming Entry

Select the files to rename and open the Modify menu. The V6 documentation lists file renaming entries in the style of File: Name=DateTime+Name, which build the new name from the file’s DateTime value. Using the stored DateTime means the name reflects when the photo was taken, not when the file was copied or exported, which is precisely the property that makes date-based names useful in an archive.

Rename in a copied test folder first and live with the result for a minute. Check that the names read well, that files from a burst taken within one second do not collide, and that the folder sorted by name now matches the folder sorted by capture date. Only then run the same operation on the real set.

• Dates verified in sorted view first.
• Test rename on a copied folder.
• Name-sorted order matches date-sorted order.

Handle Bursts, Duplicates and Mixed Types

Fast shooting produces several files with the same second, and exports can add same-named companions such as a JPEG beside a RAW file. A date-based scheme must keep those files distinct and adjacent. After the test rename, look specifically at the densest burst in the set: every frame should still exist, with names that keep the sequence unambiguous.

Mixed folders of photos and videos can also share timestamps. If the result in the test folder tangles types together in a way you dislike, split the batch by type and rename each group separately. The operation is cheap to repeat; untangling a badly renamed mixed batch by hand is not.

What Renaming Does Not Change

Renaming changes file names only. The metadata inside the files, including DateTimeOriginal itself, stays as it was, which is why the date work had to come first. Sharing copies renamed this way also still carry whatever metadata they carried, so a renamed file is not a cleaned file: use strip metadata before sharing for copies that leave your machine.

Keep a note of the scheme you used in the archive folder if a Library spans many years. Consistent naming across years is what turns renaming from a one-off tidy into a retrieval system: any file’s name then tells you when it was taken before you open it, in any tool, on any system.

A Naming Scheme You Can Keep for Years

Choose the simplest scheme that answers your retrieval questions. For most archives the capture date, with enough time detail to order a day’s shooting, plus a short sequence or the original name fragment, is sufficient, which is the spirit of the Modify menu’s DateTime-based entries. Schemes that try to encode place, subject and camera into every file name become brittle, because those facts belong in metadata, where they can be edited without renaming anything.

Apply the scheme to new imports as they arrive rather than in annual purges. A folder renamed on import joins a consistent archive immediately, and the habit reinforces the date checks that renaming depends on: a new set whose dates are wrong gets fixed while you still remember the shoot, not discovered years later when the evidence for the true date has faded.

Frequently Asked Questions

Does renaming use the capture date or the file date?
The Modify renaming functions build names from the file’s stored DateTime metadata, the capture time, not the Windows file-system date of the copy.

What if two photos share the exact same second?
Check bursts in a test rename first. The files must remain distinct after renaming; if a scheme collides, split the set or adjust the approach before renaming originals.

Should I rename before or after editing metadata?
Dates first, always: renaming reads DateTimeOriginal. Descriptive edits such as keywords can happen before or after, since they do not affect the name.

Date-based names make an archive self-sorting forever. Combine this with accurate dates and clean descriptive tags from the Tutorials hub, and a folder explains itself without any catalogue software at all.