admin@likeapro.dev: ~/epoch — zsh

// admin tools · 06

Epoch clock

Unix time ⇄ human time with auto-detected units, ISO 8601, RFC 2822 and world timezones — plus a cron explainer that tells you exactly when your job fires next.

// runs locally — nothing is uploaded

unix epoch · seconds
0000000000
ms 0000000000000
—

epoch → human

accepts s · ms · µs · ns — unit auto-detected by digit count

human → epoch

CONVERT local only · 0 bytes sent --:--:--

How it works

What it does

A live Unix clock and converter between epoch timestamps and human dates, with a world-timezone table and a cron expression explainer that lists the next run times. Timezones come from your browser's built-in Intl database, so it works offline and nothing is sent anywhere.

How to use it

  1. The header shows the current epoch in seconds and milliseconds. Copy either, or pause the clock.
  2. In --convert, paste a timestamp to see it as UTC, your local time, ISO 8601, ISO with offset, RFC 2822 and relative time. Or pick a date and time to get its epoch in the chosen timezone.
  3. --zones shows that instant around the world. Select a row to make it the active timezone.
  4. --cron explains a five-field expression in plain English and lists its next five runs in your timezone. Presets cover common schedules.

How timestamps are read

The unit is inferred from the number of digits: up to 11 digits are seconds, 12–14 milliseconds, 15–17 microseconds and 18 or more nanoseconds. That covers date +%s, JavaScript's Date.now(), Python's time.time_ns() and most log formats. Microsecond and nanosecond values are parsed with BigInt so no precision is lost before scaling. Negative values (before 1970) and fractional seconds are accepted.

Converting a wall-clock time in a timezone to an epoch uses a two-pass offset correction, so daylight-saving transitions resolve correctly.

Cron syntax supported

fields
minute hour day-of-month month day-of-week
operators
*, ranges a-b, lists a,b,c, steps */n and a-b/n
names
JAN–DEC and SUN–SAT
macros
@hourly, @daily, @weekly, @monthly, @yearly

When both day-of-month and day-of-week are restricted, the job runs when either matches. That is classic Vixie cron behaviour, and it often surprises people. Run times that fall in a daylight-saving gap are skipped, as cron daemons do.

FAQ

What is Unix time?

The number of seconds since 00:00:00 UTC on 1 January 1970, ignoring leap seconds. It's the same everywhere in the world at a given instant. Timezones only affect how it's displayed.

What about the year 2038 problem?

Signed 32-bit seconds overflow at 2147483647, which is 03:14:07 UTC on 19 January 2038. Paste that value to see it. Modern systems use 64-bit time, and JavaScript dates reach about ±273,000 years.

Why does my cron job run at an unexpected hour?

Cron runs in the server's timezone, which is often UTC. Check the next-run list with the timezone set to match your server, not your laptop.