Soccer World Reacts to D.C. Missing Out on 2026 World Cup

It’s official: the 2026 FIFA World Cup will not be coming to Washington, D.C.

FIFA revealed its host cities for the 2026 event, which is being co-hosted by the United States, Mexico and Canada. Of the 16 cities selected, 11 are in the U.S.—though the nation’s capital is not one of them.

The 2026 World Cup destinations across the USA, Mexico and Canada are now known. @brianstraus on the 11 U.S. cities that made it, the five that did not and the big reveal for the first 48-team World Cup 🏟️🌎🏆⚽🇺🇸🇲🇽🇨🇦https://t.co/QE0xd45USm pic.twitter.com/a0epQ7vEP0
— SI Soccer (@si_soccer) June 16, 2022

The decision to leave Washington out of the mix is not entirely surprising. FedExField had been in the running to host World Cup games but dropped out in April, with Washington instead choosing to merge its bid with Baltimore. In that scenario, Washington would host World Cup fan events while games would be played at the Ravens’ M&T Bank Stadium. The joint Baltimore-D.C. bid was ultimately left out.

Watch soccer online with fuboTV: Try for free!

This will mark just the third time in men’s World Cup history that the host nation’s capital will not feature games. The first time was in 1972 in what was then West Germany, then again in 2002 in Japan.

Even if the ultimate decision to leave Washington, D.C. out of the World Cup mix was somewhat expected, it still caused strong reactions from across the soccer world. Check out some of the standouts below.

No World Cup games for Baltimore-DC. This is what happens when you can't find a way to build a world-class stadium. You get left behind. The capitol city of a country should not miss an event like this.
— Brian McNally (@bmcnally14) June 16, 2022

Only other times the capital city hasn't hosted World Cup matches ...

1974: Bonn (it was complicated)
2002: Tokyo (but three venues in the region)

Massive embarrassment for D.C.
— Steven Goff (@SoccerInsider) June 16, 2022

Absolute shock in the room as DC is passed over as a host city. A World Cup without matches in the national capital seems unthinkable, but here we are. pic.twitter.com/rvvwy3ByJM
— Pablo Iglesias Maurer (@MLSist) June 16, 2022

DC/Baltimore robbed. Boston stole it. #WorldCup https://t.co/h3BMJV0pHe
— Drake Hills (@LiveLifeDrake) June 16, 2022

Gutted for DC & its soccer fans who got snubbed by FIFA for hosting the 2026 World Cup today. FedEx field is right on the metro & could've easily played host to the Beautiful Game, just as RFK did in '94. The host selection list was way too Northeast-heavy. Sorry, Mid-Atlantic! pic.twitter.com/1ofEtkCbdt
— Catless Cat Lady (@chipgoines) June 16, 2022

A collective “boo” from the crowd after the cities were announced on the east coast for the World Cup - Baltimore/DC was not one of them. @wjz pic.twitter.com/sLK9FJySKO
— Kelsey Kushner (@KelseyKushnerTV) June 16, 2022

No DC or BMore??? @FIFAWorldCup y'all trippin fr🤦🏾‍♂️
— Jon Bell🖖🏾 (@astrobell23) June 16, 2022

Headline writers: DC was not snubbed for the World Cup. Baltimore was. DC snubbed itself when it woke up and realized their cement graveyard in PG County wasn't going to be a winner. DC lost a little fair.
— Tyler Weyant (@tweyant) June 16, 2022

it’s relatively suprising but not for the reasons stated. the relative imagery of the capital city pales in comparison to the fact that soccer in all forms: participation, fans and viewership numbers is insanely popular. To choose to skip a Top 5 market is wild, stadiums aside. https://t.co/RIh6Io6BPz
— Clinton Yates (@clintonyates) June 16, 2022

Boston over DC/Baltimore is a bad decision. Boston isn’t really what most people think about a soccer city. #FIFAWorldCup
— Regina Ham (@regina_ham) June 16, 2022

I thought Baltimore/DC would host....didn't think they'd skip over the capital...DC's stadium situation is so bad and I guess they didn't want Baltimore
— Matt Stepp (@Matt_Stepp817) June 16, 2022

More Soccer Coverage: