Toolivaro

Free Unix Timestamp Converter

Convert between Unix seconds, Unix milliseconds, ISO 8601, and human-readable local time — live, fully local.

Processed locally in your browser

How is the result calculated?

A 13-digit value from a log line

A log line contains 1761330600000. The converter detects 13 digits, reads it as Unix milliseconds, and reports: Unix seconds 1761330600, ISO 2025-10-24T19:50:00.000Z, and the same instant rendered in your local time zone.

Input Value
value 1761330600000
Result 2025-10-24T19:50:00.000Z · Unix seconds 1761330600 · local time shown

What is the formula and its assumptions?

Unix time

unixSeconds = milliseconds ÷ 1000 (from 1970-01-01T00:00:00Z)

Symbol Meaning
unixSeconds whole seconds since the Unix epoch, UTC
milliseconds the platform Date value in milliseconds

10-digit inputs are seconds; 13-digit inputs are milliseconds — the tool detects both.

ISO 8601 / RFC 3339

iso = date.toISOString()

Symbol Meaning
toISOString UTC rendering as YYYY-MM-DDTHH:mm:ss.sssZ

Local-time renderings use the visitor’s system time zone via Intl.

What are the most common mistakes?

  • Confusing 10-digit seconds with 13-digit milliseconds — the single most common timestamp bug.
  • Reading a UTC timestamp as local time (or the reverse) when the value came from another time zone.
  • Assuming the epoch starts at the local midnight — the epoch is 1970-01-01T00:00:00Z, not local midnight.
  • Pasting timestamps into a web converter that uploads them — this tool is fully local.

What are the assumptions and limitations?

  • Parsing uses the platform Date machinery: dates beyond the safe integer range or far outside the platform’s supported range are rejected with a clear error.
  • Very lenient date strings may parse differently across environments; ISO 8601 and numeric inputs are the reliable forms.
  • The tool converts instants — it does not interpret time-zone abbreviations or calendar arithmetic.

Where do the numbers come from?

Last reviewed August 5, 2026 · Version 1.0.0 · Toolivaro does not guarantee external content.

Frequently asked questions

10 digits or 13 digits — what is the difference?

Unix seconds are the classic 10-digit epoch value; many modern systems and databases store 13-digit Unix milliseconds. The tool detects the length and converts accordingly — mixing the two up is one of the most common timestamp bugs, and the output shows both forms so you can spot it.

Why does the local time differ from the UTC time?

A Unix timestamp is the same instant everywhere; the local rendering applies your system’s time zone. The tool shows both the UTC and local forms so a timestamp from another time zone is never misread.

Does the converter handle dates before 1970?

Yes. Negative Unix seconds (for example -86400, which is 1969-12-31) are parsed and rendered correctly — the tool does not assume the epoch is a lower bound.

Found a mistake or have a correction? Report it — we review every correction.