Seconds vs. milliseconds
Unix timestamps come in different resolutions. Seconds (10 digits, e.g. 1748520000) are the classic Unix format used by databases, cron, and most back-end languages. Milliseconds (13 digits) are what JavaScript's Date.now() and many JSON APIs return. Microseconds (16 digits) appear in high-resolution logging. This tool detects the resolution from the number of digits, so you don't have to divide or multiply by 1000 yourself.
Why Unix time is always UTC
A Unix timestamp encodes a single absolute moment — it has no timezone. The same timestamp is the same instant everywhere on Earth; only the display changes by timezone. That's why this tool shows both your local time and UTC: the underlying value is identical, but the human-readable form differs by your offset.
The Year 2038 problem
Systems that store Unix time in a signed 32-bit integer overflow on 19 January 2038, when the value exceeds 2,147,483,647. Modern systems use 64-bit timestamps, which push that limit roughly 292 billion years into the future.