Unix Timestamp Converter – Epoch to Date, ISO 8601 & RFC 3339
Convert Unix timestamps to human-readable dates and back. Seconds, milliseconds, ISO 8601, RFC 3339 and all timezones are supported.
Input
Converted Timestamps
Additional Formats
Frequently Asked Questions
What is a Unix timestamp?
A Unix timestamp (also called epoch time) is the number of seconds elapsed since January 1, 1970 00:00:00 UTC. It is used by databases, APIs, log files, and JWT tokens to store dates as simple integers.
What is the difference between seconds and milliseconds timestamps?
A seconds-based timestamp has 10 digits (e.g., 1704067200). A milliseconds-based timestamp has 13 digits (e.g., 1704067200000). JavaScript's Date.now() returns milliseconds; most Unix/Linux systems use seconds. This converter auto-detects the format.
How do I convert epoch seconds to a date?
Paste the epoch value into the input, select "Unix Timestamp (seconds)", and the UTC date, local date, ISO 8601, RFC 3339, and relative time are all shown instantly.
What is ISO 8601 and RFC 3339?
ISO 8601 is an international date-time standard (e.g., 2024-01-01T00:00:00Z). RFC 3339 is a stricter profile of ISO 8601 commonly used in internet protocols and APIs. This tool converts between both and Unix timestamps.
How do I convert a timestamp to IST or other timezones?
Select your target timezone from the dropdown (e.g., Asia/Kolkata for IST). The result is shown in the selected timezone alongside UTC.
What is a milliseconds timestamp converter?
Some APIs (like JavaScript's Date.now() or Java's System.currentTimeMillis()) return timestamps in milliseconds. Paste the 13-digit value, select "Unix Timestamp (milliseconds)", and the human-readable date is shown.
Unix Timestamp Converter: Epoch to Date, Milliseconds, ISO 8601 & RFC 3339
Epoch time (seconds since January 1, 1970 UTC) is translated to human-readable dates and back by this Unix timestamp converter. Timestamps are used internally by databases, APIs, log files, and JWT tokens. A timestamp can be pasted to see the date, or a date can be picked to get the epoch value. Both seconds (10 digits) and milliseconds (13 digits) are supported with timezone-aware output. ISO 8601, RFC 3339, and long-to-timestamp conversions are all handled.
Seconds vs. milliseconds
Some systems use seconds (10 digits, like 1716566400) while others use milliseconds (13 digits, like 1716566400000). JavaScript's Date.now() returns milliseconds; most Unix systems use seconds. Both formats are auto-detected and handled correctly.
Timezone handling
Unix timestamps are always in UTC. When converting to a human-readable date, the timezone matters. Results are shown in both UTC and your local timezone, plus conversion to any timezone worldwide is available. Useful for debugging issues where events appear at the "wrong" time due to timezone confusion.