When we think about digital pollution, we usually picture mountains of discarded smartphones or the electricity that keeps endless video streams flowing. But Rui Mendes, a systems thinker drawn to the invisible costs of modern infrastructure, has been looking at a different kind of environmental toll: the staggering amount of energy it takes to train a single, massive neural network from scratch. What he found is a story of resource consumption that quietly challenges our assumptions about the weightlessness of the digital world.

The numbers are out there, but they tend to hide in academic appendices or the footnotes of corporate sustainability reports. Training a single large-scale language system can emit as much carbon dioxide as five average American cars do over their entire lifetimes—including the fuel they burn and the energy used to build them. And that is not a worst-case projection; it is a measurement from models already built and running. The energy isn’t just for the final training sprint, either. It covers countless trial runs, hyperparameter tweaks, and discarded versions that never see the light of day. The real cost is the sum of all those failed attempts, not just the polished result.
Why Training Is So Much Heavier Than Running a Model
To grasp the environmental cost, you have to separate two very different phases: training and inference. Inference is what happens when you ask a question and get an answer back—it is relatively light, often handled by a single chip. Training is the process of building the model in the first place. It means pushing petabytes of data through billions of parameters, over and over, for weeks or months, using thousands of power-hungry processors running in parallel. All that computation generates tremendous heat, which then requires even more energy to remove. It is an industrial process, not a casual one.
Rui points out that the public conversation often lumps these two phases together, which makes the whole thing seem less consequential. A single query might feel ephemeral, but the model that answers it was born from a sustained, energy-intensive burn. Think of training as a one-time carbon debt. Every subsequent query slowly chips away at that debt over the model’s operational life. The uncomfortable question is whether the debt ever gets fully paid off, especially when models are frequently retrained or replaced by even larger successors.
Mapping the Energy Supply Chain
The electricity that feeds a training run does not come from a single, clean source. Its carbon intensity depends entirely on the regional grid mix at the time the computation happens. A training cluster plugged into a grid dominated by coal plants will have a dramatically higher footprint than one drawing from hydroelectric dams or nuclear reactors. Yet data center locations are usually chosen based on tax breaks, land prices, and network latency—not on how clean the local grid is.

Rui sees this as a classic systems problem: the metrics we optimize for are misaligned. A company might proudly announce that its data centers are carbon-neutral thanks to renewable energy certificates, but the physical electrons powering the GPUs still come from the local grid. If that grid is dirty, the training run causes real emissions in real time, even if the accounting looks clean on paper. The gap between when energy is consumed and when renewables are generated is a mismatch that few reports bother to address.
The Lifecycle of a Training Run
To really grasp the scale, you have to look at the physical infrastructure. A state-of-the-art training cluster can contain tens of thousands of interconnected processors. Each one is a marvel of engineering that required mining rare earth minerals, purifying silicon, and shipping components across the globe. The embodied carbon of manufacturing these chips and servers is a significant upfront cost, often comparable to the operational energy used over the hardware’s lifespan. When a new generation of chips arrives every two to three years, the churn of hardware accelerates, locking in even more embodied emissions.
Then there is the cooling. The heat generated by a training cluster is immense. Data centers use chilled water, powerful fans, and sometimes even submersion in dielectric fluids to keep temperatures in check. In arid regions, water consumption for cooling competes with local agriculture and drinking supplies. A single large training run can evaporate millions of liters of water—a hidden cost that rarely makes it into environmental assessments.
The Geography of Computation
Where a training cluster sits dictates its carbon profile. A model trained in Quebec, where electricity is almost entirely hydroelectric, will have a fraction of the emissions of an identical model trained in Virginia, where the grid still leans heavily on natural gas and coal. Yet the decision of where to place these clusters is often opaque. Cloud providers may shift workloads between regions for load balancing, making it difficult for researchers to know, let alone control, the carbon intensity of their experiments.
Rui notes that this geographic lottery creates a strange ethical landscape. A research team in one country might inadvertently produce a much dirtier model than a team in another, simply because of the default region selected in their cloud console. Some researchers have started to advocate for “carbon-aware” computing, where training jobs are scheduled to run when and where the grid is cleanest. But this requires a level of transparency and flexibility that most cloud platforms do not yet offer.
The Dataset Factor
Energy is not the only resource. The datasets used to train these networks are themselves products of energy-intensive processes. Crawling the web, storing petabytes of text and images, cleaning and deduplicating the data, and then shuttling it to the training cluster all consume electricity. The larger the dataset, the more storage and network infrastructure is needed. Some training sets are so vast that they cannot be stored in a single location, requiring distributed file systems that add their own overhead.
There is also a less visible cost: the human labor of data annotation. While not a direct carbon emission, the global supply chain of annotators, often working in conditions with their own environmental and social footprints, is part of the system. Rui’s systems-minded approach insists on seeing the full picture, from the mines that extract the metals for the servers to the offices where labeling guidelines are written.
Measuring What Matters
One of the core challenges is simply measurement. Estimating the carbon footprint of a training run requires knowing the power draw of the specific hardware, the duration of the run, the Power Usage Effectiveness (PUE) of the data center, and the carbon intensity of the grid. Some of these numbers are proprietary. Hardware manufacturers may not disclose the full energy profile of their chips. Cloud providers may not reveal real-time grid mix data. Researchers are left to make rough estimates based on public information, which can vary by an order of magnitude.

Several tools have emerged to help, such as open-source calculators that estimate emissions based on hardware type, cloud region, and runtime. But these tools rely on average grid intensities that may not reflect the actual moment-by-moment mix. A training run that spans weeks will inevitably include periods of high and low carbon intensity, but without real-time data, the true impact remains fuzzy. Rui sees this measurement gap as a fundamental barrier to accountability. Without clear numbers, it is too easy to ignore the problem.
The Efficiency Paradox
There is a common counterargument: as hardware becomes more efficient, the energy per computation drops. This is true. The number of floating-point operations per watt has improved dramatically. But the total energy consumed by training runs has not decreased; it has grown. This is Jevons paradox in action: as efficiency improves, the demand for computation increases even faster, swallowing up all the gains and then some. The ambition to build ever-larger models, with ever-more parameters, outpaces the efficiency improvements of the hardware.
Rui finds this dynamic particularly troubling because it suggests that technological progress alone will not solve the problem. Without a conscious effort to prioritize efficiency over scale, or to question whether the largest models are always necessary, the environmental cost will continue to climb. The field is caught in a Red Queen’s race, running faster and faster just to stay in the same place.
Who Bears the Cost?
The environmental burden of training is not distributed equally. The data centers that host these computations are often located in regions with lower land and energy costs, which frequently overlap with lower-income communities. These communities may experience increased air pollution from the fossil fuel power plants that feed the data centers, as well as noise pollution and water stress. Meanwhile, the economic benefits of the technology accrue largely to corporations and users in wealthier regions.
This geographic displacement of harm is a pattern that repeats across many industries, but it is particularly stark in the digital space because the product feels so intangible. A user in Stockholm streaming a video or interacting with a language model has no visible connection to the coal plant in West Virginia that might be powering the backend. Rui argues that making these connections visible is the first step toward a more honest accounting of the technology’s true cost.
Can Transparency Help?
Some organizations are pushing for greater transparency. Proposals include mandatory reporting of training energy consumption, standardized efficiency benchmarks, and “energy star” style labels for models. If a model card included not just accuracy metrics but also the total carbon emitted during training, downstream users could make more informed choices. A small, efficient model might be perfectly adequate for a task, avoiding the need to invoke a massive, energy-hungry one.
Rui is cautiously optimistic about this direction but notes that transparency alone is insufficient. It must be paired with incentives. Cloud providers could offer discounts for training in low-carbon regions or during off-peak renewable hours. Funding agencies could require environmental impact statements for large-scale training projects. The goal is not to stop progress but to bend the curve of resource consumption downward while still reaping the benefits of the technology.
Rethinking Scale
The dominant narrative in the field has been that bigger is better. More data, more parameters, more compute. But a growing body of research suggests that this is not always true. Carefully curated datasets, efficient architectures, and techniques like transfer learning can achieve comparable results with a fraction of the resources. The environmental cost of training a massive model from scratch might not be justified if a smaller, fine-tuned model can perform the same task nearly as well.
Rui sees this as a design choice, not a technical limitation. The pressure to build ever-larger models comes from a culture that equates size with progress. Shifting that culture requires new success metrics that reward efficiency and parsimony alongside raw performance. Some academic conferences now ask authors to report the computational cost of their experiments, a small step that could nudge the field toward more sustainable practices.
The Water Footprint
Beyond carbon, water consumption is an underappreciated aspect of training large models. Data centers use water for cooling, and in many regions, this water is evaporated and lost to the local watershed. A single training run can consume millions of liters, enough to fill an Olympic-sized swimming pool. In water-stressed areas like the southwestern United States, this can exacerbate local shortages. The water footprint is rarely disclosed, yet it is a critical part of the environmental equation.
Rui points out that water and energy are deeply intertwined. Thermoelectric power plants, which provide much of the world’s electricity, themselves consume vast amounts of water for cooling. So the water footprint of a training run includes both the direct water used in the data center and the indirect water used to generate the electricity. This double counting makes the true impact even harder to measure but no less real.
FAQ
Why does training a large model consume so much energy?
Training involves repeatedly processing enormous datasets through networks with billions of parameters, requiring thousands of specialized processors to run for weeks or months. The computation itself draws massive power, and the hardware generates heat that demands energy-intensive cooling systems. The scale of these operations, often involving entire data center halls, is what drives the high energy consumption.
Can renewable energy solve the carbon footprint problem?
Renewable energy can significantly reduce the carbon intensity of training, but it is not a complete solution. Many data centers purchase renewable energy certificates to offset their consumption, but the physical electricity they use may still come from fossil fuel plants, especially when the sun is not shining or the wind is not blowing. Additionally, the manufacturing of hardware and the construction of data centers carry their own carbon costs that renewables do not address.
What can be done to reduce the environmental impact of training?
Several strategies can help: using more efficient model architectures, training on smaller but higher-quality datasets, scheduling training jobs in regions with cleaner grids, and improving hardware efficiency. On a systemic level, greater transparency about energy consumption and carbon emissions would allow researchers and companies to make more informed decisions. Some also advocate for prioritizing the reuse of existing models over training new ones from scratch.
Is the environmental cost of training large models justified?
This depends on the application. For some critical uses, such as medical diagnosis or climate modeling, the benefits may outweigh the costs. For others, like generating entertainment content or marginally improving a chatbot, the trade-off is harder to defend. A more careful assessment of whether a large model is truly necessary for a given task could help reduce unnecessary environmental impact.