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
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 →