You scan two hundred family photos and they all land in your library dated today, sandwiched between a grocery receipt and a picture of your dog. Or you find a whole vacation filed under 2007 because the camera's clock reset when the battery died. Or photos your sister texted you have no date at all and cluster at the bottom of your timeline like orphans.
Wrong dates are the most common metadata problem there is, and the most consequential — because date is the axis every photo app sorts on. A photo with a wrong date isn't just mislabeled. It's effectively lost, sitting somewhere you'll never think to look.
Here's how to fix it, from a single photo to ten thousand.
First: know which date you're fixing
Three different dates live on every photo file, and confusing them is why people "fix" dates and see no change.
Date taken (also called Date Original or Capture Date) is stored inside the file, written by the camera when the shutter fired. This is the one that matters. Every photo app sorts on it.
Date modified is when the file was last saved. Editing changes it.
Date created is when this particular copy appeared on this particular drive. Copying photos to a new computer resets it to today, which is why a folder of twenty years of photos can look like it's all from last Tuesday in File Explorer.
If you change the file's date in Windows Properties or with a Mac terminal command, you're usually changing created or modified — not date taken. Your photo app will ignore it entirely.
Fix date taken. Everything else is cosmetic.
Why dates go wrong
Knowing the cause tells you which fix to use.
Scanning. The scanner writes today's date because that's when the file was created. There's no original EXIF to preserve — a paper print doesn't carry one. Every scan needs its date set manually.
Camera clock never set. Digital cameras reset to a default date when the internal battery dies. Every photo from that point carries a consistent, wrong offset — usually years off. This is the easiest kind to fix because the error is uniform.
Time zone travel. A camera records local time with no time zone context. Photos from a trip may be off by hours. Usually not worth fixing.
Messaging and social platforms. Most strip EXIF entirely for privacy and file size. Photos arrive with no date taken, so apps fall back on the file's created date — the day you received it.
Screenshots of photos. Photographing a photo on a screen, or screenshotting one from social media, produces a brand-new file dated now.
Bad imports. Some transfer methods, particularly dragging files off a phone through certain apps, drop metadata on the way.
Fixing a single photo
iPhone
Open the photo, swipe up or tap the info button, then tap Adjust next to the date. Set date, time, and time zone. Done.
You can also select multiple photos in the library, then use the share sheet or the top-right menu to adjust the date for all of them at once — iOS offers both "shift all by the same amount" and "spread evenly across a range." That second option is genuinely useful for a scanned batch where you know the rough period but not individual days.
Android / Google Photos
Open the photo, swipe up or tap the info icon, tap the date, edit it. Multi-select works too: select several photos, tap the three-dot menu, choose Edit date & time.
Same two modes: shift by a fixed offset, or distribute across a range.
Windows
Right-click the file → Properties → Details tab. Find Date taken and click the value to edit it. Works, but only one file at a time, and it's slow.
Mac
In Photos: select the image, then Image → Adjust Date and Time. Works on multi-selections and offers a fixed offset.
Outside Photos, Preview's Inspector shows metadata but won't reliably edit it. Use a dedicated tool.
Fixing hundreds or thousands
This is where the real work is, and where the right approach saves you days.
The two operations you need
Shift applies a fixed offset to every selected photo: "add 12 years, 3 months, 2 days." Use this when the error is consistent — a camera clock that was wrong by the same amount for the whole batch. The critical advantage is that it preserves relative timing, so the sequence of your day stays intact and photos remain in the order they were taken.
Set overwrites the date on everything with the same value. Use this for scans, where there's no meaningful original timing to preserve and approximate is the best you can do.
Choosing the wrong one is the classic mistake: using Set on a vacation batch flattens a week of chronology into one instant.
Batch-fixing scanned photos
The efficient approach is to sort before you fix, then apply one date per group.
Organize your scans into folders by decade or event first:
_SCANS/
1940s/
1950s/
1952-summer-porch/
1967-graduation/
unknown/Then for each folder, select everything and Set the date to a representative value. For a decade folder, 1955-01-01. For a known event, the actual date.
This takes about a minute per folder, and it means a thousand scans get correct-enough dates in half an hour rather than a week.
On precision: don't chase it. A photo dated 1955-01-01 when it was actually taken in August 1956 is filed within the right neighborhood of your timeline. That's the entire goal. Being off by eighteen months costs you nothing; being off by seventy years costs you the photo.
Batch-fixing a wrong camera clock
- Find one photo from the batch where you know the true date — a birthday, a holiday, a wedding.
- Compare its recorded date to the true date. Calculate the difference: "recorded as 2007-01-01, actually 2019-04-14, so the offset is +12 years, 3 months, 13 days."
- Select the whole affected batch and apply that shift.
Verify by spot-checking two or three other photos where you know the real date. If they land correctly, the whole batch is right.
Tools for large batches
For thousands of files, you'll want a dedicated metadata tool rather than a photo app. Look for one that offers:
- Batch shift and batch set on date taken specifically
-
Filename-to-date parsing — if your files are named
1952-summer-porch-01.jpg, a good tool can read the date out of the filename and write it into the metadata. This is enormously powerful if you named your scans well. - Date-from-folder — same idea using the containing folder name
- A preview before writing, so you can confirm the change is right before it touches three thousand files
The filename-parsing feature deserves emphasis. If you followed a naming convention while scanning, you can convert an entire archive's filenames into proper metadata in a single operation. That's the payoff for naming carefully during the scan.
The one rule: back up before batch operations
Metadata edits write to the file. A batch operation applied to the wrong selection, with the wrong offset, is not always easy to undo — and some tools don't offer an undo at all.
Before any batch date change:
- Copy the folder to a backup location. Not a sync folder — an actual separate copy.
- Test on ten files first. Run the operation on a small selection, verify the result, then run it on everything.
- Check the preview if the tool offers one.
Ten minutes of caution against the possibility of scrambling twenty years of chronology is an easy trade.
Verifying the fix worked
After a batch operation, check three things:
Did the right field change? Open a fixed photo in your photo app, not just File Explorer. If the app still shows the old date, you changed the wrong field.
Is the order preserved? For shifted batches, confirm the photos still run in the sequence you expect. If a morning shot now appears after an evening one, something went wrong.
Did your photo app re-index? Apple Photos, Google Photos, and similar apps keep their own database. Files edited outside the app may not update until re-imported. If you fixed dates on disk and the app hasn't noticed, you may need to remove and re-add the folder.
That last one catches a lot of people who conclude the fix failed when it actually worked.
Photos with no date at all
Files stripped of EXIF have nothing to correct — you're supplying a date from scratch.
Work with what you have:
- The message thread. If your sister texted them, the conversation is timestamped. That's your date.
-
The filename. Many cameras and apps embed a date:
IMG_20190614_142233.jpgis June 14, 2019. - The content. Snow means winter. A birthday cake with visible candles narrows it. Kids' apparent ages bracket a range.
- Surrounding files. If the batch came off one camera card, undated photos likely sit between dated ones.
When you truly can't determine it, pick the middle of your best-guess range and move on. 2015-06-01 for "sometime in the mid-2010s" is a perfectly good answer.
Preventing this going forward
Set the camera clock every time you change the battery. Ten seconds, and it prevents the single largest category of this problem.
Ask people to share originals, not texts. AirDrop, shared albums, and cloud links preserve metadata. Text messages don't.
Date scans immediately after scanning, while you still remember which pile they came from. This is the difference between a two-minute fix and an archaeology project.
Spot-check imports twice a year. Open your library sorted by date and look at the last six months. If something is obviously misfiled, fix it now — catching a wrong clock in month two is trivial, catching it in year four means correcting four thousand files.
Next in this series: Google Photos vs Apple Photos vs Amazon Photos