How to use
- Pick the time zone at the top; it applies to both directions. The current timestamp there updates every second and copies in seconds or milliseconds with one click.
- To read a timestamp, paste it under Timestamp to date, for example 1790424000 or 1790424000000. The unit is detected from the number of digits.
- To get a timestamp, type a date under Date to timestamp — 2026-09-26 12:00, Sep 26 2026 3 pm and 26/09/2026 all work — or use the picker or the Now, Today and Tomorrow buttons.
- Copy the result you need. The last row of the first table uses your own format, such as DD/MM/YYYY HH:mm.
Options explained
- Unit
- 10 digits are seconds (used by Unix, PHP, Python time.time()), 13 digits milliseconds (JavaScript Date.now(), Java), 16 microseconds (PostgreSQL, Python datetime), 19 nanoseconds (Go time.UnixNano()).
- Time zone
- Timestamps are always UTC; the time zone only changes how the date is displayed. Dates without an offset are interpreted in the selected zone, including daylight-saving rules.
- Date input
- Recognises 2026-09-26 12:00:00, 2026/9/26, 26/09/2026 and 09/26/2026, Sep 26, 2026 3:45 PM, compact 20260926123000, a time alone such as 14:30 (today), ISO 8601 with Z or ±hh:mm, and RFC 2822. For any other layout, fill in Date format, e.g. DD.MM.YY HH:mm.
- Custom format
- Tokens follow Day.js: YYYY year, MM month, DD day, HH hour (00–23), hh hour (01–12), A AM/PM, mm minutes, ss seconds, SSS milliseconds, dddd weekday, MMMM month name, Z offset, X Unix seconds. Text in [brackets] is shown as is. The format you enter is remembered in this browser.
Getting the current timestamp
| Language | Seconds | Milliseconds |
|---|---|---|
| JavaScript | Math.floor(Date.now() / 1000) |
Date.now() |
| Python | int(time.time()) |
time.time_ns() // 1_000_000 |
| Java | Instant.now().getEpochSecond() |
System.currentTimeMillis() |
| Go | time.Now().Unix() |
time.Now().UnixMilli() |
| PHP | time() |
(int)(microtime(true) * 1000) |
| MySQL | UNIX_TIMESTAMP() |
ROUND(UNIX_TIMESTAMP(NOW(3)) * 1000) |
| Shell | date +%s |
date +%s%3N (GNU) |
Example
1790424000 → Saturday, 26 September 2026, 12:00:00 UTC → ISO 8601 in Tokyo: 2026-09-26T21:00:00.000+09:00, ISO week 39.
Frequently asked questions
What is a Unix timestamp?
The number of seconds since 00:00:00 UTC on 1 January 1970, not counting leap seconds. It is the same everywhere in the world at a given moment, which is why systems store time this way.
How do I tell seconds from milliseconds?
Count the digits. Timestamps for dates between 2001 and 2286 have 10 digits in seconds and 13 in milliseconds. If you get a date in 1970 or tens of thousands of years from now, the unit is wrong.
What happens in 2038?
Signed 32-bit systems store seconds up to 2,147,483,647, which is 03:14:07 UTC on 19 January 2038. After that they overflow; 64-bit time (used by modern systems) lasts for billions of years.
How are daylight-saving changes handled?
A time that does not exist (skipped when clocks go forward) moves forward by the gap, and a time that happens twice (when clocks go back) uses the earlier one — the same rule as JavaScript's Temporal API.
Why does my timestamp show a different date than expected?
Usually the time zone. 1790424000 is 12:00 UTC on 26 September 2026, which is 20:00 in Beijing and 08:00 in New York. Check the zone selected above.
Privacy
This tool runs entirely in your browser. Your files and text are processed on your device and are never uploaded to our servers.