Unix Timestamp Now

The number above is the count of seconds since the Unix epoch, 00:00:00 UTC on 1 January 1970. It is not a local time and it has no zone: it names one instant that every machine on earth agrees on, which is exactly why it is what logs, tokens, caches and APIs record.

The second line is the same instant in milliseconds — the same value multiplied by 1000. Which one you want depends on what will read it: 10-digit seconds for most Unix tooling, Python, Go and PostgreSQL; 13-digit milliseconds for JavaScript, Java and most log pipelines.

Need a specific moment rather than this one? Use the date to timestamp converter, or go the other way with the timestamp to date converter.

Every language has a one-liner for this, and they all return the same instant — the only thing that varies is the unit.

JavaScript — seconds

Math.floor(Date.now() / 1000)Date.now() on its own returns milliseconds.

Python — seconds

int(time.time())

PHP — seconds

time()

Go — seconds

time.Now().Unix()

Java — seconds

Instant.now().getEpochSecond()

C# — seconds

DateTimeOffset.UtcNow.ToUnixTimeSeconds()

Ruby — seconds

Time.now.to_i

Rust — seconds

SystemTime::now().duration_since(UNIX_EPOCH)?.as_secs()

Bash — seconds

date +%s

Bash — milliseconds

date +%s%3NGNU coreutils; macOS needs gdate from coreutils.

PostgreSQL — seconds

SELECT EXTRACT(EPOCH FROM now())::bigint;

MySQL — seconds

SELECT UNIX_TIMESTAMP();

Each returns the same instant; only the unit differs. To convert one of these values back into a readable date, use the timestamp to date converter, and to build a tag that shows the time in each reader’s own zone, the Discord timestamp generator.