Most camera and phone photos record the moment they were taken in hidden EXIF metadata. But a photo carries several dates, and the one your computer shows first is usually the file date, which changes every time the photo is copied. Here's which date to trust and how to find it.
Most camera and phone photos do. When the shutter fires, the device writes the date and time into the file's EXIF metadata, a block of data you don't see when you look at the picture. The trouble is that a photo carries several dates, they mean different things, and the one your computer shows you first is often the wrong one.
| Date | What it records | Written by | How far to trust it |
|---|---|---|---|
| DateTimeOriginal (EXIF) | When the shutter fired | Camera or phone clock, local time, no time zone | Best single answer, if present |
| OffsetTimeOriginal (EXIF) | The time zone for that moment, like +11:00 | Phones and newer cameras | Turns local time into an exact moment |
| DateTimeDigitized (EXIF) | When the image became digital | Same as the original for cameras; scan date for scans | Useful for scanned prints |
| DateTime / ModifyDate (EXIF) | When a program last saved the file | Whatever app touched it last | An edit date, not a capture date |
| GPSDateStamp (EXIF) | Date from the GPS fix, in UTC | Phones with location on | Independent of the camera clock |
| File "created" and "modified" dates | When this copy landed on this disk | Your operating system | Changes on copy, download and sync |
| File name (IMG_20260115_…) | When the phone named the file | Many Android phones and some apps | Easy to rename, but a useful hint |
The one you want is DateTimeOriginal. Windows shows it as "Date taken" in file properties, and Apple Photos uses it to sort your library. Everything else is either a time zone, an edit date or a fact about the file rather than the photo.
Usually because you're looking at the file date, not the capture date. File dates belong to the copy on your disk and change constantly. In our test, copying a Canon EOS R6 photo with an ordinary file copy kept the EXIF capture date of April 4, 2022 untouched, but the copy's modified date became the moment it was copied. Downloads, cloud sync and messaging apps do the same.
We checked 228 unique JPEGs from our own working folders, mostly web graphics, project assets and downloaded photos, to see how often a real capture date survives:
| What we checked | Result |
|---|---|
| Unique JPEGs checked | 228 |
| With any EXIF at all | 25 (11%) |
| With DateTimeOriginal (true capture date) | 12 (5%) |
| With a time zone (OffsetTimeOriginal) | 7, all +10:00 or +11:00 |
| With a GPS date stamp | 0 |
| File modified date matched the capture date | 0 of 12; later by 142 days to 4 years 4 months |
Two things stand out. First, a real capture date is the exception for images that have been through the web, because social networks, messaging apps and many editors strip metadata. Second, even when the capture date was there, the file date never agreed with it. If something is sorting your photos by file date, that's why the order is wrong.
The other cause is the camera clock. DateTimeOriginal records whatever the clock said. A camera never set after a battery swap, or not changed when you crossed time zones, gives a confident and wrong date. The time zone tag, when present, helps; without it, a photo taken at 11:15 in Sydney and one at 11:15 in London look identical.
Not precisely, but you can narrow it down. A reverse image search finds the earliest place the image was posted, which gives you a date it existed by. Inside the picture, look at things with known dates: phone models, signage, cars, a building that went up or came down, the length of shadows for the time of day. Investigators combine these, and none of them is as good as the original file.
Yes, easily. EXIF dates are plain text in the file, and phones, photo apps and free tools can all edit them. That's handy for fixing a wrong camera clock, and it's why a capture date is evidence, not proof. If a date matters in a dispute, ask for the original file straight from the device, and compare the capture date with the GPS date and the edit date. When they disagree, see how to tell if a photo has been edited.
The reverse matters too. If you're sharing a photo and don't want it dated, re-saving it often strips the date along with everything else. In our test, re-saving that same Canon photo with a default script save left zero EXIF tags. To do it on purpose and check the result, use the image metadata remover, which also removes GPS. Location is the bigger privacy risk; see how to remove location from photos.
Read its EXIF DateTimeOriginal tag. On Windows it's Date taken under Properties, Details; on a Mac it's in Preview's inspector; on a phone, swipe up on the photo. An online EXIF viewer shows it for any file, along with the time zone if the camera saved one.
No. A file's created and modified dates record when that copy reached your disk, and they change on every download or copy. In our test, the file date matched the capture date in none of the 12 photos that had one.
Either you're seeing the file date instead of the capture date, or the camera clock was wrong when the photo was taken. Check DateTimeOriginal in an EXIF viewer; if that's wrong too, the clock was off and you can correct the date in your photo app.
Usually not in EXIF. Screenshots are often PNG files with no camera metadata, so the only date is the file date or a date in the file name. Phones record the time in their photo library, but it's often lost when the file is shared.
Only roughly. A reverse image search shows the earliest place it was posted online, and details in the picture such as phone models, signs or buildings can bracket the date. Neither gives an exact time.