Epoch Converter: Epoch Time to UTC and Local Date

What does 1609459200 mean in a log file? It is Unix epoch time, a count of seconds from January 1, 1970, 00:00:00 UTC. Computers love it. People cannot read it. The Epoch Converter turns the number into a date and shows a live epoch clock above it.

You paste an epoch value and get GMT/UTC time, your local time, and an ISO 8601 string. It is a one-way tool, from number to date. It fits developers, support staff, and anyone reading database or server records.

Table of Contents

• What the Epoch Converter Does
• How to Use It, Step by Step
• How the Tool Reads Your Number
• The Epoch Formula
• Worked Examples in UTC
• How to Read the Results
• Epoch Time, Other Epochs, and Common Mistakes
• Limitations and Assumptions
• FAQs About the Epoch Converter

What the Epoch Converter Does

The page has a text input, a Unit select, two buttons, three live cards, and four output boxes.

• Enter Epoch Timestamp: a text box that starts at 1609459200.
• Unit: a select with Auto, Seconds, and Milliseconds.
• Convert Timestamp runs the conversion. It also runs while you type, and the Enter key works too.
• Set Current Time fills the box with the current epoch. You get whole seconds, or milliseconds when Unit is Milliseconds.
• Live Epoch (Seconds) and Live Epoch (Millis) update every second.
• Browser Time Zone shows your zone name and its current UTC offset, such as America/New_York (UTC-04:00).
• GMT / UTC Time, Your Local Time, ISO 8601 String, and Unit Used show the result.

The tool does not turn a calendar date into an epoch number. For that, use the Unix timestamp converter or the Unix timestamp generator.

How to Use It, Step by Step

1. Type or paste your number into Enter Epoch Timestamp.
2. Keep Unit on Auto, or pick Seconds or Milliseconds.
3. Read GMT / UTC Time for the universal reading of that moment.
4. Read Your Local Time to see the same moment on your device clock.
5. Copy the ISO 8601 String if you need a standard format for code.
6. Press Set Current Time to see the present moment as a date.

How the Tool Reads Your Number

In Auto mode, the tool compares the absolute value of your number with 1,000,000,000,000. Anything below that is seconds, so it is multiplied by 1,000. Anything at or above that is milliseconds. The Unit Used box tells you which choice it made.

A 10-digit value is almost always seconds, and a 13-digit value is almost always milliseconds. Negative numbers follow the same rule, so a large negative value in milliseconds works. Small millisecond values, such as 86400000, look like seconds, so pick Milliseconds for them.

The Epoch Formula

JavaScript stores dates as milliseconds since the epoch. The tool scales seconds up to milliseconds and builds a date from them.

• Seconds input: milliseconds = value × 1,000. Milliseconds input is used as is.
• Fractions are kept, so 1609459200.5 gives .500 in the ISO string.

Worked Examples in UTC

The UTC and ISO columns are the same for every reader. Only the local box changes by time zone.

Take Omar, who reads 1609459200 in a New York browser. January 1, 2021 at 00:00 UTC is 7:00 PM on December 31, 2020 there. His local box shows Thu, 31 Dec 2020 19:00:00 UTC-05:00 (America/New_York), while the UTC box shows the new year.

How to Read the Results

GMT / UTC Time uses the long format with the weekday and the word GMT. For this tool, GMT and UTC mean the same thing.

Your Local Time uses a fixed English layout, whatever your device language. It ends with the UTC offset and zone name, so you can see which zone produced it.

ISO 8601 String shows the date as year, month, day, then time with milliseconds. The final Z means UTC. Unit Used says whether the number was read as seconds or milliseconds, and whether Auto or your choice decided it.

Epoch Time, Other Epochs, and Common Mistakes

Unix epoch time ignores leap seconds. Each day counts as exactly 86,400 seconds. That keeps the math simple, and it is why a timestamp has no time zone of its own.

Some systems use another starting point. Windows file times, for example, begin on January 1, 1601. That is 11,644,473,600 seconds before the Unix epoch. This tool only understands the 1970 epoch.

The most common error is a unit mix-up. Pasting a 16-digit microsecond value, such as 1700000000000000, is read as milliseconds. The tool then shows a date in the year 55840. A 19-digit nanosecond value is outside the date range, so the output boxes show N/A and a message.

Once you have the date, the day name finder can tell you the weekday for any calendar date. To move the result into another zone, use the time zone converter. If you need a different date layout, try the date formatter. You can find related tools in the unit and time converters hub.

Limitations and Assumptions

• Conversion goes one way only. There is no date picker.
• Auto cannot tell small millisecond values from seconds. Choose Milliseconds for numbers under 1,000,000,000,000.
• Only plain numbers work: digits, an optional minus sign, and optional decimals. Hex, exponent forms like 1e9, commas, and spaces are rejected.
• Bad input or a value beyond plus or minus 8,640,000,000,000,000 milliseconds shows N/A and a message.
• The Browser Time Zone card shows your device zone. It is not a setting you can change.

FAQs About the Epoch Converter

This calculator gives general estimates only and is not professional advice. Reviewed for general accuracy by Prof. Dr. Khalil Mudassar, PhD.