Unix timestamp converter
Convert Unix timestamps in seconds or milliseconds to dates, or ISO dates to epoch time. Shows UTC, local, ISO 8601 and relative time, plus the current timestamp.
About Unix timestamp converter
The Unix timestamp converter shows the current epoch time, ticking every second, and converts any timestamp or date you enter. Paste a value from a log, database or API and you get it in Unix seconds, Unix milliseconds, ISO 8601, UTC, your local time and relative terms such as “3 days ago”, each with a copy button.
Seconds and milliseconds are detected automatically: numbers below 100 billion are read as seconds, larger ones as milliseconds. You can also enter an ISO 8601 date such as 2026-01-01T12:00:00Z to get its timestamp. Local times use your device’s time zone, and every conversion runs in your browser.
How to use Unix timestamp converter
- Copy the current Unix timestamp from the top of the tool if that is all you need.
- Enter a timestamp in seconds or milliseconds, or a date such as 2026-01-01T12:00:00Z, in the Timestamp or date field.
- Read the conversions: Unix seconds, Unix milliseconds, ISO 8601, UTC, Local and Relative.
- Select the copy button next to any row to copy that value.
Features
- Shows the current Unix timestamp in seconds, updated every second.
- Detects seconds or milliseconds automatically, using 100 billion as the threshold.
- Accepts negative timestamps for dates before 1970, as well as decimal values.
- Parses ISO 8601 dates and other date strings your browser understands.
- Shows local time with the full weekday, date and time zone, plus a relative description.
Common uses
- Reading created_at or expiry values in API responses and database rows.
- Converting log timestamps to local time while investigating an incident.
- Getting the epoch value of a date for a query, scheduled job or test.
- Checking the exp time of a JWT or a cache entry.
Tips
- Add Z or an offset such as +02:00 to a date to be explicit about its time zone. Browsers treat a date-only value like 2026-01-01 as midnight UTC, but a date-time without an offset as your local time.
Frequently asked questions
What is a Unix timestamp?
It is the number of seconds since 00:00:00 UTC on 1 January 1970, the Unix epoch, not counting leap seconds. Because it is a single number with no time zone, it is a common way to store and exchange points in time in databases, logs and APIs.
How do I tell seconds from milliseconds?
Current timestamps in seconds have 10 digits, such as 1767225600, while milliseconds have 13. JavaScript’s Date.now() returns milliseconds; most Unix tools and many APIs use seconds. This converter treats anything below 100,000,000,000 as seconds, which covers dates up to the year 5138.
What is the year 2038 problem?
Systems that store Unix time as a signed 32-bit integer overflow at 03:14:07 UTC on 19 January 2038, when the value passes 2,147,483,647, and wrap around to a date in 1901. Modern systems use 64-bit values. This converter handles dates far beyond 2038.
Does a Unix timestamp depend on the time zone?
No. A timestamp is the same everywhere at a given moment; only its display changes. The UTC row shows it in Coordinated Universal Time and the Local row in your device’s time zone. A timestamp that looks off by whole hours usually means a time zone was applied twice.
Are leap seconds included?
No. Unix time assumes every day has exactly 86,400 seconds and ignores leap seconds, which keeps calculations simple. Unix time is therefore not an exact count of elapsed seconds, but it matches what operating systems and JavaScript use.
Is my input uploaded?
Tools run in your browser. Files, text and results are not uploaded to our servers and are cleared when you leave the tool.
Your privacy comes first
Tools run in your browser. Files, text and results are not uploaded to our servers and are cleared when you leave the tool.