ISO 8601 to SQL datetime converter
ISO 8601 UTC with milliseconds → SQL datetime (YYYY-MM-DD HH:mm:ss)
SQL datetime · YYYY-MM-DD HH:mm:ss
The value's offset (UTC) is not carried into YYYY-MM-DD HH:mm:ss; the clock is written as it was.
Worked examples
| Instant | ISO 8601 | SQL datetime |
|---|---|---|
| an ordinary afternoon | 2026-06-29T14:30:00.000Z | 2026-06-29 14:30:00 |
| a leap day | 2028-02-29T09:05:07.000Z | 2028-02-29 09:05:07 |
| the Unix epoch | 1970-01-01T00:00:00.000Z | 1970-01-01 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
SQL datetime — SQL datetime (YYYY-MM-DD HH:mm:ss)
- Pattern
- YYYY-MM-DD HH:mm:ss
- Example
- 2022-06-29 13:45:31
- Seen in
- MySQL DATETIME, PostgreSQL timestamp, SQLite, CSV exports from databases
Related conversions
Thousands of values to convert?
CSV batch mode converts an entire column from ISO 8601 to SQL datetime (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.