a quiet little utility — no sign-up, no fuss
What’s the time now?
Right now, in your local timezone.
Right now, in epoch seconds
Milliseconds
paste a timestamp — seconds, milliseconds, microseconds or nanoseconds are detected automatically.
Nothing to convert yet — type or paste a timestamp.
pick a date and time in your local timezone — get the timestamp back in seconds and milliseconds.
a one-minute primer on the number behind every timestamp on the internet.
Unix epoch time counts the number of seconds that have passed since 00:00:00 UTC on 1 January 1970 — the “birth of Unix.” That single integer is how operating systems, databases, and APIs keep track of moments in time without worrying about timezones, daylight saving, or calendar quirks.
Because it’s just a number, epoch time is easy to store, compare, and do arithmetic on. A timestamp of 0 is the epoch itself; 1735689600 is midnight UTC on 1 January 2025. Negative values represent moments before 1970.
Modern systems often need finer resolution, so you’ll also meet epoch time in milliseconds, microseconds, and nanoseconds. This converter detects which one you pasted and converts accordingly — so you never have to count zeros by hand.
The Y2038 problem
Systems that store epoch seconds as a signed 32-bit integer roll over on 19 January 2038. Most modern platforms have since moved to 64-bit time, but the “Y2K38” boundary is still worth knowing about.
the handful of things people ask most often about converting timestamps.
plain-English guides to the things that trip people up when working with timestamps.