Skip to content

Convert Unix timestamps

Convert Unix epoch time in seconds, milliseconds, microseconds or nanoseconds to a readable date in any time zone and back; it all runs in your browser.

Current Unix time— 

Timestamp to date

Seconds, ms, µs or ns — the unit is detected from the size

Paste a timestamp from a log, database or API response.

Date to timestamp

Batch convert

Runs in your browser · no uploadHow it works

How to use Unix timestamp converter

  1. 1

    Paste a timestamp

    Enter seconds, milliseconds, microseconds or nanoseconds; the unit is detected automatically and can be changed.

  2. 2

    Pick a time zone

    Results show in your browser’s zone by default — choose UTC or any city zone from the list.

  3. 3

    Convert a date back

    Enter a date and time, choose its time zone, and copy the Unix seconds or milliseconds.

  4. 4

    Batch a list

    Paste many timestamps or dates, one per line, then copy the table or download it as CSV.

Limits and Pro

Free with no sign-up: convert any date between about 270,000 BC and 275,000 AD, in 400+ IANA time zones, and up to 10,000 lines per batch (the first 1,000 are shown, all are exported).

Pro removes the ads; conversion is the same on every plan. See Pro

About Unix timestamp converter

Unix time counts the seconds since 00:00:00 UTC on 1 January 1970, ignoring leap seconds, and it is how most databases, logs, APIs and JWTs store a moment. The trouble is that systems disagree on the unit: PostgreSQL's extract(epoch) and most Unix tools give seconds, JavaScript's Date.now() and Java give milliseconds, Python can return fractional seconds, and Go, InfluxDB or OpenTelemetry often use nanoseconds. Paste a number and this converter guesses the unit from its size — up to 11 digits as seconds, 12–14 as milliseconds, 15–17 as microseconds, longer as nanoseconds — and you can override the guess with one click.

Every result is shown in your browser's time zone, in UTC and in any IANA zone you pick, such as America/New_York or Asia/Kolkata, as a readable date, ISO 8601 with offset, RFC 2822 as used in e-mail and HTTP headers, and a relative time like “3 days ago”. The same instant is listed in all four units, calculated with exact integer arithmetic so nanosecond digits are never rounded away. Day of the year, ISO week number and a note when a value passes the 2038 limit of 32-bit time_t are included.

Going the other way, pick a date and time, choose the zone it belongs to and get seconds and milliseconds; times skipped or repeated by daylight-saving changes are flagged. ISO 8601 and RFC 2822 strings can be pasted too. The batch box converts up to 10,000 lines at once and exports CSV. Leap seconds and calendars other than the proleptic Gregorian one aren't modelled, as in nearly all software.

Privacy

All conversions use your browser's built-in Intl and Date functions, including the time-zone rules, so timestamps from your logs or databases are never sent anywhere. Only the selected display time zone is remembered in local storage.

Features

Unit detection

Seconds, ms, µs and ns recognised from the number’s size, exact to the nanosecond.

Any IANA time zone

Local, UTC and every zone your browser knows, with DST gaps and overlaps flagged.

Batch conversion

Up to 10,000 lines of timestamps or dates at once, exported as CSV.

Unix timestamp converter: frequently asked questions

Is my timestamp in seconds or milliseconds?
Count the digits. A current date in seconds has 10 digits (around 1.7 billion); in milliseconds it has 13, in microseconds 16 and in nanoseconds 19. The converter applies that rule automatically and labels its guess below the input. If a date comes out in 1970 or thousands of years in the future, the unit is wrong: pick it manually.
Does a Unix timestamp depend on the time zone?
No. A timestamp is the same everywhere because it counts from midnight UTC on 1 January 1970. Only the human-readable form changes with the zone: 1767225600 is midnight on 1 January 2026 in London and 7 pm on 31 December 2025 in New York. That's why storing timestamps, and converting only for display, avoids time-zone bugs.
What is the year 2038 problem?
Systems that store Unix time as a signed 32-bit integer can count only up to 2,147,483,647 seconds, which is 03:14:07 UTC on 19 January 2038. One second later the value wraps to a negative number, read as 1901. Modern 64-bit systems are fine, and the converter notes when a value is past the 32-bit limit.
How are daylight-saving changes handled when converting a date?
When clocks spring forward, local times in the skipped hour don't exist; the converter tells you and uses the moment after the jump. When clocks fall back, an hour happens twice; it shows the first occurrence and gives the timestamp of the second. Both rules come from your browser's built-in time-zone database.
Can I convert negative timestamps or dates before 1970?
Yes. Negative values count backwards from 1970, so -86400 is 31 December 1969 at 00:00 UTC. Dates as far back as about 271,821 BC and as far ahead as 275,760 AD work, which is JavaScript's full Date range. Historic local times before standardised time zones use the local mean time recorded in the time-zone database.

Related tools

All developer tools

Time zone converter

Compare times across cities and plan meetings

Cron expression builder

Build, explain and preview cron schedules

Days between dates & countdown

Count days, business days and countdown to events

JWT decoder

Decode and inspect JSON Web Tokens, verify signatures