Unix Timestamp Converter

Convert a Unix epoch timestamp into a readable date — in your local timezone and UTC — or convert a date back into epoch seconds and milliseconds. The current timestamp updates live.

epoch-converter · runs locally
current unix time (s)

What this timestamp converter does

Epoch timestamps are everywhere machines record time — server logs, JWT exp claims, database rows, analytics events, API responses — but a value like 1753142400 means nothing to a human at a glance. This converter translates in both directions: timestamp to readable date (shown in your local timezone, UTC and ISO 8601) and calendar date back to epoch seconds and milliseconds.

Unit detection is automatic. JavaScript and Java tend to use milliseconds (13 digits) while Unix tools, Python and most databases use seconds (10 digits); paste either and the tool identifies which one you gave it.

How to convert a Unix timestamp

  1. Paste the epoch value into the left field and click Convert timestamp.
  2. Read the result in local time, UTC, and ISO 8601 format.
  3. To go the other way, pick a date and time on the right and click Convert date.

Reading timestamps in logs and tokens

When debugging, the two timestamps you decode most often are log entry times (to line events up across services — compare them in UTC, not local time) and token expiry claims (an exp in the past explains a mysterious 401). The live current-timestamp readout at the top of the panel gives you the “now” to compare against.

Frequently asked questions

What is a Unix timestamp?

A Unix timestamp (or epoch time) is the number of seconds elapsed since 00:00:00 UTC on 1 January 1970, not counting leap seconds. It is the standard machine representation of time in operating systems, databases, log files and APIs.

How do I know if a timestamp is in seconds or milliseconds?

Count the digits. Current times in seconds have 10 digits; in milliseconds they have 13. This converter detects the unit automatically: values of a trillion or more are treated as milliseconds.

Why does the converted date differ from what a teammate sees?

The timestamp itself is timezone-independent, but its human-readable form depends on the timezone used to display it. This tool shows both your local time and UTC so you can compare — a 5-hour difference from a colleague is a timezone display difference, not a data problem.

What is the year 2038 problem?

Systems that store epoch seconds in a signed 32-bit integer overflow on 19 January 2038. Modern systems use 64-bit values, which are safe for roughly 292 billion years, but old embedded systems and legacy databases can still be affected.