How to use the unix timestamp converter
- Paste a timestamp (seconds or milliseconds are detected), or pick a date.
- Choose the timezone you want the result in.
- Read the ISO 8601, RFC 2822 and local forms, plus the relative time.
- Copy whichever format your system needs.
A Unix timestamp is the number of seconds since 1970-01-01T00:00:00Z, excluding leap seconds. It is timezone-free, which is exactly why databases and APIs store it — and why it looks meaningless when you print it. Milliseconds are used by JavaScript's Date.now() and by most JSON APIs, so a 13-digit number almost always means milliseconds.
Two traps cause most of the confusion. First, some systems store seconds while others store milliseconds; a factor of 1000 turns 2026 into 1970-01-01 or into the year 56000. This tool detects the magnitude, and lets you force either unit. Second, "local time" is not a property of the timestamp at all — it depends entirely on the timezone you format it in, which is why the timezone selector sits next to the input.
Useful reference points
0— 1970-01-01T00:00:00Z, the epoch itself.1000000000— 2001-09-09, the "billennium".1700000000— 2023-11-14.- 2026-01-01T00:00:00Z —
1767225600.
For durations and cron schedules, keep in mind that local-time arithmetic breaks twice a year wherever daylight saving applies; the UTC forms are the safe ones to store.
Frequently asked questions
Does it handle milliseconds?
Yes — 13-digit values are treated as milliseconds automatically, and you can switch units manually.
Which timezone does it use by default?
The timezone of your browser; pick another from the list to see the same instant formatted elsewhere.
What about leap seconds?
Unix time ignores them. Two timestamps one second apart can therefore straddle a leap second without reflecting it.
Can I convert a date back to a timestamp?
Yes, pick a date and time in the calendar field and read off the epoch value in both units.