For distributed teams

Find a meeting time that works for every city — instantly.

ZoneShift is the time zone reference built for remote teams scheduling cross-border meetings. Compare local times in 600 cities, plan calls across continents, and stop guessing whether 4 PM in Berlin is a polite hour for your colleagues in Manila.

New York City
America/New_York
16:06:00
Thu, 02 Jul 2026
London
Europe/London
21:06:00
Thu, 02 Jul 2026
Bengaluru
Asia/Kolkata
01:36:00
Fri, 03 Jul 2026
Singapore
Asia/Singapore
04:06:00
Fri, 03 Jul 2026
Sydney
Australia/Sydney
06:06:00
Fri, 03 Jul 2026
Toronto
America/Toronto
16:06:00
Thu, 02 Jul 2026

Major cities right now

Live local times for the cities your team most often coordinates with. Click any card for a full city profile, including UTC offset, daylight saving status and recommended meeting overlaps against the world's major hubs.

Compare any two hubs in one click

Permanent comparison pages for the world's busiest remote-work corridors — color-coded overlap calendars, recommended meeting windows, and an embedded converter.

Why teams use ZoneShift

Real IANA data

Every offset, abbreviation and DST transition comes from the IANA Time Zone Database — the same data your operating system uses — so what you see here matches what your team's calendars do.

Built for remote work

Most converters were designed for travellers. ZoneShift is built for engineers, recruiters and operations teams who run weekly standups across four continents and need a tool that thinks the way they do.

Hundreds of cities

We track 600 world cities with population above 100,000, sourced from public datasets. Every city gets a dedicated page with full scheduling context.

No sign-up, no tracking

ZoneShift is a static reference. We don't ask for an email and we don't follow you around the web. Bookmark a comparison and it loads instantly next time.

Browse by region

If your team works across borders, start with one of the time-zone hubs below. Each link opens a full breakdown of the cities in that zone, the countries it covers and the current offset from UTC.

See all 137 IANA time zones →

From the scheduling guide

Practical, opinionated writing for managers running distributed teams.

Foundations

Remote team scheduling fundamentals: a field guide for distributed managers

The core ideas every distributed manager should internalise before they touch a calendar invite — anchored teams, follow-the-sun, async-by-default, and the cost of every synchronous meeting that crosses a coastline.

Foundations

Follow-the-sun vs anchored overlap: choosing the right shape for your remote team

Most distributed teams default to "everyone joins one all-hands" without realising that the underlying scheduling shape is a strategic choice. We compare the two dominant models and the kinds of work each one supports.

Operations

Designing a fair meeting rotation when no single time works for everyone

When your team spans three or more continents, no single weekly slot is fair to everyone. A documented rotation, applied honestly, is the difference between a team that scales and a team that quietly resents whoever runs the calendar.

Operations

Standup times across three continents: what actually works

A practical breakdown of the standup patterns we have seen succeed in teams spanning the Americas, Europe and Asia — and the patterns that look elegant on paper but quietly burn the team out.

Time zones

Daylight saving survival guide for international teams

Twice a year, an hour quietly disappears or appears in your team calendar. If your scheduling tools and your team conventions are not built to handle it, you will lose at least one important meeting per transition.

Time zones

IANA zones vs UTC offsets: why the difference matters in practice

Treating "UTC+1" and "Europe/Berlin" as interchangeable is one of the most common bugs in scheduling tools. We explain why the IANA database is the only correct way to store and reason about time zones.

Read the full Remote Team Scheduling Guide →