ISO 8601 to HH:mm MM/DD/YYYY converter
ISO 8601 UTC with milliseconds → Time-first US date (HH:mm MM/DD/YYYY)
HH:mm MM/DD/YYYY · HH:mm MM/DD/YYYY
The value's offset (UTC) is not carried into HH:mm MM/DD/YYYY; the clock is written as it was.
Worked examples
| Instant | ISO 8601 | HH:mm MM/DD/YYYY |
|---|---|---|
| an ordinary afternoon | 2026-06-29T14:30:00.000Z | 14:30 06/29/2026 |
| a leap day | 2028-02-29T09:05:07.000Z | 09:05 02/29/2028 |
| the Unix epoch | 1970-01-01T00:00:00.000Z | 00:00 01/01/1970 |
What this conversion changes
- Dropped on the way out: seconds, 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
HH:mm MM/DD/YYYY — Time-first US date (HH:mm MM/DD/YYYY)
- Pattern
- HH:mm MM/DD/YYYY
- Example
- 10:27 07/01/2025
- Seen in
- Some scheduling and telecom exports
Related conversions
Thousands of values to convert?
CSV batch mode converts an entire column from ISO 8601 to HH:mm MM/DD/YYYY (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.