Timestamp converter
Turn a Unix timestamp into a readable date, and back again.
- Runs in your browser — your text is never sent anywhere
- No sign-up, no quotas, free to use as often as you like
How it works
Computers count time as seconds since 1 January 1970. Humans do not. Converting between the two is a constant small friction when reading logs, debugging APIs or checking when a token expires.
Seconds or milliseconds
Unix timestamps are traditionally in seconds, while JavaScript and many APIs use milliseconds. The tool infers which you meant from the length, so both work.
UTC and local
You get both. Most systems store and transmit UTC, while the time you actually care about is usually local, and the gap between them is a reliable source of off-by-hours bugs.
What it accepts
A whole number of 9 to 13 digits is read as Unix time: up to 10 digits as seconds, 11 to 13 as milliseconds. Anything else is read as a date in a format your browser understands, such as 2026-09-18T10:30:00Z or 2026-09-18. Unix times before March 1973 (8 digits or fewer) and negative ones are not recognised as timestamps.
What it shows
Each result gives the Unix time in seconds and in milliseconds, the ISO 8601 form in UTC (2026-09-18T10:30:00.000Z), the same moment written out in UTC, and the moment in your device's own time zone.
The year 2038
Software that stores Unix time as a signed 32-bit number runs out at 03:14:07 UTC on 19 January 2038 (2,147,483,647 seconds). This converter uses JavaScript's 64-bit dates, so it handles dates well beyond that.
Timestamp converter — questions
Does it handle milliseconds?
Yes. The length of the number determines whether it is read as seconds or milliseconds.
What date formats can I paste in?
Anything your browser can parse, including ISO 8601.
Is anything sent to a server?
No. The conversion happens in the page.