EpochLab

Epoch Converter

Convert epoch time, in either direction

The same conversion as a Unix timestamp, plus the other epochs a number might belong to — Windows FILETIME, .NET ticks, Excel serials, Julian days — ranked by how plausible each reading is.

Questions people ask

The things that come up about epoch converters, answered plainly.

Why 1970?

It was a convenient recent round year when early Unix was being built, and the choice stuck. It carries no astronomical meaning — which is why other platforms picked other zero points, and why a FILETIME counts from 1601 and an Excel serial from 1900.

What if my number is not Unix time?

The converter checks it against twelve epochs and ranks the readings by plausibility, so a Windows FILETIME or a .NET tick count is recognised rather than mangled into a date in the year 500,000.

Related tools

Seconds, milliseconds, microseconds and nanoseconds, in both directions.

Unix Timestamp ConverterPaste a timestamp and get the date; paste a date and get the timestamp. Seconds, milliseconds, microseconds and nanoseconds are detected from the digit count, and the guess is shown so you can override it.
Excel Date ConverterA spreadsheet serial to a calendar date and back, in both the 1900 and 1904 systems — with the phantom leap day of 1900 flagged where it matters.
Julian Date ConverterThe astronomer's continuous day count, both ways — including the half-day offset that catches everyone, since a Julian day begins at noon rather than midnight.
Timestamp to DateOne field, one answer — the timestamp as a date and time in your zone, in UTC, and in about thirty other encodings you might need to paste somewhere.

All 160 tools · More in unix time & epochs