Monitoring
Solutions
Resources
Free Tools
Pricing
Free Tools / Time & scheduling / Unix Timestamp Converter

Unix Timestamp Converter

Paste an epoch value from a log or an API and see the date in UTC, in your own time zone and in any other. Or pick a date and get the timestamp, in seconds and milliseconds.

Timestamp → date

Date → timestamp

Runs entirely in your browser — nothing you enter here is sent to a server.

What Unix time is

Unix time — also called epoch time or POSIX time — is the number of seconds that have passed since midnight UTC on 1 January 1970. It is a single integer with no time zone, no daylight saving and no formatting, which is exactly why computers favour it: two timestamps can be compared, subtracted and sorted without knowing where in the world they were recorded.

The same instant has the same Unix time everywhere. What differs is how you display it. 1773306000 is 09:00 in London, 10:00 in Berlin and 05:00 in New York on the same day — one moment, three wall clocks. Most timestamp bugs come from forgetting which of the two you are holding.

Seconds — 10 digits

The classic form, used by Unix tools, most databases, JWT claims such as exp, and many APIs.

Milliseconds — 13 digits

What JavaScript's Date.now() and Java's currentTimeMillis() return. The most frequent source of "year 58,000" surprises when mixed with seconds.

Micro- and nanoseconds

16 and 19 digits. Used by Python, Go, tracing systems and high-resolution logs.

Always UTC

An epoch value has no zone. If a tool shows one in local time, the conversion happened at display — the stored number did not change.

Pitfalls worth knowing

Seconds mixed with milliseconds. A date in 1970 means milliseconds were expected and seconds supplied; a date tens of thousands of years ahead means the reverse. The converter guesses the unit from the number of digits and tells you what it assumed.

The year 2038. A signed 32-bit integer overflows at 03:14:07 UTC on 19 January 2038. Modern systems use 64 bits, but old databases, embedded devices and file formats may still have the limit.

Leap seconds. Unix time pretends they do not exist: every day has exactly 86,400 seconds. That keeps arithmetic simple, and means Unix time is not a precise count of elapsed physical seconds.

Frequently asked questions

What is a Unix timestamp?

The number of seconds since 00:00:00 UTC on 1 January 1970, not counting leap seconds. It identifies a moment in time independently of any time zone.

How do I convert a Unix timestamp to a date?

Paste it above. In code: new Date(ts * 1000) in JavaScript, datetime.fromtimestamp(ts, tz=timezone.utc) in Python, date -d @ts on Linux and date -r ts on macOS.

How do I tell whether a timestamp is in seconds or milliseconds?

Count the digits. For current dates, seconds have 10 digits and milliseconds 13. Microseconds have 16 and nanoseconds 19.

What is the year 2038 problem?

Systems that store Unix time in a signed 32-bit integer cannot represent moments after 03:14:07 UTC on 19 January 2038. The value wraps to a negative number, read as a date in 1901. 64-bit timestamps remove the limit.

Related free tools

A calculator answers once. Monitoring answers every minute.

Upzilla checks your sites, servers and APIs around the clock and alerts you the moment something breaks. 10 monitors free, no card required.

Start monitoring free →