Skip to content
Technologydeveloper

Unix Timestamp Converter

Unix timestamp to a readable UTC date. Timestamps deliberately ignore leap seconds, which is why they are simple to compute with and slightly wrong as a count of elapsed time.

Also called: epoch converter, timestamp to date.

In
UTC date and time
2026-01-01T00:00:00Z

2026-01-01T00:00:00Z, a Thursday. That is 1,76,72,25,600 seconds since the epoch of 1 January 1970. Within the range a signed 32-bit timestamp can hold.

Day of the week
Thursday
In milliseconds
17,67,22,56,00,000
In seconds
1,76,72,25,600
Date only
2026-01-01
On the 2038 problem
Within the range a signed 32-bit timestamp can hold.
How this is calculated
Method and background

How this is calculated

A timestamp is seconds since the start of 1970 in UTC. It ignores leap seconds, so every day is exactly 86,400 seconds and the arithmetic is trivial, at the cost of drifting from true elapsed time by around thirty seconds since the epoch. A signed 32-bit timestamp overflows in January 2038, which is the reason systems moved to 64-bit counters.

a Unix timestamp counts seconds from the epoch, ignoring leap seconds
t
The timestamp

Worked examples

Each of these is asserted on every build. If a change to the engine ever moved one of these answers, the build would fail before the page could print it.

the start of 2026

Unix timestamp
1,76,72,25,600
In
Seconds

UTC date and time2026-01-01T00:00:00Z

Verified against the epoch count

Open this example

the epoch itself

Unix timestamp
0
In
Seconds

UTC date and time1970-01-01T00:00:00Z

boundary: the definitional case

Open this example

Method and limits

What it assumes

  • UTC. A timestamp has no time zone of its own.

What it deliberately does not model

  • Leap seconds are absent by design, so this is not a true elapsed-second count.

Formula version 1.0.0 · definition 1.0.0 · India · Report a problem with this calculator

Frequently asked questions

Why 1970?
It was a convenient recent epoch when Unix time was defined in the early seventies, close enough that timestamps fitted comfortably in the integers of the day.
What happens in 2038?
A signed 32-bit second counter overflows on 19 January 2038. Systems using 64-bit timestamps are unaffected, which is most modern software.