Convert Unix timestamps to human-readable dates and vice versa
A timestamp converter translates Unix timestamps into human-readable dates and back. A Unix timestamp is the number of seconds elapsed since January 1, 1970 at 00:00 UTC (the "epoch") — a single integer like 1718200000 that uniquely identifies a moment in time regardless of time zones, locales or calendar formats. That simplicity makes timestamps the standard way computers store and exchange time: databases, log files, APIs, JWT expiry fields and cron systems all speak Unix time.
The catch is that humans can't read them. This tool converts in both directions instantly — paste a timestamp to see the date in your local time and UTC, or pick a date to get its timestamp — and handles both seconds and milliseconds (JavaScript's Date.now() returns milliseconds, which is a classic source of off-by-1000 bugs).
You probably mixed seconds and milliseconds. A 10-digit value (1718200000) is seconds; 13 digits (1718200000000) is milliseconds. Treating milliseconds as seconds lands you in the year 56,000+; the reverse lands shortly after 1970.
No — that is their superpower. A timestamp is always UTC-based; the same instant has the same number everywhere on Earth. Time zones only enter the picture when you format it into a human-readable date.
Systems storing timestamps as signed 32-bit integers overflow on January 19, 2038, when the count exceeds 2,147,483,647. Modern systems use 64-bit integers, which postpone the problem by about 292 billion years.
No. Unix time pretends every day has exactly 86,400 seconds and ignores leap seconds. For everyday use this is irrelevant; only high-precision scientific timing has to care.
UUID Generator · Base64 Encoder · Base64 Decoder · Hash Generator · Color Converter · Number Base Converter