Summary
- Water UK estimates current average data centre demand at about 6.6 million litres a day, potentially rising to 19.8 million litres if capacity triples.
- Peak requirements could rise from roughly 14 million to 42 million litres a day, with individual enquiries reaching 21 million litres.
- Cooling design, location, drought conditions, and long utility lead times will determine whether proposed capacity can be served.
Water UK has warned that plans to expand British data centre capacity have not fully accounted for the amount of water facilities may require during periods of maximum cooling demand.
The trade body estimates that the sector currently consumes an average of about 6.6 million litres a day, broadly equivalent to the use of 20,000 homes. If national data centre capacity triples, average demand could rise to approximately 19.8 million litres a day.
Peak requirements are considerably higher. Water UK’s evidence to Parliament estimates current maximum demand at about 14 million litres a day, potentially rising to 42 million litres, while individual data centre enquiries have sought connections capable of supplying 21 million litres a day.
The network has to serve the hottest day
Water infrastructure is sized around demand when supply conditions may already be difficult. Facilities using evaporative or hybrid cooling can consume more water during heatwaves, when households, agriculture, industry, and river systems are also under strain.
An annual average can therefore conceal the pipe capacity, treatment plant, storage, and drought planning needed to support the site. A data centre may use relatively little water through cooler months before drawing substantially more during a short period of high outdoor temperature.
More than three-quarters of current capacity is concentrated in eastern and south-eastern England, according to Water UK. Those regions also contain major fibre routes, cloud zones, financial-services demand, and established data centre clusters, but several catchments already face severe pressure.
Cooling systems vary widely. Closed-loop air and liquid designs can operate with little routine process-water consumption, while evaporative equipment exchanges water use for lower electrical demand. Dry systems may consume more power or require larger heat-rejection equipment during hot conditions.
Direct liquid cooling changes the route by which heat leaves the processor, but it does not remove the need to reject that heat outside the building. The final water requirement depends on cooling distribution units, secondary loops, heat exchangers, chillers, dry coolers, cooling towers, and the operating temperatures of the installed hardware.
Data centre and utility programmes move at different speeds
Reservoirs and major water infrastructure can take more than a decade to plan and deliver. AI-related data centre programmes often seek utility connections within a few years, creating a mismatch between digital capacity schedules and the investment cycle of the water system.
Water UK argues that the current regulatory model does not give companies enough certainty to build large assets ahead of confirmed business demand. Developers can secure land and advance planning before discovering that a requested connection needs reinforcement or cannot arrive on the required programme.
Utilities face the opposite exposure. A cluster of proposed facilities may request substantial capacity, yet only part of that pipeline may proceed, leaving the water company unable to justify early investment without firmer commitments.
Site selection will increasingly need to consider water alongside grid capacity, fibre, land, and planning. A strong electricity connection cannot compensate for an evaporative cooling design that exceeds local water availability, while a low-water design may carry higher electrical or capital costs.
Drought restrictions add an operational dimension. Data centres have been designated as critical national infrastructure, but that status does not create additional supply inside a constrained catchment. Continuity plans will need to show how sites reduce demand or maintain cooling when water availability falls.
Developers can lower exposure by publishing both average and maximum demand, using non-potable sources where practical, capturing rainwater, improving water treatment, and selecting control strategies that reduce consumption during stressed periods. Each measure brings its own water-quality, biological, maintenance, and resilience requirements.
Heat reuse may also alter the balance by giving the cooling system another route to reject energy, although networks and customers must be available when the facility produces heat. Seasonal demand can leave the data centre relying on conventional heat rejection during summer, precisely when water conditions are tightest.
The planning figure that governs deliverability is not a national average. It is the maximum credible requirement of each site, in its own catchment, during the conditions when cooling plant and public water systems are under the greatest pressure.
