How to convert a Unix timestamp
Logs, databases, and API responses love Unix timestamps — bare numbers
like 1700000000 that mean nothing to a human until you
convert them. This guide explains what the number is, the one mistake
that makes dates come out wrong, and how to convert either direction with
the free Timestamp Converter.
The fastest way
Paste the number into the Timestamp Converter to get a readable date, or enter a date to get the timestamp back. Read on for the gotcha that catches almost everyone.
What the number means
A Unix timestamp counts the seconds since midnight UTC on 1 January 1970 — the "Unix epoch." It's a compact, time-zone-free way to pin down an exact instant, which is why systems store it instead of a formatted string.
The seconds-vs-milliseconds trap
This is behind nearly every "my date is wrong" problem:
- A timestamp in seconds for today is 10 digits.
- A timestamp in milliseconds is 13 digits (1000× bigger).
If a 13-digit value reads as a date in 1970, it's milliseconds being read as seconds. Check the digit count first and you'll avoid the mistake.
Time zones
The timestamp itself is always UTC — it carries no zone. The zone only matters when you display it: the same instant is a different wall-clock time in Tokyo than in New York. If you need to line up a time across zones, the Time Zone Converter handles that side.
A note on privacy
There's nothing to upload here — the Timestamp Converter is pure arithmetic done in your browser.