Current Epoch Time

The current Unix timestamp, live, in seconds and milliseconds. To turn any other value into a date, use the epoch time converter.

Current epoch time 1794977118
Seconds
1794977118
Milliseconds
1794977118000
UTC (ISO 8601)
2026-11-18T04:45:18Z
Your time zone
2026-11-18T04:45:18Z
RFC 2822
Wed, 18 Nov 2026 04:45:18 +0000

Values on this page were generated when it was built and refresh every second once JavaScript runs.

Runs in your browser. Nothing is sent.

How to use it:

  1. Read the current epoch time in the large clock. It updates every second.
  2. Press ms to switch to milliseconds, the format JavaScript and Java use.
  3. Press Copy to put the exact value on your clipboard, or copy any row below it.

Current Unix Timestamp in Seconds and Milliseconds

The current Unix timestamp is the number of whole seconds since 00:00:00 UTC on 1 January 1970. Today it has 10 digits. The same moment in milliseconds has 13 digits: the seconds value followed by three more digits for the fraction of a second. Both count from the same instant, so they never disagree.

Most command-line tools, databases and Python's int(time.time()) give you seconds. Browsers and the JVM count in milliseconds. If you are not sure which one an API expects, look at an example value from its documentation and count the digits.

The current timestamp in two units
UnitDigits todayExample at 2025-01-01T00:00:00Z
Seconds101735689600
Milliseconds131735689600000

Need to read a 13-digit value as a date? The milliseconds to date converter is built for exactly that.

Unix Time Now in UTC and Your Time Zone

The panel under the clock shows Unix time now as an ISO 8601 date in UTC, the same moment in your own time zone, and an RFC 2822 string. All of them describe one instant. Only the way it is written changes.

Your time zone is read from your browser, for example America/New_York or Asia/Karachi, and the offset follows that zone's daylight saving rules. The epoch time now is the same number for everyone. The local date and clock time are the only parts that depend on where you are.

How to Get the Current Timestamp in Python, JavaScript, SQL and Bash

Every language reads the current timestamp from the system clock in one line. These examples return seconds unless noted. The outputs show what each prints at 2025-01-01T00:00:00Z.

Python

import time

print(int(time.time()))      # seconds
print(time.time_ns())        # nanoseconds
Output at 2025-01-01T00:00:00Z
1735689600
1735689600000000000

More detail, including time zones and pandas, is in the Python timestamp guide.

JavaScript

console.log(Date.now());                     // milliseconds
console.log(Math.floor(Date.now() / 1000));  // seconds
Output at 2025-01-01T00:00:00Z
1735689600000
1735689600

The JavaScript timestamp guide covers the seconds vs milliseconds trap in browsers and Node.js.

SQL

-- MySQL
SELECT UNIX_TIMESTAMP();

-- PostgreSQL (returns a numeric with a fraction)
SELECT EXTRACT(EPOCH FROM now());

Bash

date +%s      # seconds
date +%s%3N   # milliseconds (GNU date)
Output at 2025-01-01T00:00:00Z
1735689600
1735689600000

On macOS, date +%s works the same way. The %N fraction is a GNU extension, so the BSD date that ships with macOS may not support it. Installing GNU coreutils gives you gdate, which does.

Why the Current Timestamp Is the Same Worldwide

The current timestamp is identical in every country because it counts seconds from one fixed instant, 00:00:00 UTC on 1 January 1970, not from a local midnight. A server in Tokyo and a laptop in London that read their clocks at the same moment get the same number, even though their wall clocks differ by hours.

That is the main reason systems store Unix time. You can compare two values, sort a log or compute a duration without ever thinking about time zones. Convert to local time only at the edge, when a person needs to read it. Chat tools rely on the same idea: the Discord timestamp generator sends one Unix value, and each reader's app shows it in their own zone.

The design has a few quirks worth knowing. Unix time skips leap seconds, so each day is exactly 86,400 seconds. It can be negative for dates before 1970. And systems that store it in a signed 32-bit integer will overflow in January 2038. For the background, read what epoch time is and why it starts in 1970.

Current Epoch Time FAQ

What is the current epoch time?

The current epoch time is the number of seconds since 00:00:00 UTC on 1 January 1970, right now. The clock at the top of this page shows it live and updates every second. Present-day values have 10 digits in seconds and 13 in milliseconds. Copy the value with the button next to it, or switch units with the ms toggle.

How accurate is the clock on this page?

It reads your device's system clock, which most operating systems keep in sync with internet time servers. That is usually accurate to well under a second. If your computer's clock is set wrong, the value shown here is wrong by the same amount, so check your system time settings if the number looks off.

Does the current Unix timestamp change with daylight saving time?

No. Unix time counts seconds on the UTC time scale, which has no daylight saving time. When clocks in your region jump forward or fall back, the local clock time changes, but the Unix timestamp keeps rising by exactly one every second. Only the conversion to local time is affected.

Why does my code return a 13-digit number?

Your language returns milliseconds. JavaScript's Date.now() and Java's System.currentTimeMillis() count milliseconds since the epoch, which gives 13 digits today. Divide by 1,000 and round down to get seconds, as in Math.floor(Date.now() / 1000). Python's time.time() returns seconds as a float, so int(time.time()) gives the 10-digit value.

Updated