Convert epoch values with an explicit unit and zone
- Choose Timestamp to date or Date to timestamp.
- Select the timestamp unit, or enter a strict date and 24-hour clock time.
- Use UTC or a supported IANA zone. Repeated clock times require an occurrence choice; skipped times are rejected.
- Read exact unit representations and copy the result. Use current time takes a snapshot of the device clock.
Formats, output and limits
Signed decimals up to 48 characters. Seconds, milliseconds, microseconds and nanoseconds allow 9, 6, 3 and 0 fractional places respectively. UTC and selected-zone dates must remain in years 0001–9999. Leap seconds, commas and exponent notation are unsupported. Zone identifiers: at most 100 characters.
A worked example
1767225600 seconds is 2026-01-01T00:00:00Z, which is 03:00 in Asia/Riyadh. -0.001 seconds is 1969-12-31T23:59:59.999Z. One nanosecond is 0.000000001 seconds.
Common questions
Will the tool guess seconds or milliseconds?
No. The selected unit is explicit. Changing a valid timestamp's unit preserves the exact instant and can produce a fractional value.
What happens when clocks change?
Converting an instant is unambiguous. A local clock time that occurs twice needs First/Second occurrence; a nonexistent local time is rejected instead of shifted.
Where do zone rules and current time come from?
Rules come from your browser's time-zone database and may vary with browser updates. Current time comes from the device, not a verified network clock. No time service is contacted.