Unix Timestamp Converter

Turn epoch seconds or milliseconds into a readable date, or the other way round, in the timezone you care about.

the picked time is read in the timezone above
—

How to use the unix timestamp converter

  1. Paste a timestamp (seconds or milliseconds are detected), or pick a date.
  2. Choose the timezone you want the result in.
  3. Read the ISO 8601, RFC 2822 and local forms, plus the relative time.
  4. Copy whichever format your system needs.

A Unix timestamp is the number of seconds since 1970-01-01T00:00:00Z, excluding leap seconds. It is timezone-free, which is exactly why databases and APIs store it — and why it looks meaningless when you print it. Milliseconds are used by JavaScript's Date.now() and by most JSON APIs, so a 13-digit number almost always means milliseconds.

Two traps cause most of the confusion. First, some systems store seconds while others store milliseconds; a factor of 1000 turns 2026 into 1970-01-01 or into the year 56000. This tool detects the magnitude, and lets you force either unit. Second, "local time" is not a property of the timestamp at all — it depends entirely on the timezone you format it in, which is why the timezone selector sits next to the input.

Useful reference points

For durations and cron schedules, keep in mind that local-time arithmetic breaks twice a year wherever daylight saving applies; the UTC forms are the safe ones to store.

Frequently asked questions

Does it handle milliseconds?

Yes — 13-digit values are treated as milliseconds automatically, and you can switch units manually.

Which timezone does it use by default?

The timezone of your browser; pick another from the list to see the same instant formatted elsewhere.

What about leap seconds?

Unix time ignores them. Two timestamps one second apart can therefore straddle a leap second without reflecting it.

Can I convert a date back to a timestamp?

Yes, pick a date and time in the calendar field and read off the epoch value in both units.

Related tools