What is a Unix timestamp?

A Unix timestamp is the number of seconds elapsed since January 1, 1970 00:00:00 UTC, the moment known as the Unix epoch. Every modern operating system, database and language keeps time internally as some flavour of this counter, which is why you meet it everywhere from API responses to log files to JWT iat/exp fields.

Does it support milliseconds?

Yes, and the unit is auto-detected by magnitude: values around 10¹⁰ are treated as seconds, values around 10¹³ as milliseconds. If the auto-detection guesses wrong on a boundary case, you can force either unit explicitly.

What happens to Unix timestamps in 2038?

Systems that still store Unix time as a signed 32-bit integer roll over on 2038-01-19 03:14:07 UTC, the Year 2038 problem. Every current 64-bit system is fine until roughly the year 292 billion. This tool uses JavaScript numbers, which are 64-bit floats, so there is no 2038 issue here.

← Back to Tools

Unix Timestamp Converter

Current Timestamp

Seconds1790171976

Milliseconds1790171976759

Timestamp to Date

Timestamp

Detected unitSeconds

UTC (ISO 8601)2023-11-14T22:13:20.000Z

Local time11/14/2023, 10:13:20 PM

Date to Timestamp

Date and time (local)

Seconds1790171940

Milliseconds1790171940000

How it works

Enter a Unix timestamp (the number of seconds, or milliseconds, since January 1, 1970 UTC, also called the epoch) and the tool shows the matching human-readable date and time in both UTC and your own local timezone. It goes the other way too: pick a calendar date and time and get the corresponding timestamp back. The unit is auto-detected, seconds or milliseconds, and a live clock shows the current timestamp ticking so you can grab 'now' without doing any arithmetic. Unix time is how databases, logs, APIs and programming languages almost universally store moments in time, which makes this an everyday tool for debugging log entries, setting expiry values, comparing two events, or sanity-checking a date field returned by an API. Everything is computed in your browser using your device's clock, with nothing uploaded or stored.

Frequently Asked Questions

What is a Unix timestamp?: A Unix timestamp is the number of seconds elapsed since January 1, 1970 00:00:00 UTC, the moment known as the Unix epoch. Every modern operating system, database and language keeps time internally as some flavour of this counter, which is why you meet it everywhere from API responses to log files to JWT iat/exp fields.
Does it support milliseconds?: Yes, and the unit is auto-detected by magnitude: values around 10¹⁰ are treated as seconds, values around 10¹³ as milliseconds. If the auto-detection guesses wrong on a boundary case, you can force either unit explicitly.
What happens to Unix timestamps in 2038?: Systems that still store Unix time as a signed 32-bit integer roll over on 2038-01-19 03:14:07 UTC, the Year 2038 problem. Every current 64-bit system is fine until roughly the year 292 billion. This tool uses JavaScript numbers, which are 64-bit floats, so there is no 2038 issue here.