Unix Timestamp Converter — Convert Epoch Time to Date Instantly
Paste a 10-digit number (seconds) or 13-digit number (milliseconds) and instantly see the ISO 8601 date, UTC datetime, and your local time. Or paste a date string like "2024-11-15" or "January 15 2025" to get the Unix epoch back. Seconds vs. milliseconds are auto-detected. Used by backend developers reading API responses, DevOps engineers parsing log timestamps, and anyone debugging JWT expiration claims.
What Is Unix Timestamp Converter?
Unix timestamps count seconds since January 1, 1970 00:00:00 UTC. A 10-digit number like 1700000000 is seconds; a 13-digit number like 1700000000000 is milliseconds. Paste either format and see the ISO 8601 date, UTC time, local time, and both epoch formats. Paste a date string to get the epoch back.
1700000000→ISO 8601: 2023-11-14T22:13:20.000Z
UTC: Tue, 14 Nov 2023 22:13:20 GMTWhen to Use Unix Timestamp Converter
Use when debugging API responses that return epoch timestamps, converting log file dates, or building date-based features that require Unix epoch values.
Paste a 10-digit number (seconds) or 13-digit number (milliseconds) to get a readable date. Paste a date string to get its Unix timestamp.
Who Should Use This Tool?
Convert "expires_at: 1700000000" in API responses to readable dates without leaving the browser.
Debug JWT "exp" claims — the expiration field in every JWT token is a Unix timestamp in seconds.
Read Unix timestamps in log files and metrics dashboards without needing a separate tool.
Convert date columns to Unix timestamps for use in time-series databases and event pipelines.
Key Use Cases
- →Decoding API timestamps — translate "created_at: 1699999999" in JSON responses to human-readable dates
- →Verifying JWT expiration — check whether an "exp" claim has passed by converting it to a date
- →Log file analysis — convert log timestamps to ISO dates for correlation across services
- →Building API queries — convert a target date to Unix epoch for use in date-range API parameters
- →Calculating durations — subtract two Unix timestamps to get elapsed seconds without timezone arithmetic
How to Use Unix Timestamp Converter
- Paste or type your text into the Input Text box.
- The result appears instantly on the right.
- Click Copy to copy the output to your clipboard.
- Click Clear to reset and process new text.
Common Mistakes & Pro Tips
- !Confusing seconds and milliseconds — 1700000000 is 2023, but 1700000000000 is also 2023 (just in ms); this tool auto-detects
- !Forgetting timezone — Unix timestamps are always UTC; display in local time only in the UI layer, never in storage
- !Using Unix timestamps for business logic dates — date arithmetic (add 1 month) is not simply "+ 2592000 seconds" due to varying month lengths
- !Year 2038 — 32-bit signed integers overflow on January 19, 2038; always use 64-bit storage for timestamps
Frequently Asked Questions
Everything you need to know about Unix Timestamp Converter
What is a Unix timestamp?
+
A count of seconds (or milliseconds) since January 1, 1970 00:00:00 UTC — the Unix epoch. The value 0 = Jan 1, 1970. Negative values represent dates before 1970. Widely used in programming because timestamps are timezone-independent integers that are simple to compare and store.
What is the Unix epoch?
+
The Unix epoch is January 1, 1970, 00:00:00 UTC — the zero point for Unix timestamps. It was chosen by Unix designers in the early 1970s as a convenient recent date. The current Unix timestamp is always growing by 1 every second.
How do I get today's Unix timestamp?
+
JavaScript: Math.floor(Date.now() / 1000). Python: import time; int(time.time()). Bash: date +%s. PHP: time(). SQL (PostgreSQL): EXTRACT(EPOCH FROM NOW()). SQL (MySQL): UNIX_TIMESTAMP().