ISO 8601 to M/D/YYYY 24h converter
ISO 8601 UTC with milliseconds → US short date with 24-hour time
M/D/YYYY 24h · M/D/YYYY HH:mm:ss
The value's offset (UTC) is not carried into M/D/YYYY HH:mm:ss; the clock is written as it was.
Worked examples
| Instant | ISO 8601 | M/D/YYYY 24h |
|---|---|---|
| an ordinary afternoon | 2026-06-29T14:30:00.000Z | 6/29/2026 14:30:00 |
| a leap day | 2028-02-29T09:05:07.000Z | 2/29/2028 09:05:07 |
| the Unix epoch | 1970-01-01T00:00:00.000Z | 1/1/1970 00:00:00 |
What this conversion changes
- Dropped on the way out: milliseconds. The conversion is lossy; converting back will not restore them.
- 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 24h — US short date with 24-hour time
- Pattern
- M/D/YYYY HH:mm:ss
- Example
- 6/29/2024 00:00:00
- Seen in
- Spreadsheets, Point-of-sale exports
Related conversions
Thousands of values to convert?
CSV batch mode converts an entire column from ISO 8601 to M/D/YYYY 24h (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.