Unix Timestamp Converter
Convert epoch timestamps (seconds or milliseconds) to UTC, Local, and ISO 8601 dates.
1. Unix Timestamp → Human-Readable Date
Supports epoch values in seconds (10 digits) or milliseconds (13 digits).
- ISO 8601 (UTC)
- 2023-11-14T22:13:20.000Z
- UTC Date & Time
- Tue, Nov 14, 2023, 22:13:20 UTC
- Local Time (UTC+00:00)
- Tue, Nov 14, 2023, 22:13:20 (UTC, UTC+00:00)
- Epoch Seconds (Detected: seconds)
- 1700000000
- Epoch Milliseconds
- 1700000000000
- Relative Time
- 3 years ago • Day 318 of year
2. Readable Date → Unix Timestamp
Enter an ISO 8601 string or calendar date (e.g., 2025-03-15T14:30:00Z).
- Unix Timestamp (Seconds)
- 1742049000
- Unix Timestamp (Milliseconds)
- 1742049000000
- Normalized ISO 8601 (UTC)
- 2025-03-15T14:30:00.000Z
- UTC Formatted
- Sat, Mar 15, 2025, 14:30:00 UTC
- Local Time (UTC+00:00)
- Sat, Mar 15, 2025, 14:30:00 (UTC, UTC+00:00)
What Does the Unix Timestamp Converter Do?
The Unix Timestamp Converter translates numeric Unix epoch values—representing the time elapsed since 00:00:00 UTC on January 1, 1970 (excluding leap seconds)—into human-readable calendar dates and vice versa.
It automatically detects or lets you explicitly select whether an input represents seconds (10 digits for modern dates) or milliseconds (13 digits, as returned by JavaScript's Date.now()).
Results are displayed side-by-side in UTC, your browser's local IANA timezone with explicit UTC offset labels, ISO 8601 format, RFC 2822 format, and relative time (e.g., '3 hours ago').
How to Use This Tool
- Enter a Unix timestamp (positive or negative integer) in the Timestamp-to-Date panel and choose Auto-detect, Seconds, or Milliseconds.
- Or enter an ISO string / date components in the Date-to-Timestamp panel and select whether the input should be interpreted as UTC or your local timezone.
- Copy any of the resulting timestamp or ISO 8601 outputs with one click.
Common Engineering Use Cases
- Debugging JWT exp (expiration) and iat (issued at) claims during authentication troubleshooting.
- Inspecting server log timestamps, database created_at integers, or cache TTL expirations.
- Generating exact epoch cutoffs for SQL queries, Prometheus metrics ranges, or cron test cases.
Practical Developer Examples
Converting a 10-Digit Unix Epoch Timestamp
A 10-digit timestamp represents seconds since 1970-01-01T00:00:00Z.
1700000000 (Seconds)
ISO 8601 (UTC): 2023-11-14T22:13:20.000Z Milliseconds: 1700000000000
Common Mistakes & Pitfalls to Avoid
- Passing a 10-digit seconds timestamp directly to new Date(ts) in JavaScript, which expects milliseconds and produces a date in January 1970.
- Assuming a local date string without a timezone designator ('Z' or '+00:00') will be parsed identically across servers in different timezones.
Frequently Asked Questions
What is the Year 2038 problem?
Systems that store Unix timestamps in a signed 32-bit integer will overflow after 2,147,483,647 seconds (03:14:07 UTC on 19 January 2038). Modern 64-bit systems and JavaScript numbers safely support dates hundreds of thousands of years into the future.