Current Unix time, live

This is the number of seconds since 1 January 1970 UTC, right now, according to your device's clock.

What you are looking at

The big number is the Unix time: how many seconds have passed since 00:00:00 UTC on 1 January 1970, not counting leap seconds. The second number is the same instant in milliseconds. Both come from your device's clock, so they are only as right as that clock is. If your phone or computer has the wrong time, so do these numbers.

What it is used for

• Logs and databases: a timestamp column is easy to sort and compare.
• Cache expiry and tokens: "valid until 1794600000" is a clear rule.
• APIs: many services expect or return timestamps in seconds or milliseconds.
• Scheduling and debugging: you can check how far apart two events were by subtracting.

Quick facts about the number

• It grows by one every second and by 86,400 every day, because Unix time counts every day as exactly 86,400 seconds.
• It has 10 digits since September 2001 and will have 10 digits until November 2286.
• The 32-bit signed form runs out in January 2038 (see the page on the Year 2038 problem).
• Milliseconds, as used by JavaScript, have 13 digits today.

Check your clock

If you suspect your clock is off, compare the UTC time shown here with a reliable time source such as the time page of your country's national timekeeping institute. In India, the National Physical Laboratory keeps the national time.

Common mistakes

1. Using the local time zone's "now" when you meant UTC.
2. Mixing up seconds and milliseconds.
3. Trusting a device clock for security decisions: servers should use their own synchronised clocks.

This is an independent guide. It is not connected with the IERS, BIPM, IANA, NIST or any company named here. Facts were read on 14 November 2026 from the sources named on each page; calculated values come from Python.