Right-clicking a photo and checking its file date rarely gives you the answer you want. That date tells you when the file was copied, downloaded or last edited — not when the picture was actually taken. The real capture time is stored separately, inside the photo itself.
This guide explains where that timestamp lives, how to read it, how accurate it is, and what to do when it is missing.
Every camera writes a field called DateTimeOriginal into the photo the moment the shutter fires. It records the date and time to the second. Any EXIF reader can show it — Photo Trace does so in your browser without uploading the file anywhere.
Your operating system shows three dates for a file: created, modified, and accessed. None of them describes the photograph. They describe the file.
Copy a photo from your phone to a laptop and the created date becomes today. Download it from a cloud backup and it becomes today. Edit it, even to straighten the horizon, and the modified date changes. A holiday photo from 2019 can show a file date of last Tuesday and nothing is wrong — the file genuinely arrived last Tuesday.
The capture time survives all of this, because it is written inside the image data rather than attached by the filesystem.
Photos carry a block of metadata called EXIF — Exchangeable Image File Format. Within it, three separate date fields can appear:
| Field | What it means |
|---|---|
| DateTimeOriginal | The moment the shutter fired. This is the one you want. |
| DateTimeDigitized | When the image was converted to a digital file. Identical to the above on a digital camera; different on a scanned film photograph. |
| DateTime | When the file was last modified by software. Changes if the photo is edited. |
Alongside these, many phones record SubSecTimeOriginal for fractions of a second, and OffsetTimeOriginal for the time zone. That last field matters more than it sounds — see below.
You do not need to install anything. A browser-based EXIF reader opens the file locally and shows the stored fields:
You can also select several photos at once and step through them, which is quicker than opening each one separately when you are dating a whole batch.
A camera records local time as it was set on the device, with no time zone attached by default. A photo taken at 9:58 PM in Bengaluru reads 9:58 PM wherever in the world you later view it.
Most modern phones additionally store the UTC offset, which tells you which zone the camera clock was set to. That matters when you are sorting photographs from a trip that crossed zones: without it, a flight can appear to arrive before it departed.
Where the offset is missing, it can often be worked out by comparing the local capture time against the GPS satellite clock, which is always in UTC. If a photo carries both, the difference between them is the offset.
The timestamp is exactly as accurate as the camera’s clock was at the moment of capture. Phones synchronise their clocks over the network, so they are generally correct to the second. Standalone cameras rely on a clock you set by hand, and those drift — minutes a month is common, and nobody adjusts them after a flight.
There is no way to detect this from the file. If a camera clock was an hour slow, the photo records the wrong hour and reports it with complete confidence. When a timestamp looks implausible, the camera clock is the usual explanation.
Some photos arrive with no capture time at all. The cause is almost always one of these:
| Cause | How to recognise it |
|---|---|
| Shared through a messaging app | WhatsApp, Instagram, Facebook and Telegram re-compress images and discard metadata. Filenames often contain the app name. |
| It is a screenshot | A screenshot records the screen, not a camera exposure. It carries only the moment the screenshot was taken, and no camera details. |
| The file was re-saved | Some editors and converters write a new file without copying the original metadata across. |
| It is a scan | A scanned print records when it was scanned. The original photograph’s date was never digital. |
In each case the information is gone from that copy rather than hidden. It cannot be recovered from the file, though the original may still have it — on the phone that took it, or in a cloud backup held at original quality.
When the timestamp is genuinely absent, other recorded details can still narrow the range. The camera make and model tell you which device took it, which bounds the date to the years you owned that camera. Exposure settings hint at conditions: a very slow shutter speed suggests low light, and therefore evening or indoors.
None of this is conclusive, but combined with what you remember it often pins a vague recollection to a specific occasion. Our guide on recovering old photo memories covers this in more depth.
EXIF dates can be edited. Software exists specifically to change them, and a modified timestamp leaves no obvious trace in the file. For casual purposes this does not matter. Where a date carries weight — an insurance claim, a legal matter, a disputed sequence of events — a metadata timestamp is supporting evidence rather than proof, and is strongest when corroborated by something independent.
Photo Trace reads the capture date, GPS location and camera settings entirely inside your browser. Nothing is uploaded, and nothing is stored.