The quick answer
A Unix timestamp is simply a count: the number of seconds since 00:00:00 UTC on 1 January 1970 — the “epoch”. The moment 1700000000, for example, is Tuesday 14 November 2023, 22:13:20 UTC. Because it’s just a number, computers can sort, subtract and store timestamps without arguing about time zones, formats or daylight saving — the conversion to human dates happens only at display time, which is what the tools above do.
Seconds, milliseconds, microseconds, nanoseconds
The classic Unix timestamp is in seconds (10 digits today). JavaScript’s Date works in milliseconds (13 digits), some systems log microseconds (16 digits) and a few use nanoseconds (19 digits). Mixing them up is the most common timestamp bug: feed milliseconds into a seconds field and you land in the year 55,000-something. This converter counts the digits and detects the unit automatically — and tells you which one it found.
| Unit | Digits | Example | Used by |
|---|---|---|---|
| Seconds | 10 | 1700000000 | Unix, PHP, most APIs, databases |
| Milliseconds | 13 | 1700000000000 | JavaScript, Java |
| Microseconds | 16 | 1700000000000000 | High-resolution logs, Go, Rust |
| Nanoseconds | 19 | 1700000000000000000 | Precise timing systems |
Famous timestamps worth knowing
The epoch itself — Thursday, for the record.
The “billion seconds” party, celebrated by Unix users worldwide.
The sequential-digits moment — offices held countdown parties.
The last second a signed 32-bit timestamp can hold — the “Year 2038 problem”.
Common mistakes to avoid
- Seconds where milliseconds belong. JavaScript’s Date takes milliseconds: new Date(1700000000) lands in 1970. Multiply seconds by 1000 first — or use this page to check.
- Forgetting that timestamps are always UTC. There is no “local timestamp”. If a converted time looks off by your UTC offset, the display zone — not the timestamp — is the difference.
- Storing timestamps as strings in local format. “03/04/2026” is ambiguous (March 4 or April 3?) and unsortable. Store the epoch integer; format at display time.
- Ignoring the 2038 limit on old systems. 32-bit signed timestamps overflow on 19 January 2038. Modern 64-bit systems are fine; embedded and legacy kit may not be.
Pro tips
- Code snippets: JavaScript — Math.floor(Date.now() / 1000); Python — int(time.time()); PHP — time(); SQL — UNIX_TIMESTAMP() in MySQL, EXTRACT(EPOCH FROM NOW()) in Postgres.
- Durations are just subtraction: end timestamp − start timestamp = elapsed seconds. No calendar needed — that’s the whole point of the system.
- Relative time: the converter shows “3 days ago” style output for any timestamp — handy when scanning logs to find the entry that matters.
The complete guide
Why did computing pick 1 January 1970? What happens in 2038, and why does JavaScript insist on milliseconds? The complete guide tells the epoch story and collects conversion snippets for every major language.
Frequently asked questions
What is the current Unix timestamp?
It’s shown live at the top of this page, updating every second — the count of seconds since 1 January 1970, 00:00:00 UTC. It’s currently a 10-digit number in the 1.7–1.8 billion range during the mid-2020s.
What date is timestamp 1700000000?
Tuesday, 14 November 2023 at 22:13:20 UTC. In your local time it may show as a different clock time (and occasionally a different date) — the converter above shows UTC and your local zone side by side.
How do I convert a timestamp to a date?
Multiply seconds by 1,000 to get milliseconds, then interpret it as UTC and display it in the zone you need. On this page, just paste the timestamp — seconds, milliseconds, microseconds and nanoseconds are detected by digit count automatically.
Why does my timestamp show a date in 1970?
Almost always a unit mix-up: a milliseconds system fed a seconds value, or the reverse. 1700000000 is seconds; JavaScript’s Date expects 1700000000000 milliseconds. Check the digit count: 10 = seconds, 13 = milliseconds.
What is the Year 2038 problem?
Old 32-bit systems store timestamps in a signed integer that maxes out at 2,147,483,647 — 19 January 2038, 03:14:07 UTC. Past that, the counter wraps to negative and dates jump to 1901. 64-bit systems push the limit out by billions of years.
Are Unix timestamps affected by time zones or daylight saving?
No — that’s their biggest strength. A timestamp is one global count in UTC; time zones and DST only enter when a human reads it. Two systems anywhere on Earth agree on the timestamp even when their clocks show different local times.
Related tools
More converters and handy calculators:
