Free · No signup

Unix Timestamp Converter

Convert epoch timestamps to readable dates and back — seconds and milliseconds detected automatically, everything in UTC.

Converted — detected as seconds

ISO 8601
2026-07-13T14:13:12Z
UTC
Monday 13 July 2026, 14:13:12 UTC
Relative
0s ago
Epoch (s)
1783951992
Epoch (ms)
1783951992000

Reverse: date → timestamp

UTC

Runs instantly — no account, no limits.

What is Unix time?

Unix time counts the seconds elapsed since 1 January 1970, 00:00:00 UTC — the "epoch". It ignores leap seconds, which makes it a simple, timezone-free way for computers to store and compare instants. Most APIs, logs and databases use it under the hood.

Two flavours coexist: seconds (10 digits for current dates, used by most backends and JWT claims) and milliseconds (13 digits, used by JavaScript's Date.now() and Java). This tool detects the unit from the magnitude of the number automatically.

Watch out for the "year 2038 problem": 32-bit signed integers overflow on 19 January 2038. Modern 64-bit systems are unaffected, but legacy embedded systems and old database schemas may still store timestamps in 32 bits.

Timestamps are how you read incidents

ContinuumNexus records every check with precise timestamps and shows you exactly when your API went down — and when it recovered.

Start monitoring free Explore features

Frequently asked questions

How do I know if a timestamp is in seconds or milliseconds?
Look at the number of digits: current dates are 10 digits in seconds (e.g. 1720000000) and 13 digits in milliseconds (e.g. 1720000000000). This tool applies that heuristic automatically and tells you which unit it detected.
Is Unix time affected by time zones or DST?
No — that is its main strength. A Unix timestamp identifies a single absolute instant, always relative to UTC. Time zones and daylight saving only appear when you format that instant for display.
What is the year 2038 problem?
Systems storing Unix time as a signed 32-bit integer overflow on 19 January 2038 at 03:14:07 UTC. Modern 64-bit systems are safe for billions of years, but legacy embedded devices and old schemas may still be exposed.
Can Unix timestamps be negative?
Yes — negative values represent instants before 1 January 1970. For example, -86400 is 31 December 1969, 00:00:00 UTC. This converter handles them.
What is the difference between Unix time and ISO 8601?
They describe the same instant in different forms: Unix time is a machine-friendly number, ISO 8601 (e.g. 2026-07-11T12:00:00Z) is a human-readable, sortable string standard. APIs typically accept or emit one of the two — this tool converts between them.