DevKit

Unix Timestamp Converter

Paste a timestamp or a date — see every useful representation at once.

Free No sign-up Runs in your browser
Now
Current time—
—Seconds
—Milliseconds
—ISO 8601 UTC

Timestamps are timezone-free; the same instant renders differently in UTC and local time. Both are shown above.

Unix time, precisely

A Unix timestamp counts the seconds elapsed since 00:00:00 UTC on 1 January 1970, ignoring leap seconds. It is timezone-free by design: the integer 1700000000 denotes one instant everywhere on Earth, and local rendering is a presentation concern. That is exactly why databases, logs and APIs prefer it to formatted date strings.

The classic bug is a unit mismatch. Seconds timestamps are 10 digits today; milliseconds are 13. Passing milliseconds where seconds are expected lands you in the year 55000, and the opposite puts you in 1970. Auto-detection here uses a simple threshold — anything above 10¹¹ is milliseconds — which is reliable for any date after 1973.

What "now" is not

Current Unix time is about 1.79 billion, but the exact value depends on a clock that may be skewed. Distributed systems handle this with NTP, monotonic clocks for measuring durations, and logical clocks (Lamport, hybrid) for ordering events. Do not use wall-clock time to measure elapsed time — a clock correction will produce negative durations.

Two-digit years and the 2038 problem

Systems storing time as a signed 32-bit integer overflow on 19 January 2038 at 03:14:07 UTC. Most modern platforms already use 64-bit time, but embedded devices, old databases and file formats may not. If you maintain anything long-lived, check the width of your time columns.

ISO 8601 is the interchange format

For anything crossing a system boundary, prefer ISO 8601: 2024-01-31T10:00:00Z. It sorts lexicographically, includes the timezone, and is unambiguous — unlike 01/02/2024, which is January 2 in the US and February 1 in most of Europe. Store timestamps as ISO strings or integers, never as localised text.

Frequently asked questions

Seconds or milliseconds — how do I tell?
Count the digits: 10 digits is seconds up to the year 2286, 13 is milliseconds. Auto-detect here assumes anything above 10¹¹ is milliseconds.
Why is my date off by hours?
The input had no timezone, so it was parsed as local time, or you are reading a UTC value as local. Always include Z or an offset when the instant matters.
What is the 2038 problem?
32-bit signed Unix time overflows on 2038-01-19 03:14:07 UTC. Use 64-bit integers or ISO strings in anything that must outlive that date.
Does this handle leap seconds?
No — Unix time ignores them, and so does JavaScript. Over a 50-year span the accumulated difference is under a minute, irrelevant for display purposes.

Related tools