Converters & Math
Unix Timestamp to Date
Epoch seconds to UTC date.
UTC Date
1970-01-01T00:00:10.000Z
How it works
The Unix Timestamp Converter translates epoch timestamps into human-readable dates and times β and converts any date back to a timestamp. It detects seconds, milliseconds, microseconds, and nanoseconds automatically, and shows the result in both UTC and your local time zone.
A Unix timestamp is the number of seconds elapsed since 00:00:00 UTC on 1 January 1970, the Unix epoch. Because it is a single integer with no time zone, no locale, and no formatting, it is what databases, log files, JWT tokens, API responses, and file metadata store internally. The cost of that simplicity is that 1735689600 means nothing to a human reading a log at 3 a.m., which is exactly the gap this tool closes.
What it shows for any timestamp: - The full date and time in UTC (ISO 8601: 2025-01-01T00:00:00Z) - The same moment in your browser's local time zone, with the UTC offset - Day of the week, day of the year, ISO week number - Relative time ("3 days ago", "in 2 hours") - The timestamp re-expressed in seconds, milliseconds, and as an ISO string
Unit detection: a 10-digit value is read as seconds, 13 digits as milliseconds, 16 as microseconds, and 19 as nanoseconds. JavaScript's Date.now() and most JSON APIs use milliseconds; Unix tools, PostgreSQL, and JWT claims (iat, exp, nbf) use seconds. Passing seconds where milliseconds are expected yields a date in 1970 β the classic symptom of a missing Γ 1000.
The year 2038 problem: systems storing timestamps in a signed 32-bit integer overflow on 19 January 2038, wrapping to 1901. Anything modern uses 64-bit timestamps and is unaffected for roughly 292 billion years, but embedded devices and legacy C code still carry the bug.
Privacy: conversion uses the browser's native Date and Intl APIs. No timestamp is ever transmitted β useful when the values come from production logs or customer records.
Frequently Asked Questions
- It is the number of seconds that have passed since 00:00:00 UTC on 1 January 1970, known as the Unix epoch. Because it is one integer with no time zone or formatting attached, it is unambiguous and easy to compare and sort, which is why databases, log files, APIs, and file systems store times this way internally.
- Count the digits. A present-day timestamp in seconds has 10 digits (1735689600); in milliseconds it has 13 (1735689600000). Sixteen digits means microseconds and 19 means nanoseconds. If a converted date lands in January 1970, you passed seconds to something expecting milliseconds β multiply by 1000. If it lands tens of thousands of years in the future, you did the reverse.
- No. A timestamp always refers to a moment in UTC; the time zone only matters when you format it for display. That is what makes it a good storage format: the same integer means the same instant everywhere, and each user's client can render it in their own local time. This tool shows both the UTC value and the equivalent in your browser's time zone.
- Systems that store timestamps in a signed 32-bit integer can only count up to 2,147,483,647 seconds, which runs out at 03:14:07 UTC on 19 January 2038 and wraps around to 1901. Modern languages and 64-bit systems use a wider integer and are unaffected for billions of years, but embedded firmware, old C code, and some legacy database columns still carry the bug.