ISO 8601 to Mon DD, YYYY 12h converter
ISO 8601 UTC with milliseconds → Abbreviated month date-time (Oct 29, 2024, 12:00:00 AM)
Mon DD, YYYY 12h · MMM DD, YYYY, h:mm:ss A
The value's offset (UTC) is not carried into MMM DD, YYYY, h:mm:ss A; the clock is written as it was.
Worked examples
| Instant | ISO 8601 | Mon DD, YYYY 12h |
|---|---|---|
| an ordinary afternoon | 2026-06-29T14:30:00.000Z | Jun 29, 2026, 2:30:00 PM |
| a leap day | 2028-02-29T09:05:07.000Z | Feb 29, 2028, 9:05:07 AM |
| the Unix epoch | 1970-01-01T00:00:00.000Z | Jan 01, 1970, 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
Mon DD, YYYY 12h — Abbreviated month date-time (Oct 29, 2024, 12:00:00 AM)
- Pattern
- MMM DD, YYYY, h:mm:ss A
- Example
- Oct 29, 2024, 12:00:00 AM
- Seen in
- macOS Finder, Google Sheets default, Browser history exports
Related conversions
Thousands of values to convert?
CSV batch mode converts an entire column from ISO 8601 to Mon DD, YYYY 12h (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.