Unix timestamp converter
Read timestamps in logs, tokens and API payloads without mental arithmetic.
| Interpreted as | Unix seconds |
|---|---|
| Unix seconds | 1700000000 |
| Unix milliseconds | 1700000000000 |
| ISO 8601 (UTC) | 2023-11-14T22:13:20.000Z |
| RFC 7231 (HTTP date) | Tue, 14 Nov 2023 22:13:20 GMT |
| Local (UTC) | available after page load |
| Relative | — |
| Day of week | Tuesday |
| Day of year / ISO week | 318 / W46 |
Numbers of 12 or more digits are read as milliseconds. Everything runs in your browser.
Keep your incident timeline in one consistent time zone. Free for 5 monitors, no credit card.
Start monitoringHow it measures
- Numbers with 12 or more digits are treated as milliseconds, shorter ones as seconds.
- Dates are parsed by the browser's Date implementation; ISO 8601 with an explicit offset or Z is unambiguous.
Limits
- Dates without a zone are interpreted by the browser, which can differ from your server. Always include an offset in logs.
- Leap seconds are not representable in Unix time.
Troubleshooting
- Date is off by a few hours
- The source wrote local time without an offset. Compare with the UTC value and the zone your servers run in.