Meeting Time Zone Calculator

Scheduling a meeting with colleagues, clients, or contractors across the world sounds simple until you realize that "2:00 PM" means something completely different in New York, San Francisco, London, and Tokyo. A missed hour because of daylight saving, or a meeting booked for 4:00 AM someone's local time, wastes everyone's morning and can cost a real relationship — or a five-figure deal. This meeting time zone calculator from Smekys removes the guesswork: you type your local meeting time and your UTC offset, and instantly see what that same moment reads in US Eastern, US Pacific, London, and Tokyo, with a small flag telling you whether the meeting falls on the same day, the next day, or the previous day for each participant.

The math behind every result is just offset arithmetic through Coordinated Universal Time (UTC). First the engine converts your local time into minutes, subtracts your UTC offset to land on UTC, then adds each reference zone's offset back on and normalizes the clock into a 24-hour day. No mental carry, no off-by-one hour, no daylight saving surprise.

How to Use

1. Enter the Meeting Hour in your local time using the 24-hour clock. 2:00 PM is 14, 9:00 AM is 9, and midnight is 0.
2. Enter the Meeting Minute. For an on-the-hour meeting this is 0; for 2:30 PM it is 30.
3. Set your UTC Offset — how many hours your local clock sits ahead of (positive) or behind (negative) UTC. US Eastern Standard Time is -5, US Pacific is -8, London in winter is 0, and Tokyo is +9.
4. Read the result card. It shows the converted hour in UTC, Eastern, Pacific, London, and Tokyo. A day-shift value of 1 means that zone is one day later; -1 means one day earlier; 0 means the same calendar day.
5. Use the day-shift flags when you send the invite. Always name the timezone alongside the clock time — e.g. "2:00 PM ET (11:00 AM PT)" — so no one has to redo the conversion.

If you are not sure of your UTC offset, remember the rule of thumb: west of Greenwich (Americas) is negative, east of Greenwich (Europe, Africa, Asia, Pacific) is positive. A half-hour offset such as India's +5.5 is accepted by the field.

The Conversion Formula

Every timezone on Earth is defined by its offset from UTC, so converting between two zones is a two-step bridge:

• Step 1 — local to UTC: UTC minutes = (hour × 60 + minute) − (your offset × 60).
• Step 2 — UTC to the target zone: target minutes = UTC minutes + (target offset × 60), then take target minutes mod 1440 (there are 1,440 minutes in a day) and record how many whole days you crossed with floor(target minutes / 1440).

Worked example: a 2:00 PM (14:00) meeting on US Eastern time with offset -5. Local minutes = 840. UTC minutes = 840 − (−5 × 60) = 840 + 300 = 1,140, which is 19:00 UTC. From there, Pacific (offset −8) reads 19:00 − 8 = 11:00 AM, London (offset 0) reads 7:00 PM, and Tokyo (offset +9) reads 19:00 + 9 = 28:00, which wraps to 4:00 AM the next calendar day. That next-day flag is exactly why you should never schedule a Tokyo call at 2:00 PM ET without checking — it is their early morning.

Why UTC Offset, Not Just City Names?

City names are messy. "London time" is 0 in winter but +1 in summer. "New York" is −5 in winter and −4 in summer. By entering the raw UTC offset, you control the exact moment and avoid the daylight saving trap entirely. The four reference zones shown (ET, PT, London, Tokyo) use their standard, winter offsets so you can compare apples to apples; if your participants are on daylight saving, nudge the source offset by +1 hour for the affected side and the whole table recalculates.

This matters because remote work has gone global: a distributed team might have members on three continents, and the overlap of waking hours can be as thin as a few hours per week. Picking a slot that respects everyone's 9-to-5 window means fewer evening meetings, higher engagement, and roughly 25% more productive calls according to common remote-team benchmarks. A small conversion step up front saves hours of rescheduling later.

Examples

Example 1 — A US team calling Europe. A product manager in New York (ET, offset −5) wants a 2:00 PM working session. Enter 14:00 with offset -5. The card shows 7:00 PM in London — perfectly reasonable after the European workday — but 4:00 AM the next day in Tokyo, so Japan should not be invited. The manager instead picks 9:00 AM ET, which becomes 2:00 PM London and 11:00 PM Tokyo: Europe is happy, and Tokyo opts for a recorded follow-up.

Example 2 — Budgeting the missed-call cost. A missed client call because of a botched timezone conversion is not free. If a customer call costs a team the equivalent of a $500 consulting hour and half the invitees show up at the wrong time once a quarter, the wasted time compounds to thousands of dollars a year. A one-minute check with this converter before hitting send on the calendar invite is the cheapest insurance on the schedule.

Example 3 — The midnight boundary. Enter 00:30 (12:30 AM) with ET offset -5. UTC is 05:30, London 5:30 AM, Pacific the previous day at 9:30 PM, and Tokyo 2:30 PM the same day. Notice the Pacific day-shift flag flips to -1: the meeting is yesterday evening on the West Coast, which is why a late-night East Coast email often lands at a sensible hour for California.

FAQ

What is a UTC offset and how do I find it?

A UTC offset is the number of hours your local clock is ahead of (positive) or behind (negative) Coordinated Universal Time. For example, US Eastern Standard Time is -5, meaning New York is five hours behind UTC. You can find your offset in your phone's timezone settings, by searching your city on timeanddate.com, or by remembering that the US East Coast is −5, West Coast −8, London 0, and Tokyo +9.

How do I convert 2 PM ET to London time?

With Eastern at offset −5, 2:00 PM (14:00) ET converts to 19:00 UTC. London at offset 0 reads 19:00, which is 7:00 PM. So a 2:00 PM ET meeting is 7:00 PM local time in London in winter. If London is on daylight saving (BST, +1 in summer), add one more hour for 8:00 PM.

Why does Tokyo show the next day for an afternoon ET meeting?

Because Tokyo sits 14 hours ahead of Eastern (offset +9 versus −5). When it is 2:00 PM on Tuesday in New York, UTC is 7:00 PM Tuesday, and adding 9 hours brings Tokyo to 4:00 AM on Wednesday. The day-shift flag 1 on the Tokyo output tells you the meeting falls on the next calendar day there.

Do I need to account for daylight saving time?

Yes, and this calculator makes it easy. The reference zones use standard winter offsets (ET −5, PT −8, London 0, JST +9). When regions switch to daylight saving, adjust the affected side's offset by +1 hour for the summer months. Note that the US and Europe switch on different dates and Japan does not observe daylight saving at all, which causes a one-week mismatch twice a year.

What is the best time to schedule a global meeting?

Aim for a slot that lands between roughly 9:00 AM and 5:00 PM for as many participants as possible. A common sweet spot for US–Europe calls is early morning US time (9:00–10:00 AM ET = 2:00–3:00 PM London). Including Tokyo in the same meeting rarely works without one party accepting an early morning or late evening, so rotating the inconvenience is fairer than forcing it on the same people every week.

Can I use this for offsets that are not whole hours?

Yes. The UTC offset field accepts half-hour and quarter-hour steps, so regions like India (+5.5), Nepal (+5.75), or parts of Australia can be entered directly. The engine bridges through UTC exactly the same way regardless of whether the offset is a whole or fractional number of hours.

Disclaimer

This meeting time zone calculator from Smekys is provided for informational purposes only and does not constitute legal, travel, or scheduling advice. Converted times are computed from the UTC offsets you enter and use standard (winter) offsets for the reference zones; actual local time depends on daylight saving rules, which change by jurisdiction and year. Always double-check the final local time and timezone with your calendar invite and confirm with participants before a critical meeting.