What a Unix timestamp is
A Unix timestamp, or epoch time, is the number of seconds since 00:00:00 UTC on 1 January 1970, not counting leap seconds. 1700000000 is 22:13:20 UTC on 14 November 2023. Times before 1970 are negative.
The same instant has the same timestamp everywhere, which is why logs, databases and APIs store time this way: the time zone is only applied when the time is shown.
The converter tells the unit apart by length: up to 11 digits is read as seconds, 12 to 14 as milliseconds (JavaScript's Date.now()), 15 to 17 as microseconds and longer as nanoseconds. The answer says which it used.
Getting the current timestamp
JavaScript: Math.floor(Date.now() / 1000) for seconds, Date.now() for milliseconds.
Python: int(time.time()).
PHP: time().
Shell: date +%s, and date -d @1700000000 to read one back (on macOS: date -r 1700000000).
SQL: EXTRACT(EPOCH FROM now()) in PostgreSQL, UNIX_TIMESTAMP() in MySQL.
The year 2038 problem: a signed 32-bit number can hold timestamps up to 2147483647, which is 03:14:07 UTC on 19 January 2038. Systems that still store time in 32 bits will overflow then; 64-bit timestamps last for billions of years.
Famous timestamps
| Timestamp | Date and time (UTC) | What it is |
|---|---|---|
| 0 | 1970-01-01 00:00:00 | The Unix epoch |
| 1000000000 | 2001-09-09 01:46:40 | One billion seconds |
| 1234567890 | 2009-02-13 23:31:30 | The digits 1 to 0 |
| 1500000000 | 2017-07-14 02:40:00 | 1.5 billion seconds |
| 1700000000 | 2023-11-14 22:13:20 | 1.7 billion seconds |
| 2000000000 | 2033-05-18 03:33:20 | Two billion seconds |
| 2147483647 | 2038-01-19 03:14:07 | Last second of 32-bit time |
Start of each year in Unix time
| Year | Seconds | Milliseconds |
|---|---|---|
| 1970 | 0 | 0 |
| 2000 | 946684800 | 946684800000 |
| 2010 | 1262304000 | 1262304000000 |
| 2020 | 1577836800 | 1577836800000 |
| 2024 | 1704067200 | 1704067200000 |
| 2025 | 1735689600 | 1735689600000 |
| 2026 | 1767225600 | 1767225600000 |
| 2027 | 1798761600 | 1798761600000 |
| 2028 | 1830297600 | 1830297600000 |
| 2029 | 1861920000 | 1861920000000 |
| 2030 | 1893456000 | 1893456000000 |
| 2035 | 2051222400 | 2051222400000 |
| 2038 | 2145916800 | 2145916800000 |
| 2040 | 2208988800 | 2208988800000 |
| 2050 | 2524608000 | 2524608000000 |
Midnight UTC on 1 January.
Questions
Is a Unix timestamp in UTC?
It does not have a time zone: it counts seconds from a moment defined in UTC, so it is the same everywhere. The converter shows it in UTC and in your own time zone.
Why is my date in 1970 or far in the future?
The unit is probably wrong: milliseconds read as seconds land tens of thousands of years ahead, seconds read as milliseconds in January 1970. Check the "Read as" line.
Do Unix timestamps count leap seconds?
No. Every day is exactly 86,400 seconds in Unix time.
Can I paste an ISO 8601 date like 2022-12-28T18:28:40Z?
Yes. The converter gives its Unix timestamp in seconds and milliseconds and shows it in UTC and in your time zone. A date with no offset is read as UTC.
Which calculator do I need?
Seven calculators: days between two dates, add or subtract days, the countdowns to New Year, Thanksgiving and Black Friday, a Unix timestamp to a date and a date to a Unix timestamp. Each answers as you type, and the share bar links the calculation.
Sources
IEEE Std 1003.1 (POSIX), Base Definitions, section 4.16 "Seconds Since the Epoch".
ECMAScript Language Specification, section "Time Values and Time Range".
Written by the ufactory team and checked in October 2026.