Unix Timestamp & Epoch Converter

Convert Unix epoch timestamps to human-readable dates — or any date back to its epoch value. Live clock, auto-detects seconds vs milliseconds, free & instant.

100% FreeNo Sign-upRuns in BrowserLive Clock

Current Unix Epoch Time (live)

Seconds

1,783,066,258

Milliseconds

1,783,066,258,000

Friday, July 3, 2026 — 08:10:58 UTC

Timestamp → Human Date

Unix Timestamp(seconds or milliseconds)

Human Date → Timestamp

Date & Time(your local timezone)

What is a Unix Timestamp?

A Unix timestamp (also called epoch time or POSIX time) is the number of seconds that have elapsed since January 1, 1970, 00:00:00 UTC — a moment in time known as the Unix Epoch. It provides a language-agnostic, timezone-agnostic way to represent any point in time as a single integer.

Unix timestamps are the universal standard for time storage in databases, APIs, log files, JWT tokens, and server-side code. Unlike formatted date strings (which vary by locale and timezone), an epoch value has exactly one meaning everywhere on Earth.

Seconds vs Milliseconds

The traditional Unix timestamp counts in seconds and is currently a 10-digit number (e.g. 1749459940). Many modern languages and APIs — especially JavaScript's Date.now() — use milliseconds, producing a 13-digit number. Our tool auto-detects which unit you have pasted so you never need to guess.

Epoch Time Cheat Sheet — Get Current Timestamp by Language

Copy and paste the snippet for your language to get the current Unix epoch timestamp:

Language	Seconds	Milliseconds
JavaScript	Math.floor(Date.now() / 1000)	Date.now()
Python	import time; int(time.time())	import time; int(time.time() * 1000)
PHP	time()	round(microtime(true) * 1000)
Java	System.currentTimeMillis() / 1000L	System.currentTimeMillis()
Go	time.Now().Unix()	time.Now().UnixMilli()
C#/.NET	DateTimeOffset.UtcNow.ToUnixTimeSeconds()	DateTimeOffset.UtcNow.ToUnixTimeMilliseconds()
Ruby	Time.now.to_i	(Time.now.to_f * 1000).to_i
Rust	SystemTime::now().duration_since(UNIX_EPOCH).unwrap().as_secs()	SystemTime::now().duration_since(UNIX_EPOCH).unwrap().as_millis()
Bash	date +%s	date +%s%3N
PostgreSQL	EXTRACT(EPOCH FROM NOW())::BIGINT	EXTRACT(EPOCH FROM NOW()) * 1000
MySQL	UNIX_TIMESTAMP()	UNIX_TIMESTAMP() * 1000

Why Are Unix Timestamps Used?

Timezone Independence

A Unix timestamp has no timezone. It always represents the same moment in time regardless of where the server or user is located. When you convert it to a human-readable format, you apply timezone information at display time — keeping storage and logic clean and unambiguous.

Simple Arithmetic

Because timestamps are plain integers, date arithmetic is trivial. To check if something expired 7 days ago: compare createdAt + 604800 (7 × 24 × 60 × 60 seconds) against the current epoch. No date-parsing libraries needed.

JWT & API Tokens

JSON Web Tokens use Unix timestamps in their iat (issued at) and exp (expiration) claims. If your API is returning a 401 and you need to debug expiry times, paste the exp value into our converter above.

FAQ

What is the Unix Epoch?

The Unix Epoch is the reference point for all Unix timestamps: midnight on January 1, 1970, Coordinated Universal Time (UTC). Every Unix timestamp is simply the number of seconds (or milliseconds) that have passed since that exact moment.

What is the Year 2038 Problem?

Traditional 32-bit systems store Unix timestamps as a signed 32-bit integer, which overflows on January 19, 2038 at 03:14:07 UTC (the value exceeds 2,147,483,647). Modern systems use 64-bit integers, which can represent dates billions of years into the future, making this a solved problem on current hardware.

How do I convert a negative Unix timestamp?

Negative timestamps represent dates before January 1, 1970. For example, -86400 is December 31, 1969 at midnight UTC. Our converter handles negative values correctly via JavaScript's native Date object.