How does the heatmap work?

Each row is a team member's local hours. Green cells indicate everyone is within their working hours; yellow means partial overlap; red means someone would have to attend outside work hours.

Are working hours customizable per person?

Yes. Each team member can have unique working hours (e.g., one person 8 AM–4 PM, another 10 AM–6 PM).

📅 Meeting Time Finder

Q: What if no time works for everyone?

For globally distributed teams, perfect overlap may not exist. Use the heatmap to find times that minimize the burden on the fewest people, and consider rotating which region is inconvenienced.

Find the perfect meeting time across multiple timezones. Add team members, set working hours, and let the heatmap show you the best overlap instantly.

✓ Visual Heatmap ✓ Custom Hours ✓ Unlimited Members

⚡ Quick Answer

Add each team member with their timezone and working hours. The heatmap turns green when everyone is available, yellow for partial overlap, and red when someone is outside work hours. Click any green cell to copy the meeting time formatted for all timezones.

👥 Team Members

🔥 Availability Heatmap

Hours shown in UTC. Click a green or yellow cell to copy the meeting time formatted for every team member's local timezone.

All available Some outside work hours Most outside work hours

How to Find the Best Meeting Time

Add each team member with their name and IANA timezone (e.g., America/New_York, Europe/London).
Set their working hours — adjust the start/end times if someone has a non-standard schedule.
Read the heatmap — each column is one hour (UTC). Green = everyone available, yellow = some inconvenience, red = avoid.
Click any cell to copy a multi-timezone meeting announcement to your clipboard, ready to paste into Slack, email, or a calendar invite.

Why a Visual Heatmap Beats Mental Math

When two people in two timezones need to meet, mental math works. When five people spanning San Francisco, New York, London, Berlin, and Singapore need to meet, mental math fails. A heatmap turns 24 hours × N people into one glance.

The "Follow-the-Sun" Strategy

For globally distributed teams (8+ hours apart), perfect overlap often doesn't exist. The most successful remote organizations rotate which region accommodates: this week New York stays late, next week Singapore comes in early. The heatmap makes this fairness visible.

Key Takeaways

Aim for at least 2 hours of green overlap for synchronous decision-making.
If only yellow exists, rotate inconvenience across regions.
Record meetings for absent team members to enable async catch-up.
For purely informational updates, prefer async over sync.

Frequently Asked Questions

How does the heatmap calculate overlap?

For each UTC hour, we check whether every team member's local time falls within their personal working hours. Green = 100% inside, yellow = at least one outside but ≤ 1 hour, red = significant misalignment.

What if no time works for everyone?

For globally distributed teams (e.g., NYC ↔ Tokyo), perfect overlap may not exist. Use the heatmap to find the time that minimizes inconvenience for the fewest people, and rotate the burden weekly.

Can each person have different working hours?

Yes. Adjust the start/end time for any individual — perfect for early risers, parents on school runs, or part-time team members.

Does this handle daylight saving time?

Yes. We use the browser's built-in IANA timezone database, which automatically reflects current DST rules for every supported region.