How does automatic epoch unit detection work?
The parser inspects the number of integer digits before any decimal point to infer whether a numeric input represents seconds, milliseconds, microseconds, or nanoseconds. This avoids forcing you to toggle unit dropdowns every time you switch between backend logs, browser events, and telemetry metrics.
| Input digit count | Detected unit | Divisor to JS milliseconds | Common source systems |
|---|---|---|---|
| 1 to 11 digits | Seconds | Multiply by 1,000 | POSIX time_t, JWT exp/iat, Linux date +%s |
| 12 to 14 digits | Milliseconds | 1 (native unit) | JavaScript Date.now(), Java System.currentTimeMillis() |
| 15 to 17 digits | Microseconds | Divide by 1,000 | PostgreSQL TIMESTAMP, Go UnixMicro(), Python logs |
| 18 or more digits | Nanoseconds | Divide by 1,000,000 | Kubernetes events, Prometheus, Go UnixNano() |
Digit-length thresholds for seconds through nanoseconds
Modern systems emit epoch integers across four orders of magnitude. Entering 1700000000 (10 digits) resolves to November 14, 2023 as whole seconds, whereas 1700000000000 (13 digits) resolves to the exact same instant in milliseconds. Comparing a seconds vs milliseconds timestamp is straightforward because every millisecond value is 1,000 times larger.
If you paste a 13-digit millisecond value into a tool expecting seconds, the output jumps thousands of years into the future. Under the MDN JavaScript Date Object Reference, valid Date instances span +/- 8,640,000,000,000,000 milliseconds (8.64e15 ms) from the epoch, so out-of-range numbers trigger an invalid-date message instead of silent wrapping.
Handling negative pre-1970 timestamps and decimal fractions
Negative numbers such as -3600 represent instants prior to 1970-01-01T00:00:00Z. The digit counter strips any leading minus sign and trailing decimal fraction before choosing the unit, so -1700000000 still reads accurately as seconds.
Decimal timestamps like 1700000000.5 preserve sub-second milliseconds when multiplied into the Date constructor. When pulling raw numbers out of messy server traces, you can first extract timestamp numbers from raw log lines before pasting them here for conversion.
Converting Unix time to dates, ISO 8601 strings, and IANA time zones
You can type or paste human-readable strings into Timestamp or date to get both Unix seconds and Unix milliseconds back immediately. The tool supports unzoned dates, full zoned timestamps, and the literal keyword now.
Resolving unzoned ISO dates against your chosen time zone
Standard JavaScript Date.parse() treats 2026-04-19 as UTC midnight while treating 2026-04-19T14:30:00 as local time, which frequently causes off-by-one-day mistakes. To prevent that mismatch, this converter parses unzoned YYYY-MM-DD and YYYY-MM-DDTHH:mm:ss inputs using a two-step IANA convergence loop inside the active Time zone selection.
When an input already includes an explicit Z suffix or numeric offset like +05:30, the parser honors that exact instant as defined by IETF RFC 3339 Date and Time on the Internet. Changing the Time zone dropdown then updates the Converted display without altering the underlying UTC epoch.
Using the live clock, preset buttons, and date picker
The Now card at the top ticks every 1,000 milliseconds so you can grab the current Unix second with one click. Below the input box, three preset buttons let you jump straight to Now, In 24 hours (+86400 seconds), or Unix epoch (0).
For visual scheduling, Pick a date and time renders a native datetime-local control with one-second precision (step="1"). Any change in the picker writes the corresponding integer seconds back into Timestamp or date, making it straightforward to check recurring cron schedules alongside converted timestamps.
Why do daylight saving shifts and leap seconds cause bugs?
Unix time defines every day as exactly 86,400 seconds and ignores UTC leap seconds, while civil clocks shift forward or backward during daylight saving transitions. Mixing those two models without an IANA time zone database leads to duplicate hours, missing hours, and misaligned billing windows.
Tip: Always store and transmit timestamps as UTC integers or explicit RFC 3339 strings with offsets, and convert to an IANA zone like
America/New_YorkorEurope/Berlinonly at the final display layer.
POSIX 86,400-second days vs true UTC leap seconds
Because Unix timestamps assume 86,400 seconds per day, adding 86400 seconds always advances the UTC clock by 24 hours, even across a daylight saving boundary where local wall-clock time jumps by 23 or 25 hours. During a fall-back transition, an unzoned local time like 01:30 occurs twice, so explicit UTC offsets are essential for audit trails.
The Converted panel relies on the MDN Intl.DateTimeFormat API Reference to format Your time zone according to current and historical IANA rules. You can also inspect Relative time deltas calculated via Intl.RelativeTimeFormat across second, minute, hour, day, week, month, and year buckets.
Reading ISO week numbers and day-of-year counters
Analytics pipelines and log-rotation jobs often partition data by ordinal day or week number rather than calendar month. The Day of the year row counts from 1 to 365 (or 366 in leap years) in UTC, while ISO week outputs YYYY-Www anchored on the Thursday of each week.
Token-based authentication workflows share the same integer-second convention. When debugging expired sessions, you can inspect JWT expiration and issued-at claims (exp, iat, and nbf) and cross-check their exact UTC and local wall times here.
Debugging API logs, database indexes, and browser privacy
Checking production timestamps often involves sensitive customer records, session tokens, or internal deployment schedules. Running conversions directly inside your browser tab ensures none of those values cross the network, while keeping every converted format one click away.
- Verifying microsecond and nanosecond logs: Paste 16-digit PostgreSQL timestamps or 19-digit Kubernetes event times directly to confirm human-readable UTC dates without counting zeros by hand.
- Auditing database sort order: Compare two consecutive Unix milliseconds values to verify whether event rows or time-ordered IDs are monotonically increasing inside primary-key indexes.
- Tracing clock skew across microservices: Switch Time zone between
UTCand regional zones such asAsia/TokyoorAmerica/Chicagoto spot servers logging local wall time without explicit offsets. - Comparing log captures: When troubleshooting race conditions between two deployments, you can compare two log snapshots side by side after normalizing their epoch timestamps to ISO 8601.