New York-London
Inputs: New York and London, 09:00-17:00 local hours, 60 minutes. A strong overlap is typically late morning in New York and late afternoon in London.
Start with the date mode: a single date, today, tomorrow, the next five business days, the next seven days, or a custom range. Add each participant, search for their city or timezone, then set the local hours they prefer for work calls. The calculator scans the range in 30-minute steps, ranks the best shared meeting windows, and shows a timeline so you can see overlaps before choosing a slot.
The selected-slot area turns the best window into a practical proposal. You can copy a short message, copy a link that preserves the setup, open Google Calendar, download an iCalendar file for Outlook or Apple Calendar, or copy email-ready text with every participant's local time.
candidate slots = selected dates scanned in 30-minute incrementsscore += 3 for each participant fully inside their local working windowscore -= outside-hours penalty when a slot starts too early or ends too late locallytie-breakers = fewer off-hours participants, fewer outside minutes, then earlier UTC startThe details table explains each result with local date, local start-end time, UTC offset, timezone abbreviation, inside-hours status, minutes outside preferred hours, and score contribution per participant.
Inputs: New York and London, 09:00-17:00 local hours, 60 minutes. A strong overlap is typically late morning in New York and late afternoon in London.
Inputs: Los Angeles and India, 09:00-17:00 local hours, 30-60 minutes. The best compromises often sit early in California and evening in India, so the ranking explains who is outside hours.
Inputs: London and Singapore, 09:00-17:00 local hours. Midday London is evening Singapore and often works better than early-morning UTC choices.
Inputs: a US East Coast team, Central Europe, and Singapore. Use the multi-day finder because the best day may be more important than the earliest possible day.
Inputs: interviewer city, candidate city, and a shorter 30-minute duration. Copy the selected proposal so the candidate sees their local time and timezone abbreviation clearly.
Daylight saving time can change a meeting's fairness even when the UTC time stays fixed. This tool uses the browser's IANA timezone data through Intl.DateTimeFormat, so local offsets and abbreviations update for the selected dates. Recurring mode checks future weeks and flags offset changes that can push a standing call outside someone's preferred hours.
UTC is useful for a neutral timestamp, but it is not enough for humane scheduling. A fair compromise should account for local dates, normal workday windows, meeting length, and whether the same person always absorbs the early or late slot. Use the participant-level score details to decide whether to choose the mathematically highest score or rotate inconvenience across teams.
This page supports between two and six participants, each with their own city or timezone and preferred local working window.
Yes. The location fields accept common cities, country hints, IANA timezone names, and abbreviations such as UTC, GMT, EST, PST, IST, CET, JST, and AEST.
The tool scores slots higher when participants stay fully inside their preferred local hours. It subtracts penalty points for minutes outside those hours and uses fewer conflicts as a tie-breaker.
Yes. Local times, UTC offsets, and timezone abbreviations are produced with the browser's built-in IANA timezone data through Intl APIs, so daylight saving changes are reflected automatically.
Yes. Search for New York or EST and India, Kolkata, or IST, then use the multi-day finder to compare ranked shared windows across one day or a date range.
Yes. Recurring meeting mode evaluates selected weekdays across future weeks and flags weeks where daylight saving time changes affect local offsets or working-hour fit.
Yes. After calculating, choose a slot to copy a proposal, copy a link to the setup, open Google Calendar, download an iCalendar file, or copy email-ready text.
No. Names, locations, work hours, ranked slots, and share text are calculated locally in your browser.
When one region changes clocks before another, a previously balanced meeting can suddenly become an off-hours slot.
A single UTC time can still push someone into early-morning or late-evening work depending on geography.
Seeing a colleague name next to the local time is often more useful than seeing the timezone label alone.
A 30-minute meeting may fit inside all work windows while a 90-minute version creates an off-hours spillover.
Teams spread across North America, Europe, and Asia can have only a small daily window that works well for everyone.
This tool is intended for scheduling convenience. Always confirm local holidays, part-time schedules, travel, and team-specific working agreements before finalizing a meeting time.