Measure the Water Footprint of Your Software
Software feels weightless, but it isn't. Every API call, video stream, and AI query runs on physical infrastructure — and that infrastructure has a water footprint. The Software Water Intensity (SWI) specification will give software teams a consistent, comparable way to measure, report, and reduce that impact.
What is SWI?
The Software Water Intensity (SWI) specification is a new standard being developed by the Green Software Foundation to measure the water footprint of software systems. Modelled on the proven SCI approach — a rate relative to the useful work performed — SWI will give developers and organisations a clear, comparable number that captures how much water their software consumes. Reducing an SWI score will only be possible through actions that genuinely reduce water consumption.
Software's Hidden Water Footprint
Data centres contribute to water consumption in multiple ways: directly through evaporative cooling systems that wick heat off servers by turning water to vapour, indirectly through the electricity they draw — since power generation itself often consumes water — and through the semiconductor fabrication process used to manufacture compute hardware. As AI workloads grow and data centres expand, sometimes into regions already facing water scarcity, software's water footprint has become a material environmental impact. Yet the software industry has had no consistent, shared way to measure it — until now.
Why Water Matters Now
Think back to where carbon was just a few years ago. When the Green Software Foundation began work on the Software Carbon Intensity (SCI) specification, software's carbon footprint was barely on the radar — poorly understood, inconsistently measured, and rarely discussed in engineering teams. Today SCI is ratified as ISO/IEC 21031:2024 and used across the industry to make carbon comparable, reportable, and improvable. For software, water is at a similar stage — material in impact, but fragmented in measurement. Regulations and disclosure requirements around water are tightening across many regions. As data centre operators begin publishing water data, the industry needs a standardised way to make sense of it. The teams that help shape SWI now will help decide what the standard looks like.
Three Sources of Water Impact
A software system's water footprint comes from three distinct sources, each requiring different measurement approaches.
Direct Cooling
Many data centres use evaporative cooling systems that consume water directly — wicking heat off servers by turning water to vapour.
Electricity Generation
The electricity that powers data centres is itself often water-intensive to generate — from hydropower to thermal cooling at power stations.
Hardware Manufacture
Semiconductor fabrication — the process used to make compute hardware — can be highly water-intensive, representing an embodied water footprint.
Our Approach
SWI is being developed within the GSF Standards Working Group, building on the approach that made SCI successful. The specification will be modelled on the SCI family of standards — a high-level specification applying to all software, with domain-specific extensions to follow for areas like AI and hardware where water consumption behaves differently.
Water consumption relative to useful work performed
Like SCI, SWI will adopt an interpretable, rate-based form — making water comparable across systems, regions, and workloads.
The substantive design decisions — such as how to account for electricity-related water and how to factor in regional water stress — are open questions for the working group to decide together. That's by design. The best standards are built collectively, with broad input, not settled in advance.
"The scale at which AI and data centers are consuming water is unprecedented — and the industry has no consistent way to measure it. Developing the Software Water Intensity specification is a direct response to that gap. I am honoured to lead this project and to work alongside exceptional researchers and industry practitioners who share the conviction that water-aware software is not only necessary, but achievable."
Get Involved
Help Shape Software Water Intensity
