Unix timestamp converter
Turn a Unix timestamp into a date in your time zone, UTC and ISO 8601, or a date into a timestamp. Reads seconds or milliseconds, and makes Discord codes.
- Runs in your browser
- Nothing is uploaded
- Free, no sign-up
Current Unix time
…
seconds
…
milliseconds
Enter a Unix timestamp like 1700000000, or a date like 2026-10-05 14:30 (add Z for UTC).
How it works
Enter a timestamp and the page shows the moment it stands for: in your time zone, in UTC, in ISO 8601 (the 2026-10-05T14:30:00Z form that APIs and logs use) and as an HTTP date, with how long ago or how far ahead it is. It also gives the same moment in seconds, milliseconds, microseconds and nanoseconds.
A bare number is read by its length: up to 11 digits as seconds, up to 14 as milliseconds, up to 17 as microseconds, and longer as nanoseconds. You can override that with the unit menu, or by writing the unit after the number, as in 1700000000ms.
It works the other way too. Type a date like 2026-10-05 14:30, or pick one, to get its timestamp. A date without a time zone is read as your local time; add Z for UTC or an offset like +02:00. The current Unix time at the top counts up every second from your device's clock.
Questions
What is a Unix timestamp?
The number of seconds since midnight UTC on 1 January 1970, not counting leap seconds. It is the same number everywhere in the world at the same moment, which is why programs and databases store times this way. Times before 1970 are negative.
Is my timestamp in seconds or milliseconds?
Count the digits. A timestamp for a date between 2001 and 2286 has 10 digits in seconds and 13 in milliseconds; microseconds have 16 and nanoseconds 19. This page reads the unit from the length, says which it chose, and lets you pick another.
How do I make a Discord timestamp?
Convert the time here, then copy one of the codes under Discord timestamps, such as <t:1700000000:R>, into a message. Discord shows it to each reader in their own time zone and language. The letter at the end picks the style: R is relative, like "in 2 hours", and F is the full date and time.
What is the year 2038 problem?
Programs that store Unix time in a signed 32-bit number run out at 2,147,483,647 seconds, which is 03:14:07 UTC on 19 January 2038. One second later the number wraps around to a date in 1901. Systems that use 64-bit numbers, as most now do, aren't affected.
Limits
Dates are shown to the millisecond; finer digits are kept exactly in the seconds, microseconds and nanoseconds values. Dates reach forward to the year 275760 and back to 271821 BC, the furthest a browser can show. Unix time has no leap seconds, so a time like 23:59:60 can't be entered.
Your time is shown in your device's time zone only; other time zones aren't offered yet. Dates written in other forms, like "5 October 2026", are read by your browser's own parser, which differs a little between browsers. The ISO form is always read the same way. Discord previews are close to what Discord shows, but its app formats them itself.
What you enter is kept after the # in the page address, so you can bookmark or share it. That part of an address is never sent to a server.
Privacy
This tool runs entirely in your browser. The files you open and what you type are never sent to a server, and nothing is stored after you close the page. See the privacy page.
Related tools
JWT decoder
Paste a JSON Web Token to read its header and claims, see when it expires and check its signature. The token never leaves your browser.
QR code generator
Make a static QR code for a link or text. It never expires, has no tracking redirect, and downloads as PNG or SVG.
Remove EXIF data and location from photos
See and remove the hidden GPS location, camera details and dates in photos, iPhone HEIC too. Nothing is uploaded, and JPEG, PNG and WebP aren't re-compressed.