Convert a Unix timestamp to a human-readable date — or any date back to Unix epoch time — instantly in your browser. Automatically handles both seconds and milliseconds.
Current Unix Time (live)
Seconds (10-digit)
1778751990Milliseconds (13-digit)
1778751990902Tell us whether the Timestamp Converter workflow felt clear, or report what slowed you down.
A Unix timestamp is an integer that counts the total number of seconds elapsed since January 1, 1970 at 00:00:00 UTC — a fixed reference point called the Unix epoch. It was introduced with the Unix operating system in the early 1970s and has since become the universal standard for representing time in software.
Because a timestamp is just a number, it carries no time-zone information and is the same value anywhere in the world. Whether a system is running in New York, London or Tokyo, the timestamp 1712217600 always refers to exactly the same moment: April 4, 2024 at 00:00:00 UTC. Converting it to a local time is a separate step that depends on the observer's time zone.
The original Unix standard measures time in seconds, giving a 10-digit number for any date after September 2001. Most backend languages — Python, PHP, Go, Ruby — return seconds by default. However, JavaScript's Date.now() and Java's System.currentTimeMillis() return milliseconds, producing a 13-digit number.
1712217600April 4, 2024 00:00:00 UTC
Used by: Python, PHP, Go, Linux, SQL databases
1712217600000Same moment, × 1,000
Used by: JavaScript, Java, many web APIs
This tool automatically detects which format you have entered by counting the digits. You never need to choose manually. The detected format is shown directly below the input field.
Paste your timestamp into the first input field above. Conversion happens automatically as you type — no button press needed. The tool shows six output formats simultaneously:
2024-04-04T00:00:00.000Z) used in APIs, databases and log files.A Unix timestamp is always stored in UTC. When you display it to a user, you convert it to their local time zone. When you store or transmit it between systems, you keep it as UTC or as the raw timestamp.
This distinction matters in real situations:
2024-04-04T00:00:00Z is midnight UTC — which is 8:00 AM in Singapore (UTC+8) and 8:00 PM the previous day in New York (UTC-4 during Eastern Daylight Time).Developers
Debug API responses with timestamp fields. Verify token expiry times. Check created_at, expires_at and iat/exp values in JWTs.
QA & Testers
Confirm that a feature triggered at the right time. Check event ordering in test logs. Verify time-based conditions behave correctly across time zones.
Log Analysis
Server logs, application traces and error reports often include raw Unix timestamps. Convert them instantly to understand when an incident occurred.
Databases & APIs
SQL databases store timestamps as integers. REST and GraphQL APIs return epoch values. Convert them to verify data before writing migrations or integration tests.
There are two very common causes:
If you pass 1712217600 (seconds) to a JavaScript new Date() constructor without multiplying by 1,000, you will get a date in January 1970 — because the constructor expects milliseconds. Always check your digit count: 10 digits = seconds, 13 digits = milliseconds.
The UTC output and local output will differ by your time zone offset. If you expect midnight UTC but your system is UTC-5, local time will show 7:00 PM the previous day. This is correct behaviour — both values represent the same moment. Use the UTC output for system comparisons; use local time for user-facing display.
17122176001712217600000Both examples refer to the identical moment. They differ only in unit.
Paste any value below into the converter to explore. Seconds are shown; multiply by 1,000 if you need to mimic Java-style millisecond APIs.
| Seconds (example) | UTC moment (reference) | Note |
|---|---|---|
| 0 | 1970-01-01 00:00:00 UTC | Unix epoch start |
| 978307200 | 2001-01-01 00:00:00 UTC | Common “Y2K-era” test boundary |
| 1000000000 | 2001-09-09 01:46:40 UTC | One billion seconds since epoch |
| 1609459200 | 2021-01-01 00:00:00 UTC | Start of UTC year 2021 |
| 1700000000 | 2023-11-14 22:13:20 UTC | Illustrative “round” billion-scale value |
When an API returns 1700000000000 (13 digits), that is the same instant expressed in milliseconds. This tool counts digits and picks seconds versus milliseconds automatically so you are less likely to misread logs or JSON payloads.
A Unix timestamp is the total number of seconds elapsed since January 1, 1970 at 00:00:00 UTC — called the Unix epoch. It is a plain integer with no time-zone component, making it the most reliable way to store and compare time across distributed systems, databases and APIs.
A 10-digit timestamp is in seconds (e.g. 1712217600). A 13-digit timestamp is in milliseconds (e.g. 1712217600000). They represent the same moment — just at different precision. JavaScript uses milliseconds; most other languages and databases use seconds. This tool detects the format automatically.
Paste your Unix timestamp into the top input field. The tool converts it instantly as you type and shows six formats: local time, UTC, ISO 8601, epoch in seconds, epoch in milliseconds, and relative time (e.g. "3 hours ago"). Each output has its own Copy button.
The two most common causes: (1) mixing up seconds and milliseconds — a 10-digit seconds value passed to a JavaScript new Date() without multiplying by 1,000 will appear to be in 1970; (2) time-zone confusion — the UTC and local outputs will differ by your offset, but both are correct representations of the same moment.
Both, always. Every conversion shows your local time (in your browser's system time zone), UTC, and ISO 8601 (which uses the Z suffix for unambiguous UTC). The relative time — such as "2 days ago" — is always calculated from the current moment and is time-zone independent.
Yes — free and no account is required. Conversions run in your browser using the JavaScript Date API; your timestamp and date values are not sent to UseBoldTools servers to perform the conversion. Like most websites, aggregate page analytics may apply — see the Privacy Policy for details.
Explore more utilities on the Developer Tools hub, or jump to these popular companions: