Epoch to Date Converter

A tool that converts Unix epoch timestamps (seconds, ms, us, ns) to readable dates in ISO 8601, RFC 2822, locale, and timezone-aware formats.

Yes. The converter inspects magnitude and picks seconds/ms/us/ns automatically. You can override manually at any time.

Yes. Switch to Bulk mode, paste one epoch per line, and download a CSV with ISO UTC, local time, day of week, ISO week, day of year, and relative time.

Yes, the Epoch to Date Converter is 100% free with no registration, no hidden fees, and no usage limits. All processing happens locally in your browser, ensuring complete privacy.

Absolutely. The Epoch to Date Converter processes everything client-side in your browser. No data is uploaded to or stored on any server. Your content remains private on your device at all times.

Yes, the Epoch to Date Converter is fully responsive and works on smartphones and tablets. You can use it on any device with a modern web browser -- no app download required.

No account or registration is needed. Simply open the Epoch to Date Converter in your browser and start using it immediately. There are no sign-up walls or usage restrictions.

Simply enter your input in the provided field, adjust any settings to your preference, and the tool will process it instantly. You can then copy the result to your clipboard or download it.

The Epoch to Date Converter works in all modern browsers including Chrome, Firefox, Safari, Edge, and Opera. For the best experience, use the latest version of your preferred browser.

A Unix epoch timestamp is the number of seconds that have elapsed since 00:00:00 UTC on 1 January 1970, known as the "Unix epoch." So 1700000000 means roughly 1.7 billion seconds after that reference point, which works out to 14 November 2023 at 22:13:20 UTC. Computers favor this format because it is a single timezone-free integer that is trivial to store, sort, and subtract, but the raw number tells a human almost nothing at a glance. The value is always counted in UTC, so the same integer represents one fixed instant worldwide; only the displayed wall-clock time shifts when you apply a timezone. Paste your number above and the converter instantly turns it into a readable ISO 8601, RFC 2822, and locale-formatted date so you never have to do the math by hand.

The quickest tell is digit count for the current era. A seconds timestamp for a recent date is 10 digits (around 1.7 billion), while a milliseconds timestamp is 13 digits because it carries three extra digits of precision. Microseconds run to 16 digits and nanoseconds to 19. This converter applies that same magnitude logic automatically: it inspects the size of your number and picks seconds, milliseconds, microseconds, or nanoseconds for you, then labels which unit it chose so there is no silent guessing. JavaScript's Date.now() returns milliseconds, the Unix date +%s command returns seconds, and Go's UnixNano() returns nanoseconds, which is why mismatches happen. If the auto-detection picks wrong on an unusually small value, lock the unit manually with one click and the date updates instantly.

An epoch value points to one fixed instant in absolute time, but the clock-on-the-wall reading of that instant depends on where you stand. The integer itself never changes; only its presentation does. For example, 1700000000 is 22:13:20 in London but 17:13:20 in New York and 03:43:20 the next morning in Mumbai (IST), because each region sits at a different offset from UTC. Daylight-saving rules complicate this further, shifting some zones by an hour for part of the year. This converter renders your timestamp against UTC, your browser's local zone, or any of 17 named IANA zones, and it applies the correct daylight-saving offset automatically using the browser's internationalization engine. Pick a timezone above and the ISO, locale, day-of-week, and relative-time outputs all update to match that zone.

ISO 8601 is the international standard for machine-readable dates, written as 2023-11-14T22:13:20.000Z, where the trailing Z marks UTC. Its year-month-day ordering sorts correctly as plain text and is the safest choice for APIs, databases, and logs because it is unambiguous worldwide. RFC 2822 is the older format used in email headers and HTTP, written as Tue, 14 Nov 2023 22:13:20 GMT, with a spelled-out weekday and month that reads more naturally to people but is harder for machines to parse. They describe the same instant, just for different audiences. This converter outputs both side by side, plus a full locale string and a date-only and time-only breakdown, each with its own copy button. Convert your epoch above and grab whichever format your system expects.

A JWT stores its expiry in the exp claim as a Unix epoch value in seconds, and its issued-at time in the iat claim the same way. These are bare integers like 1735689600, so you cannot read them directly inside the token payload. Paste the exp value into this converter and it returns the exact expiry date and time in your chosen timezone, plus a relative time such as "in 3 days" or "2 hours ago" that tells you at a glance whether the token is still alive. Because exp claims are always in seconds, leave the unit on Auto and the tool detects it correctly. If you are auditing several tokens, switch to the Bulk tab, paste one exp value per line, and download a CSV with the ISO UTC time and relative time for every token at once.