Key takeaways
- The timestamp unit must be known; automatic detection is only a magnitude heuristic.
- A display time zone changes the clock representation of an instant, not the instant itself.
- Reverse conversion requires Z or a numeric offset to avoid ambiguous local date input.
The Unix timestamp converter translates a numeric timestamp into device-local time, UTC, ISO 8601 and a chosen display zone. It also converts an ISO date with an explicit offset into seconds and milliseconds. Use it when inspecting API responses, comparing logs or checking a stored date’s intended instant.
Keep three questions separate: what unit the number uses, what instant it represents and which zone should display it. A timestamp can be correct while a clock display looks surprising because the display uses another zone. Conversely, choosing a familiar zone cannot repair a timestamp read in the wrong unit.
Before you start
Check the producer’s documentation for seconds or milliseconds. Contemporary second timestamps commonly have about ten digits, while millisecond timestamps commonly have about thirteen, but this is not a definition. Dates near the epoch or far into the future can break that shortcut. Use the explicit unit option whenever the source tells you which one it uses.
The Unix epoch corresponds to 1970-01-01 at midnight UTC. JavaScript Date represents time with millisecond precision, and this interface uses those Date values for formatting. The ECMAScript Date specification explains the time model and supported range; checked 16 November 2026. Leap seconds are not represented as separate seconds here.
For reverse conversion, prepare an ISO-style date that ends with Z or a numeric offset such as +05:30. The interface deliberately requires that information. It does not interpret a bare wall-clock date in the selected display zone, which would need rules for ambiguous and missing times around daylight-saving transitions.
Step by step with CrizaTools
- Open Unix Timestamp Converter and enter Unix timestamp.
- Choose Timestamp unit as Auto-detect, Seconds or Milliseconds. Use the explicit setting when the source unit is known.
- Alternatively press Now. It captures the device clock once and selects Milliseconds.
- Choose Display time zone. The list comes from the browser’s Intl support, with UTC and the device zone available.
- Read Local time (device), UTC, ISO 8601 and the row named for the selected zone. Use Copy ISO if you need a portable UTC string.
- For the reverse direction, enter Date to timestamp (ISO with offset), including
Zor an offset. - Read the separate Seconds and Milliseconds results and use their copy buttons. The display-zone selector does not reinterpret that date input.
Both directions update independently. An invalid numeric timestamp does not prevent you from checking a valid reverse date, and an invalid reverse date does not erase a valid numeric timestamp’s formatted output. Read the error beside the relevant field rather than assuming every row belongs to a single combined operation.
Two worked examples
Example 1: the epoch with explicit units. Enter 0 and select Seconds. ISO 8601 output is 1970-01-01T00:00:00.000Z. UTC also shows midnight on 1 January 1970. Choose Asia/Kolkata for the display zone and the corresponding clock time is 05:30 on the same date.
The instant did not move when the zone changed. Local time (device) still follows your own device settings. As a unit check, enter 1000 and choose Milliseconds: the result is one second after the epoch. Choose Seconds instead and it becomes 1000 seconds after the epoch. Small values are therefore a useful reminder that the unit matters independently of digit count.
Example 2: one modern instant represented two ways. Enter 2026-11-16T00:00:00Z under Date to timestamp. The reverse results are 1794787200 seconds and 1794787200000 milliseconds. Enter either value in the numeric field with the corresponding explicit unit and the ISO output returns to the same UTC instant.
Now replace the date text with 2026-11-16T05:30:00+05:30. The offset says that the written clock is five hours and thirty minutes ahead of UTC. Subtracting that offset gives midnight UTC, so both numeric results remain exactly the same. Changing Display time zone affects the readable output, not either numeric timestamp from this date input.
Limits and what to watch for
Auto-detection treats an absolute numeric value of at least 100,000,000,000 as milliseconds and smaller magnitudes as seconds. This is a documented heuristic. It can misclassify early millisecond dates and very distant second dates. A negative value is allowed and represents an instant before the epoch; its magnitude follows the same heuristic.
JavaScript Date’s range is bounded at an absolute 8.64 × 10^15 milliseconds. Out-of-range numeric values are rejected. Date formatting has millisecond resolution, so a fractional second input can retain milliseconds but does not provide arbitrary sub-millisecond precision. Numeric notation is plain decimal; scientific notation is not accepted in the timestamp field.
The reverse field checks real calendar dates and requires an explicit offset. It rejects examples such as 29 February in a non-leap year or an hour of 24. Use an actual date and a conventional time instead of relying on permissive rollover behaviour from another parser.
Time-zone labels and daylight-saving rules come from browser Intl data. The ECMA-402 date-time formatting specification defines that interface; checked 16 November 2026. A browser with older zone data may differ from a newly updated system for changed regional rules. Record the zone and source context when investigating historical logs.
Common mistakes
- Reading milliseconds as seconds and obtaining a distant date.
- Treating the digit-count shortcut as a universal timestamp definition.
- Assuming a Unix timestamp stores a country or time zone.
- Omitting the offset from a reverse-conversion date.
- Expecting the selected display zone to rewrite the date input.
- Treating Now as a continuously running clock rather than a captured value.
Questions and answers
Does the timestamp number include a time zone?
No. It describes an instant relative to the epoch using a specified unit. The local, UTC and selected-zone outputs are different clock representations of that instant, rather than different instants stored in the number.
When should I override Auto-detect?
Override it whenever the producer specifies seconds or milliseconds, and especially for dates near 1970 or far in the future. Automatic magnitude detection is a convenience for common modern values, not evidence about the source’s data contract.
Why must a reverse date include Z or an offset?
It makes the instant explicit. A bare date and time can be ambiguous during a clock change, or mean different instants in different regions. The tool avoids guessing by requiring the offset in the text itself.
Does Now keep updating the result?
No. It reads the device clock once when pressed and stores that millisecond value. Press it again for a new capture. The result is only as accurate as the device clock supplying the value.
Can I convert times before 1970?
Yes. Enter a negative timestamp and explicitly select the correct unit. The supported range still follows JavaScript Date limits, and displayed historical zone offsets depend on the browser’s time-zone data.
Sources
- ECMAScript: Date objects, checked 16 November 2026.
- ECMA-402: DateTimeFormat, checked 16 November 2026.
Inspect instants with Unix Timestamp Converter and calendar intervals with Date Calculator.
Free tools for this
PDF & image
Unix Timestamp Converter
Convert Unix seconds or milliseconds to local time, UTC and ISO 8601. Inspect another time zone, use Now, or convert a date with an explicit offset.
Calculators
Date & Days Calculator
Count the days, weeks and working days between two dates, or add and subtract days from a date.
Calculators
Age Calculator
Find your exact age in years, months and days from your date of birth, on today or any date, plus total days, weeks and a countdown to your next birthday.