Date Converter
Converts a date between many formats — Unix timestamps, ISO 8601, RFC 3339, RFC 7231, UTC, locale strings, Excel serial numbers and Mongo ObjectIDs.
Convert between date formats online — ISO 8601, RFC 3339, UTC, locale, Excel, Mongo ObjectID and Unix timestamps.
Steps and notes
What is Date Converter — Formats, Time Zones and ISO 8601?
Date format tokens are a minefield because the letters lie: YYYY, YY, MM, M, DD, dd, HH, hh, mm, ss each mean something specific, and two of them are the classic traps. YYYY is the ISO week-numbering year — for a handful of days around New Year it differs from the calendar year, which is why a Dec-31 date printed with YYYY can show the wrong year in strict ISO contexts. HH is 24-hour, hh is 12-hour, and forgetting the case distinction produces "14:00" as an invalid 12-hour time or "02:00 PM" when you meant 14:00. This converter works with the ISO 8601 family — the formats machines exchange — and shows how the same instant renders across common patterns (YYYY-MM-DD, DD/MM/YYYY, MM/DD/YYYY, RFC-style with weekday and timezone). The DD/MM versus MM/DD collision remains the most destructive ambiguity in international data: 01/02/2026 is two different dates depending on who typed it, and no format string can fix that — only unambiguous YYYY-MM-DD can. When two systems disagree about a date, the disagreement is almost always one of these: token case, week-year boundary, or a missing UTC offset on what was assumed to be local time.
- Use the current time or enter one manually
- Read the Unix timestamp and the formatted results
- Note whether you need seconds or milliseconds
- Unix timestamps are usually seconds (10 digits), while JavaScript Date.now() is milliseconds (13 digits)
Frequently asked questions
- What is the difference between YYYY and yyyy?
- YYYY is the ISO week-numbering year; yyyy is the normal calendar year. Around New Year, a few days belong to the previous or next week-year, so YYYY can print a different number.
- Why does 01/02/2026 cause bugs in international teams?
- It is 1 February in day-first convention and 2 January in month-first convention. No format string resolves intent — only switching to ISO YYYY-MM-DD removes the ambiguity.
- What does the Z or +08:00 suffix mean?
- It is the UTC offset. A date without one is a wall-clock reading, not an instant; systems exchanging data should always carry the offset or convert to Zulu time.
- Why did my parsed date shift by a day?
- Classic cause: parsing a local-time string as UTC (or back) crosses a day boundary. Check whether the offset was assumed or explicit at both ends.
Category: Converter
JWT tools workflow
JWT Decoder & Parser — Inspect Header, Payload and Expiration → Base64 Encoder & Decoder — Padding, URL-Safe, Binary-Safe → Date Converter — Formats, Time Zones and ISO 8601 → Unix Timestamp Converter — Epoch to Date, Seconds vs Milliseconds