Unix Timestamp Converter
Convert Unix epoch timestamps to readable dates and back. Auto-detects seconds, milliseconds, microseconds and nanoseconds, supports every time zone and converts whole lists at once.
What Is a Unix Timestamp?
The number of seconds since 1 January 1970, 00:00:00 UTC — the clock computers agree on.
A Unix timestamp (also called epoch time or POSIX time) counts the seconds elapsed since the Unix epoch, 1970-01-01T00:00:00Z, ignoring leap seconds. 0 is the epoch itself, 1767225600 is 1 January 2026 at midnight UTC, and negative values are dates before 1970.
Because it is a single number with no time zone, it is perfect for storing and comparing moments in databases, logs, APIs, JWT exp/iat claims and cookies. You convert it to local time only when showing it to a person.
Different systems use different units: Unix, PHP, Python and most databases use seconds (10 digits today); JavaScript and Java use milliseconds (13 digits); some APIs and Go use micro- or nanoseconds (16 or 19 digits). This converter detects the unit from the number of digits.
Time zones come from your browser's built-in IANA database, so daylight saving time is handled correctly for any date in any zone.
Get & Convert Timestamps in Your Language
Copy-paste snippets for the current Unix time (seconds) and back to a date.
| Language | Current timestamp | Timestamp → date |
|---|---|---|
| JavaScript | Math.floor(Date.now() / 1000) | new Date(ts * 1000).toISOString() |
| Python | int(time.time()) | datetime.fromtimestamp(ts, tz=timezone.utc) |
| PHP | time() | date('c', $ts) |
| Go | time.Now().Unix() | time.Unix(ts, 0).UTC() |
| Java | Instant.now().getEpochSecond() | Instant.ofEpochSecond(ts) |
| C# | DateTimeOffset.UtcNow.ToUnixTimeSeconds() | DateTimeOffset.FromUnixTimeSeconds(ts) |
| MySQL | UNIX_TIMESTAMP() | FROM_UNIXTIME(ts) |
| PostgreSQL | extract(epoch from now())::bigint | to_timestamp(ts) |
| Bash | date +%s | date -u -d @ts (macOS: date -u -r ts) |
How to Use the Unix Timestamp Converter
Get your result in under ten seconds.
Paste a timestamp
Enter seconds, milliseconds, microseconds or nanoseconds — the unit is detected automatically, negatives included.
Pick a time zone
See the moment in UTC, your local zone or any of the 400+ IANA zones, plus ISO 8601, RFC 2822 and relative time.
Convert back or in bulk
Choose a date and time to get its timestamp, or paste a whole column of timestamps to convert them all at once.
Why Use the Unix Timestamp Converter on Developers Web Tools
Fast, accurate and private — built for developers.
Smart unit detection
10, 13, 16 and 19-digit timestamps are recognised as s, ms, µs and ns — no more dates in the year 55,000.
Every time zone
Uses the IANA database built into your browser, including daylight saving rules for past and future dates.
Live epoch clock
The current Unix time in seconds and milliseconds, one click to copy.
Bulk conversion
Convert thousands of timestamps from logs or CSV exports and download the result as CSV.
Every format
ISO 8601, RFC 2822, UTC, local, relative time, day of year and ISO week number.
Private & offline
All conversion happens in your browser. Nothing is sent to a server.
Frequently Asked Questions
Count the digits. Current timestamps in seconds have 10 digits (e.g. 1767225600); in milliseconds they have 13 (1767225600000). Microseconds have 16 and nanoseconds 19. This tool detects it automatically, and you can override the unit.
Systems that store Unix time as a signed 32-bit integer overflow on 19 January 2038 at 03:14:07 UTC (timestamp 2147483647) and wrap to 1901. Modern systems use 64-bit integers, which last for billions of years — but old embedded devices and databases may still be affected.
No. A timestamp identifies the same instant everywhere on Earth; it is always relative to UTC. The time zone only matters when you display it as a calendar date and clock time.
No. Unix time assumes every day has exactly 86,400 seconds, so leap seconds are not counted. That's why converting is simple arithmetic.
Yes. Negative values are dates before 1 January 1970, for example −86400 is 31 December 1969.
Usually daylight saving time or a zone mismatch. Make sure the time zone selector matches the zone you expect; this tool applies the correct DST rules for the date being converted.
When clocks jump forward (for example 02:30 on the spring-forward night), that local time never happens. The converter tells you and shows the nearest valid moment.