Unix Timestamp Converter
Convert between unix timestamps and readable dates in both directions, live as you type.
Current unix time
—
Options
Processed on your device — nothing is sent anywhere.
How it works
- Paste a unix timestamp to see the matching date in your local time zone and in UTC.
- Or pick a date and time to get the corresponding timestamp in seconds and milliseconds.
- Use the copy buttons to grab the current unix time or any converted value.
Frequently asked questions
- What is a unix timestamp?
- A unix timestamp is the number of seconds that have elapsed since January 1, 1970 at 00:00:00 UTC, known as the unix epoch. It is a compact, time-zone-independent way to represent a point in time, widely used in databases, log files and APIs.
- How does the tool tell seconds from milliseconds?
- Timestamps in seconds currently have 10 digits, while millisecond timestamps have 13. The tool assumes values with 12 or more digits are milliseconds and everything shorter is seconds, and it shows which unit was detected so you can verify. This heuristic works for all dates between 1973 and far into the future.
- Why do the local and UTC dates differ?
- A timestamp itself has no time zone — it marks a single instant worldwide. The local date shows that instant in your device’s time zone, while the UTC date shows it at Coordinated Universal Time. The difference between the two is simply your UTC offset, including any daylight saving shift.
- How do I convert a date back into a unix timestamp?
- Use the date picker to choose a day and time, and the tool immediately shows the matching timestamp in both seconds and milliseconds. The date you pick is interpreted in your local time zone, which is what most people expect. If you need the timestamp for a UTC time instead, adjust the time by your UTC offset before reading the result.
- What is the year 2038 problem?
- Systems that store unix time in a signed 32-bit integer overflow on January 19, 2038, when the count of seconds exceeds 2,147,483,647. Modern platforms use 64-bit integers, which pushes the limit billions of years out. This converter uses JavaScript numbers and handles dates far beyond 2038 without any issue.
About this tool
This unix timestamp converter translates machine time into human time and back again. Paste any epoch value — seconds or milliseconds — and it instantly shows the corresponding date in your local time zone and in UTC. Work the other way by picking a calendar date and time to get the exact timestamp, and copy the current unix time whenever you need a fresh reference point.
Everything runs client-side in JavaScript. The value you paste is parsed by your own browser using its built-in Date implementation, so nothing is sent to a server, logged, or stored. That matters when the timestamps you are debugging come from production logs, authentication tokens, or customer records — the data never leaves your machine. Detection between seconds and milliseconds is automatic based on digit count, and the tool labels which unit it assumed so you can confirm at a glance.
Timestamps show up everywhere in day-to-day development: expiry claims in JWTs, created_at columns in databases, cache headers, cron debugging, API responses, and crash logs. Rather than mentally dividing by 86,400 or hunting through documentation, you can settle questions like “when does this token expire?” or “what local time was this error logged?” in a couple of seconds. Because both local and UTC renderings are shown side by side, off-by-one-timezone mistakes are easy to catch.
A few practical tips: if a converted date lands decades in the past or future, you probably mixed up seconds and milliseconds — a factor of 1,000 shifts a 2026 date to 1970 or to the year 56,000. When comparing timestamps from different servers, convert both to UTC first so daylight saving changes cannot mislead you. And remember that a timestamp is an instant, not a date: the same value can fall on two different calendar days depending on the time zone reading it.