Fix Dates on Scanned Photos: Set a Real Capture Date

A scanned print carries the date of the scanning session, not the day the picture was taken, and some scans carry no capture date at all. Timelines then file a 1980s childhood photo under last Tuesday. ExifToolGui lets you set a real DateTimeOriginal on those files visually: the tool is V6.3.12 by Frank Bijnen, the maintained fork of Bogdan Hrastnik’s GUI for Phil Harvey’s ExifTool, and the date-setting workflow is its Workspace plus Modify date functions.

This guide covers choosing a defensible date, writing it to one scan or a sitting’s worth of scans, and keeping approximate dates honest. The single-date mechanics are shared with changing DateTimeOriginal. Both guides sit across the Metadata Tasks hub and the Tutorials hub; the program is on the download page.

Decide the Real Date, and How Sure You Are

Work from evidence on and around the print: dates on the back, a dated event the photo shows, clothing and ages that bound a range, or a lab stamp on the border. Write down what you know in three grades: an exact day you can defend, a month or season you are confident of, or a year that is a best estimate. The grade decides what you write into the file.

For an exact day, set that full date. For a confident month with no known day, a conventional choice inside the month, recorded in your notes as approximate, keeps sorting sane without pretending to a precision you do not have. For a year-only estimate, mid-year is the common convention. What matters is that your archive notes preserve the uncertainty the metadata field itself cannot express.

Set DateTimeOriginal on One Scan

Open the scan in the GUI, select it, and set DateTimeOriginal in the Workspace to the date you decided, following the same steps as the general DateTimeOriginal guide: enter the value, save, then re-select the file and confirm the stored value reads back. Scanners often write their own software tags and the scanning date into other fields; the capture field is the one timelines read, so it is the one to set.

If the same session produced a stack of scans from one event or one roll, select the whole sitting and set the shared date once in a batch, as batch-editing a whole folder describes. Individual frames that you can place more precisely can then be adjusted one by one on top of that base correction.

• Grade the evidence: exact day, month, or year.
• Set DateTimeOriginal in the Workspace and re-read it.
• Batch one sitting together, then refine individuals.

Equalize Copies and Name the Files

After setting the capture date, run the Modify menu’s DateTime equalize on the scans so EXIF and XMP copies agree; otherwise a catalogue reading the other family will keep filing the scan under the scanning date. This is the same divergence problem explained in EXIF vs IPTC vs XMP, and scans hit it constantly because scanner software writes partial metadata.

With real dates stored, renaming becomes meaningful: apply rename photos by capture date to the scan folder, and decades of prints settle into chronological names that interleave correctly with born-digital photos from the same family archive.

Keep the Scanning Facts Too

Setting a capture date does not require erasing the scan’s own history from your records. Keep an archive note, at folder level, recording when and from what the scans were made, especially where originals are fading prints whose condition matters. The photo file tells when the picture was taken; your notes tell how this digital copy came to be.

Resist back-filling false precision later. If a relative supplies the exact date for a photo you estimated, correct the file then, gladly, and note the correction. An archive maintained that way, estimates labelled and corrections welcomed, stays trustworthy in a way a confidently invented archive never does.

Sort Scans Into the Timeline Gradually

A family archive rarely gets dated in one sitting, and it does not need to be. Work in sittings of one roll, one album page or one event at a time, setting the dates you can defend and leaving the rest clearly in the scanning-date state rather than guessed. A partly true timeline, where dated scans sit correctly and undated ones are visibly unprocessed, is more useful than a fully populated timeline of mixed fact and invention.

Enlist relatives as evidence, not as an afterthought. A shared folder of undated scans with a simple question, who remembers when this was, produces the event names and holiday years that anchor a whole sitting at once. Feed each answer into the files while the conversation is fresh, with the certainty grade from this guide recorded in your notes.

Frequently Asked Questions

What date should a scan show, scanning date or photo date?
The photo’s capture date. DateTimeOriginal means when the picture was taken, and timelines, sorting and renaming all interpret it that way.

What if I only know the year a photo was taken?
Set a conventional mid-year date so the scan sorts correctly, and record in your archive notes that the date is a year-level estimate, not a known day.

Why does my catalogue still show the scanning date?
The capture time may also exist in XMP, or the catalogue may be reading a different copy. Run DateTime equalize after setting the date so EXIF and XMP agree.

Real capture dates rescue scans from the digital present and return them to the family timeline. Work through the remaining date and description tasks in the Metadata Tasks hub to finish the archive.