SyncHours — Timezone Overlap Meeting Planner for Remote Teams
Stack every city your team works from into one visual timeline, drag a single scrubber through the day, and see exactly which hours actually work for everyone — no signup, no spreadsheet, no mental math.
Global Time-Zone & Overlap Planner
Detecting…
No saved teams yet. Build a city stack and save it for instant 1-click loading.
New York
EDTWed, Aug 19
•London
GMT+1Wed, Aug 19
•Tokyo
GMT+9Wed, Aug 19
•Working, Fringe, and Rest Hours: How the Overlap Model Works
Most timezone converters stop at "it's 3pm there." SyncHours goes further by classifying every hour of the day into one of three tiers for each city in your stack, so you can see at a glance not just what time it is, but how reasonable a meeting actually is for the people on the other end.
- Working hours — inside each city's configured 9-to-5 (or whatever custom range you set per city). These are the green blocks: safe territory for standups, client calls, and anything synchronous.
- Fringe hours — the amber blocks just outside working hours (roughly two hours before start, three after end). Fine for a quick async check-in or an occasional call, not something to schedule daily without asking first.
- Rest hours — the dark, protected block. SyncHours flags these deliberately so a "green" overlap in one city never quietly means "someone's asleep" in another.
Every city card also flags day shifts ("+1 Day" when the selected UTC hour lands on tomorrow somewhere) and weekends, and the "Find Best Overlap" button scans all 24 UTC hours to surface the single slot with the most combined working-hours coverage across your whole roster — so scheduling across three or four time zones is one click, not a spreadsheet.
Frequently Asked Questions
Does SyncHours handle Daylight Saving Time?
Yes, automatically. Every conversion runs through the full IANA timezone database via Luxon, so DST transitions — including the fact that not every region observes them, or shifts on the same date — are already accounted for. You never have to manually adjust for it.
What about half-hour and 45-minute offsets, like India or Nepal?
Fully supported. Not every timezone sits on a clean hour boundary — India Standard Time is UTC+5:30 and Nepal Time is UTC+5:45. Because SyncHours calculates from real IANA zone data rather than rounding to whole-hour offsets, cities on these fractional offsets line up correctly in the overlap grid instead of drifting by 30 or 45 minutes.
Do I need to create an account?
No. There's no signup, login, or email capture anywhere in the product. Your city stack, custom work hours, and saved team presets are stored locally in your browser, and shareable links encode your selection directly in the URL — nothing is tied to an account.
Does SyncHours work offline?
Once the page has loaded, all the timezone math runs entirely in your browser with no server round-trips, so a dropped connection mid-session won't interrupt the scrubber or calendar export. Loading the site fresh, however, still requires a connection — for guaranteed offline use, install the Android app. See the Android app below.
Common Timezone Pairs
Scheduling across a specific pair of zones? These dedicated overlap pages explain what each abbreviation actually means and preload the scrubber with both:
- Pacific Time (PST) to India Time (IST)
- Eastern Time (EST) to India Time (IST)
- Eastern Time (EST) to UK Time (GMT)
- Pacific Time (PST) to UK Time (GMT)
- Eastern Time (EST) to Central European Time (CET)
- Pacific Time (PST) to Central European Time (CET)
- Eastern Time (EST) to Japan Time (JST)
- Pacific Time (PST) to Singapore Time (SGT)
- UK Time (GMT) to India Time (IST)
- Eastern Time (EST) to Australian Eastern Time (AEST)
Get SyncHours on Android
Prefer a native app? SyncHours is also available on the Play Store, with the same visual overlap grid, team presets, and calendar export — plus a one-time in-app purchase to remove ads if you'd rather not see them.
📱 Download on Google Play