Understand photo timezones before converting a stored date

Pair the offset with the correct date field

The EXIF date and its offset are stored separately. OffsetTime applies to DateTime, OffsetTimeOriginal to DateTimeOriginal, and OffsetTimeDigitized to DateTimeDigitized. Use the source/tag labels rather than borrowing the timezone from another field or from your computer. The linked CIPA table documents the paired UTC-offset fields; current Adobe XMP date documentation likewise keeps an omitted timezone unknown.

This reader supports full date-time values and the simple standard-XMP properties shown in its coverage. It is not a complete implementation of every EXIF/XMP date syntax or the whole current Exif standard. An offset is also not the name of a timezone region or a record of its historical daylight-saving rules.

• CIPA Exif/XMP date-field table, 2017 reference — Fixed primary-source definitions of OffsetTime and OffsetTimeOriginal as UTC offsets for their paired EXIF date fields. Later standards do not make every reader a complete implementation.
• Adobe XMP Date type — The current documentation allows an omitted timezone and says that its value then remains unknown.
• CIPA's current standards index — The index lists Exif 3.1, published in 2026. Our tools' listed format and field coverage remains narrower than the complete standard.

Compare the known and unknown cases

1. Step 1

   Read the explicit-offset case

   Open the date viewer and click Try explicit offsets. Original capture time has local 2020:01:02 10:20:30, subseconds 123456789 and +05:30. Subtract five hours and thirty minutes to obtain 2020-01-02T04:50:30.123456789Z.

   Open the photo date viewer

2. Step 2

   Load the same local time without an offset

   Click Try unknown timezone. The capture string and all subsecond digits remain, but offset displays Timezone unknown and UTC instant remains unknown. The browser's separate file-modification card can still have a UTC value; it is not used to fill the capture offset.

3. Step 3

   Check the real cross-date fixture

   Click Try UTC date crossing, or choose date-crossday.jpg. Its capture string is 2020:01:02 00:20:30, with +05:30 and subseconds 123456789. The UTC instant is 2020-01-01T18:50:30.123456789Z: the previous calendar day. Other recorded dates remain separate.

4. Step 4

   Keep raw and converted values together

   Use Download date JSON to retain the stored local text, offset, full subsecond digits and UTC interpretation. Avoid exporting only a rounded date label that hides whether the offset was known.

Expected interpretation table

• Download explicit offset — Known +05:30 conversion.
• Download unknown timezone — The local date is retained without an inferred instant.
• Download the cross-date example — Known +05:30 conversion moves capture to the preceding UTC day.

GPS UTC, conflicts and invalid values

GPS UTC date/time is a separately stored record. A GPS clock does not automatically supply an offset for another camera timestamp. Keep the source of each value, especially if their times differ.

Try conflicting dates illustrates a comparable ordering conflict when both dates have explicit offsets. Unknown offsets can prevent such comparisons, so the absence of a conflict message is not proof of a correct chronology. Invalid offsets, invalid calendar values and unreadable date fields are retained with warnings rather than being converted using the browser's local timezone.

For a real photo without a recorded offset, preserve the unknown state. An original camera log, separately documented workflow or a person with firsthand knowledge may supply context later; the file alone has not supplied it. This tool does not alter the image or write a guessed timezone back into it.

Sources and reproducible inputs

• Adobe XMP Date type — The current documentation allows an omitted timezone and says that its value then remains unknown.
• CIPA Exif/XMP date-field table, 2017 reference — Fixed primary-source definitions of OffsetTime and OffsetTimeOriginal as UTC offsets for their paired EXIF date fields. Later standards do not make every reader a complete implementation.
• Download the self-authored camera example — A 240 × 160 labeled corner chart, invented EXIF dates and a separately encoded 48 × 32 purple thumbnail. Camera fixtures v1; not a camera photograph.