Unix Timestamp Converter
Paste a Unix timestamp (seconds or milliseconds) or any date to see it in UTC, local time and ISO 8601.
Current Unix time:
Worked examples
Reading a Unix timestamp
1700000000
Unix (seconds) 1700000000 Unix (milliseconds) 1700000000000 ISO 8601 (UTC) 2023-11-14T22:13:20.000Z UTC Tue, 14 Nov 2023 22:13:20 GMT
The local time line depends on your timezone and the relative line changes as time passes, so only the first four lines are fixed.
ISO date to timestamp
2026-10-15T09:30:00Z
Unix (seconds) 1792056600 Unix (milliseconds) 1792056600000 ISO 8601 (UTC) 2026-10-15T09:30:00.000Z UTC Thu, 15 Oct 2026 09:30:00 GMT
Because the input ends in Z, it is read as UTC; a date without a timezone would be read in your local timezone instead.
About Unix Timestamp Converter
A Unix timestamp counts the seconds elapsed since 1 January 1970 at 00:00:00 UTC, known as the Unix epoch. Many systems store times this way because a single integer is simple to compare, sort and calculate with. Some platforms use milliseconds instead, so a 13-digit value rather than a 10-digit one usually indicates milliseconds.
This converter turns a timestamp into UTC, local time, ISO 8601 and relative time, and it works in both directions, so you can also turn a date into a Unix value. Choose seconds or milliseconds before converting to avoid a result that is off by a factor of one thousand. Leap seconds are not counted in Unix time, so results can differ slightly from atomic time.
How to use Unix Timestamp Converter
- Enter a Unix timestamp, or a date and time, in the input field.
- Select seconds or milliseconds so the value is read correctly.
- Read the UTC, local time, ISO 8601 and relative time outputs.
- Copy the format your code, log or database requires.
Common uses
- Decoding a created_at field from a JSON API response.
- Comparing event times in server logs that use UTC.
- Setting an expiry time for a token or cache entry.
- Converting a date into ISO 8601 for a database import.
Frequently asked questions
What is the Unix epoch?
The Unix epoch is the reference point 1 January 1970 at 00:00:00 UTC. Unix time is the number of seconds that have passed since that moment, and it is counted the same way worldwide. Negative values represent moments before the epoch. Because the count starts from UTC, the same timestamp shows different clock times in different time zones.
How do I tell whether a timestamp is in seconds or milliseconds?
Count the digits. A current timestamp in seconds has ten digits, while the same moment in milliseconds has thirteen. Millisecond values are exactly one thousand times larger. If a converted date lands in 1970 or in the far future, the unit is probably wrong, so switch the setting and convert again.
Does Unix time account for leap seconds?
No. Unix time assigns every day exactly 86,400 seconds, so leap seconds are not counted as extra seconds. Systems handle leap seconds in different ways, so timestamps can differ slightly from International Atomic Time. For most applications the difference is negligible, but precise timing work needs care.
Why does my timestamp show a different time than I expect?
A common reason is a time zone mismatch. Unix timestamps are defined in UTC, so the displayed clock time depends on the offset you apply. Daylight saving changes can also shift the local reading. Compare the UTC output with your expected value first, then apply your time zone offset to find the difference.
What is the ISO 8601 format for dates?
ISO 8601 is an international standard for writing dates and times in a fixed order, from year to second. A UTC example is 2026-10-15T09:30:00Z, where the letter T separates date and time and the Z indicates UTC. Offsets such as +01:00 can be added instead. The format sorts correctly as text, which makes it popular in logs and APIs.