Skip to content

ISO 8601 to DD.MM.YYYY 24h converter

ISO 8601 UTC with milliseconds → European date-time (DD.MM.YYYY, HH:mm:ss)

DD.MM.YYYY 24h · DD.MM.YYYY, HH:mm:ss

29.06.2024, 00:00:00

The value's offset (UTC) is not carried into DD.MM.YYYY, HH:mm:ss; the clock is written as it was.

Worked examples

InstantISO 8601DD.MM.YYYY 24h
an ordinary afternoon2026-06-29T14:30:00.000Z29.06.2026, 14:30:00
a leap day2028-02-29T09:05:07.000Z29.02.2028, 09:05:07
the Unix epoch1970-01-01T00:00:00.000Z01.01.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

DD.MM.YYYY 24h — European date-time (DD.MM.YYYY, HH:mm:ss)

Pattern
DD.MM.YYYY, HH:mm:ss
Example
15.05.2024, 21:11:29
Seen in
German, Russian and Nordic locales, SAP exports, European banking CSVs

Thousands of values to convert?

CSV batch mode converts an entire column from ISO 8601 to DD.MM.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.