World Cup Hydration Breaks Are Dividing Teams And Observers—Here’s Why

BreakingBusinessWorld Cup Hydration Breaks Are Dividing Teams And Observers—Here’s WhyByAntonio Pequeño IV,Forbes Staff. Pequeño is a breaking news reporter who covers tech and more.Follow AuthorJun 16, 2026, 05:35pm EDTToplineThe 2026 World Cup has sparked a divide with the inclusion of hydration breaks at this year’s games, with players, coaches and observers expressing mixed feelings about how the breaks disrupt the competitive flow of matches and interrupt games with advertisements.Kylian Mbappe #10 of France looks on during a hydration break in the FIFA World Cup 2026 Group I match between France and Senegal.Photo by Hannah Peters - FIFA/FIFA via Getty ImagesKey FactsFollowing the sweltering 2025 FIFA Club World Cup in the U.S. last year, FIFA introduced the three-minute hydration breaks, which take place midway through the two halves of each game and are taken regardless of weather or temperature conditions at this year’s World Cup.The rule divides games into a total of three breaks, or four quarters, a significant difference from the singular 15-minute break taken in the middle of typical 90-minute matches.Virgil van Dijk, star defender for the Netherlands, jabbed at commercials airing during the hydration breaks and said it’s “not great,” for neutral fans watching on TV and that the breaks would be useful for hot conditions but, “I think you have to look at it in every game, separately, in my opinion.”Emma Hayes, the head coach of the U.S. women's national team, characterized the hydration breaks as “momentum breaks,” acknowledging their usefulness for teams on the backfoot and noting, “It’s a shame… but it seems like it could be something that could be here for good,” according to ESPN.U.S. men’s national team head coach Mauricio Pochettino told reporters he does not like the water breaks, adding, “I only like it when the conditions are extreme, but when the conditions are good, it is unnecessary.” if (!window.cnxel) { window.cnxel = {}; window.cnxel.c...