Epoch Clock

The current Unix timestamp, live, in seconds and milliseconds.

About Epoch Clock

The current Unix timestamp, updated every second, in seconds and milliseconds, with the same instant as ISO 8601, local time and RFC 2822, plus code snippets.

How to use

  1. The large number is the current Unix time in seconds; press Copy to take it.
  2. The table under it shows the same instant in milliseconds, as an ISO 8601 UTC string, in your browser's time zone and in RFC 2822 form, each with its own copy button.
  3. The code panel shows how to get the current epoch in JavaScript, Python, Go, Java, C#, PHP, Ruby, Rust, bash, PostgreSQL and MySQL.
  4. To convert a specific timestamp or date rather than now, use the link to the Unix to UTC converter.

What it does

  • Reads the clock with Date.now() once a second, so the display is as accurate as your computer's clock.
  • The Unix time is the number of seconds since 1970-01-01T00:00:00Z, not counting leap seconds. It is the same everywhere in the world; only the local time row depends on your zone.
  • Milliseconds are what JavaScript, Java and most logging systems use; seconds are what most APIs, JWTs and Unix tools use. Divide by 1,000 to go from one to the other.

Example

Seconds        1761643200
Milliseconds   1761643200000
ISO 8601       2025-10-28T09:20:00.000Z
RFC 2822       Tue, 28 Oct 2025 09:20:00 +0000

Privacy

The time comes from your own computer's clock. No request is made, and nothing is stored.

Frequently asked questions

What is the Unix epoch?
Midnight UTC on 1 January 1970, the instant from which Unix time counts. A Unix timestamp is the number of seconds (or milliseconds) elapsed since then, ignoring leap seconds, so the same number names the same moment in every time zone.
Is a Unix timestamp in seconds or milliseconds?
Traditionally seconds, which is what C, PHP, Python's time.time() and most REST APIs use. JavaScript's Date.now() and Java's System.currentTimeMillis() return milliseconds, so a 13-digit number is milliseconds and a 10-digit number is seconds.
What is the year 2038 problem?
Systems that store Unix time in a signed 32-bit integer overflow at 2,147,483,647 seconds, which is 03:14:07 UTC on 19 January 2038, and wrap to 1901. Modern operating systems and languages use 64-bit time values, so only old embedded systems and file formats are affected.