Unix Timestamp Converter
Timestamp to human date and back — seconds and milliseconds auto-detected, shown in your timezone and UTC, with a live current timestamp.
676 views
Invalid timestamp
Seconds Since 1970
A Unix timestamp counts seconds since 1970-01-01 00:00 UTC (the epoch): 1,784,000,000 lands in July 2026. APIs and databases love it because it is timezone-free and sorts numerically. JavaScript and many APIs use milliseconds instead — 13 digits instead of 10 — which this tool detects automatically. Conversion runs both directions and displays both your local timezone and UTC.
Trivia that bites: 32-bit signed timestamps overflow on 19 January 2038 (the "Y2038" problem) — modern 64-bit systems are safe for 292 billion years. Negative timestamps encode dates before 1970.
Frequently Asked Questions
Why is my timestamp 3 hours off?
Timestamps are UTC by definition; the shift appears when displaying. Compare the UTC line here with your API — if they match, the data is right and only local rendering differs.
Seconds or milliseconds — which does my system use?
Count digits: 10 digits = seconds (until 2286), 13 = milliseconds. Unix tools and PHP time() use seconds; JavaScript Date.now() and Java use milliseconds.
Similar Tools
Report a Problem
Unix Timestamp Converter