Unix Timestamp Converter

Convert Unix timestamps (seconds, ms, µs, ns) to dates in any time zone, and dates back to epoch time. Live current timestamp and batch mode.

Turn a Unix timestamp like 1735689600 into a readable date — in UTC, your own time zone or any other — and turn a date and time back into a timestamp. The current epoch time ticks live at the top, ready to copy.

The converter recognises seconds, milliseconds, microseconds and nanoseconds from the length of the number, handles daylight saving time correctly, and converts long lists in one go. It runs in your browser using its built-in time zone database.

How to use Unix Timestamp Converter

  1. Copy the current Unix time from the top, or type a timestamp into “Timestamp → date”.
  2. The unit (seconds, ms, µs or ns) is detected automatically; choose one yourself if needed.
  3. Pick another time zone to see the same moment there.
  4. To go the other way, choose a date, time and time zone in “Date → timestamp” and copy the seconds or milliseconds.

Features

  • Live current Unix time in seconds and milliseconds.
  • Timestamp to date: ISO 8601, RFC 2822, your local time, any IANA time zone and relative time (“3 days ago”).
  • Detects seconds, milliseconds, microseconds and nanoseconds automatically.
  • Date to timestamp in any time zone, correct across daylight saving changes.
  • Negative timestamps (before 1970) and far-future dates.
  • Batch mode: convert a whole list and copy it as CSV.
  • One-click copy for every value; works offline once loaded.

What is a Unix timestamp?

A Unix timestamp (also called epoch time or POSIX time) is the number of seconds that have passed since 00:00:00 UTC on 1 January 1970, not counting leap seconds. It is the same everywhere in the world at a given moment, which makes it ideal for storing and comparing times in databases, logs, APIs and JWT tokens.

JavaScript, Java and many APIs use milliseconds instead of seconds, so their timestamps have three more digits.

Seconds, milliseconds, microseconds or nanoseconds?

The converter guesses the unit from the number of digits of a present-day timestamp.

UnitDigits todayExampleUsed by
Seconds101735689600Unix, PHP, Python time.time(), JWT exp/iat
Milliseconds131735689600000JavaScript Date.now(), Java, many APIs
Microseconds161735689600000000PostgreSQL, Python datetime precision
Nanoseconds191735689600000000000Go time.UnixNano(), InfluxDB

Useful epoch timestamps

Some well-known moments as Unix timestamps (seconds, UTC).

Moment (UTC)Unix timestamp
1970-01-01 00:00:00 (the epoch)0
2000-01-01 00:00:00946684800
2001-09-09 01:46:40 (1 billion)1000000000
2025-01-01 00:00:001735689600
2033-05-18 03:33:20 (2 billion)2000000000
2038-01-19 03:14:07 (32-bit limit)2147483647

The year 2038 problem

Older systems store Unix time as a signed 32-bit number, which can count only up to 2,147,483,647 seconds — reached at 03:14:07 UTC on 19 January 2038. One second later such systems wrap around to December 1901. Modern systems use 64-bit time, which lasts for billions of years; check embedded devices, old databases and file formats that may still use 32 bits.

Time zones and daylight saving time

A timestamp has no time zone — it is a single moment. Time zones only matter when you show it as a date or turn a local date into a timestamp. When clocks go forward in spring, some local times do not exist (for example 02:30 in New York on the second Sunday of March); when they go back in autumn, one hour happens twice. The converter tells you when either case applies and picks a sensible result.

Frequently asked questions

How do I convert a Unix timestamp to a date?

Paste it into “Timestamp → date”. You immediately see the date in UTC, in your time zone and in any zone you choose, plus ISO 8601 and RFC 2822 formats.

How do I get the current Unix timestamp?

It is shown live at the top in seconds and milliseconds — click Copy. In code: Math.floor(Date.now() / 1000) in JavaScript, time.time() in Python, time() in PHP.

Why is my date in 1970 or far in the future?

The unit is wrong: a millisecond timestamp read as seconds lands tens of thousands of years in the future, and a second timestamp read as milliseconds lands in January 1970. Automatic detection avoids this; you can also pick the unit yourself.

Is a Unix timestamp in UTC?

Yes. It counts seconds since midnight UTC on 1 January 1970, so the same timestamp is the same moment everywhere. Only its display as a date depends on the time zone.

Can Unix timestamps be negative?

Yes. Negative values are dates before 1970 — for example -86400 is 31 December 1969. The converter supports them.

Does Unix time include leap seconds?

No. Unix time ignores leap seconds: every day is exactly 86,400 seconds. That is why it is simple to calculate with.

Can I convert many timestamps at once?

Yes. Open “Convert many timestamps at once”, paste one per line and copy the results as CSV.

Related tools