Skip to content

ISO 8601 — ISO 8601 UTC with milliseconds

Pattern YYYY-MM-DDTHH:mm:ss.SSSZ · e.g. 2024-06-29T00:00:00.000Z

About this format

Fields
Year, Month, Day, Hour, Min, Sec, Ms
Clock
24-hour
Carries a time zone
Yes (the trailing Z means UTC)
Typically seen in
JSON APIs, JavaScript Date.toISOString(), Log files, MongoDB

Sample values

  • 2026-06-29T14:30:00.000Z
  • 2028-02-29T09:05:07.000Z
  • 1970-01-01T00:00:00.000Z

Read the full guide

Rules and pitfalls

  • The basic format, written without hyphens or colons (20260615T184510Z, 20260615T1845Z, 20260615T184510.123Z, 20260615T184510+0530), is read as the same instant; results are always written in the extended form shown above. A basic date-time is not combined with an extended offset or time (20260615T184510+05:30 and 20260615T18:45:10Z are refused); an extended date-time with a ±hhmm offset, such as 2026-06-15T18:45:10+0530, is read, as it always was.
  • A date alone in the basic form (20260615) is the YYYYMMDD format, not this one. Week dates (2026-W25-1) and ordinal dates (2026-166) are not read in either form.

Try it: ISO 8601 to Unix timestamp

Unix timestamp · Unix Timestamp (sec)

1719619200

Convert ISO 8601 to…

Convert to ISO 8601 from…