Why is the date on my photo wrong, and how do I fix it?
Short answer: the date you see is read from a hidden field in the photo file (EXIF DateTimeOriginal), and that field is wrong, missing or being read in the wrong time zone. The usual causes: a phone or camera clock not set to automatic, a trip across time zones, a scanned, screenshotted or messaged photo with no original date, or a dead camera clock battery. The Exif standard stored the time with no time zone until an offset tag arrived in 2016, so older files are open to interpretation.
To fix it: set the clock to automatic, check the photo's info, and correct the date in Google Photos or Apple Photos if needed. Some of those corrections change what your library shows, not what the exported file says.
Where does the date on a photo come from?
A camera writes the moment the shutter fired into the file as the EXIF tag DateTimeOriginal, in the form YYYY:MM:DD HH:MM:SS. In the CIPA Exif 2.31 standard that definition says nothing about a time zone. Three offset tags, OffsetTime, OffsetTimeOriginal and OffsetTimeDigitized, store the difference from UTC as ±HH:MM; the revision history lists them as added in version 2.31 (2016). A photo from an older camera, or from an app that never wrote them, carries a wall-clock time with no zone.
Windows reads the same tag: Microsoft documents the property behind "Date taken", System.Photo.DateTaken, as "read from the camera in the file's Exchangeable Image File (EXIF) tag", property ID 36867. If the tag is empty there is no "Date taken", only the file's created and modified dates, which can change when the file is copied or saved again.
Which of six causes is yours?
1. The time has no time zone. A photo stamped 14:30 with no offset tag is 14:30 somewhere. Your phone may show 14:30; a desktop program may assume UTC or your current zone and show 09:30 or 19:30. Nothing is corrupted; two programs are guessing differently.
2. The phone clock is set by hand. With automatic time off, the camera writes whatever the clock says. The settings are named in step 3 below.
3. You traveled. The camera wrote local time. Back home, the gallery either keeps that time or shifts it to your home zone, depending on the app, not the file.
4. The photo was imported, scanned or screenshotted. These tools create a new file. If they do not write DateTimeOriginal, the gallery falls back to the date the file was saved: the import date.
5. It came through a messaging app or a social network. Many services re-encode images and drop the metadata. The IPTC standards body tested the big platforms in 2019 and found that Twitter stripped metadata from saved files and that Facebook removed all EXIF but a few rights fields. A photo that arrives with no EXIF date gets filed under the moment it was received. The guide on what happens to a timestamp when you text a photo goes channel by channel.
6. The camera's clock battery died. Canon's EOS-1D X manual says the date/time battery "maintains the camera's date and time", is a CR2025 cell lasting about five years, and that a date and time reset at power-on means it needs replacing. Canon's EOS M10 page says the Date/Time screen then appears at every power-on until you set it again. Photos taken in between carry whatever the reset clock says.
Symptom, likely cause, fix
| What you see | Likely cause | Fix |
|---|---|---|
| Phone and computer show the same photo hours apart | No OffsetTimeOriginal tag; each program assumes a zone | Note the zone; adjust in Photos if order matters |
| Every recent photo is off by the same minutes or hours | Clock set by hand and drifting | Turn on automatic date, time and time zone |
| Photos from a trip sit on the wrong day | Local time written, viewed in home zone | Batch-adjust the dates in Google Photos or Apple Photos |
| Scans, screenshots or saved images all show the import day | No EXIF date in the file | Set the date by hand in your photo app |
| A photo someone sent shows the day you received it | Messaging app stripped EXIF | Ask for the original as a file; set the date by hand |
| Camera asks for date and time at every power-on | Dead backup battery | Replace or recharge it, then set date, time and zone |
How do I check and correct the date?
- Look at the file's own date. iPhone: open the photo, swipe up or tap the Info button; Apple's guide says you see "the date and time the photo or video was taken". Android: in Google Photos, tap More, then About, or swipe up. Windows: right-click the file, Properties, Details tab, "Date taken". Mac: in Photos, select the photo and press Command-I for the Info window.
- Decide what is wrong. EXIF right, gallery wrong: time zone (cause 1 or 3). EXIF wrong: clock (cause 2 or 6). No EXIF date: cause 4 or 5.
- Set the clock to automatic. Android (Google's Pixel help): Clock app, More, Settings, "Change date and time", switch on "Automatic date and time" and "Automatic time zone". iPhone: Settings, General, Date & Time, "Set Automatically". If it is still wrong, Apple says to switch automatic off and pick a city or set the date yourself.
- Correct a photo in Google Photos. Open it, tap More, About, then Edit next to the date, choose new values, tap Save. Google's page says this works only for backed-up photos, that the app then displays the new date, and that a shared or downloaded copy "may show the original date and time saved by your camera".
- Correct a photo on iPhone or Mac. iPhone: tap More, Adjust Info, Adjust Date & Time, set the calendar and clock, tap Adjust; use Select to do several at once; the same menu has Revert. Mac: Image, Adjust Date and Time, which also has a time zone map, the one place in these tools that fixes the zone rather than the clock reading.
- Fix the camera. If it asks for the date at power-on, replace or recharge the backup battery per the manual, then set date, time and home zone.
Why does a date printed into the photo avoid most of this?
Everything above concerns a hidden field that programs read differently and that disappears on re-encoding. A date drawn into the pixels is different: the reader sees it without opening file properties, and it survives texting, uploading, screenshots and pasting into a PDF. For photos you already have, the Android guide to stamping existing photos explains how a stamp can be drawn from the file's EXIF.
Be clear about what a stamp is not. It is pixels, and pixels can be edited, just as EXIF can. A printed "14:30" is only as good as the clock behind it. What a stamp can honestly do is say where each value came from: GPS, a map lookup, a phone clock checked or not checked against a time server, the photo file itself, or something you typed. An app like Asof prints that source next to each value and flags a clock that disagrees with the time server. That tells the reader how much to trust the number; it does not settle whether the number is true.
Questions people ask
Why does the same photo show two different times on my phone and my computer?
The time inside the file has no time zone unless the camera wrote the OffsetTimeOriginal tag, which the Exif standard only added in version 2.31 (2016). Each app then guesses a zone: your phone may show the time where you took the photo, your computer may assume its own zone. Two programs read the same numbers differently.
If I change the date in Google Photos or Apple Photos, is the file fixed?
Not always. Google's help page says Google Photos displays the new date, but a photo shared to other apps or downloaded "may show the original date and time saved by your camera", and the change is only available for backed-up photos. Apple's iPhone guide describes Adjust Date & Time and a Revert option, and does not say whether an exported copy changes. Treat these as fixes for your library and check the exported file before you rely on it.
Is a timestamp camera app safe to use?
It depends on the app, so read its privacy policy and the privacy section of its store listing, and check whether photos stay on the device, whether an account is needed, and where the time comes from. If the app prints the phone's clock and the clock is wrong, the stamp is wrong, and the fix is the same Date & Time setting. A printed date is visible and survives sharing, but it is pixels and can be edited, so it does not settle whether the date is true.