Turn a timestamp into a date you can read
Paste a Unix timestamp or an ISO date to see a readable date, UTC, the selected time zone, and exact values in seconds and milliseconds. One value produces individual results with copy buttons. A column produces a table with one result per input and an explanation for each invalid row. Use it when inspecting API data, database exports, event logs, or expiration dates. All conversion happens locally; choosing a time zone does not contact an external service.
Timestamp conversion examples
Read Unix seconds
Input
1793707200
Result
2026-11-03T12:00:00.000Z
This value is read as seconds and represents noon UTC on November 3, 2026. The selected zone is shown alongside UTC. Switching the display zone changes the clock shown, not the underlying instant.
Recognize milliseconds
Input
1793707200000
Result
1793707200 seconds
The thirteen-digit value represents the same instant in milliseconds. The result names the detected unit. Override detection when working with older timestamps or values whose length makes the unit ambiguous.
Use an explicit offset
Input
2026-11-03T07:00:00-05:00
Result
2026-11-03T12:00:00.000Z
An offset describes the instant unambiguously. Dates with no offset are read as UTC, as stated beside the input. This avoids guessing which local time zone a copied date originally used.
How to convert timestamps and dates
- Paste one value or a column with one value per line. Numbers and ISO dates can be mixed. Blank lines are skipped while original line numbers are retained.
- Leave unit detection on for ordinary contemporary timestamps, or choose Seconds or Milliseconds explicitly. The selected unit applies only to numeric inputs.
- Choose a named time zone or use your device zone. Use current time for a fresh value, or Choose a date to enter a UTC date and time.
- Copy an individual representation for a single value. For multiple values, review rows needing attention and download the complete CSV, including original inputs and errors.
Timestamp conversion questions
How are seconds and milliseconds detected?
Numbers with up to ten digits before the decimal point are treated as seconds; thirteen digits are treated as milliseconds. Other lengths need an explicit unit choice. Detection is a convenience, not proof of what a source system intended.
Does changing the time zone change the timestamp?
No. Unix time identifies an instant. Time zones change its readable representation. UTC remains visible, and named zones apply the daylight-saving rules available in your browser.
Are fractional seconds rounded?
Seconds accept up to three decimal places, and milliseconds must be whole numbers. Extra precision is reported instead of rounded away. Negative values and zero are supported, within dates from year 0000 through 9999.
What happens if one row is invalid?
Other valid rows still convert. The problem row retains its original input and a correction message. The preview shows up to 200 rows; copying or downloading CSV includes every row within the 10,000-line limit.
Be explicit about dates and units
Use YYYY-MM-DD HH:mm:ss or ISO syntax with Z or a numeric UTC offset. Ambiguous regional dates and leap-second notation are not guessed. Dates without a zone mean UTC. The tool uses your browser’s time-zone database and does not promise historical rules beyond that database. Spreadsheet applications may reinterpret CSV values, so import identifiers and original inputs as text.