Unix Timestamp Converter

Count digits. Current-era epoch values have 10 digits in seconds and 13 in milliseconds. If a conversion lands you in the year 56,000 or so, you fed milliseconds into a seconds field.

Your log almost certainly printed local time while the epoch value is timezone-free. Compare against the UTC row first, then apply your zone's offset, and the gap should equal that offset exactly.

1970-01-01T00:00:00Z, the starting point of Unix time. Every epoch value is just the count of seconds before or after that instant.

You get both: a UTC row that's the same for everyone and a Local row rendered in your browser's configured timezone. Comparing the two is a quick way to confirm your machine's offset.

Yes. Moments before the epoch are simply negative second counts, and JavaScript's Date type handles them, so a value like -86400 resolves to the last day of 1969.

No. Unix time pretends every day has exactly 86,400 seconds, which keeps the math simple. The tradeoff is that epoch arithmetic can drift a second from atomic time, which almost no application cares about.

Whatever your operating system and browser report. Change your system timezone and reload, and the Local row shifts accordingly while UTC and the epoch value stay fixed.

Paste epoch seconds into the Unix timestamp field and you instantly convert timestamp to date in three forms: the UTC string, your local time, and ISO 8601. Nothing needs a button press; the rows update as you type.

Yes. The timestamp converter is live, so to convert timestamp to date online you just paste the number and read the rows. Each row has its own copy button for grabbing the exact format you need.

No. As a timestamp converter online it reads epoch seconds and renders the date, so the result matches what any language computes from the same number, whether it came from Python, Go, or a database column.

Yes. The unix time converter shows a date from epoch seconds, and the second card reverses it, so it doubles as a unix date converter that turns an ISO date back into seconds and milliseconds.

Yes. Feed epoch seconds in and you convert epoch time to date across three views: a UTC row identical for everyone, your local row, and ISO 8601. The UTC row answers most debugging questions on its own.

The epoch to utc converter gives you the exact UTC timestamp string, while the epoch to human date converter turns a bare number like 1719912345 into a date and time you can read at a glance. Both come from the same input row.

Both directions live on the page. Paste epoch seconds to convert timestamp to datetime as a full UTC or ISO string, or type an ISO date into the second card to convert timestamp to unix time in seconds and milliseconds. The two cards mirror each other.

Yes. The UTC row never shifts with your machine's timezone, which is the point of a utc time converter. Reading your local row against it works as a time to utc converter too, since the gap between the two rows is exactly your current offset.

Sure. Drop one epoch value in and read the clock time from the UTC or local row; as a time converter that's all it takes, with no setup required.

It shows the full date and time, but as a time converter online you can read just the hour and minute from any row. That also makes it a timestamp to time converter when the clock time is all you're after.

Yes, the second card is that date converter: type an ISO date like 2026-05-26T12:00:00 and it returns the value in seconds and milliseconds. As a date converter online it saves the timezone arithmetic you'd otherwise do by hand.