Timestamp to Date

What this tool does

This tool turns a Unix timestamp — a plain integer like 1700000000 — into a date a person can actually read. It auto-detects whether the number is in seconds or milliseconds, then shows the same instant five ways: the ISO 8601 string, the UTC string, your local string, a friendly relative time such as “3 hours ago”, and a field breakdown of the year, month, day, weekday, time and time-zone offset. A live-ticking current Unix timestamp sits at the top so you always have a reference value to hand. Every conversion happens in your browser — the timestamp never leaves your device.

Why you might need it

Unix timestamps are everywhere in software: database created_at columns, log files, JWT exp claims, API responses, cookie expiry values and event payloads. They are compact and time-zone-neutral, which is great for machines and useless for humans. When you are debugging a log line that says 1699999999 you need to know when that was, fast. Pasting the number here answers that immediately, and the relative-time line (“2 days ago”) tells you whether an event is recent without any mental arithmetic.

How to use it

1. Copy the timestamp you want to decode — from a log, a database row or an API response.
2. Paste it into the Unix timestamp box. The converted date appears instantly.
3. Leave Unit on Auto to let the tool guess seconds vs milliseconds, or pick Seconds or Milliseconds to force the interpretation.
4. Click Now to drop in the current timestamp if you just want to see today’s value.
5. Use the copy button on any output row to grab the ISO string, UTC string or any other value.

Common pitfalls

The single most common mistake is the seconds-versus-milliseconds mix-up. A timestamp of 1700000000 is November 2023, but 1700000000000 — the same digits with three zeros — is also November 2023 only because it is interpreted in milliseconds. Feed a millisecond value to a tool expecting seconds and you land tens of thousands of years in the future. Auto-detect handles the usual cases, but if a result looks absurd, flip the unit toggle. Another trap is the time zone: the local string depends on your operating system’s clock settings, so the same timestamp shown on two machines in different regions will read differently even though both are correct.

Tips and advanced use

For debugging, the Relative row is often the fastest signal — “in 5 minutes” versus “3 weeks ago” tells you at a glance whether a token is about to expire or a record is stale. When you need a value to paste into code or a test fixture, copy the ISO 8601 string: it is unambiguous, sorts correctly as text, and is accepted by virtually every language’s date parser. If you are comparing two events, convert both timestamps and read the field breakdown side by side rather than counting seconds. And because everything runs locally, it is perfectly safe to decode timestamps pulled from production logs or internal systems — none of that data is transmitted anywhere.