Unix Timestamp Converter
Convert Unix timestamps to human-readable dates and dates back to timestamps — live, bidirectional, with UTC, ISO 8601, local time and relative output.
Current Unix timestamp
1782715004
Mon, 29 Jun 2026 06:36:44 GMT
What is a Unix timestamp?
A Unix timestamp (also called epoch time or POSIX time) is the number of seconds that have elapsed since 00:00:00 UTC on 1 January 1970 — an instant known as the Unix epoch. It's a single integer that represents any moment in time unambiguously, regardless of timezone or locale.
Unix timestamps are the universal language of time in computing. Databases store them. APIs return them. Log files include them. Every programming language can convert to and from them trivially. When you see 1717200000 in a JSON response or a database row, this tool tells you it means June 1, 2024, 00:00:00 UTC.
This tool goes bidirectional: paste a timestamp, get the date in multiple formats. Pick a date, get the corresponding timestamp. A live counter at the top shows the current Unix time ticking in real time.
How to use the converter
- 1
Timestamp → Date
Type or paste a Unix timestamp (in seconds) into the left input. UTC, ISO 8601, local time and relative time appear instantly.
- 2
Date → Timestamp
Use the date/time picker on the right to select any moment. Its Unix timestamp (seconds and milliseconds) appears below.
- 3
Use the live counter
Click 'Use now' to load the current timestamp into the converter and inspect today's date in all formats.
Why developers reach for this daily
Debug API responses
Turn the createdAt: 1717200000 in that API response into a readable date without opening a REPL.
Set expiry times
Calculate the Unix timestamp for 'tomorrow at midnight' or '7 days from now' for token and cache expiry.
Read log files
Server logs often store timestamps as integers. Convert them instantly to understand when an event happened.
Timezone-safe
UTC output eliminates timezone ambiguity — essential for distributed systems with servers in multiple regions.
Common timestamp values to know
- 0 → 1970-01-01T00:00:00Z (the Unix epoch — the origin of time, as far as computers are concerned)
- 1000000000 → 2001-09-09T01:46:40Z — the internet celebrated 'Billennium' when the epoch hit one billion seconds
- 2147483647 → 2038-01-19T03:14:07Z — the 'Year 2038 problem': the max value of a signed 32-bit integer used by old systems to store timestamps
- Current → see the live counter at the top of the tool. At the time of writing, we're roughly 1.7 billion seconds into the Unix era.
Seconds vs. milliseconds
Different languages and APIs use different resolutions. JavaScript's Date.now() returns milliseconds since epoch. Most Unix/Linux tools, databases, and APIs use seconds. The difference is a factor of 1,000 — if your timestamp looks like 1717200000000 (13 digits), it's in milliseconds; divide by 1,000 to get the seconds-based value this tool expects.
Frequently asked questions
Unix time is a count of seconds (a number). UTC is a timezone (an offset from Greenwich Mean Time). A Unix timestamp always represents a moment in UTC, but UTC is how you express that moment in human-readable form.
Your value is probably in milliseconds, not seconds. Divide it by 1,000 and try again. Alternatively, a value of 0 or very small numbers legitimately fall near the Unix epoch in 1970.
On 32-bit systems that store timestamps as signed integers, the maximum is 2,147,483,647 — January 19, 2038. 64-bit systems extend this far beyond any practical concern (billions of years).
JavaScript: Math.floor(Date.now() / 1000). Python: import time; int(time.time()). Bash: date +%s. Go: time.Now().Unix(). Java: Instant.now().getEpochSecond().
Unix time intentionally ignores leap seconds — each day is always exactly 86,400 seconds. This simplifies arithmetic but means Unix time diverges from true UTC by the number of accumulated leap seconds (currently 37).
Need another tool?
Browse the full toolbox or dig into the blog for the engineering behind it.