What is this tool?
Convert and inspect Unix epoch timestamps in seconds and milliseconds across ISO 8601, RFC 3339, RFC 2822, UTC, and local timezone formats with live relative time calculations.
When to use it?
Debug database timestamps (PostgreSQL, MongoDB, MySQL), analyze server access logs, inspect token exp/iat claims, convert API dates to human-readable timestamps, or resolve timezone offset bugs.
How does it work?
Parses numeric inputs (treating 10-digit values as seconds and 13-digit values as milliseconds) or ISO date strings into millisecond epoch values, initializes a native JavaScript Date object, and maps the components to standard date representation formats.
Technical Specifications & Standards
Unix time represents the number of non-leap seconds elapsed since January 1, 1970 00:00:00 UTC (the Unix Epoch). 10-digit timestamps represent seconds; 13-digit timestamps represent milliseconds.
Operating Limits & Considerations
- Dates before 1970 or after the Year 2038 (32-bit signed integer overflow limit) are handled using 64-bit JavaScript Numbers, supporting accurate representation up to Year 275760.
- Timezone conversions depend on your local operating system and browser timezone settings.
Example Conversions
1719600000 (10-digit Unix Seconds)
ISO 8601: 2024-06-28T18:40:00.000Z RFC 3339: 2024-06-28T18:40:00Z UTC: Fri, 28 Jun 2024 18:40:00 GMT
Standards & Technical References
Frequently Asked Questions
A 10-digit integer (e.g. 1719600000) represents seconds elapsed since the Unix epoch, commonly used in Unix command lines, JWT exp claims, and C libraries. A 13-digit integer (e.g. 1719600000000) represents milliseconds, used by JavaScript Date.now() and Java/JVM runtimes.
Systems storing Unix time as signed 32-bit integers will overflow on January 19, 2038 at 03:14:07 UTC. Modern 64-bit systems and JavaScript runtimes avoid this problem by using 64-bit representations.