Epoch Time Converter
Convert Unix timestamps to human-readable dates and vice versa. Supports seconds, milliseconds, and microseconds with multiple timezone displays.
Current Unix Time
1777063804
Seconds
Precision:
Converted Date
ISO 86012026-04-24T20:50:04.000Z
UTCApr 24, 2026, 20:50:04 UTC
New YorkApr 24, 2026, 16:50:04 EDT
LondonApr 24, 2026, 21:50:04 GMT+1
BerlinApr 24, 2026, 22:50:04 GMT+2
TokyoApr 25, 2026, 05:50:04 GMT+9
SydneyApr 25, 2026, 06:50:04 GMT+10
Notable Timestamps
| Date | Unix (s) |
|---|---|
| Unix epoch (1970-01-01) | 0 |
| Y2K (2000-01-01) | 946,684,800 |
| Unix billion (2001-09-09) | 1,000,000,000 |
| Y2K38 overflow (2038-01-19) | 2,147,483,647 |
| Unix 2 billion (2033-05-18) | 2,000,000,000 |
How to Use Epoch Time Converter
- 1Enter a Unix timestamp to convert to a readable date.
- 2Or enter a date and time to get the Unix timestamp.
- 3Toggle between seconds, milliseconds, and microseconds.
- 4See the time displayed in UTC and your local timezone.
Zenovay
Track your website performance
Real-time analytics, session replay, heatmaps, and AI insights. 2-minute setup, privacy-first.
Related Tools
JSON Formatter & ValidatorFormat, validate, and beautify JSON data with syntax highlighting and error detection.
JWT DecoderDecode and inspect JWT tokens. View header, payload, and verify signatures.
Base64 Encode/DecodeEncode text to Base64 or decode Base64 back to text. Supports UTF-8 and binary data.
URL Encode/DecodeEncode or decode URL components. Handle special characters, query strings, and full URLs.
Frequently Asked Questions
What is Unix time / epoch time?▾
Unix time (also called POSIX time or epoch time) is the number of seconds elapsed since 00:00:00 UTC on January 1, 1970 — the Unix epoch. It is used in virtually all operating systems and programming languages because it provides a universal, timezone-independent point of reference. Unix time does not account for leap seconds, so it increases uniformly without discontinuities.
Why does JavaScript use milliseconds?▾
JavaScript's Date object uses milliseconds since the epoch (not seconds) — so Date.now() returns the current time in milliseconds. In most databases and server-side languages, seconds are standard. Python's time.time() returns seconds as a float; datetime.datetime.utcnow().timestamp() also returns seconds. Go's time.Now().Unix() returns seconds; time.Now().UnixMilli() returns milliseconds. Always check which unit an API uses to avoid 1000× errors.
What is the Year 2038 problem?▾
The Year 2038 problem (Y2K38) affects 32-bit signed integers storing Unix timestamps. The maximum value of a signed 32-bit int is 2,147,483,647, which corresponds to 03:14:07 UTC on January 19, 2038. After this, the value overflows to a large negative number, causing date calculations to fail. Modern 64-bit systems use 64-bit integers, which can represent times billions of years into the future. Legacy embedded systems and old databases are at risk.
How do I get the current epoch time?▾
JavaScript: Date.now() (ms) or Math.floor(Date.now()/1000) (s). Python: import time; time.time() (s) or int(time.time()). Unix shell: date +%s. SQL: UNIX_TIMESTAMP() (MySQL), extract(epoch from now()) (PostgreSQL). Go: time.Now().Unix() (s). Java: System.currentTimeMillis() (ms) or Instant.now().getEpochSecond(). PHP: time() (s). Ruby: Time.now.to_i (s).
What is ISO 8601 format?▾
ISO 8601 is the international standard for representing dates and times. Format: YYYY-MM-DDTHH:mm:ssZ. Examples: 2024-01-15T10:30:00Z (UTC), 2024-01-15T10:30:00+05:30 (IST), 2024-01-15T10:30:00.000Z (with milliseconds). The T separates date and time; Z means UTC (Zulu time). Most APIs (REST, GraphQL) use ISO 8601. JavaScript's new Date().toISOString() produces ISO 8601 with milliseconds.