DoItAl

Data utility

Unix Timestamp / Epoch Converter

Convert Unix seconds or milliseconds to UTC, local and selected-zone dates, or resolve a local date into an epoch. Copy precise timestamps and ISO 8601 results.

Browser-local • No upload

Loading tool controls…

Local tool controls

Unix epoch is 1970-01-01T00:00:00Z. Seconds may include up to three fractional digits; milliseconds are integers. Auto uses 10/13-digit conventions and clearly labels its assumption; other lengths require an override. UTC years 0001–9999 are supported. Displayed local dates near these boundaries must also fit this range.

What this tool does

Converts Unix seconds/milliseconds to UTC ISO and human-readable zone dates, or resolves a chosen local date/time into exact epoch values.

How to use it

  1. Choose timestamp-to-date or date-to-timestamp.
  2. Select seconds/milliseconds explicitly when auto cannot safely identify your intended unit; for local dates choose a zone and any needed repeated-time occurrence.
  3. Convert and copy seconds, milliseconds or ISO, or use the current device time for a quick conversion.

Worked example

1704067200 seconds and 1704067200000 milliseconds both represent 2024-01-01T00:00:00.000Z. At that instant Asia/Singapore shows 2024-01-01 08:00:00, while America/New_York shows 2023-12-31 19:00:00. −0.001 seconds represents the last millisecond before 1970.

Processing and explanation

Unix timestamps measure elapsed time from 1970-01-01T00:00:00Z, without a local time zone. Integer/decimal strings are parsed with BigInt scaling so millisecond precision is retained. ISO output ending in Z is UTC. Changing the display zone changes the wall-clock representation, not the timestamp; resolving a local date first uses the same DST-aware rules as Time Zone Converter.

Limits and common mistakes

UTC years 0001–9999, with supported local dates inside that range. Seconds accept up to three fractional digits; milliseconds are whole integers. Auto interprets 10 digits as seconds or 13 as milliseconds and labels that assumption: those lengths are conventions, not proof, so confirm historical/future values manually. Other lengths need a unit override except zero/fractional seconds. Exponents, leap seconds, micro/nanoseconds and batch conversion are unsupported. Device current-time accuracy depends on its clock.

Privacy and your input

All inputs and results stay in this browser tab. Dates, time-zone selections, identifiers and file contents are not uploaded, saved in browser storage or included in aggregate analytics. Clipboard copies and downloaded files are managed by your device.

Frequently asked questions

Is a Unix timestamp local time?
No. It identifies a moment independent of the zone used to display it.
Why can a small number not use auto?
A small integer could mean seconds or milliseconds since 1970. A manual unit avoids a silent guess.
Can I convert dates before 1970?
Yes. Negative values represent earlier instants within the supported year range, including fractional negative seconds.

Material content update: