Why boundaries matter
Most timestamp bugs appear at the edges: a signed 32-bit time_t overflows at 2038-01-19T03:14:07Z, JavaScript Date ends at year 275760, int64 nanoseconds end in 2262, and NTP era 0 wraps in 2036. Test fixtures that include these values catch overflow, sign and rounding errors before production does. Every example here converts exactly, and the converter shows a note when a value is beyond a common runtime's limit.
Examples to try
Using the examples as fixtures
Each example loads with its unit locked, so the output does not depend on auto-detection. Copy the ISO and Unix rows straight into your test cases. The Batch tab converts a whole list of fixtures at once, and the JSON export records the settings that produced them.
Questions
- What happens in 2038?
- Signed 32-bit Unix time reaches 2147483647 at 2038-01-19T03:14:07Z and wraps to -2147483648 (1901-12-13). Systems using 64-bit time_t are not affected.
- Is epoch 0 midnight on 1 January 1970 everywhere?
- It is 00:00:00 UTC. In New York it was 19:00 on 31 December 1969, and in India it was 05:30 on 1 January 1970.
- What is the smallest negative 32-bit timestamp?
- -2147483648, which is 1901-12-13T20:45:52Z.