Current Unix Timestamp

The current Unix timestamp is the number of seconds since 1 January 1970 UTC at this very moment. It ticks once per second and is the canonical way to record “now” in a portable, zone-independent form.

The live clock below updates in real time. Copy the seconds or milliseconds value, or grab the one-liner for your language further down the page.

Worked example

Input 1700000000 converts to 1700000000:

UTC
Tue, 14 Nov 2023, 22:13:20 UTC
ISO 8601 (UTC)
2023-11-14T22:13:20.000Z
RFC 3339 (UTC)
2023-11-14T22:13:20Z
RFC 2822
Tue, 14 Nov 2023 22:13:20 +0000
Unix seconds
1700000000
Unix milliseconds
1700000000000
Microseconds
1700000000000000
Nanoseconds
1700000000000000000
Hex (seconds)
0x6553f100
Binary (seconds)
1100101010100111111000100000000

Code examples

JavaScript
const d = new Date(1700000000000);
console.log(d.toISOString()); // 2023-11-14T22:13:20.000Z
Math.floor(Date.now() / 1000); // current epoch
Python
from datetime import datetime, timezone
print(datetime.fromtimestamp(1700000000, tz=timezone.utc))  # 2023-11-14T22:13:20.000Z
import time; int(time.time())
Go
package main
import ("fmt"; "time")
func main() {
  fmt.Println(time.Unix(1700000000, 0).UTC()) // 2023-11-14T22:13:20.000Z
  fmt.Println(time.Now().Unix())
}

See all 14 languages on the code examples pages.

Frequently asked questions

What is the current Unix timestamp?
It is the live count of seconds since the 1970 epoch, shown and updated in real time above. Milliseconds, microseconds, and nanoseconds are also provided.
How do I get the current timestamp in code?
Use Math.floor(Date.now()/1000) in JS, int(time.time()) in Python, time.Now().Unix() in Go — see the snippets below.
Is the timestamp the same in every country?
Yes. Unix time is defined in UTC, so the integer is identical worldwide at any given instant.

Related conversions

Copied