Developer Tools

Unix Timestamp Converter

Get current Unix timestamp and convert dates.

How to Use Unix Timestamp Converter

1

Paste the numeric Unix timestamp into the box, using 10 digits for seconds or 13 for milliseconds.

2

Select UTC or your local timezone so the readable date lines up with the logs you are reading.

3

Click the "Process" button to expand it into a full date, time, day of week, and ISO string.

4

Use the live counter to grab the current epoch value when you need the timestamp for right now.

Features

Shows the current Unix time updating every second, in seconds and milliseconds
Accepts negative timestamps for dates before 1970 rather than rejecting them
Renders the day of week, ISO 8601 value, and UTC offset beside the readable date
Copes with the 10-digit and 13-digit mix that trips up JavaScript date handling
Useful for JWT exp and iat claims, Redis TTL values, and cron schedules
No upload, no account, and the conversion is instant in the browser

Frequently Asked Questions

It is free, needs no registration, and everything is computed locally in your browser. Nothing you paste is transmitted or written to a log, so it is safe to check timestamps derived from production data.
Two separate problems. Passing seconds where milliseconds are expected, or vice versa, gives a date near 1970 or far in the future. Passing a bare integer to the Date constructor treats it as milliseconds in every modern engine, so convert seconds by multiplying by 1000.
No. Unix time deliberately ignores leap seconds and drifts a little behind atomic time, which keeps the arithmetic simple and predictable. Most systems follow that convention, so it is rarely the cause of a timestamp mismatch in practice.
The live counter at the top of the tool shows it, updating every second in both seconds and milliseconds. Click it to copy the value, which is useful for setting an expiry in a config file or a Redis EXPIRE command.

About Unix Timestamp Converter

Unix time counts seconds since midnight UTC on 1 January 1970, and nothing since. That single definition is why a timestamp means the same thing in every language and every timezone, which is exactly why so much infrastructure stores it. The cost is that it is unreadable on its own, and it is the tool you reach for whenever a raw integer appears in a log, an API field, or a config value.

This converter focuses on that job. It shows the current epoch value updating live, in both seconds and milliseconds, and expands any value you paste into a full date, time, day of week, ISO 8601 string, and UTC offset. It accepts negative timestamps too, so dates before 1970 decode correctly instead of being rejected.

It also handles the 10-digit versus 13-digit split that causes so much confusion. PHP and most databases give you 10 digits, JavaScript gives you 13, and feeding one to the other produces a date in 1970 or the year 55,000. The converter identifies the unit from the length so you see the real instant rather than a nonsense result. Note that Unix time ignores leap seconds, so it drifts slightly from atomic time by design.

When to Use This Tool

  • Reading exp and iat claims from a JWT while debugging an auth failure
  • Setting a Redis EXPIRE or cache lifetime value in seconds
  • Checking the next_run or scheduled_at epoch in a job queue record
  • Writing a timestamp filter for an API that expects epoch seconds
  • Grabbing the current epoch value to seed a fixture or a test case