← All tools
Unix Timestamp Converter
Epoch to date and back, with the unit detected rather than guessed.
Why this exists
Logs, JWTs and APIs record time as Unix epochs — unreadable at a glance, and ambiguous between seconds and milliseconds. Convert both ways when correlating log lines across systems.
🔒 Runs in your browser — nothing is sent anywhere
Read as seconds (detected)
| ISO 8601 (UTC) | 2025-08-19T10:40:00.000Z |
| RFC 1123 (UTC) | Tue, 19 Aug 2025 10:40:00 GMT |
| Your timezone | … |
| Day | Tuesday |
| Epoch seconds | 1755600000 |
| Epoch milliseconds | 1755600000000 |
| Relative | … |
The unit is the part that bites. A bare number can be seconds, milliseconds, microseconds or nanoseconds, and reading it wrong gives you 1970 or the year 57000 with no error at all — so the detected unit is always shown, and can be overridden.