Unix Time Conv
Convert Epoch timestamps to human dates instantly.
Convert Epoch timestamps to human dates instantly.
Details
Quick Reference
| Event | Timestamp |
|---|---|
| Now | 1784582860 |
| 1 Hour Ago | 1784579260 |
| 1 Day Ago | 1784496460 |
| Start of 2026 | 1767225600 |
| Start of 2025 | 1735689600 |
| Start of 2024 | 1704067200 |
| Y2K (2000) | 946684800 |
Recommended Tools
Hand-picked utilities you might find useful
Converting Between Unix Timestamps and Human Dates
Overview
A Unix timestamp is the number of seconds since January 1, 1970 (UTC) — a compact, timezone-free way computers store time. It's everywhere in logs, APIs, and databases, but it's unreadable to humans. This converter turns a timestamp into a normal date and time, and a date back into a timestamp, instantly in your browser with no upload.
How to Use (Step by Step)
- 1
Enter a timestamp or a date
Paste a Unix timestamp to decode, or pick a date and time to encode.
- 2
Convert instantly
The tool shows the matching date (in UTC and local time) or the timestamp value.
- 3
Copy the result
Use the human date for reading, or the number for code, logs, or a database.
How It Works
The tool takes a Unix timestamp (in seconds or milliseconds) and adds it to the 1970 epoch to produce a calendar date and time, shown in UTC and your local timezone. Going the other way, you pick a date and it counts the seconds since the epoch. Because time is stored as a single number, the conversion is pure arithmetic done locally — nothing is sent to a server.
When to Use This
Reading a timestamp from a log file, API response, or database record. Generating a timestamp to insert into code or a query. Checking what local time an event happened at from its UTC timestamp. Debugging why two systems disagree about a time. Converting between seconds and milliseconds when an API expects one. Verifying a token or cache expiry time.
Frequently Asked Questions
Unix timestamps are traditionally in seconds (10 digits around now), but JavaScript and many APIs use milliseconds (13 digits). If your result looks wildly off, you likely mixed the two — check the digit count.
Important Notes
Classic 32-bit Unix timestamps overflow in January 2038 (the 'Year 2038 problem'). Modern systems use 64-bit values, but old software may misbehave with far-future dates.