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.
No need to specify seconds or milliseconds — the tool detects 10, 13, and 16-digit formats automatically.
Copy results in ISO 8601, RFC 2822, or raw timestamp format. Built for engineers who work with APIs and databases daily.
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.
See also: Unix Timestamps in JavaScript → Python DateTime Guide → SQL Timestamp Reference →
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.
Using time(), strtotime(), and DateTime objects for epoch conversion in PHP.
Instant.now(), System.currentTimeMillis(), and date handling in modern Java.
What negative timestamps mean, which languages support them, and edge cases to watch out for.
Step-by-step formula to convert epoch time to a readable date inside Microsoft Excel.
Using Date.now(), new Date(), and toISOString() to work with epoch values in JS and TypeScript.
How to use time.Now().Unix(), time.Unix(), and time.Time for epoch handling in Go.
Working with SystemTime, UNIX_EPOCH, and the chrono crate for timestamp handling in Rust.
How MySQL, PostgreSQL, MongoDB, and Redis each store and query Unix timestamps differently.
Why most REST and GraphQL APIs use epoch integers instead of ISO strings, and when to choose each.
Off-by-one-hour errors, millisecond confusion, timezone traps — and how to fix them fast.
Using Time.now.to_i, Time.at(), and ActiveSupport helpers for epoch conversion in Ruby and Rails.