Skip to content

ISO 8601 to Long date converter

ISO 8601 UTC with milliseconds → Long date (December 13, 2023 at 12:24:03 PM)

Swap → Long date to ISO 8601

Long date · MMMM DD, YYYY at h:mm:ss A

June 29, 2024 at 12:00:00 AM

The value's offset (UTC) is not carried into MMMM DD, YYYY at h:mm:ss A; the clock is written as it was.

Worked examples

InstantISO 8601Long date
an ordinary afternoon2026-06-29T14:30:00.000ZJune 29, 2026 at 2:30:00 PM
a leap day2028-02-29T09:05:07.000ZFebruary 29, 2028 at 9:05:07 AM
the Unix epoch1970-01-01T00:00:00.000ZJanuary 1, 1970 at 12:00:00 AM

What this conversion changes

  • Dropped on the way out: milliseconds. The conversion is lossy; converting back will not restore them.
  • The 24-hour clock becomes a 12-hour clock with AM/PM; the clock change itself loses nothing.
  • The trailing "Z" (UTC marker) or offset of ISO 8601 is not carried into the target, which has no offset field: the clock is written as it appears in the value (for "Z", that is UTC), and the tool names the dropped offset.

ISO 8601 — ISO 8601 UTC with milliseconds

Pattern
YYYY-MM-DDTHH:mm:ss.SSSZ
Example
2024-06-29T00:00:00.000Z
Seen in
JSON APIs, JavaScript Date.toISOString(), Log files, MongoDB

Long date — Long date (December 13, 2023 at 12:24:03 PM)

Pattern
MMMM DD, YYYY at h:mm:ss A
Example
December 13, 2023 at 12:24:03 PM
Seen in
Apple Notes and Photos, Word processors, Printed documents

Thousands of values to convert?

CSV batch mode converts an entire column from ISO 8601 to Long date (or any of the 82 formats, with time-zone shifts), entirely in your browser, with no row limit set by us (your device's memory is the practical ceiling). $9.99/month, hides the ads, cancel anytime.