Unix timestamp converter — seconds & milliseconds
Convert Unix timestamps (seconds or milliseconds) to readable dates — local time and UTC together so an “off by eight hours” moment does not waste your afternoon. One-click current time helps with logs, orders, and token expiry fields.
Timestamps count from 1970-01-01 UTC in seconds or milliseconds. `1710000000` in a log is meaningless until converted.
Local vs. UTC differs by your timezone — for many users that is eight hours from UTC, and that is expected, not a bug. Cross-timezone systems: trust UTC first.
Ten digits ≈ seconds; thirteen ≈ milliseconds. Swapping them lands in 1970 or the far future.
How to convert
- Enter timestamp or date, or click current time
- Confirm seconds vs. milliseconds
- Copy ISO, local, or UTC as needed
Pain this page removes
- Local and UTC side by side at a glance.
- Seconds/milliseconds toggle to avoid magnitude mistakes.
- Current time button for quick test data.
Scenarios
- Reading epoch values in server logs
- Checking whether JWT `exp` already passed
- Writing event start time as epoch for storage
Tips
- Count digits before picking seconds vs. milliseconds.
- For logs, prefer UTC, then map to local mentally.
- DST regions follow browser timezone rules.
Examples
| Input | Output | Note |
|---|---|---|
| 10-digit number | Interpreted as seconds | Common in logs |
| 13-digit number | Interpreted as milliseconds | Common in JavaScript |
Timestamp FAQ
- Why eight hours off?
- Compare local and UTC fields — often comparing local to UTC directly.
- Pick any timezone?
- This page focuses on browser local and UTC. Convert further in code if needed.
- Date string formats?
- ISO strings work best; if parsing fails, try the timestamp direction instead.