Meeting Time Finder
Compare local times across multiple time zones to find optimal meeting slots for global teams.
Back to all tools on ToolForge
Local Times
About Meeting Time Finder
This meeting time finder converts a base time across multiple time zones, displaying local times for each location. It's designed for distributed teams scheduling cross-timezone meetings, webinars, conference calls, and international events.
How Time Zone Conversion Works
Time conversion uses UTC (Coordinated Universal Time) as the reference point:
Time Zone Conversion Formula:
localTime = utcTime + (offset × 60 minutes)
Example: Convert 15:00 UTC to various zones
UTC+0 London: 15:00 + (0 × 60) = 15:00 (3:00 PM)
UTC+1 Paris: 15:00 + (1 × 60) = 16:00 (4:00 PM)
UTC+5:30 Mumbai: 15:00 + (330 min) = 20:30 (8:30 PM)
UTC+8 Singapore: 15:00 + (8 × 60) = 23:00 (11:00 PM)
UTC-5 New York: 15:00 + (-5 × 60) = 10:00 (10:00 AM)
UTC-8 Los Angeles: 15:00 + (-8 × 60) = 07:00 (7:00 AM)
JavaScript Implementation:
function convertUTC(utcDate, offsetHours) {
const utc = utcDate.getTime() + (utcDate.getTimezoneOffset() * 60000);
const local = new Date(utc + (offsetHours * 3600000));
return local;
}
Common UTC Offsets Reference
| Offset | Time Zone | Major Cities |
|---|---|---|
| UTC-10 | HST (Hawaii) | Honolulu |
| UTC-8 | PST (Pacific) | Los Angeles, San Francisco, Vancouver |
| UTC-7 | MST (Mountain) | Denver, Phoenix, Calgary |
| UTC-6 | CST (Central) | Chicago, Houston, Mexico City |
| UTC-5 | EST (Eastern) | New York, Toronto, Bogota |
| UTC-4 | AST (Atlantic) | Halifax, Santiago, Caracas |
| UTC-3 | BRT (Brasilia) | Sao Paulo, Buenos Aires |
| UTC+0 | GMT/BST (London) | London, Dublin, Lisbon, Accra |
| UTC+1 | CET (Central European) | Paris, Berlin, Rome, Madrid |
| UTC+2 | EET (Eastern European) | Athens, Cairo, Johannesburg |
| UTC+3 | MSK (Moscow) | Moscow, Istanbul, Riyadh |
| UTC+4 | GST (Gulf) | Dubai, Baku, Tbilisi |
| UTC+5:30 | IST (India) | Mumbai, Delhi, Colombo |
| UTC+7 | ICT (Indochina) | Bangkok, Jakarta, Hanoi |
| UTC+8 | CST/SGT (China/Singapore) | Beijing, Singapore, Perth, Taipei |
| UTC+9 | JST/KST (Japan/Korea) | Tokyo, Seoul, Pyongyang |
| UTC+10 | AEST (Australian Eastern) | Sydney, Melbourne, Brisbane |
| UTC+12 | NZST (New Zealand) | Auckland, Wellington, Fiji |
Optimal Meeting Time Windows
Best overlapping hours for common region combinations (in local times):
| Regions | Best Window | Notes |
|---|---|---|
| US West + US East | 12-3 PM EST / 9 AM-12 PM PST | 3-hour overlap during work hours |
| US East + Europe (UK) | 2-4 PM GMT / 9-11 AM EST | Prime overlap window |
| US + Europe + Asia | Rotate times | No ideal time; consider recording |
| Europe + Asia (India) | 2-4 PM CET / 6:30-8:30 PM IST | Late afternoon Europe, evening India |
| Asia (India) + Asia (Japan) | 10 AM-12 PM JST / 7-9 AM IST | Morning overlap |
| US West + Asia (Japan) | 8-10 PM JST / 4-6 AM PST | Very early US or late Asia |
Time Zone Conversion Algorithm
JavaScript Time Zone Conversion:
function parseOffset(offsetStr) {
// Handle formats: +8, -5, +5:30, -3:30
const match = offsetStr.match(/^([+-])(\d+)(?::(\d+))?$/);
if (!match) return null;
const sign = match[1] === '+' ? 1 : -1;
const hours = parseInt(match[2], 10);
const minutes = match[3] ? parseInt(match[3], 10) : 0;
return sign * (hours + minutes / 60);
}
function convertToZone(utcDate, offsetStr, label) {
const offset = parseOffset(offsetStr);
if (offset === null) return null;
// Get UTC timestamp in milliseconds
const utc = utcDate.getTime() + (utcDate.getTimezoneOffset() * 60000);
// Apply offset (convert hours to milliseconds)
const local = new Date(utc + (offset * 3600000));
// Format as readable string
const timeStr = local.toLocaleTimeString('en-US', {
hour: '2-digit',
minute: '2-digit',
hour12: true
});
const dateStr = local.toLocaleDateString('en-US', {
weekday: 'short',
month: 'short',
day: 'numeric'
});
return {
label: label,
offset: offsetStr,
time: timeStr,
date: dateStr,
iso: local.toISOString().slice(0, 16).replace('T', ' ')
};
}
// Usage:
const baseTime = new Date('2024-03-15T14:00:00'); // 2 PM UTC
const result = convertToZone(baseTime, '-5', 'New York');
console.log(result);
// { label: "New York", offset: "-5", time: "09:00 AM", date: "Mar 15" }
Daylight Saving Time (DST) Reference
DST shifts clocks forward 1 hour during summer months. Not all regions observe DST:
| Region | Observes DST? | DST Period | Offset Change |
|---|---|---|---|
| United States | Yes (most states) | 2nd Sun Mar - 1st Sun Nov | +1 hour |
| European Union | Yes | Last Sun Mar - Last Sun Oct | +1 hour |
| United Kingdom | Yes (BST) | Last Sun Mar - Last Sun Oct | +1 hour |
| China | No | N/A | None |
| India | No | N/A | None |
| Japan | No | N/A | None |
| Australia | Some states | 1st Sun Oct - 1st Sun Apr | +1 hour (southern summer) |
| Brazil | No (abolished 2019) | N/A | None |
Common Use Cases
- Global Team Standups: Find rotating times fair to all team members across continents
- Webinar Scheduling: Pick times that maximize attendance across target regions
- Client Calls: Schedule calls with international clients in their business hours
- Conference Planning: Set keynote times accessible to global virtual attendees
- Remote Work Coordination: Align async work windows for handoffs between time zones
- Customer Support: Plan 24/7 coverage across regional support centers
- Live Streaming: Schedule broadcasts for peak viewing in multiple regions
Time Zone Abbreviations Reference
| Abbreviation | Full Name | UTC Offset |
|---|---|---|
| EST | Eastern Standard Time | UTC-5 |
| EDT | Eastern Daylight Time | UTC-4 |
| CST | Central Standard Time | UTC-6 |
| PST | Pacific Standard Time | UTC-8 |
| PDT | Pacific Daylight Time | UTC-7 |
| GMT | Greenwich Mean Time | UTC+0 |
| BST | British Summer Time | UTC+1 |
| CET | Central European Time | UTC+1 |
| CEST | Central European Summer Time | UTC+2 |
| IST | India Standard Time | UTC+5:30 |
| JST | Japan Standard Time | UTC+9 |
| AEST | Australian Eastern Standard Time | UTC+10 |
Scheduling Best Practices
- Avoid early morning calls: Before 8 AM local time reduces engagement
- Respect lunch hours: 12-2 PM local is often unavailable
- Consider Friday afternoons: Many cultures end work early or avoid meetings
- Rotate inconvenient times: Share burden when no perfect time exists
- Send calendar invites with timezone: Use IANA timezone IDs (America/New_York) not just offsets
- Record meetings: Allow async participation for those who can't attend live
- Check DST transitions: Verify times during spring/fall transition weeks
How to Find Meeting Times
- Set base time: Select the meeting time in your local timezone or UTC.
- Enter time zones: List UTC offsets with optional labels (e.g., "UTC+8 Singapore").
- Click Compare: Local times display for each timezone.
- Review results: Identify if the time works for all participants.
- Copy result: Share the time comparison with your team.
Tips
- Use format "UTC+X Label" for clear output (e.g., "UTC+5:30 Mumbai")
- Include half-hour offsets for India, Nepal, Australia Central
- Check if any location falls outside business hours (before 8 AM or after 6 PM)
- For recurring meetings, verify DST transition dates don't create conflicts
- Consider using World Clock apps alongside for ongoing coordination
Frequently Asked Questions
- How does meeting time calculation work?
- Meeting time calculation converts a base time to different time zones using UTC offsets. Each zone's offset (e.g., UTC-8, UTC+5:30) is added to the UTC time to get local time. For example, 3 PM UTC is 7 AM EST (UTC-5) and 11 PM IST (UTC+5:30). This tool handles half-hour and 45-minute offset zones like India (UTC+5:30) and Nepal (UTC+5:45).
- What are common UTC offsets for major cities?
- Major city offsets: New York UTC-5 (EST), Chicago UTC-6 (CST), Denver UTC-7 (MST), Los Angeles UTC-8 (PST), London UTC+0 (GMT), Paris UTC+1 (CET), Moscow UTC+3, Dubai UTC+4, Mumbai UTC+5:30, Singapore UTC+8, Tokyo UTC+9, Sydney UTC+10. Note: Many regions observe daylight saving time, shifting offsets by +1 hour in summer.
- What is the best time for global team meetings?
- For US-Europe overlap: 2-4 PM CET (8 AM-10 AM EST). For US-Asia overlap: 8-10 PM JST (7-9 AM EST). For Europe-Asia: 2-4 PM CET (7:30-9:30 PM IST). Three-continent meetings are challenging—consider rotating times, recording sessions, or splitting into regional meetings. Tuesday-Thursday 14:00-16:00 UTC often works best for US-Europe.
- What is daylight saving time and how does it affect scheduling?
- Daylight Saving Time (DST) shifts clocks forward 1 hour in spring, back 1 hour in fall. Observed in most of US, Canada, Europe, but NOT in most of Asia, Africa, or South America. DST dates vary by country, creating 'gap weeks' where offsets temporarily change. When scheduling year-round meetings, verify current offsets twice yearly during transition periods.
- What are time zone abbreviations and are they reliable?
- Common abbreviations: EST (Eastern Standard), PST (Pacific), GMT (Greenwich), CET (Central European), IST (Indian/Israel), JST (Japan), AEST (Australian Eastern). However, abbreviations are ambiguous: IST = India Standard Time OR Israel Standard Time OR Irish Standard Time. Always use UTC offsets or IANA time zone IDs (America/New_York) for clarity.
- How do I handle half-hour and 45-minute offset time zones?
- Some zones use non-hour offsets: India UTC+5:30, Nepal UTC+5:45, Australia Central UTC+9:30, Newfoundland UTC-3:30, Chatham Islands UTC+12:45, Marquesas UTC-9:30. When calculating, convert offsets to minutes: UTC+5:30 = 330 minutes. Add to UTC time in minutes, then convert back. This tool handles fractional offsets automatically.