Unix Timestamp Converter
Convert between timestamps, ISO dates and local time. Free, and runs entirely in your browser — nothing you enter is uploaded, stored or sent to a server.
About Unix Timestamp
Unix time counts seconds since 1970-01-01 UTC, which makes it unambiguous and easy to compare — and completely unreadable. Paste a timestamp and get the ISO form and local time; paste a date and get the timestamp. Leave the field empty to convert the current moment.
Because the same instant is a different wall-clock time everywhere, the result is also laid out across the time zones you select, with an hour-by-hour strip. That turns “this log entry is at 1735689600” into “that was during the European afternoon and the American morning”.
The strip covers a full day by default and scrolls sideways, opening on the hour you asked about. The zone names stay pinned to the left as the hours pass under them, every row shares the same columns so one column is one instant, and a zone chosen twice is still shown once.
Where it helps
- Both directions, with seconds and milliseconds recognised automatically.
- Shows the same instant in as many time zones as you add.
- The hour strip makes overlap between regions immediately visible.
- Runs locally, using your browser's own IANA time zone database.
Limits
- Unix time ignores leap seconds, so it is not a precise count of elapsed SI seconds.
- Zone conversions use the rules your browser knows; a very recent political change may not be reflected in an older browser.
- Historic dates before time zones were standardised carry offsets that are approximations.
- 32-bit systems overflow in 2038; timestamps beyond that are correct here but may not be elsewhere.
Frequently asked questions
Is my timestamp in seconds or milliseconds?
Ten digits is seconds, thirteen is milliseconds. Values are interpreted accordingly, so both paste in cleanly.
Why does the local time differ from my server's log?
The server is probably logging in UTC. The instant is the same; only the presentation differs.
What is the 2038 problem?
A signed 32-bit timestamp overflows on 19 January 2038. Anything storing time in a 32-bit integer needs a wider type before then.
Does it handle dates before 1970?
Yes, as negative timestamps. Some systems reject those, so check what consumes the value.
Related tools
- Timezone Converter — Convert a moment between time zones
- Date Calculator — Difference between dates, or add and subtract time
- Cron Expression Viewer — Explain a cron schedule and list the next runs
- UUID Generator — UUID v1 to v7 — generate any version, or read what one encodes
- Duration Converter — Convert between ISO 8601 durations, seconds, clock time and plain words
More Date & Time tools
- Timezone Converter — Convert a moment between time zones
- Date Calculator — Difference between dates, or add and subtract time
- Cron Expression Viewer — Explain a cron schedule and list the next runs
- Duration Converter — Convert between ISO 8601 durations, seconds, clock time and plain words