Current Unix Timestamp — Epoch Time Now

Unix Timestamp Now

——————————seconds since epoch
—————————————milliseconds since epoch
Ad

Get it in your code

JavaScript

Math.floor(Date.now() / 1000)

Python

import time; int(time.time())

Go

time.Now().Unix()

Rust

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

Java

Instant.now().getEpochSecond()

Bash / Terminal

date +%s

Need more languages? See all 16 language examples →

What is the current Unix timestamp?

The live number above is the current Unix timestamp in seconds — the number of seconds that have elapsed since January 1, 1970 at 00:00:00 UTC (the Unix epoch). It increments by 1 every second, everywhere in the world simultaneously, regardless of timezone. The millisecond version increments 1,000 times per second and is the format used by JavaScript's Date.now() and Java's System.currentTimeMillis().

Seconds vs. milliseconds — which do I need?

A 10-digit number (like 1708560000) is seconds. This is the standard format for Unix systems, databases (PostgreSQL, MySQL), JWT tokens, and most REST APIs. A 13-digit number (like 1708560000000) is milliseconds — used by JavaScript, Java, Android, and many browser APIs. When in doubt: 10 digits = seconds, 13 digits = milliseconds.

Why use Unix time instead of a formatted date?

Formatted dates like "2024-02-22 14:00:00" are ambiguous — is that local time? UTC? Which timezone offset? A Unix timestamp is always UTC and always unambiguous. You can sort, compare, and do arithmetic on timestamps with simple integer operations. That's why APIs, log systems, databases, and operating systems all use Unix time internally.

Convert a timestamp to a date

Have a timestamp you want to read as a human date? Use the full converter — paste the number and instantly see the date, time, timezone, day of week, ISO 8601 format, and relative time ("3 hours ago", "in 2 days").

Open the converter →
Ad