Skip to content

Unix Timestamp Converter

Convert epoch time to a date and back, in seconds or milliseconds

Runs entirely in your browser. Nothing you enter is sent to a server.

Current Unix time

  • Seconds—
  • Milliseconds—

Timestamp to date

Whole numbers or decimals, negative too. Paste an exponent such as 1.7e9; a phone keypad has no e.

Type or paste a timestamp to see the date.

Date to timestamp

Local time is your browser's time zone.

ISO 8601 such as 2024-03-10T02:30:00Z, or 2024-03-10 02:30, or Mar 10, 2024 2:30 PM.

Type or paste a date to see the timestamp.

How the conversions work

What a Unix timestamp is

A Unix timestamp counts the time since 1 January 1970, 00:00:00 UTC, called the epoch. Unix time ignores leap seconds, so every day has exactly 86,400 seconds. A timestamp names one instant; the date and time it shows depends on the time zone you read it in.

Seconds, milliseconds, microseconds and nanoseconds

With Detect from the size, a value below 100,000,000,000 is read as seconds, below 100,000,000,000,000 as milliseconds, below 100,000,000,000,000,000 as microseconds, and anything larger up to 9,223,372,036,854,775,807 (2^63 − 1) as nanoseconds. A value above that is refused until you pick a unit, because the page cannot tell what it counts. Choose a unit to override the guess; a small negative number such as -14182940000 is read as seconds unless you say milliseconds.

Exact values

Digits are read as exact integers, never as floating-point numbers, so 9007199254740993, which the page reads as microseconds, keeps its last digit. Decimals and exponents such as 1.7e9 are exact too, up to 30 decimal places after conversion to seconds. The seconds and milliseconds rows show every digit the value has. The page can show dates from -271821-04-20T00:00:00Z to +275760-09-13T00:00:00Z, the span a JavaScript Date holds; anything outside it gets a message. Years before 1 CE are numbered with year 0 as 1 BCE, as ISO 8601 does.

Local time, daylight saving and zones

Local time is the time zone your browser reports. A local time can be missing, when the clocks jump forward, or happen twice, when they go back. The page says so and names the instant it used. For a time that does not exist it applies the offset from before the jump, and for a time that happens twice it takes the first, as JavaScript, Python and Temporal all do. Add an offset to the date, such as -05:00, or Z, to name the instant yourself. Zone rules come from your browser, so a date far in the future follows the rules the browser knows today.

Privacy

Runs entirely in your browser. Nothing you enter is sent to a server. The converter makes no request while you use it and stores nothing on your device.