A Unix timestamp represents an instant as a numeric distance from the epoch. Errors appear when an application confuses seconds with milliseconds, applies a time zone twice, or tries to store the value in a type that is too small.
Quick verification path
- Identify whether the number uses seconds or milliseconds.
- Convert it and display the UTC date first.
- Apply a local time zone only when presenting the instant to a person.
- Check the range of the destination language, database, or protocol.
- Keep a known example around the epoch for integration tests.
An instant is not its representation
1970-01-01T00:00:00Z is a textual representation of the instant whose
timestamp is 0. A local date without a zone does not necessarily identify one
instant: it may be missing or repeated during a daylight-saving transition.
The tool requires an explicit UTC or local choice and a seconds or milliseconds unit. The guides also cover negative values, the 32-bit limit, leap seconds, and time claims stored in JWTs. This lets you separate a formatting problem from a genuine limit in the receiving system.