About this tool
What does it convert?
Between Unix timestamps, ISO 8601 strings, relative times (“3 days ago”) and human-readable dates — timezone- and locale-aware. The lingua franca for debugging logs, APIs and scheduled jobs.
How to use it
- Paste a timestamp, ISO string or date to convert all ways at once.
- Switch timezones to read server logs in local time.
- Generate the exact format your API expects.
Examples
1728000000→ 2024-10-04T00:00:00Z: when did that token expire?- Reading UTC cloud logs in your local timezone.
- Producing ISO strings with offsets for API payloads.
Important limitations
- Unix timestamps ignore leap seconds; ultra-precise systems need TAI-aware libraries.
- Ambiguous formats (01/02/2024: Jan 2 or Feb 1?) depend on locale — prefer ISO 8601.
- Daylight-saving transitions create missing/repeated hours; schedule critical jobs outside them.
Privacy
Conversion is local arithmetic. Log timestamps can reveal infrastructure patterns — they stay here.
Frequently asked questions
Milliseconds or seconds?
10 digits = seconds, 13 = milliseconds. Divide or multiply by 1000 to switch.
Why is my date off by hours?
Timezone mismatch — check whether the source is UTC or local, and whether an offset was applied twice.
What format should APIs use?
UTC ISO 8601 with offset (2024-10-04T00:00:00Z): unambiguous everywhere.