A log line says 1763510400. A database column holds 1763510400000. An API returns "iat": 1763510400. They are all moments in time, and getting from the number to a date, or from a date to the number, is a daily task for anyone who reads logs or builds APIs. The Timestamp Converter does the conversion, but most mistakes come from two questions the number alone does not answer: the unit, and the time zone. This guide shows how to settle both.
What a Unix timestamp is
A Unix timestamp is the number of seconds since 1 January 1970, 00:00:00 UTC, a moment called the epoch. It counts the same everywhere on earth. There is no time zone inside the number. A time zone only comes in when you turn the number into a date that a person reads: the same timestamp is a different clock time in Tokyo and in New York, but it is one and the same moment.
Seconds, milliseconds, microseconds or nanoseconds?
Different systems count the same moment in different units. You can usually tell by the number of digits for dates around now:
| Digits | Unit | Where it appears |
|---|---|---|
| 10 (up to 11) | Seconds | Unix and Linux tools, JWT claims, many APIs |
| 12–13 | Milliseconds | JavaScript Date, Java, many databases |
| 14–16 | Microseconds | Some databases and tracing systems |
| 17 and more | Nanoseconds | Go, some logging and monitoring systems |
The converter applies this rule automatically when you type a plain number into the Unix timestamp field, so you can paste 1763510400 or 1763510400000 and get the same date. If the result is in January 1970, you gave seconds where milliseconds were expected; if the date is in the far future, the opposite. A timestamp of a few billion read as milliseconds is only a few weeks after the epoch.
Timestamp to date
- Paste the number into the Unix timestamp field in the Timestamp to human time card.
- Read the full date and time, the date only, the time only, and the relative time such as "3 days ago" or "in 2 hours".
- Use the switch Use UTC time zone. With it on, the date is shown in UTC. With it off, the date is shown in your own time zone, which the page reads from your browser and shows below the switch.
- Copy any line with the copy button next to it.
The field also accepts a date string instead of a number, such as an ISO date, and tries to parse it.
Date to timestamp
In the Human time to timestamp card, choose a date and time with the picker. The result shows the same moment in several formats at once: Unix seconds, Unix milliseconds, ISO 8601, RFC 2822 and the date object text. Note that the picker is read as your local time, so choosing 09:00 in Tokyo gives a different timestamp than 09:00 in London. If you need a UTC moment, convert from local carefully, or check the ISO 8601 line, which ends in Z for UTC.
Quick timestamps and the live clock
At the top of the page the current time ticks in the selected zone. Under it, Quick timestamps gives now, one hour ago, one day ago, one week ago, one month ago and one year ago; click one to load it. These are handy when you need a timestamp for a test, or an expiry value for a token or cache. The month and year offsets are averages, not calendar months.
Why dates come out wrong
- Off by 9 hours or 5 hours, or by "one day". The timestamp is right, but you read it in a different zone than the system that wrote it. Switch UTC on and compare with what the log says.
- Year 1970 or year 50000. A unit mismatch: seconds were read as milliseconds or the reverse.
- The date is a day off near midnight. A UTC date and a local date straddle midnight. Compare in the same zone.
- The converted time is off by an hour twice a year. Daylight saving time. A timestamp is not affected; the local clock time shown for it is.
- A string like "2026-11-19 09:00" was parsed oddly. Without a time zone marker, the browser treats it as local time. Add Z or an offset such as +09:00 to be exact.
- Decimal timestamps. A number with a decimal part, such as 1763510400.5, is read as seconds with a fraction.
Good habits
- Store and transmit times as UTC timestamps or as ISO 8601 with a zone offset, and convert to local time only for display.
- Name the unit in field names, such as created_at_ms, so nobody has to guess.
- When you read a token, remember that its exp, iat and nbf claims are in seconds. The JWT Decoder converts them for you.
- Do not use timestamps in seconds as 32-bit signed numbers if you can avoid it: that format overflows in January 2038.
Limits
The converter handles any date your browser can represent; it does not know business calendars, leap-second tables or historic time-zone rules beyond what your browser provides. The result in your local zone depends on the settings of your computer.
Frequently asked questions
How can I tell seconds from milliseconds?
Current dates have 10 digits in seconds and 13 in milliseconds.
Is my input uploaded?
No. Conversion happens in your browser.
Why does the result change with the time zone?
The timestamp is one moment; the clock time you read from it depends on the zone you view it in.
What is ISO 8601?
A standard text format for dates and times, such as 2026-11-19T09:00:00.000Z. The Z means UTC.