Unix Timestamp Converter — Guide
Convert a Unix epoch timestamp (seconds or milliseconds) to a readable date, or turn a date into a timestamp online.
What it is and when to use it
A Unix timestamp is one integer with three disguises: seconds, milliseconds, and — rarely, in telemetry from old systems — microseconds. The single most common debugging error in this format is reading milliseconds as seconds: a 13-digit number decoded as seconds lands in the year 45,000-something, and reading seconds as milliseconds lands in 1970. Digit count is the fastest triage (10 digits is seconds for anything after 1970 until 2038, 13 digits is milliseconds). The second classic is time zone: the same integer prints as different wall-clock times in different tools, and only because rendering differs — the instant itself is unambiguous. That is why logs should store UTC and render locally. The third edge everyone eventually meets: 2038-01-19, when the signed 32-bit seconds counter overflows on legacy systems; modern 64-bit code is unaffected, but embedded devices, old databases and some file formats still carry the limit. This converter shows all three unit readings side by side, so a wrong-digit mistake becomes visible instead of silent.
Converts a Unix epoch timestamp (seconds or milliseconds) into a readable date, or turns a date back into a timestamp.
How to use it
- Paste a timestamp or enter a date and let the format auto-detect
- Read the Unix timestamp in seconds and the milliseconds value
- Switch the format if you need ISO 8601, RFC 3339, UTC or your locale
A worked example
Things that trip people up
- Unix timestamps in seconds are 10 digits (good until 2286); milliseconds are 13 digits
Questions people ask
- How do I tell seconds from milliseconds at a glance?
- Count the digits: 10 digits is seconds (until 2038), 13 digits is milliseconds. A 13-digit value read as seconds produces an absurd far-future date — that absurdity is the tell.
- Does the timestamp itself contain a time zone?
- No. An Unix timestamp is an absolute instant; time zones only affect how it is displayed. Store UTC, render local — the integer never changes.
- What is the 2038 problem?
- Signed 32-bit seconds counters overflow on 2038-01-19. 64-bit systems are fine, but embedded devices, old databases and some file formats still carry the limit.
- Why do two tools show different times for the same number?
- Different rendering time zones or different unit assumptions. Check digit count first, then the tool timezone setting; the underlying instant is identical.
Next steps
Open the Unix Timestamp Converter tool
- JWT Decoder & Parser
- Base64 Encoder & Decoder
- Date Converter
- Integer base converter
- Roman numeral converter
- Base64 to Image
Spotted something wrong on this page? Tell us via Contact Us