São Paulo · New York

São Paulo to New York Time —
The Real Scheduling Guide

It's only one or two hours. That's exactly why people stop paying attention.

Gap 1–2 hrs
Overlap 5–7 hrs
Who pays São Paulo

The gap in plain language

São Paulo runs on Brasília Time (BRT, UTC−3). Brazil does not currently observe daylight saving time — it was suspended in 2019 and has remained fixed since. New York runs on Eastern Time (EST/EDT) and does observe DST.

  • US winter (EST): São Paulo is 2 hours ahead.
  • US summer (EDT): São Paulo is 1 hour ahead.

The shift happens entirely on the US side — in March the gap shrinks from 2 hours to 1, and in November it expands back. The distance is small. The seasonal swing is what catches teams off guard.

The honest overlap window

Assume working hours of 9am–6pm in both cities. Here's what actually overlaps — broken out by season:

US winter (2-hour gap):

🇧🇷 São Paulo🇺🇸 New York
9:00am – 11:00am7:00am – 9:00am
11:00am – 6:00pm ✦9:00am – 4:00pm ✦

In winter the clean overlap is 11am–6pm São Paulo / 9am–4pm New York — five solid hours. That's generous by any international standard.

US summer (1-hour gap):

The overlap expands further to 10am–6pm São Paulo / 9am–5pm New York — seven workable hours. On paper, this is one of the easiest international pairs in the Western Hemisphere. The problem isn't the overlap. It's the drift that happens because the overlap feels safe.

The fairness problem

Because the gap is small, meetings drift later without anyone noticing. A 4pm New York meeting is 5pm São Paulo during US summer — still inside the day. During US winter it's 6pm São Paulo. That's the difference between "still inside the day" and "end of day."

US teams often anchor the calendar assuming proximity means symmetry. But during US winter, Brazil consistently runs two hours ahead. Late US afternoon quietly pushes Brazil into evening. The cost is subtle, rarely dramatic, and accumulates over months.

The DST trap

This pair used to be messier. Brazil historically observed DST on dates that didn't align cleanly with the US — the offset would swing unpredictably for weeks at a time. That's why many teams still instinctively distrust the corridor.

Today Brazil stays fixed at UTC−3 year-round. The US switches in March and November. The gap flips between 1 and 2 hours overnight on a single Sunday — no staggered window, no gradual confusion.

A recurring 9am New York meeting lands at 10am São Paulo in summer and 11am São Paulo in winter. Small shift, real impact on morning routines. Many teams still operate as if Brazil might switch back. As of now, it doesn't — but that assumption lingers in calendars and muscle memory.

Practical recommendations

1
If New York leads, avoid scheduling after 3pm ET for recurring calls. It pushes São Paulo to 5–6pm depending on the season — end-of-day territory that accumulates silently.
2
Anchor shared meetings between 10am–2pm ET. That keeps both sides comfortably inside working hours year-round, regardless of which seasonal phase you're in.
3
Reconfirm recurring meetings every March and November. The offset changes by one hour. A 9am New York call becomes either a 10am or 11am São Paulo call — worth checking explicitly.
4
Don't rely on outdated DST assumptions about Brazil. Brazil is fixed at UTC−3 unless legislation changes. Many calendars and tools still apply historical Brazilian DST rules incorrectly.
5
If timing is critical, align explicitly to "New York time" in writing. The small gap makes people assume a shared mental model that often doesn't exist across teams.

🇧🇷 São Paulo
--:--
🇺🇸 New York
--:--
Meeting Planner — drag to explore
09:00
0h6h12h18h23h
Meeting Cost Who pays?
12am36912pm36912am
Fair for all
Shared stretch
Unequal
Unfair