How to use the Unix timestamp converter
- Paste a timestamp, such as 1700000000, or a date, such as 2026-01-01 09:30, into Timestamp or date. Leave it empty to see the current time.
- Leave Timestamp unit on Detect or choose Seconds, Milliseconds, Microseconds or Nanoseconds.
- Choose a Time zone. Dates you type are read in this zone, and timestamps are shown in it.
- Read the main result, then copy whichever format you need from the Every format table.
What it does and when to use it
Timestamps are easy for computers and hard for people. This converter is for the moments when you need to read one, or make one:
- Reading a
created_atvalue in a database row or an API response. - Making sense of times in log files from servers in different regions.
- Checking the
exporiatclaim in a token. For JWTs, the JWT Debugger decodes these for you. - Building a timestamp for a test, a query or a URL parameter.
- Finding out whether a value is in seconds or milliseconds before a bug ships.
To find the gap between two dates or timestamps, use the Timestamp Difference tool. To see when a scheduled job will run next, try the Cron Parser.
How it works
A Unix timestamp counts seconds from 1970-01-01 00:00:00 UTC. To convert, the tool turns your input into an exact instant in milliseconds, then formats it with the browser’s built-in Intl date functions.
- Unit detection. In Detect mode, 10 digits are read as seconds and 13 as milliseconds. Microseconds and nanoseconds can be chosen by hand.
- Dates you type without an offset are read in the chosen time zone. A date like 2024-02-29T12:00:00+05:30 carries its own offset.
- Daylight saving. If you type a local time that does not exist because clocks went forward, the tool moves it forward and warns you.
The Every format table includes seconds, milliseconds, ISO 8601 in UTC and in your zone, the RFC 2822 / HTTP date, a long form, the relative time, day of year, ISO week, an Excel serial date and the Julian day. Everything runs in your browser.
Worked examples
A timestamp in seconds. 1700000000 in UTC is Tuesday, 14 November 2023, 22:13:20, or 2023-11-14T22:13:20.000Z in ISO 8601. It falls in ISO week 2023-W46.
A date in India to a timestamp. “2024-02-29 12:00” read in Asia/Kolkata gives Unix timestamp: 1709188200. In UTC that is 06:30 on the same day, because India is 5 hours 30 minutes ahead.
Thirteen digits. 1700000000000 is shown as Read as: milliseconds and gives the same instant as the first example.
Past 2038. 2147483648 is 2038-01-19 03:14:08 UTC, one second past the largest signed 32-bit value. The tool warns that it is beyond the limit of signed 32-bit timestamps.
Limits and tips
- Unix time ignores leap seconds, so every day is treated as exactly 86,400 seconds.
- If a timestamp in seconds lands in 1970, the value was probably in milliseconds or another unit. The tool points this out.
- Store times as UTC timestamps and convert to local time only when you display them.
Frequently asked questions
What is a Unix timestamp?
Is my timestamp in seconds or milliseconds?
Why does my date look a few hours off?
What is the 2038 problem?
How do I get the current timestamp?
How do we know nothing is uploaded? Test it yourself on the privacy proof page.