Water Permits Are Becoming Data Centers’ Next Site-Selection Bottleneck

Every data center site-selection checklist has the same top line: power. In 2026, a second line is climbing fast enough to block deals on its own — water. Six state legislatures have moved past asking operators to be polite about water use and started writing permitting law around it, and at least one, Minnesota, now runs a formal tiered water-permitting review before a large facility can break ground. If you’re evaluating a site, a colocation contract, or a build timeline right now, water access has quietly become a gating item, not a sustainability footnote.

The number that actually matters: 211 billion gallons, not 17 billion

The headline stat operators like to cite is direct water consumption — the water evaporated on-site for cooling towers and adiabatic systems. In 2023 that was about 17.4 billion gallons across U.S. data centers, according to a July 2026 analysis from the Information Technology and Innovation Foundation (ITIF). Read in isolation, that sounds like a rounding error against total U.S. water withdrawals.

The number that should be in your site model is the indirect figure: roughly 211 billion gallons consumed generating the electricity those same facilities draw — about twelve times the on-site figure. That water is consumed at power plants, not at your building, which is exactly why it doesn’t show up when a colocation provider hands you a PUE and WUE sheet for their facility alone. The ratio also isn’t fixed by geography the way people assume: water intensity of power generation ranges from about 2.1 gallons per kilowatt-hour in the thermoelectric-heavy Pacific Northwest down to roughly 0.13 gallons per kWh in solar-heavy California grids. A megawatt of contracted capacity in one region can carry more than fifteen times the water footprint of the same megawatt somewhere else, before you’ve touched a single cooling tower. If your ESG reporting or your utility’s own water-stress disclosures only track the meter at your rack, you’re missing the majority of the exposure.

What states actually passed, not what they proposed

More than 200 data-center-related bills were introduced across all 50 states in 2025, with over 40 enacted into law, and water use specifically has drawn more than 60 bills in the 2025–2026 cycle alone. The ones that matter for a live deal fall into three buckets:

Technology mandates. South Carolina’s HB 4583 and Kansas’s SB 400 require closed-loop cooling systems — sealed loops with no atmospheric fluid contact — with South Carolina’s language pushing toward “zero net water withdrawal and net zero wastewater discharge” for covered facilities. That’s a design constraint you need in your RFP before you pick a cooling vendor, not after.

Disclosure and transparency. California’s AB 1577 requires monthly water reports to the state energy commission. Georgia’s SB 421 goes further and bans non-disclosure agreements that hide water or energy consumption data — a direct response to utilities and operators historically negotiating usage terms under seal. Iowa’s HF 2261 creates a separate water-utility customer class specifically for facilities drawing 20+ MW, which means a different rate schedule and a different negotiating table than the one your utility account team may be used to.

Hydrologic review. This is the one that actually stops a project. Minnesota is the first state to formalize water-permitting requirements for large data centers, with review tiers set by watershed stress levels — a facility proposed on an already-stressed watershed faces a materially longer and more uncertain permitting path than the identical facility twenty miles away on a healthier one. California is building similar hydrologic-impact assessments into its own review process. Virginia’s SB 417, which would have tied state grant funding to using treated wastewater for cooling, missed its 2026 crossover deadline and won’t be reconsidered until 2027 — a reminder that this legislative landscape is still moving, not settled, and today’s near-miss is next session’s requirement.

Why this is now a timeline problem, not just a compliance problem

ITIF’s analysis puts a number on the consequence: more than $130 billion in U.S. data center projects were delayed or abandoned in Q1 2026 alone, as power and water reviews stacked on top of each other in constrained markets. That figure sits alongside the grid-interconnection delays covered in our earlier look at 2026 site-selection timelines — the two are increasingly the same conversation, since a hydrologic review and an interconnection study can both run in parallel on the same project and either one can become the pacing item. The practical effect for a buyer negotiating a colocation or build-to-suit deal: a facility’s water sourcing plan is no longer something you confirm during commissioning. It needs to be underwritten during site selection, alongside power availability, because a watershed-stress designation can add months a power-only timeline never accounted for.

The technology response, and its real tradeoffs

Vendors have an answer, and it’s not free. Closed-loop direct-to-chip systems — the kind Microsoft has deployed and that Nvidia’s newest Rubin-generation platforms are designed around — get facilities close to zero water consumption for cooling by recirculating coolant rather than evaporating it. That matters more than it used to: Nvidia’s Vera Rubin platform is specified at densities up to 227 kW per rack, which forces a cooling architecture decision regardless of what the water statute says, and closed-loop liquid cooling is increasingly the only practical way to reject that much heat anyway.

For facilities staying on air or hybrid cooling, dry cooling cuts water consumption by more than 90% versus traditional evaporative towers, but it isn’t free thermodynamically — it typically requires 1–1.5% of a plant’s total output just to run the fans, a real capacity and PUE tradeoff that needs to go into your total-cost model, not just your water model. Hybrid wet/dry systems split the difference, cutting annual evaporative losses by up to 75% while keeping evaporative cooling available on the hottest design days. And zero-liquid-discharge systems, which use reverse osmosis to recover and recycle wastewater on-site, add well under 0.1% of a facility’s electricity load to run — cheap in power terms, but a real capital and O&M line item that a five-year-old colocation contract almost certainly didn’t price in.

What a capacity buyer should actually do with this

Ask any colocation or build-to-suit counterparty for their facility’s water source, whether it’s municipal, groundwater, or reclaimed, and whether that source sits in a state with an active technology mandate, disclosure law, or hydrologic review process — not just whether they report a WUE number. Request the indirect water intensity of the specific power mix serving the site, not a national average; a PPA tied to a thermoelectric-heavy grid carries a materially different footprint than one tied to solar or wind, even at an identical WUE. And build permitting-review time into your go-live model as its own line item in any state that has adopted or is actively debating watershed-tiered review, the same way you’d already budget separately for a utility interconnection study. The legislative landscape here is moving quarter to quarter, not year to year — Virginia’s near-miss this session is a preview of what’s likely to reappear, expanded, in 2027, and the operators who treat water sourcing as a procurement question today will have a real negotiating advantage over the ones still treating it as a footnote in a sustainability report.

Start your next site evaluation with our Data Center Buyer’s Toolkit for a structured way to weigh power, water, and permitting risk before you sign.

Written by

Raajeev Ratra

Data Center Infrastructure Expert | 15+ Years in DC Design, Operations & Project Management

Raajeev is a seasoned data center professional with hands-on experience in hyperscale facilities, colocation design, power & cooling infrastructure, and global DC operations. He shares practical insights to help engineers and IT leaders build better infrastructure.

Connect on LinkedIn →