How does automatic epoch unit detection work?

Digit magnitude distinguishes probable seconds, milliseconds, microseconds and nanoseconds; a manual override is always available.

How are daylight-saving ambiguities handled?

Nonexistent wall times are rejected, and repeated times require an explicit earlier or later choice.

/tools/epoch-converter

Unix Epoch Converter

Convert seconds through nanoseconds, inspect dates in any IANA timezone, and find likely timestamps in API responses or logs.

epoch://local

1. Epoch to date

Convert one value or a batch

Enter epoch values separated by spaces, commas or new lines.

2. DiscoverFind timestamps in JSON or logsOpen

Candidates are ranked by field-name and magnitude evidence.

3. Date to epochResolve an IANA wall clockOpen

DST gaps are not shifted. Repeated times require an earlier/later choice.

Ready. Timestamp values stay in this browser.

/units

Epoch unit reference

Unit	Typical digits today	Resolution
Seconds	10	1 second
Milliseconds	13	0.001 second
Microseconds	16	0.000001 second
Nanoseconds	19	0.000000001 second

Automatic detection is a high-probability magnitude inference. Use the manual unit control when working with historical or unusually distant timestamps.

/precision

BigInt before Date

The original integer is converted to nanoseconds with BigInt. Browser Date supplies calendar and timezone rules at millisecond resolution; remaining sub-millisecond digits are retained and shown rather than rounded away.

/faq

Epoch questions

What happens during a DST gap?

The wall time is reported as nonexistent. The converter never moves it silently.

Why can one wall time have two epochs?

When clocks move backward, the same local clock reading occurs twice. Choose the earlier or later UTC instant explicitly.

Is pasted JSON uploaded?

No. Timestamp discovery and conversion are local and content is not included in analytics.