Unix Timestamp Converter
ConverterConvert between Unix timestamps and human-readable dates with ISO 8601 output. Essential for log analysis, API debugging and cross-timezone scheduling work.
01970-01-01 00:00:00 GMT+00:00Related Tools
About Unix Timestamp Converter
A log shows 1700000000, the database stores milliseconds, an API returns a Unix time — all just digit strings you cannot read by eye. This tool converts Unix timestamps to and from human-readable date-time locally in your browser. For instance, Unix seconds 1710000000 becomes 2024-03-09 17:00:00 (UTC), or back to epoch milliseconds — useful for log and API fields.
How to Use
- Open the Timestamp Converter tool
- Enter a Unix timestamp (seconds or milliseconds) or select a date/time
- Automatically converts to human-readable date and ISO 8601 format
- View timezone information and relative time
- Supports batch conversion: one timestamp per line
Use Cases
- Read log times — Convert a Unix timestamp from a log into a local date to pinpoint when an event happened.
- Debug time zones — Toggle one timestamp between UTC and local to spot an offset problem.
- Build test values — Convert a chosen date to a timestamp for boundary tests in APIs or databases.
- Check expiry — Turn a token or cache expiry timestamp into a date to see if it has lapsed.
- Tell ms apart — Decide if a number is seconds or milliseconds to avoid a 1000x error.
- Schedule cron jobs — Convert a human-readable schedule to a Unix timestamp for testing cron trigger logic.
- Migration ordering — Turn a migration file's timestamp prefix into a readable date to verify the ordering of pending migrations.
FAQ
How does it tell seconds from milliseconds?
It judges by digit count: 10 digits is usually seconds, 13 is usually milliseconds. You can also set the unit manually to prevent misreads.
What is the Unix epoch?
Time elapsed since 1970-01-01 00:00:00 UTC, independent of time zone; the offset is applied only when displaying in your chosen zone.
Are negative timestamps supported?
Yes. Negative values represent times before 1970, useful for converting earlier historical dates.
Does the year 2038 problem affect it?
The 2038 issue stems from 32-bit signed overflow. This tool uses a wider numeric range, so dates beyond 2038 convert fine.
Does my computer time zone affect the result?
It displays in your selected zone. Choosing local ties output to system settings; pick UTC explicitly when debugging to avoid ambiguity.
Why is the API time 8 hours off from my local time?
Almost always a timezone matter: the API stores UTC while you view in your local zone (China is UTC+8). First confirm the unit — seconds vs milliseconds — then compare both in UTC. If the field ends with Z or says Utc, the source is UTC. Pin one timestamp in this tool and switch it between UTC and local side by side: if the gap is a whole number of hours, it is a timezone mismatch, not corrupted data, so fix the convention used at storage or display.
Why do seconds and milliseconds display different times for the same value?
The unit is wrong. Seconds are usually 10 digits, milliseconds usually 13: feeding seconds into a millisecond field gives a time near 1970, and the reverse shifts by roughly a millennium. Languages like JS Date.now() and datetime(3) columns return milliseconds, while many logs and shell tools like date +%s return seconds. When unsure, look at the digit count or calibrate against a known reference timestamp, then convert in the correct unit.