Konverter Unix Timestamp

Konversi antara Unix timestamp dan tanggal yang dapat dibaca

Unix timestamp saat ini

1787885315Detik
1787885315404Milidetik

Epoch ke Tanggal

Tanggal ke Epoch

Data berdasarkan database IANA.

Frequently Asked Questions

What is a Unix timestamp?

A Unix timestamp is the number of seconds that have elapsed since 00:00:00 UTC on January 1, 1970 (the Unix Epoch), not counting leap seconds. It is the standard way computers represent a point in time, and it is the same in every timezone — 1724000000 means the same instant in Tokyo, London, and New York.

What is the current Unix timestamp?

The live counter at the top of this page shows the current Unix time, updating every second. In code, get it with Date.now()/1000 in JavaScript (note: JS returns milliseconds), time.time() in Python, or System.currentTimeMillis()/1000 in Java.

How many digits does a Unix timestamp have?

Seconds-based timestamps have 10 digits until November 2286 (e.g. 1724000000). A 13-digit number is almost always milliseconds (JavaScript’s Date.now()), and 16 digits means microseconds. If your database shows 13 digits, divide by 1000 to get seconds.

How do I convert a Unix timestamp to a date?

Paste the number into the converter above — it prints the UTC time and your local time side by side. In code: new Date(ts * 1000) in JavaScript, datetime.fromtimestamp(ts) in Python (returns local time; use timezone.utc for UTC), or date -d @1724000000 on Linux.

Does a Unix timestamp change with timezones or DST?

No. Unix time is timezone-independent — it counts seconds from UTC midnight, Jan 1 1970. Only the human-readable rendering changes by timezone. When New York falls back for DST, the local wall clock repeats an hour, but the Unix timestamp keeps increasing normally.

When does the 32-bit Unix timestamp overflow (Y2K38)?

On January 19, 2038 at 03:14:07 UTC, a signed 32-bit integer holding seconds-since-epoch overflows. Modern 64-bit systems are unaffected until the year 292 billion — but embedded systems and legacy databases with 32-bit time fields still need auditing before 2038.