What Is ISO 8601? International Date Format Standard
One-line definition: ISO 8601 is the international standard for writing dates and times as strings. The format is YYYY-MM-DDTHH:MM:SSZ. The Z means UTC. It eliminates the April-6-vs-June-4 ambiguity that plagues dates like 04/06.
What ISO 8601 Looks Like
ISO 8601 has several valid formats depending on how much detail you need:
2026-06-04Date only14:00:00Time only2026-06-04T14:00:00Date and time (no timezone)2026-06-04T14:00:00ZDate and time in UTC (Z = Zulu = UTC)2026-06-04T09:00:00-05:00Date and time with UTC offset (EST)2026-06-04T19:30:00+05:30Date and time in IST (UTC+5:30)Why ISO 8601 Exists
The problem ISO 8601 solves: date formats are not universal. “04/06/2026” means April 6 in the US and June 4 in the UK and most of Europe. “6/4/26” is ambiguous to anyone who doesn't know the sender's country. This causes genuine errors in international business, software, and data exchange.
ISO 8601 uses year-month-day order (YYYY-MM-DD) — always. “2026-06-04” is unambiguously June 4, 2026 regardless of locale. It's also sortable alphabetically: sorting ISO 8601 strings alphabetically automatically sorts them chronologically, which makes database indexing and log file sorting trivial.
The T Separator and the Z Suffix
In a full ISO 8601 datetime string, T separates the date from the time. It's not a word — just a delimiter.
The trailing Z stands for Zulu time — the NATO phonetic word for the letter Z, meaning UTC. A timestamp ending in Z is in UTC. A timestamp ending in +05:30 is 5 hours and 30 minutes ahead of UTC (IST).
A timestamp without Z or an offset is technically unspecified — it could be any timezone. This is a common source of bugs: a datetime stored in a database without a timezone is ambiguous unless you know what timezone the server was in when it wrote the value.
ISO 8601 vs Unix Time
ISO 8601 and Unix time solve the same problem differently. Unix time stores a moment as an integer (1780000000). ISO 8601 stores it as a human-readable string (2026-06-04T14:00:00Z). Both are timezone-aware — Unix time is always UTC; ISO 8601 includes the timezone in the string.
Best practice: store timestamps as Unix integers internally for efficiency, and convert to ISO 8601 strings at the display layer for human readability.
Frequently Asked Questions
What is the ISO 8601 date format?
The ISO 8601 date format is YYYY-MM-DD — year, then month, then day, separated by hyphens. For example: 2026-06-04. The full datetime format is YYYY-MM-DDTHH:MM:SSZ, where Z means UTC.
What does the Z mean in a timestamp?
Z stands for UTC (Zulu time). A timestamp ending in Z — like 2026-06-04T14:00:00Z — is in UTC. It's the unambiguous way to specify that a datetime is in Coordinated Universal Time.
Is ISO 8601 the same as UTC?
No — ISO 8601 is a format standard for representing dates and times as strings. UTC is a time standard. ISO 8601 can represent times in any timezone, including UTC. When a timestamp ends in Z, it's ISO 8601 format representing UTC time.
Why does ISO 8601 use hyphens in dates?
Hyphens make the components clearly separable and readable. The format YYYY-MM-DD avoids ambiguity between month and day ordering. The hyphens also allow ISO 8601 dates to sort correctly as strings — alphabetical order equals chronological order.