FIFA set to name cities for 2026 World Cup: live updates

Andre Das

Yes, the New York Times knows that MetLife Stadium is in East Rutherford, NJ, not New York. Yes, we’ve been to Levi’s Stadium in Santa Clara, CA, and Gillette Stadium in Foxborough, MA, and yes, we know some people even spell that last spot Foxboro.

Prepare for some geo-manipulation in Thursday’s announcements of host cities for the 2026 World Cup, as FIFA have already done quite a bit of it in the process. The combined Washington-Baltimore offer, for example, would bring games to Baltimore, but not to Washington. This card alone seems to have completely detached Dallas and Denver from their moorings.

But fair warning: our live coverage will likely follow this lead, for the sake of simplicity, with specificity notations where necessary.

Each of the 22 finalists (and 23 stadiums) was attached to a major city, even if the stadium linked to each application does not technically sit in said city.

Here is the full list (with each stadium and its actual location):

United States

Atlanta (Mercedes-Benz Stadium)

Boston (Gillette Stadium, Foxborough)

Cincinnati (Paul Brown Stadium)

Dallas (AT&T Stadium, Arlington)

Denver (Empower Field at Mile High Stadium)

Houston (NRG Stadium)

Kansas City, MO (Arrowhead Stadium)

Los Angeles (SoFi Stadium, Inglewood and the Rose Bowl, Pasadena)

Miami (Hard Rock Stadium, Miami Gardens)

Nashville (Nissan Stadium)

New York/New Jersey (MetLife Stadium, East Rutherford, NJ)

Orlando, Florida (Camping World Stadium)

Philadelphia (Lincoln Financial Field)

San Francisco (Levi’s Stadium, Santa Clara, CA)

Seattle (Lumen Field)

Washington, DC/Baltimore (M&T Bank Stadium, Baltimore)


Edmonton (Commonwealth Stadium)

Toronto (BMO Field)

Vancouver (BC Square)


Guadalajara (Akron Stadium, Zapopan)

Mexico City (Aztec Stadium)

Monterrey (BBVA Stadium, Guadeloupe).

Leave a Comment