Convert epoch time to human-readable date — or any date to Unix timestamp. Instant, accurate, free.
| Format | Digits | Example | Language |
|---|---|---|---|
| Unix (seconds) | 10 | 1700000000 | time() in PHP, Python |
| Unix (milliseconds) | 13 | 1700000000000 | Date.now() in JS |
| Unix (microseconds) | 16 | 1700000000000000 | time.time_ns() Python |
| ISO 8601 | — | 2023-11-14T22:13:20Z | Universal standard |
| RFC 2822 | — | Tue, 14 Nov 2023 22:13:20 +0000 | Email headers |
Conversion happens in your browser — no server round trips, no delay. Results appear as you type.
Your timestamps never leave your device. All conversion logic runs entirely client-side.
See results in your local timezone alongside UTC. Perfect for debugging across regions.
Paste multiple timestamps at once and convert them all in a single click.
A Unix timestamp — also called epoch time or POSIX time — is the number of seconds that have elapsed since the Unix epoch: January 1, 1970, at 00:00:00 UTC. It is the most widely used system for representing a specific moment in time across programming languages, databases, and APIs.
Because it is just a single integer, Unix time is easy to store, compare, and transmit. Sorting records by timestamp is as simple as sorting numbers, and you never need to worry about timezones — the raw value is always in UTC.
The most common source of confusion is whether a timestamp is in seconds or milliseconds. Our converter detects this automatically:
1700000000)1700000000000)JavaScript's Date.now() returns milliseconds. Python's time.time() and PHP's time() return seconds. MySQL UNIX_TIMESTAMP() returns seconds.
Here are quick one-liners for getting the current timestamp in common languages:
Math.floor(Date.now() / 1000) (seconds)import time; int(time.time())time()SELECT UNIX_TIMESTAMP();date +%stime.Now().Unix()32-bit systems store Unix timestamps as a signed 32-bit integer, which overflows on January 19, 2038, at 03:14:07 UTC. Modern 64-bit systems are not affected and can represent dates far into the future. This is sometimes called the "Y2K38" problem.
A comprehensive deep dive into Unix time origin and structural design principles.
Understand the integer overflow limitations threatening legacy 32-bit timestamp structures.
Quick programmatic copy-paste references for working with epochs in Python applications.
How to parse and query system time formats across MySQL, Postgres, and SQLite databases.