StringMash.com

Unix timestamp converter

Epoch time to a readable date and back, in any time zone.

Conversion
10 characters
Updates as you type

Swap for date to timestamp

Show the steps
  1. 1767225600 has 10 digits, so it's read as seconds.
  2. That's 1,767,225,600 seconds after 00:00:00 UTC on January 1, 1970.
  3. Counted forward: 2026-01-01T00:00:00.000Z in UTC.

Using the converter

Paste a timestamp and the date appears, one per line if you paste several. The converter works out whether it's in seconds, milliseconds, microseconds or nanoseconds from how many digits it has, since that's the usual reason a converted date comes out wrong. Time zone shows the date in UTC, your own zone or another city's.

Swap to go from a date to a timestamp. Dates like 2026-10-01 12:00 are read in the chosen time zone; a date with its own zone, like 2026-10-01T12:00:00Z, uses that. Dates in numbers are read month first, so 03/04/2026 is March 4, and one that can only be day first, like 25/12/2026, works too. The US zone letters EST, CST, MST and PST work too, with their summer forms. Letters like BST mean different things in different countries, so give an offset such as +01:00 instead. Type now for the current timestamp.

What Unix time counts

Unix time is the number of seconds since 00:00:00 UTC on January 1, 1970, ignoring leap seconds. JSON Web Tokens use exactly the same count for their dates. The moment is called the epoch, which is why converters are often called epoch converters.

Some systems count in milliseconds instead, which gives a 13-digit number for dates in this century rather than 10. Microseconds give 16 digits and nanoseconds 19.

The year 2038

A signed 32-bit integer can hold numbers up to 2,147,483,647. As a Unix time, that's 03:14:07 UTC on January 19, 2038. One second later, a system that stores time in 32 bits wraps round to a negative number, a date in December 1901. The steps point it out when a timestamp is past that limit.

A worked example

1700000000 has 10 digits, so it's seconds. Counted from the start of 1970, it's 22:13:20 UTC on Tuesday, November 14, 2023. 1700000000000, the same moment in milliseconds, has 13 digits and gives the same date.

The largest number a signed 32-bit integer can hold, 2147483647, comes out as 03:14:07 UTC on January 19, 2038, and -1 is the last second of 1969: 23:59:59 UTC on December 31.

Time zones

A Unix timestamp has no time zone. It counts seconds from one moment in UTC, so the same number is the same instant everywhere, and only the way it's shown changes. 1700000000 is 22:13:20 in UTC and the same instant in any other zone, written with that zone's clock time.

Going the other way, a date without a zone is ambiguous. 2026-10-01 12:00 in London and in New York are different instants, so they have different timestamps. That's why the converter reads such dates in the zone you choose.

Questions

Why is my date in 1970?

The timestamp was probably read in the wrong unit. A millisecond timestamp read as seconds lands tens of thousands of years in the future, and the other way round lands near 1970. This converter guesses the unit from the number of digits to avoid that.

Does Unix time include leap seconds?

No. Every day counts as exactly 86,400 seconds, so a leap second doesn't get a number of its own.

Can a Unix timestamp be negative?

Yes. Negative numbers are dates before 1970: -86400 is the last day of 1969.

Sources

Added . Last updated and reviewed . What's new