ISO 8601 to ISO 8601 (local, ms) converter
ISO 8601 UTC with milliseconds → ISO 8601 local date-time with milliseconds (no offset)
ISO 8601 (local, ms) · YYYY-MM-DDTHH:mm:ss.SSS
The value's offset (UTC) is not carried into YYYY-MM-DDTHH:mm:ss.SSS; the clock is written as it was.
Worked examples
| Instant | ISO 8601 | ISO 8601 (local, ms) |
|---|---|---|
| an ordinary afternoon | 2026-06-29T14:30:00.000Z | 2026-06-29T14:30:00.000 |
| a leap day | 2028-02-29T09:05:07.000Z | 2028-02-29T09:05:07.000 |
| the Unix epoch | 1970-01-01T00:00:00.000Z | 1970-01-01T00:00:00.000 |
What this conversion changes
- 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
ISO 8601 (local, ms) — ISO 8601 local date-time with milliseconds (no offset)
- Pattern
- YYYY-MM-DDTHH:mm:ss.SSS
- Example
- 2024-06-29T00:00:00.500
- Seen in
- SQL Server datetime2 exports, Application logs, JavaScript Date without the Z
Related conversions
Thousands of values to convert?
CSV batch mode converts an entire column from ISO 8601 to ISO 8601 (local, ms) (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.