Unix Timestamp Converter
What date is 1700000000? What's the current epoch time? Paste any Unix timestamp to get UTC, local, ISO 8601, and relative time — or pick a date to get its timestamp in seconds and milliseconds.
Current Unix timestamp
—
seconds — JavaScript's Date.now() returns milliseconds (×1,000)
Detected: seconds
UTC
Tue, 14 Nov 2023 22:13:20 GMT
Your local time
—
ISO 8601
2023-11-14T22:13:20.000Z
Relative
—
Unix time counts seconds since 1970-01-01 00:00:00 UTC, ignoring leap seconds — the same instant everywhere on Earth. Signed 32-bit systems overflow at 2,147,483,647 (2038-01-19 03:14:07 UTC), the “Y2038 problem.”
How Unix Time Works
Unix time is a single integer: seconds elapsed since 1970-01-01 00:00:00 UTC, the “epoch.” It carries no time zone — 1700000000 is 2023-11-14 22:13:20 UTC for everyone, and converting to wall-clock time is purely a display step. The usual trip-up is units: classic Unix time is seconds (10 digits today), while JavaScript and Java hand out milliseconds (13 digits) — this converter auto-detects which you pasted. Systems storing the count as a signed 32-bit integer run out at 2,147,483,647, which is 2038-01-19 03:14:07 UTC: the Y2038 problem.
Timestamp landmarks
0 1970-01-01 00:00:00 UTC (the epoch) 1000000000 2001-09-09 01:46:40 UTC 1700000000 2023-11-14 22:13:20 UTC 2147483647 2038-01-19 03:14:07 UTC (2³¹−1 — the Y2038 limit) Units: 10 digits → seconds, 13 digits → milliseconds (÷ 1,000)
Frequently Asked Questions
Is a Unix timestamp in seconds or milliseconds?
Classic Unix time is seconds since 1970-01-01 00:00:00 UTC, but JavaScript's Date.now() and many APIs return milliseconds. A quick tell: current values in seconds are 10 digits, in milliseconds 13 digits. If a date comes out around the year 56,000, you fed milliseconds in as seconds — divide by 1,000.
What is the Year 2038 problem?
Systems that store Unix time as a signed 32-bit integer overflow at 2,147,483,647 (2^31 − 1), which is 2038-01-19 03:14:07 UTC. One second later the value wraps negative, reading as December 1901. Modern 64-bit time_t systems are unaffected, but embedded devices and old file formats can still be exposed.
What date is the timestamp 1700000000?
1,700,000,000 seconds after the epoch is 2023-11-14 22:13:20 UTC. Round-number timestamps are popular sanity checks: 1,000,000,000 fell on 2001-09-09, and 2,000,000,000 lands on 2033-05-18. They make handy test fixtures because they're easy to recognize in logs.
Do Unix timestamps include time zones or leap seconds?
Neither. A Unix timestamp is always UTC — the same instant everywhere on Earth — and converting to local wall-clock time is purely a display step. Unix time also ignores leap seconds: every day counts exactly 86,400 seconds, so it is about 27 seconds offset from a true atomic-second count since 1970.