Everything timestamp, in one place
A number like 1721145600 is not self-describing.
Unix seconds? Milliseconds? An Excel serial, a Windows FILETIME, a Julian day? EpochLab reads all twelve epochs, tells you which is most likely and why, then explains the instant it lands on.
Paste anything
19 formats recognised. Paste or press Enter to open it.
Your zone
Resolving your zone…
Where we are
Waiting for the clock…
The same moment at four resolutions
Memorise the digit ladder: 10, 13, 16, 19.
Signed 32-bit time runs out on 2038-01-19T03:14:07Z
Does this affect me?
At that instant a time_t holding 2,147,483,647 increments once more and wraps to −2,147,483,648, which reads as 1901-12-13T20:45:52Z. Modern 64-bit systems are fine; the exposure is embedded firmware, old filesystem formats, 32-bit database columns and any protocol that pinned the field at four bytes.
The rest of the lab
140 calculators
One page per question: business days, ages, week numbers, sunrise, cron, timesheets.
Open →Convert & explain
Twelve epochs, a dozen text formats, and the reasoning behind every reading.
Open →Batch decode
Paste a whole log column. Export as CSV, JSON or Markdown.
Open →Ranges & durations
Two instants in, every unit out, including working days and DST crossings.
Open →World clock board
One instant across every zone, with a scrubbable meeting planner.
Open →Format playground
Live-render strftime and moment patterns, with a clickable token reference.
Open →Epoch trivia
Landmarks, overflow cliffs, palindromes, and your own seconds alive.
Open →Questions people ask
What a timestamp is, and why the numbers look the way they do.
What is a Unix timestamp?
A Unix timestamp is a count of seconds since 1 January 1970 at 00:00:00 UTC, known as the Unix epoch. It names one instant on the timeline with no time zone attached, which is what makes it unambiguous to store and transmit.
How do I tell whether a number is in seconds, milliseconds, microseconds or nanoseconds?
Count the digits. For dates around the present, ten digits is seconds, thirteen is milliseconds, sixteen is microseconds and nineteen is nanoseconds. EpochLab ranks a pasted number across all twelve epochs it knows and explains why one reading is more likely than the others.
Why does the Unix epoch start in 1970?
1970 was simply a convenient recent round year when early Unix was being built, and the choice stuck. It carries no astronomical or calendrical meaning; other platforms picked other zero points, which is why a Windows FILETIME counts from 1601 and an Excel serial from 1900.
What is the year 2038 problem?
A timestamp stored in a signed 32-bit integer runs out at 03:14:07 UTC on 19 January 2038. One second later it wraps to a negative number that reads as December 1901. Modern 64-bit systems are unaffected; the exposure is embedded firmware, old file formats and any protocol that pinned the field at four bytes.
Does EpochLab send the timestamps I paste anywhere?
No. Every conversion, export and share card is computed in your own browser. Nothing you paste is uploaded, logged or transmitted, and no account is required.