Free tool
Paste a date in any common format. We auto-detect it, flag the confidence, and render 14 equivalent representations — ISO 8601, RFC 3339, Unix epoch, SQL, Python, Go, .NET, and more — each with a one-click copy button.
2026-06-20T03:30:06.506Z2026-06-202026-06-20T03:30:06.506+00:00Sat, 20 Jun 2026 03:30:06 +0000Sat, 20 Jun 2026 03:30:06 GMT2026-06-20 03:30:0617819262061781926206506Sat Jun 20 2026 03:30:06 GMT+0000 (Coordinated Universal Time')2026-06-20T03:30:06.506Z2026-06-20 03:30:06+00:002026-06-20 03:30:06 +0000 UTC2026-06-20T03:30:06.5060000ZSaturday, 20 June 2026 at 03:30 UTCjust nowSat 20 Jun 2026, 03:30:06 (Z)Written as 03/04/2026, that string means March 4th to an American reader and the 4th of March to most of the rest of the world — wait, no: it means April 3rd in Europe. That confusion is exactly the point. The US convention is month-first (M/D/Y), while Europe, most of Asia, and the ISO world put the day first (D/M/Y). The same eight digits land you on two calendar days a month apart. When our detector sees a slashed date where both numbers are 12 or below, it cannot know which you meant, so it flags the input as ambiguous and gives you a toggle to choose. Pick the interpretation and every output below updates to match.
People treat ISO 8601 and RFC 3339 as the same thing, and 95% of the time they overlap. The bites come from the edges. ISO 8601 allows a bare date with no time, a date with no offset, week dates like 2026-W22, and the literal Z or a numeric offset. RFC 3339 is a strict profile: it requires a full date and time, demands an offset (either Z or +00:00), and forbids the looser ISO forms. If you emit 2026-05-29T14:30:00 with no offset, that is valid ISO 8601 but invalid RFC 3339, and a strict parser will reject it. When in doubt, always include the offset.
The same instant has a different idiomatic string in every ecosystem. JavaScript hands you toISOString() and a chatty toString(); Python leans on strftime directives; Go uses its famous reference layout 2006-01-02 15:04:05; .NET has the round-trip o specifier; SQL wants YYYY-MM-DD HH:MM:SS; and HTTP headers follow RFC 7231's GMT-stamped form. Seeing them stacked makes it obvious which one to paste into your code, your database, or your curl command. If you also need to move an instant between cities, the time zone converter does the offset maths for you.