Unix Timestamp Converter
Epoch to human and back: paste a Unix timestamp (seconds or milliseconds — detected automatically) to read it in UTC and your local time, or turn a UTC date into its timestamp.
Timestamp conversion
Example: 1767225600 = 2026-01-01 00:00 UTC.
One instant, three representations
The worked example — 1767225600 — is 2026-01-01 00:00 UTC, which is also
1767225600000 in milliseconds and whatever your local clock shows for that same instant.
Nothing about the instant changes between representations; only the formatting does. That is the
mental model that makes timestamp debugging easy: convert to the integer, compare integers, and
only format for humans at the very end.
Frequently asked questions
What is a Unix timestamp?
The number of seconds elapsed since 00:00:00 UTC on January 1, 1970 (the "epoch"), ignoring leap seconds. It is the lingua franca of computing time: databases, APIs, and logs store instants as one unambiguous integer instead of a formatted date in some zone.
Seconds or milliseconds — how does the auto-detection work?
By magnitude. Second-timestamps for current dates have 10 digits (about 1.7 billion); millisecond-timestamps have 13. Values of a trillion or more are treated as milliseconds. The result always states which interpretation was used, and shows both forms.
Is a timestamp in my time zone?
No — that is its superpower. A Unix timestamp has no zone; it is the same instant everywhere. Zones only enter when you FORMAT it for humans, which is why this converter shows the result in UTC and in your local time separately.
What about the year-2038 problem?
Systems storing timestamps in signed 32-bit integers overflow on January 19, 2038. Modern systems use 64-bit values and are fine for hundreds of billions of years. This converter handles dates from 1900 to 2200 — comfortably past the overflow date.
Conversions are computed locally in your browser; nothing you enter is transmitted. Timestamps ignore leap seconds by definition (Unix time convention). See the methodology page.