1. Home
  2. Developer
  3. Unix Timestamp Converter

Unix Timestamp Converter

Epoch time to date and back, with seconds vs milliseconds detected for you.

Runs in your browser · No upload Works offline
Current Unix time (seconds)
—
—

Timestamp → date

10 digits are read as seconds, 13 as milliseconds and 16 as microseconds.
Local time (—)
—
Read as seconds · —
Local time (—)
—
UTC
—
ISO 8601 (UTC)
2026-01-01T00:00:00.000Z
ISO 8601 (local offset)
—
HTTP date (RFC 7231)
Thu, 01 Jan 2026 00:00:00 GMT
Seconds
1767225600
Milliseconds
1767225600000

Date → timestamp

Unix timestamp (seconds)
—
—

All conversions run in your browser using this device’s clock and time zone.

How to use

  1. The current Unix time (in seconds) at the top updates every second — use the copy button to grab it.
  2. In Timestamp → date, enter a number to see it as local time, UTC, ISO 8601, an HTTP date and relative time such as “3 days ago”. The unit is detected from the number of digits, or you can pick it yourself.
  3. In Date → timestamp, choose a date and time to get the timestamp in seconds and milliseconds. It’s interpreted in this device’s time zone unless you turn on Interpret as UTC.

What is a Unix timestamp?

It’s the time elapsed since 1970-01-01 00:00:00 UTC (the Unix epoch). The value is the same everywhere regardless of time zone, which is why servers, databases and logs use it to store moments in time. Leap seconds are not counted.

Unit Digits today Example (2026-01-01 00:00:00 UTC) Typical source
Seconds 10 1767225600 Unix/Linux, PHP, JWT, most APIs
Milliseconds 13 1767225600000 JavaScript Date.now(), Java
Microseconds 16 1767225600000000 some Python APIs, PostgreSQL internals
Nanoseconds 19 1767225600000000000 Go UnixNano()

Auto-detection goes by magnitude: below 10¹¹ is read as seconds, below 10¹⁴ as milliseconds, and larger values as microseconds or nanoseconds.

Examples

  • 1767225600 → 2026-01-01 00:00:00 UTC, which is 7:00 PM on Wednesday, December 31, 2025 in New York (EST, UTC−5).
  • 2147483647 → 2038-01-19 03:14:07 UTC, the largest signed 32-bit integer. Old 32-bit systems can’t store anything later (the Year 2038 problem).
  • -86400 → 1969-12-31 00:00:00 UTC. Negative values are before 1970.

Things to watch out for

  • Don’t mix seconds and milliseconds. Milliseconds read as seconds land tens of thousands of years in the future; seconds read as milliseconds land in January 1970. If a result looks off, set the unit manually.
  • Millisecond values before March 1973 (below 10¹¹) are auto-detected as seconds. Choose Milliseconds explicitly for those.
  • Around daylight saving changes, some local times happen twice and others don’t exist, so a date → timestamp result can be off by an hour. Turn on UTC if you need an unambiguous answer.

FAQ

How far is my time zone from UTC?

The ISO 8601 (local offset) line shows it — for example -05:00 for New York in winter. To compare cities, use the Time Zone Converter.

When does my JWT expire?

A JWT’s exp and iat are timestamps in seconds. Paste the number here, or paste the whole token into the JWT Decoder to see the time remaining.

Coming soon

Can't find the tool you need?

Tell us what you want to do. We build the most requested tools first.