Unix Timestamp Converter
Epoch Numbers Into Dates, and Dates Into Epochs

Jobs This Unix Timestamp Converter Handles for You

This Unix timestamp converter changes epoch numbers into dates you can read, and dates back into epoch numbers. The clock at the top shows the current Unix time, ticking every second. Every amount is spelled out on your own device, so it works even when you are offline after the page loads.

Timestamps turn up everywhere developers look. Logs, databases, API replies, JWT tokens and analytics exports all store time as one long number. That number is compact and easy to sort, but nobody can read 1735689600 at a glance. So this epoch converter shows it as a date, in UTC and in the time zone you choose.

It also answers the questions that come next: which weekday it was, which ISO week, how long ago, and whether the value still fits in a 32-bit field. Each output line comes with a copy button.

What the Unix Clock Really Measures

Unix time tallies seconds from midnight UTC on 1 January 1970, the instant called the Unix epoch. The count is the same everywhere on Earth at the same instant, because it has no time zone. Only the way you display it changes.

It also ignores leap seconds, so every day counts as exactly 86,400 seconds. That makes the arithmetic simple: add 86,400 for a day, 604,800 for a week. Moments before 1970 are simply negative numbers.

Seconds, Milliseconds or Nanoseconds?

The same moment can be written as 10 digits in seconds, 13 in milliseconds, 16 in microseconds or 19 in nanoseconds. JavaScript and Java usually use milliseconds, while PHP, Python and most databases use seconds. Go and some logging tools use nanoseconds.

The converter counts the digits and picks the unit for you, then tells you what it picked in the checks. If a value is ambiguous, choose the unit yourself from the menu. Long values are read with exact integer maths, so a 19-digit nanosecond timestamp keeps every digit.

Timestamp to Date in Any Time Zone

Pick a zone from the menu and every result follows it. The list holds every zone your browser knows, taken from the IANA time zone database, which records each country’s daylight saving rules and their history. Therefore a date in 1995 uses the rules of 1995, not today’s.

Each result shows the offset from UTC as well, such as UTC+05:00. In addition, the ISO 8601 line includes that offset, so the value can travel into another system without losing its meaning. That format follows RFC 3339, the profile of ISO 8601 most APIs expect.

Date to Timestamp, Even Around Clock Changes

Going the other way is where many converters slip. When clocks jump forward in spring, one hour of local time never happens. When they fall back in autumn, one hour happens twice. A naive tool silently picks something, and your scheduled job runs an hour off.

This converter checks both cases. A time that never happened is moved to the first real moment after the jump, and a time that happened twice uses the first of the two. Either way, the checks table says so in plain words.

The Year 2038 Problem

Plenty of older systems keep Unix time in a signed 32-bit integer. The largest value it holds is 2,147,483,647, which is 19 January 2038 at 03:14:07 UTC. One second later, such a counter wraps around to 1901. The checks table tells you whether each timestamp still fits, so you can spot risky database columns early.

Most modern systems already moved to 64-bit time, which lasts for billions of years. Still, small devices, old file formats and some database columns keep the 32-bit limit, so the check is worth a glance.

Epoch Converter Code for Common Languages

Getting the current timestamp is a one-liner almost everywhere. In JavaScript, Date.now() returns milliseconds, so divide by 1000 for seconds. In PHP use time(), in Python time.time(), and in a shell date +%s. MySQL has UNIX_TIMESTAMP(), and PostgreSQL has EXTRACT(EPOCH FROM now()).

Converting back is just as short, yet the time zone is where bugs hide. For example, JavaScript’s Date object always works in the visitor’s zone unless you ask for UTC. When a value looks one or more hours off, check it here in UTC first.

Turn a Full List of Timestamps Into Dates

Log files and exports rarely hold just one value. Open the list section, paste one timestamp per line, and the converter fills a table with the UTC date and the local date for each. Lines that are not timestamps are marked instead of stopping the whole list.

After that, save the table as a CSV for Excel or Sheets. If the data came as JSON, our JSON to CSV converter flattens it into columns first.

Where Timestamps Hide in Everyday Data

A JSON Web Token carries three of them: iat for when it was issued, nbf for when it becomes valid and exp for when it expires. Each of the three counts in seconds. So paste the exp value here, and you see at a glance whether a token has already expired.

Web servers use dates as well. The Expires and Last-Modified headers are written in the RFC 2822 style shown in the table, while most APIs return ISO 8601 or plain epoch seconds. Databases differ too: a MySQL TIMESTAMP column ends in 2038, whereas DATETIME and BIGINT columns do not.

Spreadsheets add one more twist. Excel and Google Sheets count days since 1899, so a date copied from a sheet may arrive as 45658. The serial row in the table gives you that number for any moment, which means you can paste it straight into a cell.