The Unix Timestamp Converter translates Unix epoch values to readable dates and back, entirely in your browser.
A live ticking counter shows the current Unix timestamp in seconds. Enter any timestamp in the first section and click Convert — the tool auto-detects whether it's in seconds, milliseconds, microseconds, or nanoseconds, then shows the equivalent GMT date, your local timezone date with offset, and a human-readable relative time like '3 hours ago' or 'in 2 days'.
The second section goes the other direction: fill in year, month, day, hour, minute, and second fields, toggle whether to treat them as UTC or local time, and convert to get the Unix timestamp in all four precisions.
A quick-reference strip lets you click any notable timestamp — the Unix epoch (0), Y2K, the 32-bit overflow date (2038), or the current second — and instantly decode it.
All conversion runs locally. Nothing is sent to a server.
To decode a timestamp: paste it into the first field and click Convert. Leave it blank to decode the current time.
The result table shows GMT, your local timezone with offset, and relative time.
To encode a date: fill in the date/time fields in the second section, choose UTC or local, and click Convert.
Use the quick-reference buttons to instantly decode notable timestamps like the Unix epoch or Y2K.
A Unix timestamp is the number of seconds (or milliseconds, microseconds, or nanoseconds) that have elapsed since 00:00:00 UTC on January 1, 1970 — called the Unix epoch. It is the most common way to represent a specific moment in time across programming languages and systems.
By magnitude. Timestamps under 10 digits are seconds; 10–12 digits are milliseconds; 13–15 digits are microseconds; 16+ digits are nanoseconds. This covers all realistic dates between 1970 and ~2100.
32-bit signed integers can only store values up to 2,147,483,647. That corresponds to January 19, 2038 at 03:14:07 UTC. Systems using 32-bit timestamps will overflow on that date. Most modern systems use 64-bit timestamps, which extend the range by billions of years.
For practical purposes they are the same — both represent time at 0° longitude with no daylight-saving offset. UTC (Coordinated Universal Time) is the modern international standard; GMT (Greenwich Mean Time) is the historical predecessor. They differ by at most 0.9 seconds.
Yes. The tool reads your browser's timezone (via Intl.DateTimeFormat) and displays the equivalent local time with the UTC offset.