Unix Timestamp Converter

Unix time counts the seconds since 1 January 1970 UTC, which makes it perfect for machines and unreadable for humans. Logs, APIs, and databases are full of these numbers. Paste one here to see local time, UTC, and ISO 8601 side by side — or go the other way and turn a date into an epoch value.

How to use it

1. Paste a Unix timestamp; seconds and milliseconds are detected automatically by length.
2. Read the local time, the UTC time, and the ISO 8601 string.
3. Use the reverse panel to turn a date and time into a timestamp.
4. Press "now" to grab the current epoch value for testing.

Frequently asked questions

How do I tell seconds from milliseconds?

Length. A current timestamp in seconds is ten digits; in milliseconds it is thirteen. The tool switches automatically, so a value interpreted as 1970 usually means the units were misread.

Why does the local time differ from UTC?

Because a Unix timestamp is always an absolute UTC instant. Local time applies your time zone offset and any daylight-saving adjustment on top of it.

What is the year 2038 problem?

Systems storing Unix time in a signed 32-bit integer overflow on 19 January 2038. Modern platforms use 64-bit values, which pushes the limit far beyond any practical concern.

Why do developers prefer epoch time?

Because it is a single integer with no time zone, no format ambiguity, and no locale. Comparing and sorting timestamps becomes plain arithmetic.

All free tools · Blog · About · Contact

Also available in: Español · Português · Français · Deutsch