Unix time ↔ human time
Live epoch clock, both conversion directions, and automatic seconds-vs-milliseconds detection — the bug this page exists to catch.
Current Unix time: …
Every timestamp bug is one of three bugs
Seconds fed as milliseconds (your log says 1970), milliseconds fed as seconds (your log says the year 56246), or a time zone applied twice. The first two are magnitude errors this converter detects and labels; the third is why it always shows UTC and your local time side by side, so you can see exactly which one your data meant. All arithmetic — including the live clock — runs off your own device.
Related text tools
Frequently asked questions
How do I convert a Unix timestamp to a date?
Paste the number into the left box — the date appears instantly in UTC and your local time zone. The other direction works too: pick a date on the right and read off the epoch seconds and milliseconds.
Why does my timestamp show a date in the year 56000-something?
You fed milliseconds to something expecting seconds. JavaScript timestamps are milliseconds (13 digits today); Unix convention is seconds (10 digits). This converter detects 13-digit input and says explicitly that it read it as milliseconds.
What is Unix time exactly?
The count of seconds since 1970-01-01 00:00:00 UTC, ignoring leap seconds. It is time-zone-free by definition — the same instant is the same number everywhere — which is why systems exchange timestamps instead of date strings.
What was the year 2038 problem?
Signed 32-bit counters overflow on 2038-01-19. Modern systems moved to 64-bit long ago, so it survives mostly in embedded devices and as an interview question — good history, rarely your bug.
Does the current-time display need a server?
No — your own device’s clock drives everything on this page. Nothing is fetched and nothing you convert is sent anywhere.