Unix Timestamp (Epoch) Converter
Convert a Unix timestamp to a readable date, or a date to its timestamp, instantly. Includes a live-updating current timestamp, automatic detection between seconds and milliseconds, local or UTC timezone, ISO 8601 format, and relative time ("2 hours ago"). Everything is computed locally in your browser.
Current timestamp
Timestamp → Date
Enter a valid numeric timestamp.
Date → Timestamp
Frequently asked questions
What is a Unix timestamp (epoch)?
It's the number of seconds elapsed since midnight UTC on January 1st, 1970 (the "Unix epoch"), not counting leap seconds. It's the most common way to represent a single instant in time in databases, APIs and programming languages, because it's one plain integer, with no timezone or format ambiguity.
How do I know if a timestamp is in seconds or milliseconds?
By its digit count: a seconds-based timestamp for a present-day date has 10 digits (e.g. 1785628800), while a milliseconds-based one has 13 (e.g. 1785628800000). This tool detects it automatically from the number's length, but you can force the unit manually if needed.
What is the "Year 2038 problem"?
Many older systems store the Unix timestamp as a signed 32-bit integer, which runs out of range on January 19th, 2038 at 03:14:07 UTC — after that moment the number overflows and can turn negative, producing incorrect dates (typically landing in 1901). Modern systems use 64 bits and aren't affected, but it's still relevant for legacy code and some embedded systems.
Is my date or time uploaded to a server?
No. Every conversion uses JavaScript's native Date object and is computed entirely in your browser. Nothing is ever sent to a server.
Why doesn't local time match UTC?
A Unix timestamp always represents the exact same instant everywhere in the world, but each timezone displays it with a different clock time (and some also shift for daylight saving). "Local" uses your device's configured timezone; "UTC" is the reference time with no offset applied.