Skip to content

ISO 8601 to M/D/YYYY h:mm A converter

ISO 8601 UTC with milliseconds → US date with 12-hour time, no seconds

M/D/YYYY h:mm A · M/D/YYYY h:mm A

6/29/2024 12:00 AM

The value's offset (UTC) is not carried into M/D/YYYY h:mm A; the clock is written as it was.

Worked examples

InstantISO 8601M/D/YYYY h:mm A
an ordinary afternoon2026-06-29T14:30:00.000Z6/29/2026 2:30 PM
a leap day2028-02-29T09:05:07.000Z2/29/2028 9:05 AM
the Unix epoch1970-01-01T00:00:00.000Z1/1/1970 12:00 AM

What this conversion changes

  • Dropped on the way out: seconds, 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

M/D/YYYY h:mm A — US date with 12-hour time, no seconds

Pattern
M/D/YYYY h:mm A
Example
6/29/2024 2:30 PM
Seen in
Calendar exports, Chat logs

Thousands of values to convert?

CSV batch mode converts an entire column from ISO 8601 to M/D/YYYY h:mm A (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.