Timestamp Converter
Convert between Unix timestamps and human-readable dates. Supports ISO 8601, RFC 2822, and more.
Last updated:
How to Use
Expand how to useCollapse how to use
- 1
Select input mode
Choose whether to convert from Unix timestamp or from a date/time string.
- 2
Enter value and timezone
Enter the Unix timestamp (seconds/milliseconds) or date/time string, and select the timezone.
- 3
Copy the result
Review the converted results in various formats (ISO 8601, RFC 2822, etc.) and copy the format you need.
Input
Enter epoch seconds or milliseconds
|value| < 10^11 = seconds, otherwise = milliseconds
Result
About Timestamp Converter
Unix Timestamp Converter translates between Unix epoch timestamps and human-readable dates with support for both seconds and milliseconds, auto-detected from the input value. It's essential for debugging server logs, inspecting JWT expiration times, analyzing database records that store epoch time, and working with REST APIs that return Unix timestamps. Output is available in multiple formats including ISO 8601, RFC 2822, locale-specific formatting, and relative time. Over 10 time zones are supported including UTC, JST, EST, PST, CET, and more, so you can quickly verify timestamps across regions.
Key Features
- Convert Unix time (seconds/milliseconds) to date/time
- Convert date/time strings to Unix time
- Support for 10+ time zones (UTC, JST, EST, PST, etc.)
- Multiple output formats (ISO 8601, RFC 2822, locale format, relative time)
- Auto-detection of seconds vs milliseconds
Common Use Cases
- Convert API timestamps (JWT exp, OAuth tokens) to readable dates
- Debug server logs that use Unix epoch format
- Analyze database records with epoch timestamps
- Compare timestamps across different time zones
- Generate Unix timestamps for API testing with Postman or curl
Frequently Asked Questions
What is Unix time?
Unix time (epoch seconds) is the number of seconds since January 1, 1970, 00:00:00 UTC. It's an absolute time representation independent of time zones, widely used in computer systems.
How are seconds and milliseconds distinguished?
In auto-detect mode, if the absolute value is less than 10^11, it's interpreted as seconds; otherwise as milliseconds. For example, "1704067200" is treated as seconds (January 1, 2024), while "1704067200000" is treated as milliseconds. You can also manually specify the unit.
How do I decode a JWT expiration timestamp?
Paste the exp value from your JWT payload directly into the input field. The tool auto-detects whether it's in seconds or milliseconds and converts it to a human-readable date, so you can tell at a glance if the token has expired.
What date/time formats can I input?
ISO 8601 format (2024-01-01T00:00:00Z), RFC 2822 format (Mon, 01 Jan 2024 00:00:00 +0000), and common date/time strings (2024/01/01 00:00:00) are supported.
Is my input data sent to a server?
No. All conversions are performed locally using the JavaScript Date API. Timestamps from JWT tokens, database records, or access logs are never transmitted.