Unix timestamp converter
This Unix timestamp converter turns seconds or milliseconds into a date in any time zone, and a date back into a timestamp. It runs on your device, and what you type stays there.
How to convert a timestamp
- Choose a time zone. Your device's zone is chosen for you.
- Type a timestamp to read its date, or a date to get its timestamp.
- Copy the results, or save them as a file.
Questions
Is it reading seconds or milliseconds?
A number under 100 billion is read as seconds, and a larger one as milliseconds, and the page says which it chose. The line is there because 100 billion seconds is the year 5138, while 100 billion milliseconds is March 1973. Set the unit yourself for a date near 1970 in milliseconds, which would otherwise read as seconds.
What happens to a time the clocks skip or repeat?
The page tells you. In New York, 2026-03-08 02:30 does not exist, so it gives no timestamp and says why. 2026-11-01 01:30 happens twice, so it shows the first and names the second, one hour later. We compared this with Python's zoneinfo.
Where do the time zones come from?
From your browser's own list, through Intl, so nothing is fetched. Your browser's copy of the rules can be older than the latest change, and rules for a far-off date are a forecast, because governments change them. Before about 1900, a zone's offset can have seconds in it, from local mean time, and the page shows them.
What about the year 2038 problem?
It does not affect this page. A browser's Date runs from about 271,821 BC to 275,760 AD, so 2147483648, one second past the 32-bit limit, reads as 2038-01-19 03:14:08 UTC. Your own system may still store times in 32 bits.
Does a Unix timestamp count leap seconds?
No. Unix time treats every day as 86,400 seconds, and so does this page, as Python and browsers do.
Is anything saved?
No. It works on this page alone, with no request and no storage. You can check the page's requests yourself.