Best Meeting Times Between US and India Teams (2026): IST to EST, CST, and PST Overlap Guide

If your team is split between the US and India, you have probably already done the math a hundred times. "9 AM my time is what in Bangalore?" It is annoying, it is error-prone, and you will still get it wrong the week DST kicks in.

This guide gives you the exact overlap windows that actually work, the DST traps to watch for, and a rotation rule so the same people are not always taking 10 PM calls.

The short answer

For a US/India team that wants one reliable daily sync, the best windows are:

US East Coast (EST/EDT) and India: 8:30 AM to 10:30 AM New York = 6:00 PM to 8:00 PM India.
US Central (CST/CDT) and India: 8:30 AM to 10:00 AM Chicago = 7:00 PM to 8:30 PM India.
US West Coast (PST/PDT) and India: 8:30 AM to 9:30 AM San Francisco = 9:00 PM to 10:00 PM India.

Everything else gets worse. Later US mornings push India past 10 PM. Earlier India mornings push the US into late evenings.

The time difference, quickly

India runs on IST (UTC+5:30) year round. India does not observe Daylight Saving Time, which means the gap between US and India shifts twice a year when the US clocks change.

US Zone	US Standard Time (Nov to Mar)	US Daylight Time (Mar to Nov)
EST/EDT	India is +10:30 ahead	India is +9:30 ahead
CST/CDT	India is +11:30 ahead	India is +10:30 ahead
MST/MDT	India is +12:30 ahead	India is +11:30 ahead
PST/PDT	India is +13:30 ahead	India is +12:30 ahead

A few quick conversions people search for all the time:

9 AM EST to IST: 7:30 PM same day (standard time) / 6:30 PM same day (daylight time).
9 AM PST to IST: 10:30 PM same day (standard time) / 9:30 PM same day (daylight time).
9 AM IST to EST: 10:30 PM previous day (standard) / 11:30 PM previous day (daylight).
9 AM IST to PST: 7:30 PM previous day (standard) / 8:30 PM previous day (daylight).

Why this trips people up

Three things go wrong, every time:

The 30 minute offset. Most time zones are whole hours. IST is not. People mentally round to +10 or +13 and book a meeting that is actually at 8:30, not 9:00.
India has no DST. When the US springs forward in March, the gap shrinks by an hour. When the US falls back in November, it widens again. India never moves.
Date line confusion. A meeting at 8 AM in San Francisco is 8:30 PM the same day in Bangalore, but an 8 AM call in Bangalore is 7:30 PM the previous day in San Francisco. Calendar invites handle this correctly, but humans reading chat messages often do not.

Best meeting windows by US region

Below are the windows where both sides are inside a reasonable working day (roughly 8 AM to 7 PM local). These assume US standard time (the "worst case" wider gap). During US daylight time, everything shifts one hour earlier for the US side and stays the same for India.

US East Coast + India

The best coast to pair with India. You get a real two hour window most days.

Morning US / Evening India: 8:30 to 10:30 AM New York = 6:00 to 8:00 PM Bangalore.
Edge case, needs rotation: 7:00 AM New York = 4:30 PM Bangalore (tight but workable once a week).

Recommended anchor: 9:00 AM Eastern = 6:30 PM India. Late enough that New York has coffee, early enough that Bangalore is not past dinner.

US Central + India

Morning US / Evening India: 8:30 to 10:00 AM Chicago = 7:00 to 8:30 PM Bangalore.
Recommended anchor: 9:00 AM Central = 7:30 PM India.

US Mountain + India

Morning US / Evening India: 8:00 to 9:00 AM Denver = 7:30 to 8:30 PM Bangalore.
Recommended anchor: 8:30 AM Mountain = 8:00 PM India.

US West Coast + India

This is the hardest pairing. Anything later than 9:30 AM Pacific pushes India past 10 PM. Anything earlier than 8 AM Pacific means someone on the US side is starting before sunrise.

Morning US / Evening India: 8:30 to 9:30 AM San Francisco = 9:00 to 10:00 PM Bangalore.
Recommended anchor: 8:30 AM Pacific = 9:00 PM India, and keep meetings to 45 minutes max.

Some teams prefer the flipped window:

Early India / Late US (previous day): 7:30 to 8:30 AM Bangalore = 7:00 to 8:00 PM San Francisco (previous day).

Pick one and stick with it. Bouncing between early and late is worse than either one.

The golden hour template

If you only run one meeting per day across US and India, use this:

45 to 60 minutes, four days a week (skip Fridays for the US; Saturdays for India if it runs a six day week).
Anchored to the US host's zone, so DST shifts are predictable.
Decisions and blockers only. Move status, demos, and long discussions to async video or written updates.
Agenda published 24 hours ahead in a shared doc linked in the invite.

The point is to compress the high-cost synchronous time into a single predictable window. Everything else should flow through writing and recordings.

Rotate the pain

Even the best window stings someone. India at 9 PM is not the same as New York at 9 AM. Track it.

A simple rule that works: every 8 weeks, flip which side absorbs the inconvenience. For a quarter, Bangalore stays late for the shared call. The next quarter, New York shows up at 7:30 AM and Bangalore finishes by 6 PM.

Document who absorbed what in a shared doc. This is the single cheapest trust builder for a cross-border team.

DST traps to put on your calendar

Put these four dates in a recurring reminder for whoever owns the team calendar:

Second Sunday of March: US springs forward. US/India gap shrinks by one hour. Your 9 AM EST meeting becomes 6:30 PM in India (instead of 7:30 PM).
First Sunday of November: US falls back. Gap widens by one hour. Same 9 AM EST meeting moves to 7:30 PM in India.
Last Sunday of March: UK and Europe spring forward. Only matters if you have Europeans in the mix, but it changes your three-way overlap.
Last Sunday of October: UK and Europe fall back.

India never moves. That is the one constant you can build around.

Use a live overlap board instead of static time tables

Static tables like the one above go stale the moment DST flips. A live board updates automatically and works for any team size.

Set it up once:

Create a board at Timezoners.
Add each teammate with their actual working hours (not an idealized 9 to 5; some engineers start at 10, some PMs start at 7).
Select the people who need to meet and the overlap highlights itself.
Paste the board URL into the recurring calendar invite. Everyone lands on the same view regardless of DST.

No signup, no password, just a shareable link.

Common questions

Can we do a real-time daily standup with US and India? Yes, but pick East Coast for the US side if possible. With Pacific, you are pushing India past 9 PM every day. That burns people out fast.

What about meetings with India and Europe? Much easier. London to Bangalore is 4.5 hours in winter, 3.5 in summer. A 2:00 PM London call is 7:30 PM India (winter) or 6:30 PM (summer). No gymnastics required.

What about India and Australia? India to Sydney is 4.5 hours in Australian standard time, 5.5 in daylight time. A 2:00 PM Bangalore call is 6:30 PM Sydney (winter) or 7:30 PM (summer).

Our India team starts at 10 AM, not 9. Does that change things? Yes. Push the US East window to 9:30 AM Eastern (7:00 PM India) so Bangalore does not end the day at 8 PM every night. Use actual working hours on your board, not defaults.

Should we just move everyone to UTC? Tempting, but no. Local time is what people live their lives in. Use UTC for logs and server scheduling, use local time for humans. We wrote about this here.

Where to go next

TL;DR

India is UTC+5:30 year round and does not observe DST.
Best daily sync with US East is 9 AM New York = 6:30 PM Bangalore.
Best daily sync with US West is 8:30 AM San Francisco = 9 PM Bangalore, capped at 45 minutes.
Anchor recurring meetings to the US host's zone and document the anchor in the invite.
Rotate the inconvenient window every quarter so the same team is not always staying late.
Use a live Timezoners board instead of static tables that break at DST.