Unix Timestamp Converter

Convert Unix timestamps to dates and vice versa. Supports seconds and milliseconds, any timezone, and shareable URLs.

Link copied to clipboard

Timestamp → Date

Date → Timestamp

Common epoch reference

EventTimestamp (seconds)
Unix epoch start0
Year 2000 (Y2K)946,684,800
Year 2038 — 32-bit signed max2,147,483,647
Year 2106 — unsigned 32-bit max4,294,967,295
Year 300032,503,680,000

How to use this tool

  1. Paste a Unix timestamp (seconds or milliseconds) into the top input to see the human-readable date.
  2. Use the date and time pickers in the lower section to convert a specific date back to a Unix timestamp.
  3. Select your timezone from the dropdown — all date outputs update instantly.
  4. Click 'Now' to fill the current Unix timestamp in one click.
  5. Copy any output with its copy button, or share the URL — it encodes your timestamp.

Why use our Unix Timestamp Converter?

Unix timestamps are the universal language of time in software. Every database, API, and log file uses them — but they're unreadable to humans. This tool gives you an instant two-way bridge between epoch numbers and real dates, in any timezone, without installing anything.

Frequently Asked Questions

What is a Unix timestamp?

A Unix timestamp is the number of seconds (or milliseconds) elapsed since January 1, 1970, 00:00:00 UTC — also called the Unix epoch. It is the standard way computers store and compare times across time zones.

Seconds or milliseconds — how do I tell?

A 10-digit number is almost always seconds (covering years 2001–2286). A 13-digit number is milliseconds. This tool auto-detects the format and shows a label confirming which unit was recognised.

What is the maximum Unix timestamp?

On 32-bit systems the signed integer maximum is 2,147,483,647 — January 19, 2038, the so-called Year 2038 problem. On 64-bit systems the limit extends to the year 292 billion, which is far beyond any practical concern.

Is Unix time the same as UTC?

Unix time counts seconds from the UTC epoch but does not track leap seconds, so it stays in lockstep with UTC on all modern systems. Converting to a local wall-clock time requires applying a timezone offset on top.

What is time_t?

time_t is the C data type used to store Unix timestamps. On 32-bit systems it is a signed 32-bit integer, which causes the Year 2038 problem. On 64-bit systems it is a signed 64-bit integer and will not overflow for billions of years.