Unix Timestamp Converter
Convert between Unix timestamps and human-readable dates. Supports seconds and milliseconds.
Enter a Unix timestamp to convert to a readable date, or enter a date to get its Unix timestamp.
1776284692What Is a Unix Timestamp?
A Unix timestamp is the number of seconds since January 1, 1970 00:00:00 UTC — a moment known as the "Unix epoch." Right now, the timestamp is somewhere around 1.7 billion. It's how computers have tracked time for over 50 years: one single number, no time zones, no formatting, no ambiguity.
Think of it as a universal clock. While humans argue about whether "01/02/2025" means January 2nd or February 1st, computers just store 1735776000 and convert to whatever format the user needs. Every database, every API, every log file understands Unix timestamps.
This converter lets you go both ways: paste a Unix timestamp to see the human-readable date, or pick a date to get the timestamp. It handles seconds and milliseconds (JavaScript uses milliseconds — just divide by 1,000 to get seconds).
Notable Unix Timestamps
| Timestamp | Date | Significance |
|---|---|---|
| 0 | 1 Jan 1970 00:00:00 UTC | The Unix epoch — where it all began |
| 1000000000 | 9 Sep 2001 01:46:40 UTC | One billion seconds |
| 1234567890 | 13 Feb 2009 23:31:30 UTC | Sequential digits — celebrated by developers |
| 1700000000 | 14 Nov 2023 22:13:20 UTC | 1.7 billion seconds |
| 2000000000 | 18 May 2033 03:33:20 UTC | Two billion seconds — Y2K38 approaches |
| 2147483647 | 19 Jan 2038 03:14:07 UTC | Y2K38 — max 32-bit signed integer overflows |
What this means for you: If your system stores timestamps as 32-bit signed integers, it will break on 19 January 2038. Most modern systems use 64-bit integers, which last until the year 292 billion. Check your database column types.
Timestamps in Different Languages
| Language | Get Current Timestamp | Unit |
|---|---|---|
| JavaScript | Date.now() | Milliseconds |
| Python | import time; time.time() | Seconds (float) |
| PHP | time() | Seconds |
| Java | System.currentTimeMillis() | Milliseconds |
| Ruby | Time.now.to_i | Seconds |
| Go | time.Now().Unix() | Seconds |
| SQL | UNIX_TIMESTAMP() | Seconds |
| Bash | date +%s | Seconds |
Common Timestamp Pitfalls
Seconds vs milliseconds
JavaScript's Date.now() returns milliseconds (13 digits). Most other languages return seconds (10 digits). Mixing them up gives you dates in the year 55,000+ or 1970. Always check the digit count.
Time zone confusion
Unix timestamps are always UTC. "1700000000" means the same moment everywhere on Earth. If you're displaying it to a user, convert to their local time zone. If you're storing it, keep it as UTC.
Negative timestamps
Dates before 1 January 1970 have negative timestamps. 31 December 1969 is -86400. Some systems don't handle negative timestamps correctly — test if your app needs to work with historical dates.
Leap seconds
Unix time ignores leap seconds. A "day" is always 86,400 seconds, even when the real day has 86,401. For most applications this doesn't matter. For nanosecond-precision systems, use TAI or GPS time instead.
ISO 8601 vs Unix Timestamps
Unix Timestamp
1713052800
Compact, unambiguous, easy to sort and compare. No time zone confusion. But completely unreadable to humans — you need a converter to know what date it is.
ISO 8601
2024-04-14T00:00:00Z
Human-readable, includes date and time zone. Standard for APIs and data exchange (JSON). Slightly larger but self-documenting — anyone can read it without a tool.
Rule of thumb: Use Unix timestamps for internal storage and computation. Use ISO 8601 for APIs, logs, and anything humans might read. Most frameworks convert between them with a single function call.
Related Tools
How to use this tool
Enter a Unix timestamp to convert to a readable date, or select a date to convert
The tool auto-detects seconds (10 digits) vs milliseconds (13 digits)
Copy any output format — local time, UTC, ISO 8601, or raw timestamp
Common uses
- Converting API timestamps to readable dates
- Debugging JWT token expiration times
- Converting log file timestamps for analysis
- Comparing timestamps across different systems
Share this tool