Skip to main content

OpenAI's Texas data centre is built to barely use water. The power plants it runs on use 300 times more water than it does

Jamie Watters

Operational resilience and AI delivery practitioner.

Published: 2 October 2026•9 min read
#ai-water#fact-check#data-centres
Card headed 'Built to barely use water: one 200 megawatt block of the Stargate campus in Abilene, Texas.' Three rows. The builder's website: 910,000 gallons a year. The builder's own report: about 2 million gallons a year, about 20,700 litres a day, three Kansas restaurants. The power plants making its electricity, on the Texas grid average: about 6.2 million litres a day, and a water-cooled site pays this too. Footer: Crusoe 2025 impact report and web page, VanSchenkhof 2011, Li and colleagues 2025 using a World Resources Institute 2020 factor.

Crusoe builds the Stargate campus in Abilene, Texas, which Oracle runs for OpenAI (DCD). It says on its website that a 200 megawatt block uses about 910,000 gallons of water a year, "comparable to fewer than 10 U.S. households" (Crusoe, impact report web page). The full report that page links to says something else. "At a 200 MW facility, total annual water use ... is estimated to be approximately 2 million gallons per year, comparable to the annual water use of fewer than 20 U.S. households" (Crusoe 2025 Impact Report, p. 28).

Same company, same 200 megawatts, two numbers. One is more than twice the other.

The bigger one is still small. Two million gallons a year is about 20,700 litres a day. A casual-dining restaurant in Kansas gets through about 6,700 litres a day, on utility records for 221 of them (VanSchenkhof, 2011). So a 200 megawatt block of Stargate uses about as much water as three restaurants. The restaurant is my comparison, not Crusoe's. Crusoe compares itself to households, and to "any office or warehouse of similar size".

In the previous piece I traced the per-prompt water numbers back to where they came from. One was the bottle of water per 20 questions, which its own authors withdrew (AI water use: the bottle per 20 ChatGPT questions was withdrawn by its own authors). I also said what I believed about the buildings: that data centre cooling is mostly a closed system, and the water actually used up is small. This piece tests that. It's wrong for the fleet that exists and right for the newest designs. And the biggest water number isn't in the building at all.


The fleet that exists

Google publishes water figures for each of its data centres, in a table at the back of its environmental report. Its Council Bluffs, Iowa site withdrew 1,746 million gallons in 2025 and consumed 1,346 million of them: evaporated, not returned (Google 2026 Environmental Report). That's about 14 million litres a day used up, at one site, reported for a year that has happened. The same table lists an air-cooled Google site in Pflugerville, Texas: 0.1 million gallons consumed in 2025, about 1,000 litres a day. Google doesn't give the size of either site, so the gap isn't all down to cooling. But it shows what a water-cooled giant evaporates. Google says water cooling "requires less energy than air-cooling technologies", and its freshwater consumption rose 37 per cent in 2025.

Three bars to one scale, litres used up per day. Google Council Bluffs, Iowa, water-cooled, reported for 2025: about 14 million, the full width. Google Pflugerville, Texas, air-cooled, reported for 2025: about 1,000, too thin to see. One 200 megawatt Crusoe block at Abilene, closed loop, the builder's estimate for every use on site: about 20,700, a hairline. Caption: Google gives no size for either site; these are totals, not rates.

That's one company. For the whole country, Lawrence Berkeley National Laboratory puts the direct water consumption of US data centres at 66 billion litres in 2023, 84 per cent of it at hyperscale and colocation sites (LBNL, December 2024). Its modelling finds plenty of ways to save water, then says "the indispensable role of evaporative cooling in dissipating internal heat from IT devices remains evident, therefore contributing to significant water consumption" (p. 44). Its average for the whole fleet is just over 0.36 litres of water per kilowatt-hour of computing.

So "mostly a closed system" is wrong for the buildings running today. Many of the big ones evaporate water on purpose. LBNL says why: evaporative systems "are generally more energy efficient than an air-cooled chiller", and "while air-cooled chillers use no water, they use more energy" (p. 45). Evaporating water saves electricity.


The efficient ones

The newest designs are different, and Crusoe isn't alone. Microsoft says every data centre it has designed since August 2024 "consumes zero water for cooling", with the first sites coming online in late 2027 (Microsoft, December 2024). Its Fairwater site in Wisconsin runs over 90 per cent of its capacity on a closed loop that takes water "only once during construction"; the rest switches to water on the hottest days (Microsoft, September 2025). In June 2026 Satya Nadella said a new Microsoft data centre uses "roughly" what "a single restaurant would use" (PCMag via Yahoo Tech, June 2026).

Here's why that's possible. Cooling the chip doesn't use water up: the liquid goes round a sealed loop. The water question is where the heat leaves the building. A cooling tower gets rid of heat by evaporating water, about 80 per cent of what it takes in (Li and colleagues, 2025). An air-cooled chiller blows it away with fans, and evaporates nothing. That's Crusoe's design: "The heated liquid is then cooled by air-cooled chillers and recirculated. No water is evaporated" (Crusoe report, p. 29).

So where do Crusoe's 2 million gallons go? Its own breakdown, for 200 megawatts (p. 28):

  • Cooling top-up: about 54,000 gallons a year. That's what the Kansas restaurant uses in about a month.
  • Kitchens, restrooms and break areas: about 460,000 gallons.
  • Equipment cleaning and facility upkeep: about 1.4 million gallons.

Where the 2 million gallons go, one bar split three ways to scale. Cooling top-up, about 54,000 gallons, a sliver at the left. Kitchens, restrooms and break areas, about 460,000. Equipment cleaning and facility upkeep, about 1.4 million, most of the bar. Caption: Crusoe's estimate for a 200 megawatt block, from its 2025 impact report; the cooling is the smallest part.

The cooling is the smallest part. Most of the water is people and cleaning.

Two labels to keep on these numbers. They're estimates: the report's words are "estimated" and "expected", and it gives no metered figure for any site. The first two Abilene buildings were handed to the tenant in mid-2025, and the report covers 2025, so a measured figure could exist. It isn't published. And none of them includes the one-off fill. Crusoe gives that three ways. Its 2025 site tour says one million gallons per building (Crusoe, August 2025). The report's text says 1.7 million for a whole 200 megawatt data centre. The same report's index says 1.7 million per building. Somewhere between 850,000 and 1.7 million gallons a building, spent once, then reused for up to 15 years.


The power plants

Electricity has water in it. Power plants that burn fuel need cooling, and hydroelectric reservoirs lose water to evaporation (LBNL, p. 56). LBNL's figure for the water consumed generating US data centres' electricity in 2023 is nearly 800 billion litres, twelve times the 66 billion they consumed on site (p. 57). It's a model, built on the average mix of each regional grid, not a measurement at any plant.

Do the same for one Abilene block. Run 200 megawatts flat out for a day and it draws 4.8 million kilowatt-hours. The Texas grid average is 1.287 litres of water consumed per kilowatt-hour: a World Resources Institute figure from 2020, used by Li and colleagues (2025 revision). That's about 6.2 million litres a day at the power plants. If the 200 megawatts is the computing load rather than the whole site, add Crusoe's design overhead of 1.2 to 1.4 and it's 7.4 to 8.6 million. That's 300 to 400 times what the block uses on site.

Two caveats. That's the grid average, not the plants that actually serve Abilene. And Abilene has its own 350 megawatt gas plant on site for backup (Crusoe report, p. 17), which the grid average doesn't see.

Now the part I got wrong in the first version of this piece. I wrote that a closed loop "moves the water bill from the site to the grid". It doesn't. A water-cooled data centre of the same size in Texas runs on the same grid and pays nearly the same 6 million litres. The power plants' water belongs to the electricity, not to the cooling. What the closed loop changes is two things: it stops evaporating water on site, and it uses a bit more electricity to do it.

So which is bigger? Li and colleagues give Microsoft's Texas data centres an on-site rate of 0.25 litres per kilowatt-hour. For a 200 megawatt water-cooled site that's about 1.2 million litres a day evaporated on site, against Crusoe's 20,700. Going dry costs water only if the extra electricity is more than about 15 per cent, my arithmetic on Li's Texas figures. Microsoft says its zero-water design costs "a nominal increase in our annual energy usage". On the numbers that exist, in Texas, the closed loop most likely cuts total water. Neither Crusoe's report nor Li's paper has a measured comparison, so I can't settle it.

Two stacked bars, litres a day, for a 200 megawatt site on the Texas grid. Water-cooled: about 1.2 million evaporated on site, on top of about 6.2 million at the power plants. Closed loop: about 20,700 on site, a hairline, on top of about 6.2 million at the power plants plus a small extra for the chillers. Caption: the power plants' water is paid by both; going dry costs water only if it adds more than about 15 per cent to the electricity.


The test, for the next data centre water number you hear

Start with a water figure for a data centre, from anyone: a company, a podcast, a headline.

  1. Measured, estimated or designed? Look for the word. Crusoe's say "estimated" and "expected". Google's table reports a year that has happened. A year in a table doesn't prove anyone measured it, so read the method note too.
  2. What does it count? Cooling only, or every tap? Does it include the one-off fill? Crusoe's 54,000 gallons is cooling. Its 2 million is everything on site. The fill is separate.
  3. Taken in, or used up? Withdrawal is water drawn from the supply. Consumption is the part that doesn't come back, mostly through evaporation. Council Bluffs withdrew 1,746 million gallons and consumed 1,346 million.
  4. Per what? A building, a 200 megawatt block, a whole campus? Two totals without sizes can't be compared, which is why Council Bluffs against Pflugerville proves less than it looks.
  5. Where does it stop? At the fence, or at the power plants? And if the power plants: how much would any data centre of that size pay, and how much is down to the cooling?

Pass: each label stated by a source you can name. Repeat the number with its labels. Fail: any one missing. Say "the company says", and say what's missing.

Run it on Crusoe's number. Estimated, not measured. Everything on site, but not the fill. The report doesn't split taken in from used up. Per 200 megawatt block, and the campus is 1.2 gigawatts. And it stops at the fence. Three of the five labels are in Crusoe's report. Its web page has two, and the smaller number.

Crusoe's website says 910,000 gallons. Its report says 2 million. Neither says what the power plants use, and that's the biggest number in this piece. It's also the one the closed loop changes least.

Corrected 2 October 2026. The first version used Crusoe's website figure of 910,000 gallons, not its report's 2 million. It credited Crusoe with a restaurant comparison that is mine, and quoted the wrong sentence from the LBNL report. It also said a closed loop moves the water bill to the grid, which this version explains is wrong. The title and the figures changed with it.


Sources

No paywall, no sponsors. If this saved you some time, you can buy me a coffee.

☕ Buy me a coffee

Get the next one in your inbox

I build with AI in the open and write up what held and what didn't. Real numbers, the failures before the wins.

Share this post