AI data center water usage: NVIDIA's 0.2% claim, liquid cooling, and the local-stress nuance

NVIDIA's viral number is not made up. The Manhattan Institute estimates data centers account for roughly 0.2% of US freshwater consumption, most of it indirect through electricity generation ^[1]. The sleight of hand is the denominator. A national percentage averages a few water-stressed counties into the entire country's farms, lawns, and rivers, so the burden disappears in the rounding. Experts who study this insist the impact is fundamentally local: the same AI workload uses different amounts of water depending on climate, cooling technology, and electricity mix, so national averages obscure acute regional stress ^[3]. The local picture is where the friction actually lives. More than 97% of major operators' water is drawn from municipal drinking-water systems, putting data centers in direct competition with residents in drought-prone regions ^[6]. Google's thirstiest Iowa data center alone used about 2.7 million gallons per day in 2024 ^[3]. A figure that is technically accurate at the national scale can still describe a genuine fight over the tap in Arizona, Texas, or Iowa, which is precisely why a reassuring 0.2% and an angry zoning hearing can both be true at once.

The most underappreciated part of this debate is that there is no agreed definition of how much water a data center uses, because the answer depends on what you decide to count. Independent analyst Brian Potter publicly revised his own estimate after scrutinizing the math, warning that headline figures are very easy to take out of context and that maximalist methods, such as counting evaporation from hydroelectric reservoirs at roughly 18 gallons per kilowatt-hour, inflate the totals ^[2]. The spread is enormous: Potter's realistic revised figure lands around 200 to 250 million gallons per day, against Berkeley Lab's 628 million gallons per day, which itself splits into 579 million indirect and 49 million direct ^[2]. In other words, the indirect electricity-related water dwarfs the water the building physically consumes, and whether you include it can change the answer by an order of magnitude. This is why the same topic produces both 'overblown' and 'crisis' headlines, often citing real numbers. Direct on-site consumption is itself non-trivial: US data centers directly consumed 17.4 billion gallons in 2023, comparable to roughly 160,000 households, and about 80% of withdrawn water evaporates rather than returning to the system ^[4]. The honest reading is that the methodology, not the technology, drives most of the disagreement.

The technical core of NVIDIA's reassurance is real. Closed-loop and direct-to-chip or immersion liquid cooling sharply reduce on-site water use versus open evaporative cooling, which sprays water and lets roughly 80% of it evaporate away ^[4]. The contrast is stark: a closed-loop campus can peak around 22,000 gallons per day against roughly 5,000,000 gallons per day for a comparable evaporative-cooled campus ^[5]. Vendors put the reduction at up to about 70% versus traditional open evaporative methods, with immersion cooling claiming up to 99% less water than air cooling ^[4]. The mechanism matters: a closed loop recirculates the same coolant rather than continuously evaporating fresh water, and warm-water designs running coolant around 45 degrees Celsius let facilities in favorable climates lean on dry coolers instead of water. But the engineering caveat that gets lost in the viral framing is that closed loop does not mean zero. These systems still require periodic blow-down to flush mineral buildup, and the upfront water to fill the loop is real. The takeaway is that liquid cooling genuinely changes the day-to-day water curve, but it shifts the problem rather than erasing it, and a campus that runs near-zero on cooling water can still draw meaningfully when you count fill, blow-down, and the electricity it consumes.

The quantitative spine of this debate is a set of numbers that look contradictory until you line them up. The headline is 0.2% of US freshwater consumption, the Manhattan Institute figure NVIDIA amplified ^[1]. Cooling technology drives the widest on-site swing: a closed-loop campus peaks near 22,000 gallons per day versus roughly 5,000,000 gallons per day for a comparable evaporative campus, a difference of more than two orders of magnitude ^[5]. National estimates diverge almost as sharply: Brian Potter's revised realistic figure is roughly 200 to 250 million gallons per day, against Berkeley Lab's 628 million gallons per day ^[2]. And the framing-by-comparison favored by skeptics is striking: Arizona data centers used about 905 million gallons in 2025, while Phoenix-area golf courses use roughly 29 billion gallons annually, putting data center draw at a small fraction of recreational turf ^[1]. Set against rising disclosed totals, US data centers directly consumed 17.4 billion gallons in 2023 ^[4], and trajectories steepen fast, with Texas data centers projected to climb from 49 billion gallons in 2025 toward as much as 399 billion gallons by 2030 ^[6]. The numbers are not in conflict; they answer different questions about scale, location, and what counts.

The 0.2% talking point did not surface neutrally. It originates with the Manhattan Institute, a free-market think tank, packaged inside a specific policy argument: the problem is not how much water data centers use but how water gets allocated among competing demands, and the fix is tradable water markets rather than construction moratoria ^[1]. NVIDIA, whose business depends on the continued data center buildout, amplified that figure to a mass audience on X, where the sentiment skewed reassuring. The policy framing is coherent on its own terms: the Institute argues that when water rights are secure and transferable, new demand can be met without harming existing users ^[1]. But the counter-pressure is material and growing. Local opposition delayed or blocked roughly $98B in data center projects between March and June 2025, and a coalition of more than 230 environmental groups has campaigned to halt new construction over water, climate, and economic concerns ^[6]. That collision, a market-friendly reassurance campaign meeting organized community resistance, is the real story under the statistics. The 0.2% figure is a true number doing rhetorical work, and recognizing whose interests it serves is part of reading it honestly.