Meeting Time Finder

Privacy-first planning tool. All calculations run locally in your browser using the dates and rules you enter.

Calculator

Participant 1

Participant 2

Participant 3

Participant 4

Participant 5

Participant 6

Results

Ready to calculate
Use the controls on the left and calculate to see your result, units, and interpretation.

About This Tool

Timezone conversion is the easy part of remote scheduling. The hard part is finding a slot that respects multiple local working days at once. A meeting that looks reasonable in UTC can still land before breakfast for one person and after dinner for another. This Meeting Time Finder is built for that real scheduling problem. Instead of converting just one time from one zone to another, it ranks candidate slots across a selected date and highlights which options keep the most participants inside their preferred local hours.

The calculator accepts between two and six participants. For each person you choose a timezone, local workday start, and local workday end. It then scans the selected date in thirty-minute steps, converts every candidate slot into each participant's local time, and scores the result. Slots that stay fully inside local working hours are rewarded. Slots that force earlier or later attendance are penalized. That gives you a practical ranked shortlist rather than a single rigid answer. The ranked output is especially useful for distributed teams, interviews, client calls, and project handoffs where you want the least disruptive compromise.

Because the tool uses the browser's timezone rules, it handles daylight saving shifts without external APIs. That matters when one country changes clocks earlier than another, or when a region such as Arizona does not shift at all. The output shows the chosen date in UTC and the corresponding local time for each participant. If a top slot still falls outside someone's stated hours, the table flags it clearly instead of hiding the tradeoff.

This page is privacy-first and intentionally lightweight. It is not a calendar replacement, but it is an excellent front-end filter before you send an invite. Use it to identify the fairest slot, then move that decision into your calendar system with confidence. For repeating meetings, it also pairs naturally with the Recurring Date Calculator so you can plan beyond a single date.

Formula

  • candidate slots = selected date scanned in 30-minute increments
  • score += 3 for each participant fully inside their local work window
  • score -= penalty for off-hours distance when the slot starts too early or ends too late

Example Calculation

Example: a 60-minute meeting on 2026-03-18 between London, New York, and Singapore may produce a top-ranked slot around early afternoon UTC, because that tends to keep London and New York in office hours while pushing Singapore to evening rather than late night.

FAQs

How many participants can I compare?

This page supports between two and six participants, each with their own timezone and preferred local working window.

What makes one slot rank above another?

The tool scores slots higher when more participants stay fully inside their preferred local hours, then uses fewer off-hour conflicts as a tie-breaker.

Does it understand daylight saving time?

Yes. Local times are produced with the browser's built-in timezone database, so seasonal clock changes are reflected automatically.

Can it find multi-day recurring meeting slots?

This calculator ranks a selected date. For repeating schedules, pair it with the Recurring Date Calculator once you choose the best slot pattern.

Is any calendar data uploaded?

No. Participant names, timezones, and working-hour windows stay in your browser.

5 Facts

A one-hour DST mismatch can break a recurring meeting

When one region changes clocks before another, a previously balanced meeting can suddenly become an off-hours slot.

Remote teams

Middle-of-the-day UTC is not equally fair

A single UTC time can still push someone into early-morning or late-evening work depending on geography.

Scheduling bias

Names help avoid timezone confusion

Seeing a colleague name next to the local time is often more useful than seeing the timezone label alone.

Operations

Meeting duration matters as much as start time

A 30-minute meeting may fit inside all work windows while a 90-minute version creates an off-hours spillover.

Planning detail

Overlap windows are often narrower than expected

Teams spread across North America, Europe, and Asia can have only a small daily window that works well for everyone.

Global teams

Important Note

This tool is intended for scheduling convenience. Always confirm local holidays, part-time schedules, and team-specific working agreements before finalizing a meeting time.

Explore more tools