Copy a card onto your Mac and every photo on it can end up stamped with today’s date. Copy the same card twice and you get two different answers. The date you actually want — the moment the shutter fired — is sitting inside each file the whole time, written there by the camera, and most of the obvious tools on macOS never look at it.

That gap is the reason renaming by date is more annoying than it should be. This guide covers what the dates are, why Finder picks the wrong one, and four ways to rename by the right one.

The three dates on every photo, and which is the shutter

Every image file on your Mac carries at least three dates, and they routinely disagree:

Date Created — when this copy of the file came into existence on this disk. Copy a photo, and the copy’s creation date is now.
Date Modified — when the file’s bytes last changed. An edit, a metadata write, sometimes a sync client touching it.
Date taken — the capture time your camera recorded inside the file, in its EXIF metadata, as DateTimeOriginal. This is the one that means “when the photo was taken”, and it travels with the file no matter how many times it is copied.

Only the third one is stable. The first two describe the file’s history on a disk; only the capture date describes the photograph. Any renaming scheme built on the first two will drift the first time the files move.

Why Finder’s rename gets it wrong

Finder has a genuinely good batch rename — select several files, right-click, Rename. It will find-and-replace, add text, or apply a format with an index, a counter, or a date.

The catch is the date it offers. Finder works from the file’s own dates and the clock, not from the EXIF capture time. It has no way to read DateTimeOriginal, so the moment you ask it for dated filenames you get dates describing when the file arrived, not when the photo was taken. On a card you have just imported, those can be the same day and the scheme looks like it works — which is exactly why the problem tends to surface months later, on an archive that has been copied once too often.

Apple Photos does not solve it either. Renaming inside Photos changes the title recorded in its library; the files on disk keep the names they had.

Automator and Shortcuts hit the same wall

The usual next step is a Quick Action — Automator’s Rename Finder Items, or a Shortcut doing the same. Both are worth knowing, and both inherit the same limitation: the date options are the file’s dates. You have automated the renaming without fixing the date it names from.

Shortcuts can read some image metadata, so a sufficiently determined Shortcut can get at the capture date. By the time you have built it, you have written a small program with no preview and no undo — which is a lot of work to arrive somewhere the next two options already are.

ExifTool in Terminal: correct, but per-shoot

ExifTool reads the capture date properly, and one command renames a folder by it. If you are comfortable in a terminal it is a genuinely correct answer, and it is free.

What it does not give you is a look before you leap. There is no preview of the resulting names, no undo if the pattern was subtly wrong, and the command has to be re-derived — or found in your shell history — every time a convention changes. For a one-off folder that is a fine trade. For a convention you apply to every shoot, it is a command you will get wrong at least once, on files that matter.

Renaming a whole shoot from its own metadata

Archyv reads the same metadata ExifTool does — it bundles ExifTool for exactly that — and puts a preview and an undo history around it.

You build the naming convention once, as a template: a pattern of the fields you want the name made of. A pattern like {yyyy}{mm}{dd}-{seq:4} produces 20260731-0001, numbered in order. Put the photographer in front of it — {artist}-{yyyy}-{seq:4} — and you get Rivera-2026-0001.

Two details make the numbering behave the way you would expect. {seq:4} zero-pads to four digits, so files sort correctly in every tool that sorts names as text. And the variables before {seq} decide when the counter restarts: with {artist}-{yyyy}-{seq:4}, each photographer-and-year group is numbered from 1 on its own, so a folder holding two photographers’ work comes out as two clean runs rather than one interleaved one.

Templates are saved and reusable, so the next shoot is a single choice rather than a fresh setup. You apply one from the Metadata Renaming process, and build or edit them on the Filename Templates tab.

What happens when a photo has no date

Real shoots have gaps. A frame from a camera whose clock was never set, a scan with no EXIF at all, a file that has been through a tool that stripped it. A renaming scheme is only as good as its answer to that case, and Archyv makes you choose one up front — the template’s Fallback Mode:

Skip leaves those files alone and renames the rest. The safest choice when you expect the data to be clean and you want to be told when it is not.
Use Fallback renames everything, substituting a placeholder (UNKN by default) where the value is missing — so the set stays consistent and the gaps are visible in the names themselves.
Prompt User stops and asks you to type each missing value during the run. Full control, at the cost of an unattended run.

Deciding this once, in the template, is what stops a stray undated frame from either silently breaking the sequence or quietly acquiring a wrong date.

Preview it, then undo it if you need to

Two safety nets, and they work differently.

Before you run anything, the template editor shows a live preview: example output built from sample metadata, so you can confirm the pattern produces what you meant before it touches a file. Turning on Simulation Mode in General Settings goes further — a full run that changes nothing and writes every proposed rename to the log, so you can read the whole result of a real batch first.

After a run, the renames are recorded in Archyv’s history, so an operation can be undone for a retention period you set. And worth stating plainly, because it is the thing people are actually nervous about: renaming changes only the file’s name. The image data and the metadata inside each file are left exactly as they were.

RAW, HEIC, and video

The capture date is not a JPEG-only idea, and neither is any of the above. Archyv reads 40 formats across 44 extensions — 9 standard image formats, 20 RAW formats from the major camera makers, and 11 video formats — so a folder mixing RAW files, HEIC from a phone, and clips from the same shoot can be renamed in one pass, on the same convention.

One thing to know if you shoot RAW alongside anything else: renaming acts on the names, so a RAW and its processed sibling keep whatever relationship their names give them. If your workflow depends on a RAW and a JPEG sharing a base name, build the template so the shared parts come first and the pair stays together.

Next: the Metadata Renaming reference walks through every option in the process, and Filename Templates covers building the pattern — including custom variables that combine several metadata fields with their own fallback chain.