Runs locally in your browser. Nothing you enter is uploaded to our servers.
Tips for Unix time
Confirm seconds vs milliseconds before converting.
Display in UTC and local time when debugging.
Leap seconds and DST do not change Unix seconds the way calendars do.
Store timestamps in UTC in databases and APIs.
Watch 32-bit overflow (year 2038) on legacy systems.
Seconds (or ms) since 1970-01-01 UTC
Processing stays in your browser — your input is not uploaded to our servers.
Unix time is an integer timestamp. This converter switches between epoch values and readable UTC/local calendar dates.
APIs disagree on seconds versus milliseconds. A value around 1e12 is usually ms; around 1e9 is seconds.
Convert Unix time
Paste a timestamp or pick a date
Keep track of whether the source used seconds or milliseconds.
Read UTC and local
Logs in UTC plus a local display prevent “it failed yesterday” arguments.
Copy the integer back
Match the precision the API documents, or you will be off by 1000×.
Unix time FAQ
Leap seconds?
Unix time ignores leap seconds. For civil time around leaps, use a proper timezone library.
Why is my date in 1970 or 5000?
Seconds/ms mix-up. Divide or multiply by 1000 and try again.
Is conversion local?
Yes. No server clock is queried.