Photo Date Rescue reads the true capture date and shows how confident it is.
How to Fix Wrong Photo Dates on Windows
Wrong “Date Taken” scrambles your whole timeline. Here is why it happens, where the real date actually lives, and how Photo Date Rescue repairs a library safely — without ever risking your originals.
Build your route
Three questions, and only the ones that actually change what you should do. Answer them and you get the sequence for your library, with the warnings that apply to it. Prefer to read the lot? The complete guide is right below, unchanged.
Where are the photos coming from?
Roughly how many photos?
Where do you want to start?
Your route appears here once all three are answered. Nothing is shown before then, because a sample route would only describe somebody else’s library.
- Keep the export exactly as it arrived. Leave a Google Takeout archive zipped and every
.jsonsidecar beside its image — PDR opens the archive itself, and the sidecar is where the original date survived. An Apple Photos export writes no JSON at all — its only sidecar is an optional XMP file — so choose Export Unmodified Original and the dates stay inside the files themselves: there is no Apple or iCloud importer. - Add the drive itself, connected. An external drive, hard disk or memory stick is added as a source exactly like a folder, and you do not need to copy the photos onto your PC first. Sub-folders on it are included automatically.
- Check free space on the output drive first. A repair writes a second, corrected copy of everything you point it at, so plan for roughly the size of the library again.
- Install the Windows desktop trial. It takes tens of thousands of files in one pass, from folders, drives and archives together, which the browser demo is not built for.
- Treat the web demo as a proof of concept, not a repair. It accepts one ZIP file of up to 200 MB and nothing else — not loose photos, not a folder, not a drive. If you have no ZIP to hand, make one from a few dozen photos, watch the confidence scoring on your own files, and then do the real work on the desktop.
- The demo cannot take a library this size. 200 MB is a few hundred photos at most, so use it only to see how the scoring behaves, and install the Windows desktop trial for the actual run.
- Add each source as its own folder. An export, a phone camera roll and a folder of scans behave very differently. Keeping them separate lets you read the confidence per source instead of one blended number.
- Point PDR at your photos. Add the folder, drive or ZIP archive on your Windows PC. Sub-folders are included automatically.
- Run one small folder first. Before committing to a long run, do a single folder and see how the confidence scoring behaves on your files.
- Let PDR read each file. It works the date out from EXIF, video metadata, JSON sidecars, filename patterns and folder structure, and scores how confident it is in the answer.
- Expect most of these to come back high-confidence. A camera or phone normally writes EXIF at the moment of capture, so the original date is usually still inside the file.
- Expect low confidence on anything from a messaging app. WhatsApp and Messenger strip most metadata, so filenames and folders are often all that survives. The social apps guide covers what can still be recovered.
- Expect the scan date, not the photo’s date. A scan carries the day it went through the scanner. The scans and legacy media guide shows how to set an accurate approximate date across a batch.
- Check the export settings if dates are still missing. The Google Takeout and iCloud article covers the exact export options that keep the original date with the file.
- Review before you commit. Spot-check anything marked low-confidence and correct it where you know better than the file does.
- Write corrected copies. PDR writes corrected copies into a new output folder. Your originals stay exactly where they are, untouched, and duplicates are detected and skipped.
- Keep the clean library. Optionally let PDR write the corrected date back into the copy’s EXIF so other apps agree, then retire the messy originals once you are happy with the result.
Read the complete guide instead — every step and every warning in one sequence, including the parts your answers would filter out.
Why photo dates go wrong in the first place
A photo carries several different dates, and they drift apart surprisingly easily. The date you care about — when the picture was actually taken — is stored inside the file as EXIF metadata. The date Windows shows in Explorer is often the file’s modified or created date, which is a completely different thing and is rewritten constantly.
Common ways the visible date gets corrupted:
- Cloud exports rewrite file timestamps to the moment you downloaded them.
- Copying between drives or phones can reset created/modified dates to today.
- Messaging apps strip metadata, leaving only the send date.
- Scans of old prints get the date they were scanned, not the year in the photo.
- Editing software sometimes overwrites the original capture time on save.
Where PDR finds the true capture date
Photo Date Rescue does not guess. It looks at every reliable source a file can carry and scores its confidence in the result, so you always know how sure it is:
| Source | What it provides |
|---|---|
| EXIF metadata | The original “Date Taken” written by the camera or phone |
| Video metadata | Creation timestamps embedded in MOV, MP4 and similar files |
| Embedded XMP | The XMP block inside the file, which is what usually answers for HEIC and AVIF |
| Google Takeout JSON | The record Takeout ships beside each photo. This is the only export format whose own metadata PDR parses — a separate .xmp file is not read |
| Filename patterns | Names like IMG_20180714_153000 encode the date directly |
| Folder structure | Year and month folders give a strong hint when nothing else survives |
Each candidate is compared, and PDR chooses the most trustworthy one. When several sources agree, confidence is high; when only a folder name survives, PDR tells you the date is an estimate rather than presenting it as certain.
Repairing a whole library, step by step
The single most important thing to understand about PDR is that it never edits your originals in place. A repair always produces a fresh, correctly dated copy:
- Point PDR at your folder. Add the folder of photos with wrong dates on your Windows PC. Sub-folders are included automatically.
- Let PDR read each file. It works out the correct date from the sources above and assigns a confidence score to every photo.
- Review before you commit. Spot-check anything marked low-confidence — usually scans or metadata-stripped files — and adjust if you know better.
- Write corrected copies. PDR writes a corrected copy into a new output folder. Your originals stay exactly where they were, untouched. Duplicates are detected and skipped so the output stays lean.
- Keep the clean library. Optionally PDR writes the corrected date back into the copy’s EXIF, so every other app agrees. Review the result, then retire the messy originals once you are happy.
Special cases worth knowing
Google Takeout and iCloud
These exports need their JSON sidecars kept alongside the images. The dedicated Google Takeout & iCloud dates article and the in-depth cloud export guide cover the exact export settings.
Messaging and social apps
WhatsApp, Messenger and similar apps remove most metadata. The social apps guide explains what can still be recovered from filenames.
Scans and legacy media
For scanned prints, see the scans and legacy media guide for setting an accurate approximate date across a batch.
Common mistakes to avoid
- Editing originals directly with other tools. Once EXIF is overwritten, the true date can be lost. Let PDR work on copies.
- Separating photos from their
.jsonsidecars. In a Google Takeout export, the sidecar holds the real date — keep them together. - Trusting the Explorer “Date” column. It is the modified date, not the capture date.
- Running one giant repair before checking a sample. Do a small folder first to see the confidence scoring in action.
Try the repair for free
The free web demo is a proof of concept: it takes one ZIP file of up to 200 MB and nothing else, so you can see the confidence scoring before installing anything. Real libraries belong on the Windows desktop app, which handles tens of thousands of files in one pass, from folders, drives and archives together.
Try the free web demo Get the desktop appFrequently asked questions
Will PDR change or delete my original photos?
No. PDR writes corrected copies to a new output folder and never edits your originals in place. If you dislike the result, you can simply delete the output.
What if a photo has no metadata at all?
PDR falls back to filename patterns and folder structure, and clearly marks the date as an estimate with a lower confidence score so you can review it.
Can it fix video files too?
Yes. PDR reads creation timestamps embedded in MOV, MP4 and similar video files alongside your photos.
Does the corrected date show up in other apps?
If you let PDR write the date back into EXIF, other photo apps and Windows will read the corrected capture date too.