WORLD TIME, IN SYNC
Time, on the same page.
Find the right time for people in different places.
Try a real example
Apply an example, inspect the result, then save it if it is useful.
A London meeting during the March changeover
An early Seoul call on the previous Los Angeles day
America/New_York
—
UTC —Asia/Tokyo
—
UTC ——
What this result means
Save up to 5 scenarios in this browser. They do not sync to an account or cloud. Remove them from this library.
Saved scenarios (0/5)
No saved scenarios yet.
Find a time that works for both
For remote teams, client calls and online lessons. Set each person’s local availability.
No shared availability on this date. Try another date or widen the hours.
Suggestions use your chosen hours, not calendars or public holidays. Same-day windows only.
Your city pair and availability stay on this device. Shared links also preserve the exact time.
THE MEETING GUIDE
Working between New York and Tokyo
A useful meeting time is more than a difference between two clocks. When coordinating New York and Tokyo, check the calendar date on both cards before you send an invitation. This converter uses America/New_York for the origin and Asia/Tokyo for the destination. Move the slider to see the same instant in both places, including any change of date. Copy the result into your message so colleagues receive a date, a time, and an explicit UTC offset instead of an ambiguous abbreviation.
Date-specific examples for 2026
New York is 14 hours behind Tokyo on 2026-01-15.
New York is 13 hours behind Tokyo on 2026-07-15.
| Date in origin city | New York | Tokyo |
|---|---|---|
| 2026-01-15 | 09:00 -05:00 | 2026-01-15 23:00 +09:00 |
| 2026-07-15 | 09:00 -04:00 | 2026-07-15 22:00 +09:00 |
These are two dated examples, not a guarantee for every date in the year. Choose your actual meeting date above. Offsets use the IANA rules available in this build or your browser.
Make room for both working days
Start with an ordinary working window of 09:00–17:00 in New York, then inspect the corresponding hours in Tokyo. These hours are a planning convention, not a statement about a particular employer or local holiday. If the working days do not overlap, agree on a short exception or use an asynchronous update. Rotate inconvenient calls across your team rather than expecting the same people to join early or late every week.
Choose the date before the hour
Time-zone differences can change throughout the year. Regions may begin or end daylight saving on different weekends, and some never change their clocks. Always choose the actual meeting date. The slider follows elapsed minutes within the origin city’s local day: a transition day may contain 23 or 25 hours. A repeated clock time has a different UTC offset. For recurring events, use an IANA time zone in your calendar and review future occurrences.
Business meeting etiquette
When inviting colleagues in New York and Tokyo, include both local dates and times in the invitation, send a short agenda in advance, and ask participants to confirm their availability. Avoid assuming that a time inside a usual working day is convenient: lunch breaks, flexible schedules and holidays differ. State the planned duration, nominate someone to share written decisions, and rotate any early or late calls across the team. If there is no comfortable overlap, offer a written update instead of requiring an overnight meeting.
For colleagues in Tokyo, confirm availability around Japanese national holidays before scheduling a recurring call. Check the actual year rather than copying last year’s dates. Japanese national holidays (official)
Frequently asked questions
Can the destination be on a different date?
Yes. Tokyo may be on the previous or following calendar day relative to New York. Read the full date under each clock. A copied conversion includes both dates to prevent this common scheduling mistake.
Does PST mean Los Angeles throughout the year?
No. In this tool PST is a fixed UTC−08:00 offset; KST is UTC+09:00. Choose Los Angeles when you want its seasonal daylight saving rules. City names and IANA identifiers are safer than short abbreviations for future appointments.
Will this work offline?
After a successful online visit, the installed app can reuse recently cached pages. Pages you have not visited may still require a connection. Calculations run on your device and use its time-zone data, so keep your browser and operating system up to date.
Clock changes this season
- Oct 25, 2026: UK and EU clocks went back one hour.
- Nov 1, 2026, 2:00 a.m. local time: most of the US and eastern Canada (Toronto, Montreal, Halifax) fall back one hour. Vancouver, Calgary and Winnipeg no longer change.
- Next: the US springs forward on Mar 14, 2027 and the EU on Mar 28, 2027.
Read more: Autumn 2026 clock-change guide: every date and gap · US fall back on Nov 1, 2026: meeting time cheat sheet · Countries without DST in 2026
WorldTimeSync
Check the date, not just the hour
A winter meeting may move by an hour in summer. A midnight call may belong to yesterday for your colleague. Explore reproducible examples before sharing an invitation.
Read the practical guide →How to use WorldTimeSync
- Pick two cities. Choose an origin under "From" and a destination under "To". Press "Swap" (or S) to reverse them.
- Choose the date first. The difference between two cities can change during the year, so set the real meeting date before the hour.
- Move the slider. It covers one local day in the origin city (00:00–23:59). The destination card shows the same instant, including its date and UTC offset.
- Copy or share. "Copy times" (or C) copies both local times with dates and UTC offsets. "Share this time" creates a link that opens the same cities, date and time. "Download calendar event" saves an .ics file you can import into most calendar apps.
Find a time that works for both
Set each person's available hours (start and end, in their own local time), choose a meeting length of 15, 30, 60 or 90 minutes, and tick "Monday–Friday only in both places" if weekends are out. The tool suggests slots that fit both ranges on the chosen date. Suggestions use only the hours you enter: they do not read calendars or check public holidays, and they stay within the same day. If nothing fits, the tool says so; try another date or widen the hours.
Examples (computed with IANA tzdata 2026c)
- Seoul ↔ London, before and after the UK change. On Wed 14 Jan 2026, 18:00 in Seoul is 09:00 in London. After London moves to UTC+01:00 on Sun 29 Mar 2026, 18:00 in Seoul is 10:00 in London.
- New York ↔ London in March. From 8 to 28 March 2026, New York is on summer time but London is not, so the gap is 4 hours instead of the usual 5. A 09:00 New York call on Mon 9 Mar 2026 is 13:00 in London, not 14:00.
- Seoul ↔ New York, different day. At 09:00 on Wed 14 Jan 2026 in Seoul, it is 19:00 on Tue 13 Jan in New York. Always read the date on both cards.
Daylight saving time
Cities are mapped to IANA zones, so daylight saving changes apply on the right dates. On the day clocks go back, one local hour happens twice; the tool labels each with its UTC offset so you can tell them apart. On the day clocks go forward, one local hour does not exist. PST and KST are fixed offsets (UTC−08:00 and UTC+09:00); pick a city if you need seasonal rules.
Sharing and privacy
Shared links contain the cities, time and availability you chose, and anyone with the link can see them. Saved scenarios (up to 5) stay in this browser only and do not sync.
FAQ
Why does the time difference change during the year?
Because one or both cities switch to daylight saving time, often on different dates. Set the actual date to get the right result.
What does the .ics file contain?
A calendar event for the selected time. Your calendar app shows it in your own time zone.
Will the suggested times avoid holidays?
No. They use only the hours you enter.
Is the result correct for future dates?
It uses the time-zone rules on your device. If a government changes its rules, results update once your device's data is updated. Confirm important meetings with the other side.