Skip to content
SPCXTools

Unix Timestamp Converter

Convert epoch timestamps to readable dates and dates to Unix time, with automatic seconds/milliseconds detection.

Runs locally — files never leave your device

Loading tool…

How to use Unix Timestamp Converter

  1. 1The current Unix time is shown at the top and updates every second — copy it with one click.
  2. 2Paste a timestamp into Timestamp to date. Seconds, milliseconds, microseconds and nanoseconds are detected automatically.
  3. 3Read the result in your local time zone, UTC, ISO 8601, RFC 2822 and relative form ("3 hours ago").
  4. 4To go the other way, pick a date and time under Date to timestamp, choose whether it is local time or UTC, and copy the seconds or milliseconds.

Convert between Unix time and dates

Computers, databases and APIs usually store time as a single number: the Unix timestamp, counting seconds since 1 January 1970 UTC. It is compact and unambiguous, but impossible to read at a glance. This epoch converter translates timestamps into dates you can read — in your own time zone and in UTC — and converts any date back into a timestamp. It runs entirely in your browser using your device's clock and time-zone settings.

Features

  • Live current Unix time in seconds, ready to copy.
  • Automatic unit detection for seconds (10 digits), milliseconds (13), microseconds (16) and nanoseconds (19).
  • Multiple output formats: localised full date, UTC, ISO 8601 (2026-10-02T08:30:00.000Z), RFC 2822 and a relative description such as "in 2 days".
  • Date to timestamp with a choice of interpreting the date as local time or UTC, returning both seconds and milliseconds.

Where you meet timestamps

Logs and monitoring. Server logs, analytics events and error trackers often record time as epoch seconds. Converting a value tells you exactly when an incident happened, in your own time zone.

APIs and JSON. Many APIs return fields like "created": 1790000000 or "expires_at". JavaScript's Date.now() and Java's System.currentTimeMillis() return milliseconds, while Unix tools, Python's time.time() and PHP's time() use seconds. Mixing them up is a classic bug.

Tokens and cookies. JSON Web Tokens use iat, nbf and exp claims in epoch seconds. The JWT Decoder converts these automatically.

Databases and spreadsheets. Converting timestamps to dates helps when checking records, and converting dates to timestamps lets you write precise range queries.

Time zones and UTC

A timestamp identifies one instant, regardless of where you are. Time zones only matter when showing it to a person. That is why the same timestamp displays as different local times in Tokyo and New York, while the UTC line stays the same. When you convert a date to a timestamp, be explicit: "9:00" in local time and "9:00 UTC" produce different numbers unless you live in a UTC time zone.

To compare times across cities, use the Time Zone Converter. To count the days between two dates, try the Date Difference Calculator.

Frequently asked questions

What is a Unix timestamp?
A Unix timestamp (also called epoch time or POSIX time) is the number of seconds that have passed since 00:00:00 UTC on 1 January 1970, not counting leap seconds. It is the same everywhere in the world at a given moment, which makes it ideal for storing and comparing times.
How do I know if a timestamp is in seconds or milliseconds?
Count the digits. Current timestamps in seconds have 10 digits (for example 1790000000), while milliseconds have 13. The converter detects this automatically, and also recognises 16-digit microseconds and 19-digit nanoseconds.
Why is the converted time different from what I expected?
Unix time is always UTC. The local result uses your device's time zone, shown next to it. If a value looks off by several hours, the system that produced it probably mixed local time and UTC. If it looks off by a factor of 1,000 (a date in 1970 or far in the future), seconds and milliseconds were confused.
What is the year 2038 problem?
Systems that store Unix time in a signed 32-bit integer can only count up to 2,147,483,647 seconds, which is reached at 03:14:07 UTC on 19 January 2038. After that the value overflows. Modern systems use 64-bit integers and are not affected.
Can I convert negative timestamps?
Yes. Negative values represent dates before 1 January 1970. For example, -86400 is 31 December 1969.
Does this tool use my data?
No. All conversions run in your browser using its built-in date and time-zone functions.