Timestamp to Date Converter: Decode Unix Epoch Time Instantly
Unix timestamps appear everywhere in software development — server log files, database records, API responses, JWT tokens, cache headers, and analytics events. Reading them as raw numbers like 1716278400 or 1716278400000 gives no instant human insight. Our Timestamp to Date Converter decodes any Unix epoch value into a full, readable date breakdown in under a millisecond.
The converter automatically detects whether your timestamp is in seconds (10 digits) or milliseconds (13 digits) and applies the correct scaling. The output includes five distinct date representations — ISO 8601, RFC 2822, locale-aware local time, date-only, and time-only — each with a one-click copy button. A date component grid shows year, month, day, weekday, hour, minute, second, and local timezone offset individually.
Pre-loaded quick examples and a historical timestamps panel (Unix Epoch, Y2K, 1234567890, and three billion-second milestones) let you explore well-known timestamps with a single click.
JavaScript's Date constructor accepts milliseconds since Unix Epoch. For second-precision timestamps, multiply by 1000. The resulting Date object is then formatted into multiple representations using the browser's Intl APIs.
Unix Timestamp Format Reference
There are two common timestamp formats used in practice:
Seconds (10 digits): Used by Unix/Linux systems, Python's time.time(), PostgreSQL's EXTRACT(EPOCH), and most REST APIs. Example: 1716278400 = May 21, 2026 00:00:00 UTC
Milliseconds (13 digits): Used by JavaScript's Date.now(), Java's System.currentTimeMillis(), and many frontend analytics libraries. Example: 1716278400000 = same date. The auto-detect uses digit count to distinguish: 10 digits → seconds, 13+ digits → milliseconds.
Negative timestamps: Represent dates before January 1, 1970 UTC. -86400 = December 31, 1969.
Maximum safe value: JavaScript's Date supports up to ±8,640,000,000,000,000 ms (year 275,760 AD).
Famous Historical Unix Timestamps
0 — Unix Epoch: January 1, 1970, 00:00:00 UTC. The universally agreed starting point for Unix time.
946684800 — Y2K: January 1, 2000, 00:00:00 UTC. The rollover that prompted massive Y2K compliance efforts worldwide.
1234567890 — The Interesting Number: February 13, 2009, 23:31:30 UTC. Celebrated internationally by programmers who watched their Unix clocks hit this sequential milestone.
1500000000 — 1.5 Billion: July 14, 2017, 02:40:00 UTC. The 1.5-billion-seconds milestone.
2147483647 — Y2K38: January 19, 2038, 03:14:07 UTC. The overflow point for 32-bit signed integer Unix timestamps — the Unix equivalent of Y2K for 32-bit systems.
Practical Examples
Decoding a Database Timestamp
A typical scenario when reading a created_at or updated_at column from a PostgreSQL or MySQL database.
- 1.Input: 1716278400 (seconds format)
- 2.Auto-detected: Seconds format (10 digits)
- 3.ISO 8601: 2026-05-21T00:00:00.000Z
- 4.Local time: Wednesday, May 20, 2026 at 07:30:00 PM GMT-4:30 (varies by timezone)
- 5.Relative: "5 days ago" (varies)
Decoding a JavaScript Millisecond Timestamp
Timestamps from Date.now() or performance.now() in JavaScript are in milliseconds and have 13 digits.
- 1.Input: 1716278400000 (milliseconds format)
- 2.Auto-detected: Milliseconds format (13 digits)
- 3.Result: Same date as 1716278400 seconds — the converter scales correctly
- 4.ISO 8601: 2026-05-21T00:00:00.000Z
- 5.Use case: Debugging JWT exp fields, API response timestamps, browser event timing
Frequently Asked Questions
What is a Unix timestamp?
A Unix timestamp (also called epoch time) is the number of seconds that have elapsed since January 1, 1970, 00:00:00 UTC. It is the universal standard for representing moments in time in software systems, databases, APIs, and log files.
Does the converter support millisecond timestamps?
Yes. The converter automatically detects whether your input is in seconds (10 digits) or milliseconds (13 digits) and converts accordingly. A badge below the input confirms which format was detected.
What date formats does it output?
Five formats: ISO 8601 (2026-05-21T07:51:11.000Z), RFC 2822 (Thu, 21 May 2026 07:51:11 GMT), Local Time (human-readable in your browser's locale and timezone), Date Only (May 21, 2026), and Time Only (07:51:11 AM).
What does 'relative time' mean?
Relative time shows how long ago or how far in the future the timestamp is from right now — for example '3 days ago', 'in 2 hours', or '5 years ago'. It updates live while you have the page open.
What is the Unix Epoch?
The Unix Epoch is timestamp 0 — January 1, 1970, 00:00:00 UTC. It is the starting point from which all Unix timestamps count forward in seconds.
What happened at timestamp 1234567890?
Unix timestamp 1234567890 occurred on February 13, 2009, 23:31:30 UTC. It was widely celebrated by programmers as a famous sequential timestamp milestone.
Can I convert negative timestamps?
Yes. Negative Unix timestamps represent dates before January 1, 1970. For example, -86400 represents December 31, 1969, 00:00:00 UTC.
Why does local time differ from UTC time?
Local time is adjusted by your browser's timezone offset. If you are in UTC+5:30 (India), a UTC timestamp of 07:00:00 will display as 12:30:00 local time. The UTC/ISO format always shows the canonical UTC value.