Convert Unix timestamps to human-readable dates and dates to epoch time. Auto-detects seconds, milliseconds, and microseconds. Timezone support, batch convert, and code snippets.
⏱️ Open Timestamp ConverterFree · No signup · Auto-detects format · Timezone support
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 — the "Unix epoch." For example, the timestamp 1704067200 represents January 1, 2024, at midnight UTC.
Timestamps are the universal language of time in computing. They are timezone-independent, easy to store as a single integer, and trivial to compare and do arithmetic with. Adding 86400 to any timestamp gives you exactly one day later — no timezone math required.
Live clock showing current Unix timestamp (seconds + milliseconds)
Timestamp → Date: converts to UTC, local timezone, ISO 8601
Auto-detects seconds (10 digits), milliseconds (13), microseconds (16)
Date → Timestamp: pick date, time, and timezone
Batch convert — paste multiple timestamps, get a table
Relative time display ("3 days ago", "in 2 hours")
Week number and day of week from any timestamp
Code snippets: JavaScript, Python, PHP, Go
| Duration | Seconds | Notes |
|---|---|---|
| 1 minute | 60 | Add to any timestamp |
| 1 hour | 3,600 | 60 × 60 |
| 1 day | 86,400 | 60 × 60 × 24 |
| 1 week | 604,800 | 86,400 × 7 |
| 30 days | 2,592,000 | approx 1 month |
| 1 year | 31,536,000 | 365 days, no leap |
Unix time was standardized in the early days of Unix operating systems as a simple, timezone-agnostic way to represent moments in time. Because it is just a number, it can be stored in a single integer field in any database, compared with a simple subtraction, and transmitted without ambiguity between systems in different time zones.
JavaScript's Date.now() returns milliseconds (a 13-digit number), while Unix's time() syscall returns seconds (a 10-digit number). When you receive a timestamp from an API and are unsure of the unit, you can tell by the digit count: 10 digits = seconds, 13 digits = milliseconds. This converter auto-detects the format for you.
The Year 2038 problem: 32-bit signed integers overflow at 2,147,483,647 seconds, which corresponds to January 19, 2038. Modern 64-bit systems support timestamps up to year 292,277,026,596 — far beyond practical concern.
Open the Timestamp Converter and the live clock at the top shows the current Unix timestamp in both seconds and milliseconds, updating every 100ms. You can copy it with one click.
Paste your timestamp into the "Timestamp → Date" tab. The converter auto-detects whether it is in seconds, milliseconds, or microseconds and shows the UTC date, local date, ISO 8601 format, and relative time.
Epoch time and Unix timestamp mean the same thing — the number of seconds since January 1, 1970, 00:00:00 UTC. "Epoch" refers to the starting point (the Unix epoch), and the timestamp is the count from that point.
Yes. Use the Batch Convert tab, paste one timestamp per line, and click Convert All to get a table with UTC date and local date for each timestamp. You can also copy the results as CSV.
Yes, completely free. All conversions run in your browser. No signup, no data stored, no rate limits.
Free · Live Clock · Batch Mode · Code Snippets
⏱️ Open Timestamp Converter