--:--:--

Convertisseur ISO 8601

Convertissez dates et horodatages en chaînes conformes à la norme ISO 8601.

Parse an ISO 8601 string

Accepted: date-only · T separator · optional seconds and fraction · Z or ±HH:MM offsets.

Build an ISO string

Comment ça marche

  1. ISO 8601 writes one moment as YYYY-MM-DDTHH:MM:SS plus an optional fraction and offset; Z means UTC, and +05:30 means local time 5 h 30 m ahead of UTC.
  2. Parsing: strings with an offset identify one exact instant; the tool normalizes them to UTC, shows the Unix timestamps, and renders the instant in UTC and your local zone.
  3. Building: your date, time and zone are resolved to an instant (daylight saving included), then emitted with that zone’s offset, plus the UTC (Z) form and Unix seconds for cross-checking.

Bon à savoir

  • Offset-less strings (2026-10-28T14:30:00) are shown as written with both the UTC and your-zone interpretations, never silently assumed to be one or the other.
  • Date-only strings (2026-10-28) are reported as dates; the implied midnight zone differs across systems, which the tool states rather than guessing.
  • RFC 3339 is the internet profile of ISO 8601 that APIs actually use; strings like 2026-10-28T14:30:00Z satisfy both standards.
Outils d’horodatageEn vedette

Convertisseur d’horodatage Unix

Convertissez les timestamps Unix en dates lisibles et les dates en horodatages en secondes ou millisecondes.

Ouvrir l’outil
Outils d’horodatage

Horodatage Unix vers date

Convertissez des horodatages numériques en dates claires avec affichage UTC et local.

Ouvrir l’outil
Outils d’horodatage

Date vers horodatage Unix

Transformez n’importe quelle date et heure en secondes et millisecondes d’époque.

Ouvrir l’outil
Outils d’horodatage

Convertisseur d’horodatage UTC

Convertissez les timestamps directement en dates et heures au format UTC pur.

Ouvrir l’outil

Foire aux questions

What does the “Z” in an ISO string mean?
Zulu, meaning the string refers to UTC. 2026-10-28T14:30:00Z is 14:30 UTC. A string with +02:00 instead describes local time two hours ahead of UTC; both denote a precise instant.
What if my ISO string has no offset at all?
Then it is ambiguous: 14:30 somewhere, but where? The tool shows it as written and explains that an offset (or Z) is required to pin down an instant, rather than silently assuming one.
Is ISO 8601 the same as RFC 3339?
RFC 3339 is an internet profile of ISO 8601, representing a subset with a fixed layout. Strings like 2026-10-28T14:30:00Z satisfy both specifications.