Compare a meeting across time zones, check a supplied work window and export a UTC calendar event.
Use up to eight browser-supported IANA names, optionally followed by | label. Common zones are listed below; no external clock service is contacted.
Enter values or load the example.
All inputs stay in this page. No uploads or application history. Input edits invalidate generated outputs. Numeric quick sliders never clamp wider exact fields. Source local dates 1970–2100, whole minutes; meeting length 1–1440 elapsed minutes. Skipped source times reject; repeated times require earlier/later. Up to eight destination zones. One supplied daily work window applies to everyone (overnight allowed), with a minute-sampled availability check. No weekend/holiday or automatic scheduling assumptions. ICS uses the actual UTC start/end. Calculation worker deadline: 10 seconds.
Generate a result to see details and reports.
Your dates, clock settings and calendar labels stay on your device. Self-hosted browser code processes the inputs without uploads, accounts or application history. Browser time-zone rules and your device clock are used without remote lookup.
Source local dates 1970–2100, whole minutes; meeting length 1–1440 elapsed minutes. Skipped source times reject; repeated times require earlier/later. Up to eight destination zones. One supplied daily work window applies to everyone (overnight allowed), with a minute-sampled availability check. No weekend/holiday or automatic scheduling assumptions. ICS uses the actual UTC start/end.
No. Timers/clocks run only in the active browser page or workspace panel. Closing, Reset or switching tools releases that session. Background throttling and device sleep can delay feedback, and device-clock adjustments affect wall-clock timers. No notification permission, service worker or server alarm is used.
No. Weekend/holiday rules are supplied by you; no regional legal calendar is inferred. Time-zone calculations use the browser’s installed rules. The Meeting planner rejects skipped local times and requires an explicit occurrence for repeated times.
No application input history is stored. Reports/downloads and explicit clipboard copies exist outside the tool when you request them. Clear, Reset, workflow switching and page exit release current application data; this is not a physical memory-erasure guarantee.
