Unix Timestamp Converter
Convert Unix timestamps (epoch time) to human-readable dates and back. Auto-detects seconds (10 digits), milliseconds (13 digits), or microseconds (16 digits). Supports ISO 8601 input for reverse conversion.
Current epoch (s): 0
Current epoch (ms): 0
About Unix Timestamp Converter
Unix timestamps are the standard way to represent moments in time across programming languages, databases, and APIs — the number of seconds since January 1, 1970 UTC. But raw integers are hard for humans to read, and different systems use different scales (seconds, milliseconds, microseconds). This converter auto-detects the scale based on the number's magnitude and shows the timestamp in every useful format simultaneously: seconds, milliseconds, ISO 8601, local time, and UTC.
The tool also converts in reverse — paste an ISO 8601 date and get the epoch values. Useful for debugging API responses that include timestamps, converting between database column formats (some use seconds, some use milliseconds), and quick sanity checks on 'when did this happen' from log files. The relative-time display ('3 hours ago', 'in 2 days') helps interpret the timestamp at a glance.
How to Use
Paste any Unix timestamp (10, 13, or 16 digits) or a date string. The tool auto-detects the format.
See the timestamp in seconds, milliseconds, ISO 8601, local time, and UTC — all at once.
Click any value to copy it to the clipboard.
Use the 'Now' button for the current moment (updates every second).
Frequently Asked Questions
What is a Unix timestamp?
The number of seconds elapsed since January 1, 1970 00:00:00 UTC — the 'Unix epoch'. A standard way to represent moments in time as a single integer, universally supported across programming languages and systems.
How do I tell seconds from milliseconds?
Length: 10-digit numbers are seconds (Unix standard); 13-digit numbers are milliseconds (JavaScript standard); 16-digit numbers are microseconds. This tool auto-detects based on the number's magnitude.
What is the year 2038 problem?
Signed 32-bit integers overflow at 2^31 seconds past 1970 — January 19, 2038 at 03:14:07 UTC. Systems using 32-bit signed integer timestamps will wrap to negative numbers. Modern systems use 64-bit integers to avoid this. Not something you personally need to fix — but a reason to prefer 64-bit epoch storage in new systems.
Are timestamps timezone-independent?
Yes — Unix timestamps represent an absolute moment in UTC. When you display them, you convert to a local timezone. Two people in different timezones looking at the same timestamp see different local times but agree on the underlying moment.