This guide covers Remote Work Time Zone Guide | TimeFlow — what it means, how it works, and how to use it. The explanations below are followed by worked examples with real dates and real times, a set of frequently asked questions, and links to the tools that do the calculation for you: the time zone converter, the world clock, and the UTC converter. Where a number is given — an offset, a date, a count — it is computed from the IANA Time Zone Database for the date stated, not copied from a table that may be out of date.

Try the tool: Time Zone Converter — convert any time between any two cities, with the daylight saving rules for the date you choose.

Remote work across time zones is now normal, but the time-zone part is still where most remote teams fail. The work itself is easy to distribute; the coordination is not. The teams that make it work share a few habits, and none of them is about working longer hours.

The first habit is to agree on core hours — a small window (often 2–4 hours) when everyone is available, and to protect it for the work that needs live conversation. Everything else is flexible. A team spread across New York, London and Tokyo might set core hours of 13:00–15:00 UTC: morning in New York, afternoon in London, evening in Tokyo. That is short, but it is enough for the meetings that matter.

The second habit is to write everything down. In a co-located office, information travels by overhearing; in a distributed team, it travels by writing. Decisions, context and status should live in documents and tickets, not in chat threads that disappear or in meetings that half the team missed. The test is simple: can a new team member in a different time zone understand what is happening without asking anyone?

The third habit is to respect the edges. Do not schedule a meeting at the edge of someone's day and then run over. Do not send a message at 23:00 their time and expect a reply. And do not assume that because someone is online, they are available — in a remote team, presence indicators lie. The best remote teams measure output, not hours online, and they let people work when they work best.

In practice

Remote work across time zones works best when the team agrees on core hours — a few hours a day when everyone is online at the same time — and leaves the rest flexible. For a team spanning New York and London, the core hours are usually 9am–12pm New York time. For a team spanning London and Tokyo, they are 9am–11am London time. The core hours are the overlap; everything else is asynchronous.

The hiring decision matters more than the tools. A team that spans 12 hours can work, but it needs people who are comfortable working alone, writing clearly, and waiting for answers. A team that spans 3 hours barely notices the difference. When you hire remotely, the time zone gap is a real constraint on the role — and it is worth being honest about it in the job description, so no one is surprised.

The legal details are easy to overlook. Employment law, tax and data protection all depend on where people actually work, not where the company is registered, and a remote worker in another country can create obligations the company did not expect. The time zone is the visible part of the problem; the invisible part is the jurisdiction. Get advice before you hire across borders, not after.

The numbers: working-hour overlap in January 2026

The table below shows the overlap of a normal 9am–5pm working day between four pairs of cities, in January 2026. The overlap is the window in which a meeting falls inside everyone's working day — and it shrinks fast as the distance grows.

Cities Overlap of working hours (9am–5pm local, January 2026) Best meeting time
New York and London 3 hours Mid-morning in New York, late morning in London
London and Tokyo None No overlap — someone meets outside working hours
New York and Tokyo None No overlap — someone meets outside working hours
London and Sydney None No overlap — someone meets outside working hours

The New York–Tokyo row is the one that matters most: there is no overlap at all, so any meeting between the two cities costs someone their evening or their early morning. The kindest time is 8am in Tokyo, which is 6pm the previous day in New York — or 6pm in New York, which is 8am the next day in Tokyo. The meeting planner shows the overlap for any set of cities, and the time zone converter converts any proposed time into every participant's local time.

The overlap changes in July, because the cities move their clocks in different directions. The same four pairs in July 2026:

Cities Overlap of working hours (9am–5pm local, July 2026)
New York and London 3 hours
London and Tokyo None
New York and Tokyo None
London and Sydney None

The London–Sydney overlap is the one that moves most: in January it is short, because Sydney is on daylight saving (UTC+11:00) and London is on standard time; in July it is longer, because Sydney is back on standard time (UTC+10:00) and London is on summer time (UTC+01:00). The gap shrinks from 11 hours to 9, and the overlap grows by two hours. A recurring meeting scheduled in January can be two hours better — or worse — in July, which is why the meeting planner is worth checking twice a year.

Key facts

  • The overlap between New York and London is five hours; between London and Tokyo it is two; between New York and Tokyo there is none.
  • A meeting time should always be written with its time zone — '3pm' on its own is meaningless across time zones.
  • Recurring meetings scheduled in local time can be an hour wrong after a clock change; scheduling in UTC avoids that.
  • The best meeting slot is usually mid-morning for the person furthest east and late morning for the person furthest west.
  • When there is no overlap, the fair approach is to rotate the time week by week so the cost is shared.

Frequently asked questions

How do remote teams handle time zones?

By agreeing on core hours — a few hours a day when everyone is online — and leaving the rest flexible and asynchronous.

What are core hours for a New York–London team?

Usually 9am–12pm New York time (2pm–5pm London). For London–Tokyo, they are 9am–11am London time.

Does the time zone gap matter when hiring remotely?

Yes. A team spanning 12 hours needs people who work well alone and write clearly; a team spanning 3 hours barely notices the difference. It is worth stating the gap in the job description.

What legal issues come with hiring across time zones?

Employment law, tax and data protection depend on where people actually work, not where the company is registered. Get advice before hiring across borders, not after.

What is the best meeting time for a global remote team?

There is no single best time — rotate it week by week so the cost is shared fairly, and prefer written updates where a meeting is not needed.

What is the overlap between London and Sydney in July?

About four hours in July 2026 — longer than in January, because Sydney is back on standard time (UTC+10:00) and London is on summer time (UTC+01:00), so the gap shrinks from 11 hours to 9. The meeting planner shows the overlap for any cities.

What is the time difference between London and Tokyo?

Nine hours in January 2026: London is UTC+00:00 and Tokyo is UTC+09:00. In July it is eight hours, because London moves to UTC+01:00 while Tokyo stays on UTC+09:00. The time zone converter gives the difference for any two cities and any date.

Related pages

Sources

  • IANA Time Zone Database, via Node.js Intl (Intl.DateTimeFormat with timeZone) — offsets, daylight saving dates and local times in this article were worked out from the IANA database, not typed from memory.
  • TimeFlow's own time-zone data (data/cities.ts, data/dst.ts), computed from the IANA database.
  • Time zone rules and offsets: the IANA Time Zone Database, as applied by this site's tools. Offsets and daylight saving dates on this page are computed from the database for the dates stated.
  • TimeFlow's time zone converter, world clock and UTC converter — the live tools behind the numbers on this page.
  • Time-zone and daylight saving rules are set by governments and can change. For flights, deadlines and meetings that cannot move, confirm the time with an official source.