A Unix timestamp counts the number of seconds that have passed since 00:00:00 UTC on 1 January 1970, the "Unix epoch." It's how most databases, APIs, and log files store a moment in time, because it's a single unambiguous number rather than a date string that depends on timezone or format.
How it works
The converter takes the number you enter as seconds since the epoch and adds it to 1 January 1970 00:00:00 UTC.
The result is shown in ISO 8601 format (the standard most APIs expect), a human-readable UTC string, the equivalent value in milliseconds (what JavaScript's Date object uses internally), and the day of the week.
Everything here is calculated in UTC deliberately: converting to a viewer's local timezone would make the page render differently for every visitor and every server, which defeats the point of a timestamp being unambiguous.
A worked example
The timestamp 1735689600 converts to 2025-01-01T00:00:00.000Z, midnight UTC on New Year's Day 2025, which is also 1735689600000 in milliseconds, the format most JavaScript code expects.
More examples
1790000000 is Monday 21 September 2026, 14:13:20 UTC. The largest signed 32-bit timestamp, 2147483647, is Tuesday 19 January 2038, 03:14:07 UTC, the moment of the year 2038 problem.
Common mistakes
- Mixing seconds and milliseconds: a 13-digit value is in milliseconds.
- Displaying UTC as local time without converting.
- Storing future dates in 32-bit timestamps that overflow after 19 January 2038.
- Assuming Unix time counts leap seconds; it doesn't.
Questions people ask
Why does my timestamp look 1,000× smaller than what my code expects?
Unix timestamps are defined in seconds, but JavaScript's Date.now() and many web APIs use milliseconds. If your number looks unusually small, multiply by 1,000; if it looks unusually large (13 digits instead of 10), it's already in milliseconds. Divide by 1,000 before using it here.
What happens after the year 2038?
Systems that store a Unix timestamp as a signed 32-bit integer will overflow on 19 January 2038, the so-called "Year 2038 problem." Most modern systems use 64-bit integers and aren't affected, but it's worth checking older infrastructure.
Can a Unix timestamp be negative?
Yes. A negative value represents a moment before 1 January 1970. Most systems support this, but some older or embedded systems don't.
How do I get the current Unix timestamp?
In JavaScript, Math.floor(Date.now() / 1000). In Python, int(time.time()). In a Linux or macOS terminal, date +%s. Each returns the seconds since 1 January 1970 UTC.
Does a Unix timestamp include a timezone?
No. A Unix timestamp is always a count of seconds from the same moment in UTC, so it means the same instant everywhere. The timezone only matters when you display it as a local date and time.
Guides
- Unix Timestamps Explained, and Why 2038 MattersA Unix timestamp is a count of seconds since 1 January 1970 UTC. Here is how to read one, the seconds vs milliseconds trap, and what happens in January 2038.
- Scheduling Meetings Across Time Zones Without the GuessworkConverting through UTC, knowing who moves their clocks, and sharing the pain fairly makes cross-time-zone meetings much easier to plan.
- Binary, Octal and Hexadecimal: How Number Bases WorkEvery number base works the same way; only the number of digits changes. Here is how to read binary and hex, with worked conversions.