ISO 8601 is the international standard for representing dates and times in a way that is unambiguous across languages, regions, and systems. It looks like this:
2026-03-10T14:30:00Z
Most people who encounter this format in a log file, an API response, or a system notification can read it, but may not know what every component means or how to use it reliably. This guide covers each component.
Breaking down the format
2026 — the four-digit year. Always four digits in ISO 8601, which avoids the Y2K-style ambiguity of two-digit years.
03 — the month, zero-padded to two digits. March.
10 — the day of the month, zero-padded. The 10th.
T — a literal separator character indicating that what follows is a time component. It stands for nothing meaningful — it is simply a delimiter.
14 — the hour in 24-hour format. 14:00 is 2pm.
30 — the minutes.
00 — the seconds.
Z — the timezone designator. Z stands for Zulu time, which is the military designation for UTC+0. A timestamp ending in Z is in UTC.
The full timestamp 2026-03-10T14:30:00Z means: 10 March 2026 at 14:30:00 UTC.
Timezone offsets in ISO 8601
Instead of Z, a timestamp may include an explicit offset:
2026-03-10T14:30:00+05:30
This means the same moment in time expressed in a timezone that is 5 hours and 30 minutes ahead of UTC — India Standard Time. To convert to UTC, subtract the offset: 14:30 minus 5:30 equals 09:00 UTC on the same date.
2026-03-10T09:30:00-05:00
This is UTC−5 (Eastern Standard Time in the US). To convert to UTC, add 5 hours: 09:30 plus 5:00 equals 14:30 UTC — the same moment as both examples above.
What ISO 8601 does not tell you
An ISO 8601 timestamp with a Z or explicit offset is unambiguous about the moment in time it represents. It does not tell you the name of the timezone, whether DST is currently active, or what the local date is in regions where the timestamp crosses midnight. For those questions, the offset must be resolved against a timezone database.
Why it matters
ISO 8601 is the format to use when precision is required. API responses, log files, database records, and any time value that will be processed by software should use ISO 8601 with an explicit offset or Z. Human-written communication should include an ISO timestamp as a canonical reference alongside the human-readable version whenever the stakes are high.