A worked example: timestamp 1757685000
The timestamp 1,757,685,000 converts to Friday, September 12, 2025 at 13:50:00 UTC — exactly that many seconds after midnight on 1 January 1970.
The formula: epoch plus seconds
Date-time = 1 January 1970 00:00:00 UTC + timestamp seconds. There's no arithmetic beyond that single addition — the entire complexity of "what date is this" lives inside correctly breaking that resulting moment down into a year, month, day, and time.
A second example: converting a future launch timestamp
The timestamp 1,798,675,200 converts to Thursday, December 31, 2026 at 00:00:00 UTC — precisely midnight, since that timestamp was chosen as an exact number of days after the epoch with no leftover seconds.
Why the result is always shown in UTC
Unix timestamps have no timezone of their own — they're a single count of seconds, the same number everywhere on Earth at that instant. Displaying the converted result in UTC avoids silently picking a timezone that may not match what the timestamp's original source intended; converting further to a local time zone is a separate, deliberate step.
The most common mistake — seconds vs. milliseconds
A 13-digit number is usually a JavaScript-style timestamp in milliseconds, not seconds — dividing it by 1,000 first (dropping the extra 3 digits) is necessary before converting it here, or the result will land thousands of years in the future.