What's a Unix timestamp?
It's the number of seconds since 1 January 1970, 00:00 UTC (the “Unix epoch”). It's the same everywhere in the world, which makes it handy for storing and comparing times. JavaScript and many APIs use milliseconds instead, so the number is 1,000× bigger.
How to use it
- Timestamp → Date: the page starts with the current time. Paste a timestamp or a date, or press Now. The line under the input says exactly how it was read; use Read as to override seconds / milliseconds.
- Date → Timestamp: type in the date and time fields, nudge them with ▴ ▾ (or − / + on a phone; hold to keep counting, ↑ / ↓ work too), or press Pick date & time for a calendar. Choose whether the time is your local time, UTC or another time zone.
- Every format appears below with a Copy button. Pick another time zone for the “Other time zone” row; it's remembered.
- Date format sets how readable dates look (ISO style, US, UK / Europe, 12 or 24 hours) and adds your own custom format. It's remembered in this browser.
How do you tell seconds from milliseconds?
By length. Today's timestamps have 10 digits in seconds and 13 digits in milliseconds. We detect it automatically and tell you what we picked.
| Digits | Read as | Example |
|---|---|---|
| up to 11 | Seconds | 1794968119 |
| 12–14 | Milliseconds | 1794968119000 |
| 15–17 | Microseconds | 1794968119000000 |
Example
1794968119 is 2026-11-18T02:15:19.000Z in ISO 8601, and Wed, 18 Nov 2026 02:15:19 GMT as an HTTP date.
Start and end of a year, month or day
In Date → Timestamp, only the year is required. Leave the later fields empty and you get the whole period: its first moment, its last second (and millisecond), and when the next one starts.
For example, November 2026 in UTC (Year 2026, Month November):
| Row | Unix seconds | ISO 8601 |
|---|---|---|
| Start | 1793491200 | 2026-11-01T00:00:00.000Z |
| End (last second) | 1796083199 | 2026-11-30T23:59:59.999Z |
| Next month starts | 1796083200 | 2026-12-01T00:00:00.000Z |
Handy for database queries: created >= 1793491200 AND created <= 1796083199, or < 1796083200 to include every
fraction of the last second. In another time zone the numbers shift: in Berlin, November 2026 starts at
2026-10-31T23:00:00Z.
Dates you can paste
- ISO 8601:
2026-11-18T10:00:00Z,2026-11-18T10:00:00+07:00,2026-11-18 10:00 - HTTP / email style:
Wed, 18 Nov 2026 03:00:00 GMT - With slashes or dots:
18/11/2026 14:30,11/18/2026 2:30 PM,18.11.2026,2026/11/18. When both readings are possible (03/04/2026), Date format decides whether the day or the month comes first;18/11/2026can only mean 18 November, so it's read that way either way. - Dates without a time zone are read as your local time, or UTC if you choose. Impossible dates like
2026-02-30are refused instead of silently moved to March.
Custom formats
Type a pattern in Date format → Custom format and a “Custom format” row shows every result that way. It uses the
tokens of the dayjs and moment libraries: YYYY-MM-DD HH:mm:ss.SSS Z turns 1795008605042 (milliseconds, in UTC)
into 2026-11-18 13:30:05.042 +00:00. Text in [brackets] is kept as it is, e.g. [at] HH:mm.
FAQ
Why does a day sometimes have 23 or 25 hours?
Daylight saving. In Berlin, 29 March 2026 has 23 hours (clocks jump from 02:00 to 03:00) and 25 October 2026 has 25 (clocks go back from 03:00 to 02:00). A time like 02:30 on 29 March never happens there, and 02:30 on 25 October happens twice; the tool tells you and lets you pick which one.
What about the year 2038 problem?
Old systems store seconds in a signed 32-bit number, which runs out on 19 January 2038. This tool uses JavaScript dates, which work far beyond that.
Is anything sent to a server?
No. Conversion uses your browser's own clock and time-zone data. See the privacy page.