Confirm the source unit
Use seconds for a seconds-based API or the JavaScript/Java preset for milliseconds. Detection proposes a unit for one 10-, 13-, 16- or 19-digit number; it waits for your confirmation.
Date and time
Convert one value or a batch using explicit units and a named timezone.
Your input is processed in this browser and is not sent to a server.
One decimal integer or strict date with seconds per line. Choose the timestamp unit. Dates may include Z or a numeric offset; otherwise the selected timezone is used. The report highlights the selected unit value and its nanosecond remainder while retaining all four units.
A suggestion for one 10-, 13-, 16- or 19-digit integer only. Confirm the source unit before applying; detection never changes it automatically.
Coarser units round toward negative infinity and flag a remainder. Now uses a millisecond device-clock snapshot; extra digits do not add clock precision.
Unzoned times that are missing or repeated at a clock change are rejected. An explicit offset determines the instant; the selected zone controls display.
Reverse requires fresh results with no errors. It uses UTC dates in one direction and nanosecond integers in the other to preserve precision.
Up to 1,000 physical lines and 100,000 UTF-16 code units. Empty lines are reported as errors.
Enter input or choose an example to begin.
A Unix timestamp converter helps when a JavaScript event, a server log and a tracing export represent the same instant with different numbers. Select the source unit before comparing the results.
This epoch converter keeps integer nanoseconds intact. A date without an offset needs a timezone; a date ending in Z or a numeric offset already identifies an instant.
The Unix timestamp converter preserves microsecond and nanosecond input instead of passing a large integer through floating-point arithmetic. Compare coarse values with the remainder markers before copying them.
An overnight log can show different calendar dates in UTC and your selected zone. Both displays refer to one instant, so a timezone change does not alter the underlying timestamp.
Use seconds for a seconds-based API or the JavaScript/Java preset for milliseconds. Detection proposes a unit for one 10-, 13-, 16- or 19-digit number; it waits for your confirmation.
Enter an IANA zone such as Europe/Berlin when a date has no offset. At a repeated or missing daylight-saving hour, supply an explicit offset to identify an instant.
Automatic conversion refreshes after edits; turn it off to run manually. Example, Clear, Now and Reverse show a replacement preview. Reverse needs fresh, entirely successful results; Undo restores the previous input and output.
Convert timestamp to date using seconds, milliseconds, microseconds or nanoseconds. Results retain all four unit values and the UTC instant.
Read the selected zone beside UTC. Date to timestamp interprets unzoned input in that zone; a supplied offset takes precedence.
One value per physical line, with line and column positions for failures. Blank lines remain errors so an incomplete batch cannot look complete.
Copy or download the report with every row, including rows beyond the visible preview. Changed input or options disable export until the report is refreshed.
Select timestamp to date, choose the unit used by the source system and enter the integer. The report shows UTC and your chosen timezone. For a batch, use one integer per line.
For contemporary dates, 13 digits usually means milliseconds and 10 usually means seconds. Digit count is a clue, not a guarantee; confirm the unit against the producer’s documentation.
The number identifies an instant relative to the UTC epoch and stores no regional timezone. A timezone is needed only to display it or interpret a local date without an offset.
Yes. Negative values describe instants before 1970-01-01T00:00:00Z. Coarser outputs use floor division, so a tiny negative fraction does not incorrectly become zero.
Regional display follows IANA timezone rules. For reverse conversion, an unzoned local time that occurs twice or does not exist is rejected; provide a numeric offset to disambiguate.
Unexpected result?
Check a known instant with the Unix timestamp converter, then export a complete report with its chosen unit and timezone.