Unix Epoch Converter

The ultimate developer tool. Seamlessly convert epochs to human dates and vice versa.

Feedback

Current Unix Epoch

1793176546

Timestamp to Date

Date to Timestamp

Target Date & Time
Time Format

Mastering the Epoch

If you are a software engineer or data scientist, you will inevitably encounter 10-digit numbers representing time. Dealing with these manually is virtually impossible without an epoch converter.

How to Use This Tool

  1. Step 1: Paste Timestamp - Enter a 10-digit Unix epoch to see the human-readable date and time.
  2. Step 2: Pick Calendar Date - Use the date picker to generate the corresponding Unix timestamp instantly.
  3. Step 3: Copy to Clipboard - Click any result to copy it for use in your code, database, or logs.

Deeper Dive

Want to learn more about how Unix time works and avoid timestamp pitfalls?

Read the full guide

How Unix time works

Unix time counts the seconds that have passed since 00:00:00 UTC on 1 January 1970, a moment known as the epoch. It is a single number with no time zone attached, which makes it a simple way for computers to store, compare and sort moments in time. A time zone only matters when the number is shown as a date for people. Unix time does not count leap seconds.

Many systems store time in milliseconds instead of seconds. A current timestamp with 10 digits is in seconds, while one with 13 digits is in milliseconds, as returned by JavaScript's Date.now(). Dividing a millisecond value by 1,000 gives seconds.

Worked examples

Three landmark timestamps

  • 0 is 1 January 1970, 00:00:00 UTC
  • 1,000,000,000 is 9 September 2001, 01:46:40 UTC
  • 1,700,000,000 is 14 November 2023, 22:13:20 UTC

Tips and common mistakes

  • If a converted date is off by a few hours, the usual cause is the time zone: the timestamp is in UTC, but the display may use your local time.
  • If a date comes out in January 1970, you probably passed seconds where milliseconds were expected, or the value is 1,000 times too small.
  • The year 2038 problem: systems that store the timestamp in a signed 32-bit integer run out of range on 19 January 2038 at 03:14:07 UTC. Modern systems use 64 bits, which does not run out in any practical sense.

Frequently Asked Questions

The Unix epoch (or Unix time) is the number of seconds that have elapsed since January 1, 1970 (midnight UTC/GMT). It is a system for describing a point in time, widely used in operating systems and file formats.
Because many older computer systems store Unix time as a signed 32-bit integer, they will overflow on January 19, 2038. Modern systems use 64-bit integers to avoid this.
No. Unix time specifically ignores leap seconds. Every day is treated as if it contains exactly 86,400 seconds.