Date Time Converter

Dates travel between systems in many formats: ISO 8601 in JSON APIs, Unix timestamps in databases and logs, RFC 2822 in email headers and HTTP, and localized strings in user interfaces. This converter accepts a date in one format and shows it in all the others, which is invaluable when debugging logs, APIs and time zone issues.

How to use it

1. Paste or type a date in any supported format, or use the current time.
2. Choose the input format if it is not detected automatically.
3. Copy the representation you need.

Common formats for the same moment

• ISO 8601: 2026-10-27T09:30:00.000Z
• Unix timestamp (seconds): 1793093400
• Unix timestamp (milliseconds): 1793093400000
• RFC 2822 / HTTP date: Tue, 27 Oct 2026 09:30:00 GMT
• Local time (India): 27 Oct 2026, 15:00 IST (UTC+5:30)

Which format should I use?

• APIs and JSON: ISO 8601 in UTC with a Z suffix or an explicit offset. It is unambiguous, sortable as text and supported by every language.
• Databases: native timestamp types in UTC. Use timestamptz in PostgreSQL.
• Display: convert to the user's local time and locale only at the edge, in the UI.

Common bugs

• Seconds vs. milliseconds: JavaScript uses milliseconds; most Unix tools use seconds. A date in 1970 or the year 55,000 usually means a unit mix-up.
• Missing offset: 2026-10-27T09:30:00 without Z or an offset is interpreted as local time in some parsers and UTC in others.
• Ambiguous formats: 03/04/2026 is March 4 in the US and 3 April in most other countries.