Unix Timestamp Converter
Overview
The Unix Timestamp Converter provides bidirectional conversion between Unix timestamps (seconds since January 1, 1970 UTC) and human-readable dates. It supports both seconds and milliseconds precision, handles multiple timezones, and offers batch conversion for working with multiple timestamps simultaneously.
Tips
Don’t mix seconds and milliseconds - JavaScript uses milliseconds (1700000000000) while most Unix systems use seconds (1700000000). The difference is a factor of 1000.
Unix timestamps are always in UTC - When you display a timestamp to users, convert it to their local timezone. The timestamp itself has no timezone information embedded.
Use 64-bit integers to avoid the Year 2038 problem - 32-bit signed integers max out on January 19, 2038. Modern systems should use 64-bit integers for timestamps.
Negative timestamps work for dates before 1970 - Unix timestamps can be negative to represent dates before the epoch (e.g., -86400 = December 31, 1969).
Store timestamps as integers, not strings - This keeps storage compact, makes sorting and comparison easy, and avoids timezone ambiguity in your database.