/time local tool
Unix Timestamp Converter
Compare Unix and wall times, resolve DST gaps or overlaps and inspect timezone offsets.
Local execution receiptinput path disclosedTool content stays out of MonoTools URLs and API requests.
- Working input
- Browser memory
- Cross-tool handoff
- Session only · 10 min
- URL payload
- Never
- Export
- Explicit action
Verify it: open DevTools Network, clear the log, use the tool, then inspect fetch/XHR requests. Page assets and optional aggregate analytics may use the network; tool input is not included.
Full privacy modelLoading tool...
01
How to use
- 01Enter a Unix value or an exact wall time, then review the detected unit and selected interpretation.
- 02Choose the date timezone and an explicit Earlier, Later, or Reject policy for DST gaps and overlaps.
- 03Compare pinned timezone rows, offset boundaries or incident timeline deltas, then export diagnostics or CSV.
02
FAQ
- Can unit detection be wrong?
- Yes. Small and historical values can be plausible in both units. Auto mode reports its confidence and evidence; Seconds and Milliseconds explicitly reinterpret the same digits.
- Why can one local time map to zero or two timestamps?
- A forward offset change skips wall times, while a backward change repeats them. Reject exposes the conflict; Earlier and Later select an adjacent or repeated instant explicitly.
- Does adding one day mean the next local calendar date?
- No. Relative calculations use elapsed durations, so one day is exactly 24 hours. Across an offset change, the local wall-clock hour can differ.
- Are leap seconds represented?
- No. Unix time and JavaScript Date model elapsed SI-like milliseconds without representing 23:59:60 as a distinct wall time.
guides
Guides
03