Timezone Meeting Planner

Pick up to three timezones and see the whole day as a colour-coded grid — green where everyone sits in core hours, yellow where someone stretches. DST handled automatically by your browser.

Free vs paid — when to upgrade

What this free tool is great for: a quick, one-off job with no signup — it runs entirely in your browser, so nothing leaves your device and there's nothing to manage.

Its honest limit: it produces a one-off output — it won't store, track, brand or manage them at scale, and it can't tell you what happens after you share it.

Where Fireflies.ai does more: Finding the slot is half the meeting; the other half is what people who were asleep missed. Fireflies.ai records, transcribes and summarises calls so every timezone catches up in its own morning.

Try Fireflies.ai →

Affiliate link — we may earn a commission if you sign up, at no cost to you. It never changes our honest take.

The remote-work problem nobody schedules around properly

Distributed teams and international clients turned "when can we meet?" from a calendar question into a geometry puzzle. Amsterdam, New York and Ho Chi Minh City never share a comfortable hour; someone is always early, late, or asleep. The usual solutions — mental arithmetic, a frantic search for "time in Singapore", a meeting invite that lands at 3 a.m. for one attendee — all fail at the same point: you need to see all the working days side by side, not convert one moment at a time. That's exactly what this planner does: pick up to three timezones and the full day appears as a colour-coded overlap grid — green where everyone is inside core hours, yellow where someone stretches, and honest empty space where a meeting simply shouldn't go.

How to read the grid (and why UTC anchors it)

Each row is one hour of the day anchored in UTC — the neutral reference that doesn't belong to anyone's country and never shifts for summer time. The columns translate that moment into each selected timezone's local clock. Green rows mean every location sits between 9:00 and 17:00 — genuinely comfortable for all. Yellow means everyone is at least within a stretched 7:00–21:00 — acceptable for a weekly sync, unfair as a daily default. Unshaded rows mean at least one person would be meeting outside anything resembling a workday. The discipline the grid enforces is seeing the whole day at once: instead of negotiating hour by hour, you see immediately that Amsterdam–Saigon offers a healthy morning-evening window while Amsterdam–Los Angeles offers only a thin late-afternoon sliver.

Daylight saving: the silent meeting-killer

The classic recurring-meeting failure isn't the first invite — it's March and October. Daylight saving time starts and ends on different dates in the EU, the US and elsewhere, and some regions skip it entirely (most of Asia doesn't observe it; parts of Australia do, parts don't). So a Amsterdam–New York meeting that worked all winter silently shifts by an hour for a few weeks each spring and autumn, and an Amsterdam–Saigon one moves twice a year even though Vietnam never changes its clocks. This tool leans on your browser's IANA timezone database, which encodes all of those rules — the grid you see is correct for today specifically, which is why it's worth a fresh glance when the clocks change anywhere in your team.

Designing a fair meeting culture across zones

Once you can see the overlap, the harder question is how to spend it. Distributed teams that feel fair follow a few patterns. Rotate the pain: if the only shared slot is 8:00 for one side and 18:00 for the other, alternate who takes the uncomfortable end rather than institutionalising one region's sacrifice. Protect the green zone: the few genuinely-shared hours are scarce collaboration capital — spend them on discussion that needs everyone live, not status updates. And write decisions down: the smaller your overlap, the more your team lives or dies by documentation, because "ask me when you're online" costs a full day per round-trip when your day ends as theirs begins.

Async first, meetings second

The honest conclusion many remote teams reach is that the overlap grid mostly teaches you to need it less. A three-zone team spanning nine hours has perhaps one or two shared hours a day — physically incapable of supporting a meeting-driven culture. The teams that thrive treat synchronous time as the exception: updates travel in written form, proposals as documents people annotate in their own morning, demos as recorded clips. The meeting earns its slot only when real-time back-and-forth is genuinely the fastest path — a negotiation, a hard design debate, a retro. Use the grid to place those precious meetings well; use its scarcity as the argument for making everything else async.

Scheduling with clients and candidates

Internal teams can rotate pain; clients mostly can't be asked to. The pragmatic rules: always propose times in the other party's timezone, stated explicitly ("14:00 your time, CET") — the single habit that prevents the most no-shows. Offer two or three options inside their comfortable hours, even if they're your yellow ones; goodwill flows toward whoever absorbs the inconvenience. For interviews, remember candidates may hide the discomfort of a 6:00 slot rather than risk the job — checking their local time first is basic decency. This grid answers "what does my proposal look like on their clock" in one glance, before the email goes out instead of after the apology.

Time-zone notation without confusion

Half of scheduling errors are notation errors. "3 PM EST" in July is technically wrong (New York runs EDT in summer) and ambiguous to everyone outside North America. The robust habits: use city names rather than zone acronyms — "15:00 Amsterdam time" survives DST transitions because the city carries its rules with it; use 24-hour notation across borders, because 8:00 versus 20:00 is exactly the mistake the AM/PM system invites; and for anything automated, use IANA identifiers like Europe/Amsterdam, which is what calendars and this tool use internally. Precision here is free; ambiguity costs a missed meeting across an ocean. And when someone sends you an ambiguous time, translate it back explicitly in your confirmation — restating the slot in both clocks takes five seconds and has saved more international meetings than any scheduling tool ever built.

Finding the slot is half the meeting — where Fireflies.ai does more

A well-placed meeting still evaporates if nobody remembers what was decided — and in distributed teams, the people who couldn't attend that 8:00 slot need the outcome as much as those who did. That's where Fireflies.ai does more: it joins your calls, transcribes and summarises them, and turns decisions and action items into a searchable record you can share with the teammates who were asleep. Combined with this planner, the loop closes: schedule inside the humane overlap, record what happened, and let the other timezones catch up in their own morning — which is what asynchronous-friendly meetings actually look like.

Frequently asked questions

More free generators & utilities

Browse all free tools →

Embed this tool on your site

Blogger, teacher or toolmaker? Put this calculator on your own page — free forever, no strings. Copy the snippet below (the credit link is appreciated and keeps the tool free):

This tool is free and runs entirely in your browser. The link above is an affiliate link: we may earn a commission if you sign up, at no extra cost to you, and it never changes our honest take.