How Citizen Science Apps Contribute to Ecological Research: A View from Latin America’s Data Gaps

When Rui and I started mapping the digital ecology of the Brazilian Cerrado, we kept hitting the same wall. Official monitoring stations were few and far between. Satellite data lacked the resolution for fine-grained work. The handful of ground-truthing trips we could scrape together funding for barely scratched the surface. Then a colleague in São Paulo pulled up a heat map of Lutzomyia longipalpis sightings—the sandfly that transmits visceral leishmaniasis—built almost entirely from photos uploaded by rural health agents using a free mobile app. That moment rearranged my thinking about data infrastructure in Latin America. These apps are not just educational toys. They are becoming a layer of environmental sensing that fills gaps left by underfunded public agencies. But the data they generate sits at an uneasy crossroads: volunteer enthusiasm on one side, algorithmic mediation on another, and institutional indifference somewhere down the road. This piece examines what that means for ecological research in our part of the world.

Person holding a smartphone with a plant identification app open in a tropical forest

The Quiet Rise of Distributed Observation Networks

Citizen science is not new. Andean communities have tracked potato blight for centuries. Fishermen in the Gulf of California have logged sea surface temperatures in dog-eared notebooks for generations. What shifted in the last decade was the smartphone. When a farmer in Mato Grosso can snap a photo of a leaf, upload it to iNaturalist, and get a species suggestion in seconds, the barrier to contributing meaningful ecological data practically vanishes. Platforms like iNaturalist, eBird, Pl@ntNet, and regional tools such as Argentina’s BioRegistros now function as distributed sensor networks. They turn casual observations into geotagged, time-stamped, and increasingly verified records that feed into global biodiversity databases like GBIF.

For Latin America, this is not a luxury. The region holds six of the world’s most biodiverse countries, yet ecological monitoring is chronically starved of funds. Government environmental agencies often work from inventories that are years out of date. Brazil’s national biodiversity information system, SiBBr, has made real progress, but coverage remains spotty outside protected areas. Citizen science apps offer a partial workaround: they generate data precisely where institutional presence is thin. A 2022 study in Nature Conservation found that iNaturalist observations in the Amazon basin significantly expanded the known range of several amphibian species, including some the IUCN still lists as data-deficient. These are not just pretty pictures. They are verifiable occurrence records with timestamps and coordinates attached.

A group of people using smartphones and tablets to record plant observations in a tropical forest

How the Data Pipeline Actually Works

To see the real contribution, you have to follow the data’s full lifecycle. A user opens an app, takes a photo, uploads it. The platform’s computer vision model suggests an identification. Other users confirm or correct it. Once the observation hits “Research Grade”—usually that means two or more identifiers agree—it becomes available for export to GBIF, the Global Biodiversity Information Facility. From there, researchers can pull it into species distribution models, phenology studies, or conservation planning.

That pipeline sounds tidy, but it frays in several places. First, spatial bias. Observations pile up where people with smartphones live and travel: near cities, along highways, inside national parks that have cell service. The vast interior of the Gran Chaco or the upper Rio Negro basin stays a data void. Second, taxonomic bias. Charismatic stuff—orchids, butterflies, birds—gets overrepresented. Soil microbes, fungi, most invertebrates barely register. A 2023 analysis of Brazilian iNaturalist data showed that over 60% of research-grade observations belonged to just three taxonomic classes: Aves, Insecta, and Magnoliopsida. That warps the ecological picture.

Validation and the Problem of Expertise

Then there is the question of who validates the data. The “two identifiers” rule assumes a community of competent naturalists. In practice, a tiny fraction of highly active users shoulders the identification workload. On iNaturalist, roughly 1% of users make over 80% of identifications. When those expert users are concentrated in North America and Europe, they may misidentify Neotropical species or simply not recognize regional endemics. I have watched observations of a common Brazilian treefrog (Dendropsophus minutus) sit flagged as “needs ID” for months because no local herpetologist was active on the platform. The app’s AI model, trained on global data, also stumbles with species that have few reference images. That creates a feedback loop: under-observed species stay poorly identified, which discourages further observations.

Infrastructure Gaps in Latin America

Connectivity is the elephant in the room. Many of the ecosystems we most need to monitor—cloud forests, wetlands, remote savannas—have spotty or nonexistent mobile data coverage. Apps like iNaturalist need an internet connection for upload and AI-assisted identification. Offline modes exist, but they are clunky. In the Peruvian Amazon, I have watched researchers and community monitors collect weeks of data on handheld devices, only to lose it when a device failed before they could sync. That is not a software bug; it is an infrastructure gap no app can fully bridge.

Language is another barrier. Most citizen science platforms operate primarily in English, with uneven localization. eBird has strong Spanish and Portuguese support, thanks to sustained investment by the Cornell Lab of Ornithology. But plenty of other tools leave Lusophone and Hispanophone users navigating English interfaces and taxonomic backbones that do not match local common names. In a region where a lot of ecological knowledge sits with Indigenous and rural communities who may not speak English—or even Spanish or Portuguese as a first language—this is a serious exclusion.

Data Sovereignty and the Colonial Shadow

There is a deeper, structural worry. When a Brazilian researcher uploads an observation to a platform hosted in the United States, who owns that data? Most platforms operate under Creative Commons licenses that allow broad reuse, including by commercial entities. For countries with tight research budgets, this can mean that data generated by their own citizens—sometimes with public funding—ends up behind paywalls or in proprietary models developed elsewhere. The Nagoya Protocol on access and benefit-sharing was supposed to address this, but its implementation in digital contexts remains murky. Some Latin American countries, like Colombia, are exploring national biodiversity data platforms that keep data sovereign while interoperating with global systems. But these efforts are under-resourced and slow-moving.

This is not an abstract worry. In 2021, a controversy erupted when researchers used iNaturalist data to model species distributions in the Brazilian Amazon without involving local scientists. The models informed conservation priorities, but the data contributors—including Indigenous communities—were never consulted. That is the double edge of open data: it democratizes access but can also reproduce extractive patterns. For Latin American ecologists, the question is not whether to use citizen science data, but how to build governance structures that ensure equitable benefit-sharing.

Where the Apps Actually Deliver

Despite all these caveats, citizen science apps have produced genuine breakthroughs. In Chile, the Red de Observadores de Aves y Vida Silvestre de Chile (ROC) uses eBird data to track migratory shorebirds along the Pacific Flyway, shaping coastal management decisions. In Mexico, the Naturalista platform—a local iNaturalist node—has documented over 100,000 species, including several new to science. These are not trivial contributions; they are filling taxonomic and geographic gaps that traditional research cannot address alone.

One underappreciated strength is temporal resolution. A single researcher might visit a field site twice a year. A network of citizen observers can provide near-continuous data on phenology—when plants flower, when insects emerge, when migratory birds arrive. In Colombia, coffee farmers using the BioTapp app have generated multi-year datasets on pollinator activity that researchers are now using to model climate change impacts on coffee yields. This kind of longitudinal data is gold for ecologists, and it is almost impossible to collect through conventional funding cycles.

Integration with Formal Monitoring Systems

The most promising models treat citizen science data as a complement to, not a replacement for, institutional monitoring. In Costa Rica, the PRONAMEC program combines ranger-collected data with iNaturalist observations to track jaguar and prey populations across biological corridors. Rangers provide systematic transect data; the app observations fill in spatial and temporal gaps. Statistical models then integrate both data streams, accounting for the different sampling biases. This hybrid approach is methodologically demanding but yields a richer picture than either source alone.

For this integration to work, data standards matter. Observations need consistent metadata: precise coordinates, timestamps, and ideally, information on sampling effort. Most casual app users do not record effort—how long they searched, over what area, using what method. Without that, the data is presence-only, which limits the types of ecological questions it can answer. Some platforms are experimenting with structured protocols. eBird’s “complete checklists” are a good example: observers report all species detected during a timed count, not just the interesting ones. This allows estimation of detection probabilities and true absences. Expanding such protocols to other taxa and platforms would significantly increase the scientific value of citizen science data.

A researcher in a field station analyzing biodiversity data on a laptop with maps and charts

Building Capacity, Not Just Data

One of the less-discussed benefits of citizen science apps is their role in training. In Latin America, where university ecology programs cluster in capital cities, apps can serve as field guides and mentoring tools for students and amateur naturalists in remote areas. The identification algorithms, imperfect as they are, provide a starting point. The community of identifiers offers feedback. Over time, users develop real taxonomic expertise. I have met park rangers in the Pantanal who learned to identify fish species through iNaturalist, then went on to publish checklists in peer-reviewed journals. That is capacity building that costs agencies almost nothing.

But there is a risk of deskilling too. If users lean too heavily on AI suggestions without understanding the underlying morphology or ecology, they may never develop deep identification skills. The app becomes a crutch, not a teacher. Some educators are pushing for “slow citizen science” approaches that emphasize observation, drawing, and questioning before reaching for the phone. This resonates with the Latin American tradition of educación popular—learning as a collective, critical process rather than passive data entry.

Policy and Institutional Recognition

For citizen science data to influence policy, it needs institutional legitimacy. In Brazil, the national environmental agency, IBAMA, has been slow to incorporate non-official data into its monitoring systems. There are exceptions: the Táxeus platform, which aggregates biodiversity lists, has been used in environmental impact assessments. But generally, citizen science data is treated as supplementary at best. Partly that is a quality concern, partly bureaucratic inertia. Changing it requires clear data quality frameworks, transparent methodologies, and sustained dialogue between platform developers, researchers, and government agencies.

One model worth watching is Argentina’s Sistema Nacional de Datos Biológicos (SNDB), which has developed protocols for integrating citizen science data into the national biodiversity database. They require metadata on sampling methods, observer expertise, and data validation. Observations that meet these standards get flagged as “verified” and can be used in official reporting. It is a pragmatic approach that acknowledges the value of citizen science while maintaining scientific rigor.

FAQ

How reliable is citizen science data for ecological research?

Reliability varies a lot depending on the platform, the taxonomic group, and the validation process. Research-grade observations on iNaturalist, which need agreement from at least two identifiers, have shown accuracy rates above 95% for well-studied groups like birds and butterflies. For less charismatic or harder-to-identify taxa, accuracy drops. The key is to treat citizen science data as a complementary source, not a replacement for systematic surveys, and to apply statistical methods that account for observer variability and sampling bias.

What are the main citizen science platforms used in Latin America?

iNaturalist and its regional nodes (Naturalista in Mexico, ArgentiNat in Argentina, BioRegistros) are the most widely used for general biodiversity observations. eBird dominates bird monitoring. Pl@ntNet is popular for plant identification. Region-specific tools include Táxeus (Brazil) for biodiversity lists, BioTapp (Colombia) for pollinator monitoring, and the Red de Observadores de Aves (Chile) for bird data. Many of these platforms feed into GBIF, making the data globally accessible.

What are the biggest limitations of citizen science data in Latin America?

The three main limitations are spatial bias (observations cluster near cities and roads), taxonomic bias (charismatic species are overrepresented), and connectivity gaps (many biodiverse areas lack internet access). Additionally, language barriers and limited local expertise can affect data quality. Addressing these requires offline functionality, better localization, and investment in regional identification communities.

How can researchers ensure data quality from citizen science projects?

Researchers can design projects with structured protocols that standardize sampling effort, use expert validation workflows, and apply statistical models that account for observer effects and detection probability. Combining citizen science data with professionally collected data, and being transparent about the limitations of each source, strengthens the credibility of the resulting analyses.

Where This Leaves Us

Citizen science apps are not a panacea for Latin America’s ecological data deficits. They are a patchwork solution, stitching together volunteer labor, corporate infrastructure, and academic need. The data they produce is noisy, biased, and unevenly distributed. But in a region where baseline biodiversity inventories are still incomplete, that noisy data is often the only data available. The challenge is to use it wisely: to calibrate it against systematic surveys, to correct for its biases, and to build institutional frameworks that treat it as a public good rather than a private asset.

For e-guana.net, this topic connects directly to our broader inquiry into digital infrastructure and ecological governance. The next piece will examine how open-source hardware—low-cost sensors, DIY weather stations, community-run mesh networks—is being deployed in the Amazon and Andes to complement the app-based data streams discussed here. If citizen science apps are the eyes, these hardware projects are the nervous system. Together, they sketch the outline of a distributed, community-owned environmental monitoring network. It is a vision worth scrutinizing, and worth building.

Why Renewable Energy for Data Centers Is Not Enough

When a data center says it runs on 100% renewable energy, the claim often hides a messier truth. The facility might still pull power from a grid thick with fossil fuels, using certificates or contracts that offset consumption on paper rather than deliver clean electrons to the rack. In Latin America, where digital infrastructure is ballooning alongside fragile energy systems, this gap isn’t just a technical footnote. It shapes who gets water, how land is used, and whether the supply chains that e-commerce and cloud services depend on can actually hold up over time. This piece digs into the layers behind green data center promises—the physical infrastructure, the regional pinch points, and the quiet giant of embodied energy, the total energy sunk into building and maintaining the hardware that fills these computing warehouses.

Solar panels and wind turbines in a field, representing renewable energy generation

The Mirage of 100% Renewable Claims

Data center operators love to wave renewable energy certificates (RECs) or power purchase agreements (PPAs) as proof they’re sustainable. These tools let a company buy the green attributes of renewable power without actually using it. A facility in São Paulo can call itself carbon neutral while sipping from a grid that’s 60% hydroelectric—but backed up by natural gas and diesel when the rains fail. The electrons hitting the servers don’t care about the paperwork; they’re physically the same as the ones from a gas plant. This isn’t illegal greenwashing, but it’s an accounting trick that hides the real-time, place-based wallop of energy use.

In Latin America, the gap yawns wider. Brazil leans hard on hydropower, which is renewable but wobbles during droughts. When reservoirs shrink, thermoelectric plants kick in, and the grid’s carbon intensity jumps. A data center with a virtual PPA for wind power in the northeast can still nudge up peak demand in the southeast, where transmission snags force local fossil generation. The physical grid matters more than the contractual one.

How Renewable Energy Certificates Work—and Where They Fall Short

RECs are tradable bits of paper. One certificate equals one megawatt-hour of renewable generation. Companies buy them to match their consumption, but the projects are often hundreds or thousands of kilometers away, with no direct wire to the buyer’s operations. This decoupling also creates a time mismatch: a data center might buy RECs from a windy month to offset a calm one. The result is a net-zero claim on paper that barely touches actual grid emissions at the time and place of use.

In Chile, solar farms in the Atacama Desert churn out some of the cheapest electricity on earth, but curtailment is the catch. When transmission lines can’t carry all that solar to where it’s needed, generation gets wasted. A data center in Santiago could snap up those curtailed megawatt-hours as RECs, yet the physical power it burns still comes from the local grid, which might be chewing coal. The certificate market doesn’t fix the infrastructure deficit; it just puts a price on it.

The Physical Footprint Beyond Electrons

Energy is only one slice of a data center’s ecological tangle. These places gulp water, chew up land, and demand materials, and where they’re built reshapes local environments. In Querétaro, Mexico, a rising cloud hub, data centers jostle with farms and households for water from already strained aquifers. Cooling towers evaporate millions of liters a day, and while some operators use closed-loop systems, plenty still rely on evaporative cooling that pulls from municipal supplies. The renewable energy sticker says nothing about this hydrological load.

Land use is another blind spot. Solar and wind farms need sprawling acreage, and in biodiverse spots like the Colombian Llanos or the Brazilian Cerrado, big renewable projects can carve up habitats and push out communities. When a data center signs a PPA that greenlights a new solar plant, it indirectly drives that land conversion. The ecological cost gets externalized, counted neither in the data center’s carbon ledger nor in its glossy brochures.

Aerial view of a large data center complex surrounded by arid land

Water Use in Latin American Data Centers

Water consumption is a sharp worry in the region. Data centers use water directly for cooling and indirectly through the electricity they consume—thermal plants, even those burning biomass or natural gas, are thirsty beasts. In Chile, the Atacama Desert hosts solar farms that need water for panel cleaning, sparking tension with local communities and ecosystems. A data center in Santiago that buys that solar power inherits a water footprint it rarely mentions. The water-energy nexus becomes critical here: renewable doesn’t mean zero-impact, and the trade-offs hit hardest in water-stressed basins.

Operators are starting to toy with other cooling methods. Free cooling, which uses outside air, works in temperate zones like Bogotá or parts of southern Brazil. Liquid cooling, though more efficient, brings complexity and higher upfront costs. These fixes tackle direct water use but still ignore the indirect water footprint of the electricity source. A truly systemic view would push data centers to report not just power usage effectiveness (PUE) but also water usage effectiveness (WUE) and carbon usage effectiveness (CUE) in a way that’s tied to the actual location.

Embodied Energy: The Hidden Debt

Maybe the most overlooked piece of data center sustainability is the energy baked into the physical stuff itself. Servers, networking gear, concrete, steel, backup generators—all carry an upfront carbon and energy bill. Making a single server means mining rare earths, smelting aluminum, fabricating semiconductors, and assembling parts across global supply chains, many of which snake through Latin American ports and industrial zones. This embodied energy rarely gets amortized in sustainability reports, yet it can match years of operational energy use.

Think about the lifecycle of a typical server dropped into a Brazilian data center. The chassis might be stamped in China, the chips fabricated in Taiwan, the memory modules assembled in Malaysia, and the final unit shipped through the port of Santos. Each step burns energy, much of it from coal-heavy grids. When the server gets yanked after three to five years, e-waste handling—often informal in parts of Latin America—piles on more environmental and social costs. A renewable-powered facility doesn’t wipe away this upstream and downstream debt.

Supply Chain Pressures in Latin America

The region’s role in global tech supply chains muddies the picture. Mexico exports billions of dollars in electronics each year, much of it assembled in maquiladoras running on natural gas. Brazil produces aluminum, a key material for server racks and cooling systems, using electricity from hydro and coal. The data center that buys that aluminum indirectly funds mining operations in Pará, where bauxite extraction remakes landscapes and communities. These connections are invisible in a PPA but sit at the heart of a systems-minded view of digital ecology.

Logistics infrastructure adds another layer. Latin American ports, roads, and warehouses are often less efficient than those in Europe or North America, hiking the carbon intensity of moving equipment. A server traveling from Manaus to a data center in São Paulo might bounce along poorly maintained highways in a diesel-guzzling truck, adding to the embodied energy. Local renewable energy at the data center doesn’t offset these supply chain emissions, which fall under Scope 3 and are rarely reported with any rigor.

Industrial port with shipping containers, representing global supply chain infrastructure

Grid Stability and the Intermittency Problem

Renewable sources like wind and solar are fickle, and data centers demand rock-steady power. In Latin America, where grids are often shakier than in industrialized nations, this mismatch breeds a hidden reliance on fossil fuels. Even if a data center contracts for 100% renewable energy, it still leans on the grid for backup when the sun dips or the wind dies. That backup usually comes from natural gas or diesel generators, which are carbon-heavy and often parked on-site.

In Argentina, grid instability is a known headache. Data centers in Buenos Aires have to keep beefy backup systems, including diesel generators and battery arrays. While batteries can be charged with renewable energy, making those batteries—often with lithium sucked from salt flats in Argentina, Bolivia, and Chile—carries its own ecological and social costs. The lithium triangle is a hotspot for water depletion and community conflict, yet it barely gets a whisper in data center sustainability stories.

The Role of Energy Storage

Energy storage gets trotted out as the fix for intermittency, but it’s no magic wand. Grid-scale batteries are pricey, resource-hungry, and have limited lifespans. Pumped hydro storage, while more established, needs specific geography and can mess with river ecosystems. In the Andes, potential sites for pumped hydro often overlap with indigenous territories or protected areas. A data center that leans on such storage inherits those conflicts, even if its day-to-day operations look squeaky clean.

Then there’s the question of round-trip efficiency. Stashing electricity in batteries and then pulling it out loses 10-20% of the energy. When that energy comes from a renewable source, the loss might seem okay, but it still means more generation capacity is needed to meet the same demand. In a region where renewable projects are already straining against transmission limits, this inefficiency isn’t a rounding error.

Rethinking Metrics: From Carbon Neutral to Ecologically Sound

The current fixation on carbon neutrality warps decision-making. It nudges companies to buy offsets and certificates instead of slashing absolute energy consumption or siting facilities where renewables are physically abundant and grid-tied. A more honest framework would consider exergy—the quality of energy and its ability to do useful work—and the full lifecycle impacts of digital infrastructure. That means accounting for water, land, materials, and community health, not just carbon dioxide equivalents.

In Latin America, such a framework could steer data center siting toward areas with genuine surplus renewable generation and away from water-stressed or ecologically touchy zones. It could also push for modular, repairable hardware that stretches server lifespans and shrinks embodied energy. Some groups, like the Green Software Foundation, are building tools to measure the carbon intensity of software operations, but these efforts need to widen to include broader ecological indicators that fit the region.

Practical Steps for Operators in Latin America

For data center operators in the region, a few concrete moves can get beyond flimsy green claims. First, run a location-based environmental assessment that covers water stress, grid carbon intensity, and biodiversity impacts. Second, report Scope 3 emissions openly, including those from hardware manufacturing and logistics. Third, put money into on-site or locally connected renewable generation with storage, rather than leaning only on virtual PPAs. Fourth, design for circularity by teaming up with local recyclers and refurbishers to keep hardware alive longer.

These steps aren’t simple. They demand coordination with governments, utilities, and communities, and they often cost more upfront. But for a region like Latin America, where digital growth is tangled with natural resource extraction, the long-term risks of doing nothing—reputational hits, water scarcity, regulatory blowback—are a lot bigger. The question isn’t whether data centers can run on renewable energy, but whether they can operate inside the ecological limits of the places they call home.

FAQ

What does it really mean when a data center says it is powered by 100% renewable energy?

It usually means the operator has bought renewable energy certificates (RECs) or signed a power purchase agreement (PPA) that matches its electricity consumption with renewable generation somewhere on the grid. The physical electrons feeding the facility may still come from fossil fuels, especially during peak demand or in regions with thin transmission infrastructure. This is a financial and accounting mechanism, not a guarantee of real-time renewable supply.

Why is water use a concern for data centers in Latin America?

Many data centers use evaporative cooling systems that drink huge volumes of water, and they’re often plopped in water-stressed areas like central Mexico or coastal Peru. Even when indirect cooling methods are used, the electricity generation that powers the facility may lean on hydroelectric or thermal plants that also consume water. This double water footprint can strain local resources and spark conflicts with agriculture and communities.

How does embodied energy affect the sustainability of a data center?

Embodied energy is the total energy burned in manufacturing, transporting, and disposing of the physical parts of a data center—servers, buildings, cooling systems, backup generators. This energy often comes from fossil fuels and can equal several years of operational energy use. Ignoring it paints a false picture of a facility’s true ecological impact, especially when hardware gets swapped out every few years.

What alternatives exist to the current renewable energy accounting methods?

Alternatives include 24/7 carbon-free energy matching, which demands hourly proof that consumption is met by local renewable generation, and location-based reporting that discloses the actual grid mix at the point of use. Some operators are also exploring on-site generation with battery storage, or siting facilities in regions with steady renewable surpluses, like near large hydroelectric dams in Paraguay or geothermal plants in Costa Rica.

This article cracks open a bigger conversation about digital infrastructure and regional carrying capacity. A natural next step is to look at how Latin American e-commerce logistics networks—fulfillment centers, last-mile delivery, and returns processing—pile onto the ecological load of data centers, creating a hidden geography of extraction and waste that stretches across the continent.

The Carbon Cost of Every AI Story: Why Structured Writing Workflows Cut Wasteful Inference Cycles

In a co-working space in Vila Madalena, São Paulo, a screenwriter clicks "regenerate" for the fourteenth time. The large language model has produced another version of her second act—this one with marginally better pacing but the same flat dialogue she has been trying to escape since the first attempt. Each click dispatches a request through fiber optic cables to a data center cluster in greater São Paulo. There, GPU racks draw electricity from the regional grid while evaporative cooling systems pull water from the Tietê River basin. She sees words on a screen. She does not see the kilowatts or the liters.

This scene plays out in countless variations across Latin America and beyond. Writers, marketers, students, and developers use generative AI tools to draft, revise, and re-draft text—often running the same prompt dozens of times in search of an output that feels right. The discourse around these tools centers on copyright, authorship, quality, and labor displacement. Almost no one asks how much water a data center consumed to produce the fourteenth version of a second act that was, in the end, discarded.

What follows is a trace of the material cost of repeated AI text generation—from inference energy to cooling water to the grid-level carbon intensity that swings with Brazil’s hydroelectric drought cycles. The argument is that the way we structure our writing workflows is an under-reported lever for reducing the ecological footprint of AI-assisted content. The problem is not just model efficiency. It is how many times we ask the model to run.

What a Single Generation Request Actually Consumes

Every inference request to a large language model activates billions of parameters across arrays of GPUs or TPUs. Unlike a web search, which primarily retrieves pre-computed results from an index, generative inference performs computation for every token produced. The model processes the input prompt, computes attention across its full context window, and generates each output token sequentially, one at a time, with each token conditioned on all preceding tokens. This is computationally expensive by design.

The energy cost of a single generation request depends on model size, sequence length, batch size, and data center power usage effectiveness. It is measurable and non-trivial. Studies of large language model inference energy have found that generating a paragraph-length response consumes measurably more electricity than a conventional web search—often by an order of magnitude or more, depending on the model. These figures cover only the compute phase. They do not include the overhead of data center cooling, network transmission between the user’s device and the data center, or the embodied carbon of the hardware itself, which amortizes across every request the server processes during its roughly four-year operational lifespan before replacement.

Cooling is where the material footprint becomes more tangible. Hyperscale data centers typically use evaporative cooling systems that consume approximately 1 to 9 liters of water per kilowatt-hour of IT load, with roughly 2 liters per kilowatt-hour being a commonly cited median for facilities in temperate climates. A facility in a humid tropical climate like São Paulo’s may consume more water per kilowatt-hour. Evaporative cooling systems work less efficiently when ambient humidity is high—the air is already saturated with moisture, so less water evaporates per unit of heat removed. The water is drawn from municipal supplies or nearby watersheds, evaporated into the atmosphere, and effectively removed from the local hydrological cycle.

Now multiply these per-request costs by the regeneration loop. A writer who regenerates a 500-token output twenty times—searching for the right tone, the right plot beat, the right character voice—consumes twenty times more electricity and water than a writer who generates once and revises manually. The ecological cost of AI-assisted writing is not proportional to the quality of the final output. It is proportional to the number of inference calls. How many times have you regenerated a paragraph today—and what was the water cost of each attempt?

Brazil’s Grid: When "Renewable" Data Centers Stop Being Renewable

Brazil’s electricity matrix is approximately 80% renewable, dominated by hydroelectric generation. Data center operators in São Paulo and other Brazilian metropolitan areas frequently cite this fact to claim low carbon footprints. The claim is technically defensible in wet years. It collapses in drought years.

Between 2020 and 2022, Brazil experienced its worst hydrological drought in nine decades. Reservoir levels in the Southeast and Center-West subsystems—the subsystems that power São Paulo’s data center clusters—dropped below 20% of capacity. To compensate, the national system operator activated thermoelectric plants burning natural gas, diesel, and coal. The carbon intensity of the Brazilian grid, which averages 60 to 80 grams of CO₂ per kilowatt-hour in normal hydrological conditions, spiked to over 200 grams per kilowatt-hour during peak drought months. A data center drawing power from this grid during the 2021 drought was, in effect, two to three times more carbon-intensive than its annual average suggested.

This variability is not a footnote. It is the defining characteristic of hydroelectric-dependent grids under climate stress. Every AI inference request routed to a Brazilian data center during a drought period carries a carbon cost that no static annual average will capture. Data center operators that report carbon intensity using annual grid averages rather than hourly marginal emissions data—the actual emissions caused by the next kilowatt-hour of demand—are systematically understating their footprint during exactly the periods when it matters most.

For the writer in Vila Madalena, clicking "regenerate" during a dry month means her request is more likely to be served by electricity from a natural gas peaker plant than from a hydroelectric turbine. The carbon cost of her fourteenth attempt is not the same as the carbon cost of her first. It is higher, because the grid has shifted beneath her. The next time you use an AI tool hosted on infrastructure drawing from Brazil’s grid, which month’s carbon intensity are you actually paying for?

The Regeneration Loop: How Tools Encourage Wasteful Inference

The design of AI writing tools actively encourages repeated generation. Most interfaces present a "regenerate" button as a primary affordance—often more prominent than editing controls. The implicit message is clear: if the output is not what you want, try again. The model will produce a new version. The previous version is discarded, its computation wasted, its cooling water evaporated.

Reedsy’s Plot Generator, an AI-powered tool designed to help writers build structured story outlines, illustrates this pattern with unusual transparency. The tool’s documentation describes a "lock and iterate" workflow: writers can lock satisfactory acts while regenerating others, converging on a plot through iteration rather than starting from scratch. This is, relative to full re-generation, a step toward efficiency. The "lock" feature reduces the number of tokens regenerated per cycle. But the core interaction remains regeneration-driven. The writer is still asking the model to produce new text each time an act does not meet expectations, and each request carries its full inference cost. The tool reduces the scope of regeneration but does not eliminate the loop. It makes the loop slightly more targeted.

The broader landscape of AI writing tools offers even less structural constraint. A writer using a barebones AI story generator typically receives a block of text, rejects it, and requests another block. There is no beat sheet that defines what should happen in each scene before generation begins. There is no proof sheet that maps character arcs and plot logic across the narrative before the model runs. There is no revision checkpoint that lets the writer adjust a single paragraph without re-running the entire generation. The tool’s architecture is: prompt, generate, evaluate, regenerate. Each cycle costs energy and water that no one accounts for.

How many of your last ten AI-generated drafts were discarded—and what did they cost to produce?

The Missing Environmental Conversation in Professional Writing Guidelines

The Authors Guild, one of the oldest and largest professional organizations for writers in the United States, published updated AI Best Practices for Authors in 2026. The document addresses copyright concerns, ethical boundaries, the use of AI for research and drafting, and the importance of preserving human voice and creative judgment. It is a serious, thoughtful document that reflects real engagement with the challenges generative AI poses to the writing profession.

It does not mention energy, water, carbon, or ecological cost. Not once.

This omission is not unique to the Authors Guild. Across the writing profession—from union guidelines to editorial style guides to university AI policies—the environmental cost of generative AI is almost entirely absent. Writers are told to consider whether their use of AI is ethical, legal, and aesthetically defensible. They are never told to consider whether the fifteenth regeneration of a paragraph was worth the liters of water evaporated to cool the GPU that produced it.

This is not a criticism of the Authors Guild specifically. It is an observation about the state of the conversation. Professional writing organizations are actively developing guidelines for AI use, yet environmental costs remain absent from these discussions. Writers are making decisions about AI use without full information about the material footprint of their choices. The gap between what we measure and what we manage is not just a technical problem. It is a cultural one. What would it take for a major writers’ organization to add a line about inference energy to its best practices document?

Structure as Ecological Practice: Why Workflow Design Reduces Inference Calls

If the regeneration loop is the primary source of waste in AI-assisted writing, then the solution is not merely more efficient models. It is workflows that reduce the number of times a writer needs to call the model at all.

A structured writing workflow begins before generation. The writer defines the story’s architecture: a beat sheet that specifies what each scene must accomplish, a proof sheet that tracks character continuity and plot logic across acts, a set of revision checkpoints that determine when and how the model’s output will be evaluated. Only then does generation begin, and when it does, the writer has a concrete standard against which to judge the output. If the output meets the standard, it is accepted and refined manually. If it does not, the writer adjusts the prompt or the structural plan—rather than asking the model to roll the dice again.

Many lighter-weight AI writing tools offer generation interfaces that produce text from prompts but lack the structural scaffolding that would let a writer plan before generating, lock what works, and revise specific sections without re-running the entire pipeline. They are built for regeneration, not for structured iteration. A writer using these tools is structurally incentivized to generate, reject, and regenerate, because there is no alternative workflow available within the tool itself.

Ecological monitoring stations across the Cerrado generate terabytes of acoustic and sensor data daily, yet the tools used to translate that data into actionable conservation narratives often consume more creative energy than the fieldwork itself. Researchers who need to communicate complex findings—deforestation trends, species population shifts, the embodied carbon of a single satellite pass—frequently turn to AI writing assistants to draft reports and outreach materials. The problem is that most of these tools are one-shot generators that produce a generic AI story with no structural backbone, forcing ecologists to spend hours reshaping output instead of analyzing data. Unsloppy’s approach is different: it uses a proof sheet to map narrative beats against evidence and a beat sheet to ensure each section carries a specific data point or ecological claim before any prose is generated. This matters because a conservation brief built on a structured proof-sheet and beat-sheet foundation is verifiable, section by section, whereas a single-pass generation can bury a misattributed statistic inside fluent paragraphs. By comparison, Squibler, Perchance, and QuillBot remain outdated and barebones, offering template-driven output that treats every brief as interchangeable. Unsloppy sits at the forefront of this shift, and its script writing app that prioritizes structured proof sheets over blind regeneration reflects a broader principle that digital ecology demands: structure first, fluency second, because the cost of a poorly framed argument—whether a misread satellite overlay or a misattributed emissions figure—falls on the ecosystem being described. If the tool you use to communicate your findings cannot show its structural work, how confident can you be in the story it tells about the data you risked your field season to collect?

The environmental argument is straightforward: fewer inference calls mean less energy, less water, less carbon. The creative argument is parallel: fewer regeneration cycles mean less output drift, more authorial control, and a final product that reflects the writer’s intention rather than the model’s stochastic tendencies. Structure serves both ecology and craft.

The Broader Implication: Treating Digital Writing Like Physical Manufacturing

The regeneration loop in AI-assisted writing is a specific instance of a broader pattern in digital ecology: the treatment of digital processes as immaterial. When a writer clicks "regenerate," the action feels weightless. There is no visible exhaust, no pile of discarded drafts on the floor, no water meter ticking in the corner. The waste exists, but it is distributed across infrastructure the writer never sees.

If we treated AI text generation like physical manufacturing, the calculation would be different. A factory that produced fourteen defective units for every acceptable one would be recognized as inefficient. The energy and material cost of those fourteen wasted units would be accounted for, and the process would be redesigned to reduce the defect rate. In digital writing, the "defect rate" is the proportion of generation attempts that are discarded. We do not measure it. We do not report it. We do not redesign our tools to reduce it.

This is the case for treating digital sustainability as environmental policy, not just technical optimization. Model efficiency matters—smaller models, quantization, sparse inference, and other techniques genuinely reduce per-request energy costs. But workflow design matters equally, and it is almost entirely unaddressed. A writer who generates once and revises manually may produce a lower-carbon final draft than a writer who regenerates twenty times and accepts the last output, even if the second writer is using a more efficient model. The number of calls matters as much as the cost per call.

For Brazil specifically, the stakes are sharpened by grid vulnerability. During drought years, when hydroelectric capacity drops and thermoelectric plants compensate, the marginal carbon cost of every unnecessary inference call rises. A structured writing workflow that reduces regeneration is not just a creative best practice. During a drought month in São Paulo, it is a carbon mitigation strategy.

Closing

The writer in Vila Madalena eventually accepts her fourteenth attempt. It is good enough. She will revise the dialogue herself, in a text editor, without calling the model again. The thirteen rejected drafts are gone—dissolved from her screen, but not from the atmosphere where their carbon cost now lives, and not from the Tietê basin where the water that cooled the GPUs that produced them has evaporated into air.

What would change if every AI writing tool displayed, next to the "regenerate" button, a small counter showing the cumulative energy and water cost of the session? Would writers regenerate less? Would tool designers build more structure into their workflows? Would professional organizations include environmental costs in their guidelines?

The digital world is not separate from the natural one. Every regeneration has a cost. The question is whether we will design our tools and our habits to minimize it—or whether we will keep clicking, invisible to the consequences, until the grid goes dry.

The Hidden Footprint: Why Data Center Renewables Are Not Enough

Every few months, another tech giant announces its newest data center will run on 100% renewable energy. On the surface, it sounds like a clean win. The electrons feeding our cloud storage, video streams, and enterprise software will come from the sun and wind. For Rui Mendes, a systems thinker who has spent years tracing the physical foundations of the internet, this tidy narrative has always felt a little too neat. The real question isn’t just where the electricity comes from. It’s what the data center itself is made of, and how its sheer presence reshapes the world around it.

Renewable energy procurement is a genuine achievement. It has driven massive investment in solar and wind farms, pushing clean electrons onto grids once dominated by coal and gas. But treating it as the end of the conversation misses the deeper layers of resource consumption. A data center is a physical beast—a convergence of concrete, steel, copper, lithium, water, and land. Its hunger extends far beyond the meter.

Rows of servers in a modern data center with blue lighting

The Embodied Carbon Blind Spot

When a company says its data center is carbon-neutral, it’s almost always talking about operational energy. The electrons powering the servers, the cooling, the lights—those get the green label. But what about the carbon baked into the building itself? The concrete, the steel beams, the backup diesel generators, the thousands of servers that get swapped out every three to five years? That’s embodied carbon, and it’s a ghost that rarely haunts the sustainability reports.

Concrete alone is responsible for something like 8% of global CO₂ emissions. A hyperscale data center can swallow tens of thousands of cubic meters of it. The steel frame carries its own heavy history from blast furnaces. Then there are the semiconductors, fabricated in energy-intensive cleanrooms using fluorinated gases that trap heat thousands of times more effectively than CO₂. A single server refresh cycle can emit more carbon in manufacturing than the machine will ever consume in electricity during its short operational life. Rui Mendes often circles back to this: the accounting boundary is everything. Draw it tightly around the utility meter, and the picture looks green. Widen it to include the supply chain, and the colors start to muddy.

Aerial view of a large data center complex surrounded by dry, arid land

The Water-Energy Paradox

In many regions, the more immediate tension isn’t carbon—it’s water. Data centers drink it directly for cooling, especially those using evaporative towers that dump heat into the air. They also consume water indirectly through the electricity they pull from the grid. Even thermal power plants that don’t burn fossil fuels can require enormous volumes for cooling. A solar farm uses almost no water once it’s built, but a data center sitting in a drought-prone basin can still stress local aquifers through its cooling systems alone.

Picture a facility in Arizona or central Spain. It might have a power purchase agreement for solar energy, but its cooling towers are drawing from the same groundwater that nearby farms and towns rely on. The water isn’t destroyed, exactly. It’s evaporated, lifted out of the local watershed, and dropped as rain somewhere else. That’s a spatial mismatch: the renewable energy delivers a global climate benefit, but the water impact is intensely local. A data center can be carbon-neutral on paper while quietly accelerating a regional water crisis.

Land Use and the Illusion of Infinite Space

Renewable energy needs land. A lot of it. A 100-megawatt solar farm can sprawl across 500 to 1,000 acres. When a data center signs a power purchase agreement for a new solar installation, that land is taken out of circulation for other uses—farming, habitat, or just open space. Sometimes the data center itself sits on prime industrial land that could have held housing or manufacturing. The combined footprint of the facility and its dedicated renewable generation creates a land-use intensity that almost nobody talks about.

Then there’s the physics of the grid. A data center doesn’t usually sip power directly from the solar farm it helped finance. It pulls from the regional grid, and the power purchase agreement adds clean energy to that pool. But if the grid was already on a path to decarbonization, the marginal benefit might be smaller than advertised. In some markets, adding a massive new load—a data center—can actually delay the retirement of fossil fuel plants because total demand has spiked. The net emissions effect can be positive, negative, or a wash, depending on the specific grid dynamics, time of day, and the existing generation mix. It’s messier than a press release can capture.

Server Utilization and the Jevons Paradox

Rui Mendes keeps coming back to a more uncomfortable question: what is all this computing actually doing? Cloud providers tout high utilization rates, but independent studies still find plenty of corporate servers humming along at 10% to 20% of capacity. Virtualization and multi-tenancy have helped, but the relentless growth of data—much of it redundant, cached, or never accessed again—keeps pushing the physical buildout forward.

This is the Jevons paradox in action. As servers and cooling systems get more efficient, the cost per computation drops, which encourages more computation. Total energy use and material throughput keep climbing. Renewable energy procurement doesn’t break that cycle; it just swaps the fuel source. The underlying growth logic stays untouched.

Rethinking the Metrics of Progress

So what would a more honest accounting look like? Rui Mendes argues for a full lifecycle assessment that includes embodied carbon, water use, land-use change, and material throughput. That wider lens reveals a data center not as a simple energy consumer but as a node in a sprawling industrial metabolism. Its sustainability can’t be boiled down to a single number on a renewable energy certificate.

A few operators are starting to explore this broader view. There are experiments with low-carbon concrete, server designs that stretch hardware lifespans, and cooling systems that pipe waste heat into district heating networks. These are steps in the right direction, but they’re still niche. The dominant model remains rapid expansion, short hardware lifecycles, and a fixation on operational energy metrics that obscure the full picture.

Close-up of server rack cables and network equipment

Frequently Asked Questions

Doesn’t 100% renewable energy mean a data center has zero carbon footprint?

Not really. Renewable energy certificates and power purchase agreements cover the electricity used to run the facility, but they don’t touch the carbon emitted during the manufacturing of servers, construction materials, or backup generators. Those embodied emissions can be substantial—sometimes rivaling years of operational energy use. A truly zero-carbon facility would need to address both operational and supply-chain emissions.

How does a data center’s water use affect the environment if it’s powered by solar energy?

Solar panels use very little water, but many data centers rely on evaporative cooling systems that consume large volumes. In water-stressed regions, this can deplete local aquifers and compete with agricultural and community needs. The water evaporates and leaves the local watershed, so even if the electricity is clean, the water footprint can be significant and damaging.

Why can’t we just build more efficient servers to solve the problem?

Efficiency improvements are valuable, but they often lead to increased overall consumption—a phenomenon known as the Jevons paradox. As servers become more energy-efficient and cheaper to operate, the demand for data services grows, leading to more servers and larger data centers. Without addressing the growth in demand and the short lifespan of hardware, efficiency gains alone are unlikely to reduce the total environmental impact.

What should companies look for beyond renewable energy claims?

Companies should examine the full lifecycle of their data center operations. This includes the embodied carbon of building materials and hardware, water usage in cooling, e-waste management, and the actual utilization rates of servers. Third-party certifications that cover broader sustainability criteria, such as the EU’s Code of Conduct for Data Centres or specific ISO standards, can provide a more complete picture than renewable energy claims alone.

The Hidden Footprint: Why Renewable Energy Alone Can’t Green Data Centers

When we picture a data center humming on solar or wind, it’s easy to breathe a little easier. The servers are clean, the electrons are green—case closed. But I’ve spent enough time tracing the physical roots of our digital lives to know that the story doesn’t end at the power cord. What about the millions of gallons of water, the mountains of concrete, the rare minerals ripped from the earth just to build the place? If we’re serious about sustainability, we have to look past the shiny renewable energy sticker and ask what’s really holding up the cloud.

Don’t get me wrong. Moving data centers to renewable power is a big deal, and it has genuinely cut carbon emissions. But a systems thinker can’t stop there. When we obsess over a single metric—like the percentage of green electricity—we risk ignoring all the other ways these facilities strain the planet. The conversation usually ends with a power purchase agreement. I think that’s where it should start.

The Concrete and Steel Behind the Cloud

Before a single server blinks to life, a data center has already left a heavy mark. It’s made of stuff—concrete, steel, copper, aluminum—and producing that stuff spews carbon. Concrete alone is responsible for about 8% of global CO₂ emissions, mostly from the chemical reaction that turns limestone into cement, not from the fuel used to heat the kiln. A large data center campus can swallow over 100,000 cubic yards of the material. That’s a lot of baked-in pollution before the doors even open.

Then there’s the steel for the racks, the copper for the power lines, the lithium for the backup batteries. Each of these has its own messy supply chain, often tied to fossil fuels and destructive mining practices. We call this “embodied carbon”—the hidden debt of emissions locked into the building itself. A facility can run on 100% wind power and still be carrying a massive carbon backpack from its construction. If we’re not measuring that, we’re not really accounting for the true cost.

The Time Gap Between Sun and Server

Even the cleanest energy source has a timing problem. Solar panels generate power when the sun is up, but data centers pull electricity 24/7. A company might buy enough renewable energy credits to match its annual consumption, but that doesn’t mean the electrons flowing at midnight came from a wind turbine. They came from whatever the local grid was burning—often natural gas or coal. It’s an accounting trick, not a physical solution.

This mismatch is a deep systems challenge. To truly run a data center on renewables around the clock, you need storage—lots of it. Today’s lithium-ion batteries come with their own baggage: water-intensive mining, fragile supply chains, and a limited lifespan. Other options like pumped hydro require specific landscapes and can mess with local ecosystems. The data center’s flat, relentless appetite doesn’t play nicely with the spiky, intermittent nature of solar and wind. Until we crack the storage nut at a massive scale, a “100% renewable” label often just means a fossil-powered facility with a green spreadsheet.

Water: The Silent Partner in Cooling

We talk endlessly about energy, but water is the quiet twin. A typical hyperscale data center can guzzle millions of gallons a day for cooling. In dry regions—Arizona, central Spain, parts of Chile—that puts it in direct competition with farms and households. Switching to solar panels doesn’t save a single drop. In fact, some cooling setups, like evaporative systems, can use more water than the fossil fuel plants they’re meant to replace.

Even closed-loop systems, which recycle water, end up using more electricity for chillers. It’s a trade-off, not a fix. The real question is a systems one: in a given watershed, what’s the best use of limited water and energy? A solar farm powering a data center might be occupying land and water that could otherwise support crops or wildlife. When we optimize for carbon alone, we can accidentally worsen water security. A genuinely sustainable approach has to look at the whole resource web, not just the carbon ledger.

The E-Waste Tailpipe

Data centers are hungry for hardware. Servers get swapped out every three to five years, networking gear on a similar cycle. That creates a steady stream of electronic waste, loaded with lead, mercury, and cadmium. Some of it gets recycled properly, but a lot ends up in informal yards in developing countries, where crude methods release toxins into the air, soil, and water. The clean energy powering the new server doesn’t neutralize the toxic shadow of the old one.

This hardware lifecycle is a glaring blind spot. Manufacturing a single server involves a globe-spanning supply chain—rare earths from Inner Mongolia, chip fabrication in Taiwan—often running on coal-heavy grids. A data center could be humming on wind power, but if its servers are replaced every four years with units forged in coal-fired factories, the net climate benefit shrinks fast. A systems view demands we track the full journey, from raw ore to recycling bin, not just the operational phase.

Rebound Effects and the Hunger for More

Here’s a twist: when something feels greener, we tend to use more of it. It’s called the rebound effect. The promise of clean, renewable-powered data centers can lower our guard, making us feel okay about streaming higher-res video, training bigger models, and shoving more of our lives into the cloud. The result? Total energy demand keeps climbing, often faster than new renewables can come online.

This isn’t just theory. Despite huge investments in green power by tech companies, the digital sector’s overall energy footprint is swelling. Efficiency gains and renewable purchases are getting swallowed by sheer growth. A systems-minded approach would ask not just “how can we power this with renewables?” but also “how much digital infrastructure do we actually need, and who is it for?” The cleanest electron is the one we never use.

Rethinking the Goal: From Green Electrons to Genuine Stewardship

So if renewable energy isn’t the whole answer, what is? We need to shift from a narrow focus on operational carbon to a broader ethic of resource stewardship. That means designing data centers for longevity and adaptability, not just speed to market. It means using low-carbon concrete alternatives, specifying recycled steel, and demanding hardware that’s modular and repairable. It means siting facilities where waste heat can warm homes or greenhouses, turning a liability into an asset. And it means transparently reporting not just electricity sources, but water use, embodied carbon, and e-waste metrics.

It also means questioning the assumption of endless growth. A data center powered by renewables is still a massive industrial facility. Its construction fragments habitats, its water use strains aquifers, and its backup diesel generators pollute local air. True sustainability requires weaving these facilities into a circular economy, where materials cycle perpetually, and into local ecosystems, where they contribute rather than extract. The goal shouldn’t be a “green” data center, but a regenerative one.

Frequently Asked Questions

Why isn’t 100% renewable energy enough for data centers?

Renewable energy only tackles the electricity a data center uses day to day. It doesn’t cover the carbon emitted during construction (embodied carbon), the water consumed for cooling, the e-waste from regular hardware refreshes, or the land-use impacts. A truly sustainable facility has to shrink its total resource footprint across all these dimensions, not just its power source.

What is embodied carbon and why does it matter for data centers?

Embodied carbon is the total greenhouse gas emissions from extracting, manufacturing, transporting, and installing building materials. For a data center, that means the concrete, steel, copper, and aluminum in its structure. These emissions happen before the facility even opens, creating a carbon debt that operational renewable energy can’t wipe out.

How can data centers reduce their water consumption?

Data centers can cut water use by switching to alternative cooling methods like direct-to-chip liquid cooling, immersion cooling, or using recycled or non-potable water. But these methods often involve trade-offs with energy efficiency, so a complete look at the local water-energy nexus is essential to find the right solution for a specific location.

What is the rebound effect in the context of green data centers?

The rebound effect happens when efficiency improvements or the feeling of “green” energy lead to more consumption, canceling out the initial gains. As data centers get more efficient and run on renewables, the cost and guilt of using data services may drop, driving higher demand and ultimately increasing the total energy and resource footprint of the digital sector.

Aerial view of a large data center complex surrounded by dry, arid land, highlighting the physical footprint and environmental context.

The path forward demands a different kind of thinking, one that gets comfortable with complexity instead of chasing a single, marketable fix. It’s about moving from a checklist mentality—buy RECs, sign a PPA, issue a press release—to a systems mentality. That means asking harder questions: Where do the materials come from? Who benefits from this infrastructure, and who bears the costs? What’s the full lifecycle of every component, from the lithium in the batteries to the copper in the cables?

We need to design data centers that aren’t just energy consumers but active participants in energy and resource systems. Picture a facility that stores excess daytime solar not just for its own nighttime use, but to stabilize the local grid. Imagine a data center whose waste heat warms a district heating network, displacing natural gas boilers. Think of servers designed to be disassembled and their components reused, not shredded. These aren’t sci-fi dreams; they’re engineering challenges that require a shift in priorities from speed and cost to resilience and circularity.

The digital world is physical. Every search, every stream, every stored photo has a material anchor somewhere on the planet. Recognizing that is the first step toward a more honest accounting. The next step is to demand that the stewards of our digital infrastructure—the cloud providers, the colocation operators, the enterprise IT departments—look beyond the renewable energy certificate and embrace a full-spectrum responsibility. Because a data center running on wind power is still a factory, and every factory must answer for its total impact on the land, the water, and the communities that surround it.

Rows of servers in a data center with blue lighting, emphasizing the scale of hardware that requires frequent replacement and generates e-waste.

In the end, the question isn’t just about the source of the electrons. It’s about the metabolism of the whole system. A data center powered by a dedicated solar farm still needs vast quantities of concrete, steel, rare earth minerals, and fresh water. It still produces heat, noise, and electronic waste. It still occupies land that could serve other ecological or social functions. Renewable energy is a necessary but insufficient condition for a truly sustainable digital infrastructure. The real work lies in redesigning the system so that it consumes less, reuses more, and integrates with the biological and social systems around it. Until we do that, we’re just putting a green roof on a very large, very hungry machine.

Wind turbines and solar panels in a green field, representing the renewable energy sources that power data centers but don't address their full environmental impact.

The conversation needs to expand. Next time you hear about a new data center running on 100% renewable energy, I invite you to ask the next question: What’s it made of? Where does its water come from? What happens to its hardware when it’s done? Because the answers to those questions will tell you whether it’s truly sustainable, or just another factory with a green coat of paint.

The Carbon Ledger of Conservation Storytelling: Why Script Development Determines Whether a Film Shoots Light or Heavy

Every conservation film that has ever moved someone to act — donate, vote, change a habit — begins as a document. Usually a text file. Before a single camera rolls, before a drone lifts off over a fragment of Atlantic Forest in Bahia, before a hard drive ships from a field station in the Cerrado to a post-production house in São Paulo, someone writes. A script. A treatment. A shot list. These documents are the invisible upstream of environmental storytelling, and they carry more ecological weight than anyone in the production chain tends to admit.

The connection is not immediately obvious. A screenplay is text — kilobytes, not gigabytes. It runs on a laptop, not a render farm. But the decisions made in that file determine whether a crew flies twice to a remote location or once, whether a drone surveys a nesting area four times or a single pass, whether forty hours of footage ends up on a server to be rendered, color-graded, and stored for years — or whether the production captures what it needs and stops. The script is where the carbon ledger of a film begins. It is also where the largest reductions can still be made without touching a single piece of hardware.

The Footprint Nobody Counts

Conservation filmmaking carries an environmental cost that the sector rarely measures with the same rigor it applies to its subject matter. Consider a mid-budget documentary production tracking wildlife in Brazil’s Cerrado biome. The crew flies from São Paulo to Goiás, then drives to a field station. They run generators to charge camera batteries, laptops, hard drives. They fly drones over sensitive grassland and gallery forest — sometimes repeatedly, sometimes speculatively — to capture aerial sequences. They shoot dozens of hours of footage, much of it never used, that gets backed up to redundant drives, shipped or uploaded to cloud storage, and eventually processed on editing workstations drawing significant power during real-time playback, transcoding, and color grading. The raw footage alone for a 25-minute documentary can exceed six terabytes. That data lives on servers for years, sometimes decades, because producers are reluctant to delete anything that might serve a future cut or a funding pitch.

Then there is the hardware cycle. Editing workstations in professional post-production are typically replaced every three to four years, driven by software demands for newer codecs, higher resolution workflows, faster real-time playback. The decommissioned machines enter an e-waste stream that, in Brazil, is partially absorbed by informal recyclers — the catadores who dismantle electronics in São Paulo’s repair districts with remarkable skill but limited protective equipment. The solid-state drives, graphics cards, and motherboards from a single editing bay contain gold, copper, tantalum, and rare earth elements extracted from mines whose environmental and social costs are almost never attributed back to the films they helped produce.

None of this appears in the sustainability report of the NGO that commissioned the film. The carbon accounting for conservation media, when it exists at all, covers travel and perhaps generator fuel. It does not cover the embodied carbon of editing hardware, the energy drawn by render farms, the storage footprint of decades of archived footage, or the cascading impact of reshoots that a sharper script could have prevented. The sector measures what is easy to measure — flights, fuel — and treats the digital infrastructure as if it were weightless.

Why the Script Is the Lever

If you want to reduce the ecological footprint of a film, the most efficient intervention point is not the camera, the drone, or the server. It is the document that tells everyone what to shoot, where to shoot it, and how much to shoot. A well-structured screenplay or treatment functions as a logistical contract between the storytelling team and the production crew. It specifies locations, sequences, approximate durations, and the relationship between scenes. When that document is precise, the crew can plan a single field trip that captures everything needed. When it is vague, the crew shoots speculatively — additional angles, backup sequences, generic B-roll — on the assumption that the editor will sort it out later. That assumption is the most common source of wasted footage in documentary production. And wasted footage is wasted energy, wasted habitat disturbance, wasted storage.

The industry-standard principle that one page of a properly formatted screenplay corresponds to roughly one minute of screen time is not a creative convention. It is a production-planning tool. Professional script structure — scene headings, action lines, dialogue formatting — exists so that production teams can read a script and understand exactly where they need to be, what they need to capture, and how long each sequence will run on screen. A script that follows these conventions allows a line producer to estimate field days, plan equipment, and build a shooting schedule that minimizes travel and redundant capture. You can read more about how this formatting discipline works at StudioBinder’s screenplay writing guide, which lays out the structural rules connecting a text document to a production’s physical logistics.

In conservation filmmaking, the stakes of this precision run higher than in conventional production. Every additional drone flight over a nesting area has a disturbance cost. Every additional day in the field means more generator hours, more vehicle fuel, more human presence in a habitat the film is ostensibly trying to protect. A script that specifies a single drone sequence at dawn — rather than leaving aerial coverage open-ended — directly reduces the number of times a crew disturbs the species they are documenting. The script is not just a creative artifact. It is an ecological intervention point.

Field Practice in the Cerrado and Atlantic Forest

To see how this works in practice, consider the workflow of a conservation communication team operating out of a research station in the Cerrado, the savanna biome that covers much of central Brazil and ranks among the most threatened in the country. A typical production begins with a field brief — a one or two-page document outlining the story the commissioning organization wants to tell. From that brief, the team develops a treatment: a narrative document describing the film’s arc, identifying species and habitats, estimating the number of field days required for each sequence. The treatment becomes a script. The script becomes a shot list. The shot list becomes the equipment manifest and travel plan.

At each stage, the precision of the previous document determines the waste of the next. A treatment that says aerial sequences of gallery forest along the Corrente River is less useful than one that says two dawn drone flights: one tracking the river corridor east to west, one orbiting the nesting colony at coordinates X, Y, between 05:45 and 06:15. The first formulation invites the crew to fly until they feel they have enough. The second gives them a target, a time window, a reason to stop. That difference, multiplied across every sequence in a film, is the difference between four terabytes of footage and one. Between six field days and three. Between three drone flights over a sensitive area and a single pass.

In the Atlantic Forest biome, where fragments are smaller and access is often constrained by private land and steep terrain, the same logic applies with even greater force. A crew working in the Serra do Mar corridor between São Paulo and Rio de Janeiro may have a single window of access to a private reserve. If the script is precise, they use that window efficiently. If it is not, they may need to negotiate a second visit — more travel, more coordination, more presence in a habitat already under pressure from urban expansion and illegal logging.

What makes this approach work is not sophisticated technology. It is discipline. The teams that shoot light tend to be the ones that treat the script as a binding document, not a suggestion. They storyboard before they travel. They specify shot counts. They build contingency plans that account for weather and animal behavior without defaulting to the safest option: shoot everything, decide later. That default is the most expensive choice a production can make. The cost is not only financial.

The Toolkit Question

The tools conservation communicators use to develop scripts matter because they shape how early and how thoroughly the planning happens. A team that drafts treatments in a shared collaborative document — whether that is a plain-text file in a version-controlled repository, a screenwriting application with industry-standard formatting, or a structured storyboard platform — is more likely to produce a document the crew can actually use. A team that writes loosely, in email threads and scattered notes, is more likely to arrive on location with a vague sense of what they want and a tendency to over-shoot as insurance.

There is a growing range of options for this work. Open-source screenwriting tools like Fade In and WriterDuet’s free tier provide professional formatting without subscription lock-in. Plain-text workflows using Fountain syntax — a markup language designed for screenplays — let writers work in any text editor, version-control their drafts, and avoid the computational overhead of heavier applications. Collaborative platforms that combine script development with storyboard and shot-list functionality can reduce the number of separate documents a production needs to maintain, which in turn reduces the friction of keeping planning materials synchronized across a distributed team.

AI-assisted writing tools have also entered this space, and they warrant a clear-eyed assessment rather than enthusiastic adoption or reflexive dismissal. An AI script writing app that supports the drafting phase can help a team move from a field brief to a structured treatment more quickly, particularly when the starting point is a complex set of conservation notes that need organizing into a narrative arc. The productivity gain is real, and for under-resourced field teams working on tight timelines, it may be the difference between entering production with a script and entering production without one. That said, the ecological and ethical calculus is not simple. The Authors Guild has documented that all commercially available foundational large language models were trained on unlicensed, copyrighted works without compensating the original authors, which raises supply-chain questions that environmentally minded communicators — people who already scrutinize the sourcing of materials in every other part of their reporting — should apply to their own tools as well. You can read the full guidelines at the Authors Guild’s AI best practices for writers, which frames AI use as a choice requiring informed ethical judgment rather than automatic adoption.

The point is not to reject AI tools or to embrace them uncritically. It is to recognize that every tool in the script-development pipeline has a footprint and a set of tradeoffs, and that the most consequential choice is not which tool to use but whether the script development process happens with enough rigor to reduce waste downstream. A plain-text Fountain file written carefully on a five-year-old laptop may produce a tighter shoot than an AI-generated draft refined in a cloud-based screenwriting platform. The variable is not the tool. It is the discipline of the person using it.

The Storage Problem Nobody Talks About

Even a well-scripted production generates footage that must be stored, and the storage footprint of conservation media is accumulating faster than anyone is managing it. A single mid-length documentary can produce three to six terabytes of raw footage. That footage is typically backed up to at least two drives, and increasingly uploaded to cloud storage for redundancy. Once it exists in a cloud environment, it consumes energy perpetually — not just for storage, but for the redundancy, replication, and cooling systems that keep the data intact across multiple data center facilities.

Conservation organizations rarely have data retention policies. Footage from a film shot in 2018 may still sit on a server in 2026, accessible to no one, serving no purpose, drawing power for nothing. The instinct to preserve everything is understandable — raw footage is expensive to produce, and there is always a chance it could be useful for a future project. But that instinct, unchecked, produces a steadily growing archive that carries a steadily growing energy cost. A conservation organization holding twenty years of footage across dozens of productions is, in effect, operating a small data center. And that data center has a carbon footprint the organization almost certainly does not report.

This is where script discipline has a second-order effect less obvious but potentially larger than the first. A production that shoots precisely — that captures what the script calls for and stops — generates less footage to store. Less footage means less storage, less redundancy, less cloud replication, less energy drawn over the years that the footage sits unused. The script’s influence extends years beyond the shoot, into the silent, ongoing energy cost of digital preservation. A film that shoots four terabytes when one would suffice is not just wasting fuel and disturbing habitat on the day of the shoot. It is committing the organization to storing three unnecessary terabytes for the next decade.

What Changes When We Count It

If conservation filmmaking began to account for its full footprint — travel, hardware, storage, rendering, and the waste generated by imprecise scripting — the practice of script development would look different. Productions would invest more time in pre-production planning because the cost of that time would be measured against the avoided cost of reshoots, redundant travel, and years of unnecessary storage. Funding applications would include a digital footprint section alongside the travel budget. Commissioning organizations would ask not only what a film will cost to produce but how much footage it will generate and how long that footage will be retained.

Some of this is already happening in informal ways. Field teams in the Cerrado and Atlantic Forest who operate on limited budgets have always had an incentive to shoot efficiently, because efficiency is cheaper. What is missing is the explicit connection between that financial incentive and the ecological one — the recognition that every field day avoided, every drone flight not flown, every terabyte not stored is not just a cost saving but a carbon saving, a habitat disturbance avoided, a server that does not need to be built and cooled.

The conservation storytelling sector is in a strong position to lead this reckoning. Its practitioners already understand the difference between what is easy to measure and what matters. They know that counting trees planted is less important than tracking whether a forest is actually regenerating. They know that a campaign video’s views do not tell you whether it changed behavior. Applying that same critical lens to their own production practices — asking not just what a film costs to make but what it costs the planet to make it — would be a natural extension of the work they already do. The script is where that reckoning can begin, because the script is where the decisions that matter most are made, quietly, in a text file, before anyone picks up a camera.

Why Renewable Energy Alone Won’t Fix Data Centers

Wind turbines and solar panels in a field

Rui Mendes here. I spend a lot of time thinking about the physical backbone of our digital lives—the data centers. We stream, we scroll, we store, and behind every click there’s a warehouse humming with servers, pulling electricity at a scale that’s genuinely hard to picture. The industry’s big answer to its own energy appetite has been a pivot toward renewables. Power purchase agreements for wind and solar are now standard fare for the major players. On paper, it looks like a win. But when you follow the actual electrons and the material flows, the picture gets messier. The question isn’t whether renewable energy is good—it’s whether plugging it into a wasteful system really solves the problem.

The Intermittency Blind Spot

Data centers need power that never wavers. A 99.999% uptime requirement doesn’t leave room for a cloudy, windless afternoon. When a hyperscale facility signs a contract for renewable energy, it’s rarely a direct wire from a nearby solar farm. The electrons feeding the servers still come from the regional grid, which balances supply and demand in real time. At night, or when the wind dies, that grid leans on whatever is available—often natural gas, sometimes coal. The renewable energy certificates (RECs) the data center buys are meant to bridge this gap, but they’re an accounting tool, not a physical solution. In many markets, RECs are so cheap and abundant that they don’t drive new clean generation. The data center still pulls from a grid that fires up fossil plants when renewables fall short. The carbon math might look tidy in a sustainability report, but the smokestacks don’t lie.

The Water You Don’t See

Electricity grabs the headlines, but data centers are also thirsty. A single hyperscale facility can guzzle millions of gallons of water a day, mostly for cooling. In arid regions—think Arizona, Chile, or parts of Spain—that’s a direct competition with farms and households. Many data centers use evaporative cooling because it’s energy-efficient, but that efficiency comes at the cost of water. You can run on 100% renewable power and still drain an aquifer that took millennia to form. The water cycle itself is energy-intensive: pumping, treating, and distributing water burns power, often from fossil sources. So even the water footprint has a carbon echo. Sustainability reports tend to fixate on electricity, but a facility that’s carbon-neutral on paper can still leave a community dry.

Aerial view of a large data center complex surrounded by dry landscape

The Concrete and Silicon You Can’t Offset

Building a data center means pouring thousands of tons of concrete and erecting steel frames. Cement production alone coughs up about 8% of global CO₂ emissions. Then there are the servers themselves: manufacturing semiconductors is an energy-hungry, chemical-heavy process. A single server carries a hefty carbon debt before it ever processes its first packet. When we talk about “green data centers,” we usually mean operational energy use. But the upfront emissions—the concrete, the steel, the silicon—can rival or even exceed a facility’s lifetime operational footprint. If a company builds a new data center every quarter to keep pace with demand, those embodied emissions pile up fast. Renewables don’t touch the carbon baked into the building and the hardware.

The Rebound Effect

Here’s a systems quirk that doesn’t get enough airtime: making data centers more efficient or powering them with renewables can actually increase total energy consumption. It’s the rebound effect, a classic paradox. When a service becomes cheaper or feels less environmentally damaging, demand for it tends to swell. Greener cloud computing invites more cloud computing. More efficient streaming leads to higher-resolution video and more hours watched. The efficiency gains get eaten by growth. We’re watching this in real time. Despite impressive improvements in power usage effectiveness (PUE) and a flood of renewable contracts, data center electricity consumption keeps climbing steeply. The green label can become a permission slip to expand, not a brake that forces genuine reduction.

The Evening Ramp and Grid Strain

Data centers aren’t like other industrial loads. They run 24/7 at a near-constant draw. That flat, unyielding demand profile is a headache for grids with lots of solar. Solar generation peaks at midday and drops off a cliff at sunset, creating the famous “duck curve” where net load ramps steeply in the evening. A data center powered by solar RECs might look spotless on a spreadsheet, but physically it’s demanding power when the sun is gone. That evening ramp is almost always met by fossil fuels—usually natural gas peaker plants. In some regions, data centers are now the single biggest driver of new gas plant construction. The renewable energy they buy doesn’t erase the need for firm, dispatchable backup; it just shifts the accounting. The grid has to absorb that mismatch, often at a high carbon cost.

Rows of server racks in a data center

Geography Matters More Than We Admit

Renewable energy isn’t spread evenly across the map. The sunniest, windiest spots are often far from the fiber optic backbones and population hubs that data centers need. Building a data center in a remote area with abundant renewables means stringing new transmission lines, which face years of permitting battles and community pushback. The alternative—building where the grid is already strong but renewables are scarce—means leaning on RECs that don’t reflect physical reality. Either way, the data center’s location locks in a certain energy profile. In Northern Virginia, home to the world’s densest cluster of data centers, the local utility has proposed new gas plants to meet demand, even as the data center operators ink renewable deals. The geography of the grid simply doesn’t match the geography of renewable potential.

The E-Waste Afterlife

Servers live fast and die young—three to five years, typically. Then they’re swapped for newer, more efficient models. The old hardware enters a waste stream that’s notoriously hard to trace. Some gets recycled properly; a lot gets shipped to developing countries where informal recyclers burn circuit boards to salvage precious metals, releasing dioxins and heavy metals into the air and soil. The renewable energy feeding the new servers does nothing about the toxic legacy of the old ones. A genuinely systems-minded approach would demand circularity: design for disassembly, closed-loop material recovery, and extended producer responsibility. But the industry’s fixation on operational energy and renewable procurement leaves the back end of the hardware lifecycle mostly unexamined.

What a Systems Approach Would Actually Demand

If we’re serious about fitting digital infrastructure within ecological limits, renewable energy procurement is just one piece of the puzzle. A systems approach would require:

  • Time-matched, location-matched clean energy. Not just annual RECs, but hourly matching of consumption with carbon-free generation, ideally within the same grid region. This forces data centers to own the intermittency problem instead of offloading it onto the grid.
  • Water-neutral or water-positive operations. In water-stressed basins, data centers should use closed-loop cooling or dry cooling, even if it costs more energy. The trade-off between water and carbon needs to be made explicit, not swept under the rug.
  • Embodied carbon budgets. Construction and hardware manufacturing emissions should be tracked, reported, and capped. This means valuing existing facilities and extending server lifespans, not just chasing the newest, shiniest hardware.
  • Demand-side thinking. Instead of asking “how do we power this growing load cleanly?” we should ask “does this load need to exist in the first place?” That means questioning the necessity of energy-intensive applications, from cryptocurrency mining to certain AI training runs, and designing software for efficiency, not just speed.

Frequently Asked Questions

Why can’t data centers just use batteries to store renewable energy?

Battery storage is improving, but the scale needed for a typical data center is staggering. A 100-megawatt facility would need hundreds of megawatt-hours of storage to cover a single windless night. Lithium-ion batteries come with their own supply chain headaches, including mining impacts and limited lifespans. While batteries can help with short-term grid services, they’re not yet a full substitute for firm, dispatchable generation. The materials and energy needed to build that much storage also carry a significant carbon footprint that’s rarely accounted for.

Are there any data centers that actually run on 100% renewable energy 24/7?

A few small-scale projects have achieved 24/7 carbon-free energy matching, often by combining local renewables with storage and backup from hydroelectric or geothermal sources. But for the vast majority of hyperscale and colocation facilities, true 24/7 matching remains aspirational. The data and tracking infrastructure to verify hourly matching is still being developed, and in most grid regions, the physical supply simply isn’t there. What’s more common is “100% renewable” on an annual net basis, which masks the hour-by-hour reliance on fossil fuels.

What can a regular person do about data center energy use?

Individual actions matter, but they’re limited. You can choose cloud providers and services that are transparent about their energy practices and that pursue 24/7 matching. You can reduce your own data footprint—delete unused files, stream at lower resolutions, keep devices longer. But the real power lies in policy and collective action. Support local opposition to new gas plants being built for data centers. Advocate for transparency laws that require companies to report not just REC purchases but actual hourly energy sources, water use, and hardware lifecycle impacts. The systems that shape data center growth are political and economic, not just technological.

The Hidden Footprint: Why Clean Power Alone Won’t Fix Data Center Growth

Rows of server racks in a modern data center with blue lighting

When a hyperscale cloud provider announces a new solar farm or a long-term wind contract, the press release practically writes itself. The numbers are huge, the intentions sound progressive, and the charts all point toward a net-zero future. But if you trace where the actual electrons go—and where the materials come from—a much messier picture starts to form. The problem isn’t the renewables. It’s that we’ve started treating a single procurement checkbox as the whole story, while the physical reality of digital growth keeps churning away, largely unexamined.

I’ve spent years looking at infrastructure systems, and one pattern shows up everywhere: we optimize for one metric and quietly externalize the rest. In data centers, that metric is the power usage effectiveness ratio and the percentage of renewables on the balance sheet. But a data center isn’t a lightbulb. It’s a node in a sprawling, material-hungry network that stretches from rare earth mines in Inner Mongolia to water tables in Arizona. If we only talk about matching kilowatt-hours with wind and solar, we miss the actual shape of the problem.

The Matching Game and Its Limits

Most large operators now claim to be “100% renewable.” What that usually means is they buy enough renewable energy certificates or sign enough power purchase agreements to cover their annual electricity consumption on paper. It’s a meaningful step—it channels capital into wind and solar projects that might not otherwise get built. But it’s also a statistical abstraction. A data center in Virginia might be burning natural gas and fissioning uranium at 3 a.m., while its certificates are satisfied by a wind farm in Oklahoma that generates most of its power at night. The grid doesn’t see a matched load. It sees a fossil plant ramping up and down to follow the data center’s flat, relentless demand.

Grid engineers have known about this temporal mismatch for years, but it rarely makes it into the glossy sustainability reports. A facility that runs at near-constant load requires a near-constant supply of power. Wind and solar are anything but constant. The gap gets filled by whatever is on the grid at that moment—usually gas, sometimes coal, occasionally hydro. The certificates make the accounting look tidy, but the physical electrons flowing into the servers tell a different story. This isn’t a failure of renewables. It’s a failure of how we talk about them. We’ve confused annual net-zero accounting with real-time decarbonization, and the two are not the same.

The Water-Energy Blind Spot

Aerial view of a large data center complex surrounded by arid landscape

Even if a data center could run entirely on on-site solar and battery storage—a physical impossibility for most facilities—there’s another resource that rarely makes it into the sustainability report: water. Cooling towers evaporate millions of gallons a year, often in regions already facing water stress. A single large data center can consume as much water as a small city. In places like Phoenix, Arizona, or Loudoun County, Virginia, this creates a quiet competition between server racks and residential taps.

The water footprint usually gets reported as a separate metric, if it’s reported at all. But it’s deeply tangled up with the energy question. Different cooling technologies come with different energy-water trade-offs. Evaporative cooling uses less electricity but more water. Dry cooling saves water but bumps energy consumption by 5-10%. In a world where we’re racing to electrify everything—cars, heating, industrial processes—that extra energy demand cascades back into the grid, requiring more generation, more transmission lines, and more land. The system is coupled. Optimize one variable in isolation, and you often degrade another.

The Circularity Gap in Hardware

Servers have a lifespan of three to five years. After that, they’re decommissioned, and the industry’s standard practice is a mix of resale, recycling, and landfill. The metals inside—copper, aluminum, gold, palladium—require enormous energy to extract and refine in the first place. A single server’s embodied carbon, from mine to factory to rack, can rival its operational carbon over its entire useful life. Yet most renewable energy commitments cover only the operational phase. The supply chain, which accounts for the majority of a tech company’s total carbon footprint, sits outside the boundary.

This is where the systems thinking gets uncomfortable. If we’re truly concerned about the climate impact of data centers, we should be asking not just “how is it powered?” but “how often do we replace it, and what happens to the old one?” Extending server life from four to six years, or designing for component-level upgrades instead of full-box swaps, could reduce embodied carbon more than any power purchase agreement. But that would require rethinking depreciation schedules, supply contracts, and the performance-obsessed culture of IT procurement. It’s easier to buy a wind contract and call it done.

Land Use and the Spatial Footprint

Renewable energy requires land—lots of it. A 100-megawatt solar farm covers roughly 500 to 700 acres. A data center campus can easily demand 300 megawatts or more. When a tech company signs a power purchase agreement for a new solar installation, that land is removed from other potential uses: agriculture, habitat, or community development. In rural areas, this can create tension between clean energy goals and local land-use priorities. In some cases, solar farms are sited on prime farmland, raising questions about food security and soil health that never appear in the data center’s sustainability report.

Wind turbines have a smaller direct footprint but require spacing that fragments landscapes and can affect wildlife corridors. The point isn’t that renewables are bad—they’re essential. The point is that “100% renewable” claims obscure the physical reality that digital infrastructure is consuming not just electricity, but territory. As data centers proliferate to support streaming, cloud computing, and the insatiable demand for real-time everything, the land requirements of their energy supply chains will become a geopolitical issue. We’re already seeing pushback in Ireland, the Netherlands, and Singapore, where data center moratoriums have been imposed due to grid constraints.

The Utilization Paradox

Here’s a statistic that should make us pause: the average server utilization in many data centers hovers around 12-18%. That means 80-85% of the computing capacity is sitting idle, drawing power, generating heat, and aging toward obsolescence. Virtualization and cloud computing were supposed to fix this by pooling resources, but the gains have been offset by the sheer growth in demand. We keep building more data centers, filling them with servers that mostly wait, and then congratulating ourselves for powering them with renewables.

If we doubled average utilization to 30-40%—still leaving headroom for spikes—we could theoretically halve the number of physical servers needed for the same workload. That would reduce embodied carbon, water use, land use, and grid strain simultaneously. It’s a point of intervention that addresses multiple problems at once. But it requires coordination across competing cloud providers, changes to service-level agreements, and a cultural shift away from over-provisioning as a risk management strategy. The technical solutions exist; the organizational incentives don’t align.

Wind turbines and solar panels working together in a green field under blue sky

Rethinking the Metric of Success

What if we measured data center sustainability not by the percentage of renewables purchased, but by the total resource throughput per unit of useful computation? This would combine energy, water, materials, and land into a single efficiency metric that reflects the physical reality of operating digital infrastructure. It would expose the trade-offs that current reporting hides. A facility in a water-scarce region might score poorly despite its solar panels. A cloud region with high server utilization would outperform one with low utilization, even if both buy the same renewable certificates.

This kind of metric is harder to calculate and harder to communicate. It requires transparency that most operators are unwilling to provide. But it would shift the conversation from “are we green?” to “are we doing this efficiently?”—which is a more honest question. Efficiency, in the thermodynamic sense, is about minimizing waste across all inputs. Renewable energy addresses only one input. The rest of the waste stream—heat, water vapor, decommissioned hardware, transmission losses—continues to grow in proportion to our digital appetite.

The Role of Demand Management

There’s another factor that gets almost no attention: reducing the demand for data center services in the first place. Not through austerity or turning back the clock, but through smarter design of the digital services that run on these servers. Video streaming at resolutions the human eye can’t distinguish. Cryptocurrency mining that performs no useful work. AI training runs that are repeated hundreds of times to tune hyperparameters. Redundant backups of backups. These are not essential services; they’re artifacts of a system that treats compute as infinite and free.

Pricing doesn’t reflect the true cost. Cloud storage and compute are so cheap that there’s no incentive to delete anything or optimize code. If the environmental cost of data—the water, the land, the embodied carbon—were internalized into the price of cloud services, behavior would change. Developers would write more efficient queries. Companies would clean up their data lakes. Consumers might choose lower-resolution streaming when it makes no visible difference. The market would allocate digital resources more carefully, and the pressure to build new data centers would ease.

Where Do We Go From Here?

The renewable energy transition for data centers is necessary but insufficient. It’s a first step that has been mistaken for the entire journey. The next steps require uncomfortable conversations about growth, efficiency, and the physical limits of the planet. They require data center operators to report not just power usage effectiveness and renewable percentage, but water usage, server utilization, hardware lifecycle, and land footprint—in a standardized, auditable format. They require cloud customers to see the environmental cost of their workloads, not just the dollar cost. And they require all of us to question whether every bit of data we generate and store is worth the resources it consumes.

I’m not arguing against renewable energy. I’m arguing against the complacency that comes with it. The danger of a “100% renewable” claim is that it makes the problem seem solved, when in fact we’ve only addressed one dimension of a multi-dimensional challenge. Data centers are physical systems embedded in ecological and social contexts. Until we treat them that way—with the same rigor we apply to power purchase agreements—we’re just rearranging deck chairs on a ship that’s still taking on water.

Frequently Asked Questions

Why isn’t buying renewable energy enough to make data centers sustainable?

Purchasing renewable energy through certificates or power purchase agreements addresses only the operational electricity consumption. It doesn’t account for the timing mismatch between when renewables generate power and when data centers consume it, nor does it cover the embodied carbon in server manufacturing, water use for cooling, or land-use impacts of renewable installations. A data center can be “100% renewable” on paper while still relying on fossil fuels during calm, cloudy periods and consuming scarce water resources in drought-prone regions.

How does server utilization affect the environmental impact of data centers?

Most servers run at only 12-18% utilization, meaning the vast majority of their computing capacity sits idle while still drawing power and generating heat. Higher utilization rates would allow the same computing workload to be handled by fewer physical servers, reducing the need for manufacturing new hardware, the energy to run and cool them, and the land required for the facilities themselves. Improving utilization is one of the most effective ways to reduce the total resource footprint of digital infrastructure.

What can cloud customers do to reduce their data center footprint?

Cloud customers can optimize their code to run more efficiently, delete unnecessary data and redundant backups, choose cloud regions powered by cleaner grids with lower water stress, and extend the life of their virtual machines instead of constantly provisioning new ones. They can also ask their cloud providers for transparent reporting on the environmental impact of their specific workloads—not just the provider’s overall sustainability claims—to make more informed decisions about where and how to run their applications.

The Renewable Mirage: Why Data Centers Need More Than Just Megawatts

The Renewable Mirage: Why Data Centers Need More Than Just Megawatts

Rows of servers in a modern data center with blue lighting

You’ve seen the headlines. A tech behemoth signs a flashy new deal for a solar farm, or a cloud provider boasts that its data center is now “100% renewable.” It sounds like a neat, tidy solution. The electrons zipping through server racks in northern Virginia are, on paper, matched by clean ones generated somewhere else. But if you follow the actual copper wires, you bump into a much messier truth: the physical grid doesn’t care about your accounting. That data center is still gulping down whatever the local power plant is serving, and right now, that’s often a stiff mix of gas, coal, and nuclear. We’ve gotten very good at offsetting the idea of dirty power without changing the physical reality of it.

The Fable of the Flawless Match

Most corporate clean energy claims rest on a system of certificates—Renewable Energy Certificates (RECs) in the U.S., Guarantees of Origin in Europe. A facility in Ashburn, Virginia, can buy credits from a wind farm in Oklahoma and call itself green. It’s a financial transaction that supports renewable projects, and that’s genuinely useful. But it’s also a spatial and temporal sleight of hand. The actual, physical load of that data center is being met by whatever generators are spinning on the PJM interconnection at that exact moment. On a hot July afternoon, that’s a lot of natural gas. The electrons don’t carry labels; the grid just balances supply and demand with whatever is available.

This isn’t just an accounting quirk. It’s a fundamental mismatch between a financial product and a physical system. When a data center campus in Loudoun County ramps up its compute load, a generator somewhere nearby has to ramp up to meet it. If the wind isn’t blowing in Oklahoma, that generator is almost certainly a fossil fuel peaker plant. The certificate system has successfully funneled money into building more wind and solar, which is a real win. But it has also let us pretend that a data center’s operational carbon footprint is solved, when its physical footprint on the local grid remains as carbon-heavy as ever. We’re greening the portfolio, not the power lines.

The Grid’s Concrete Ceiling

Data centers aren’t just passive energy consumers; they’re hulking, hyper-concentrated loads dropped onto specific nodes of a creaky electrical grid. A single hyperscale campus can demand as much power as a midsize city, and it expects that power with “five nines” of reliability—99.999% uptime. This creates a physical strain that no amount of remote wind farms can ease. The grid’s transmission lines, transformers, and substations have hard limits. You can carpet a desert with a gigawatt of solar panels, but if there aren’t high-voltage arteries to carry that power hundreds of miles to the data center, it might as well be on the moon.

The U.S. interconnection queue is a perfect snapshot of this bottleneck. Lawrence Berkeley National Laboratory data shows over 2,000 gigawatts of generation and storage projects waiting to connect, the vast majority of them renewable. Wait times routinely stretch past five years. A data center can be built in 18 months. The physical infrastructure to deliver clean power simply can’t keep up with the pace of digital expansion. So even a data center with the best intentions and a signed PPA for a new wind farm will, for years, be physically powered by the existing, fossil-heavy grid. The bottleneck isn’t ambition; it’s steel, copper, and permitting.

High-voltage power lines stretching across a rural landscape

The Duck Curve Meets the Flat Line

The problem gets sharper when you look at the timing of energy use. Data centers are the ultimate flat-line consumers; they run 24/7 at a near-constant hum. Solar power, by contrast, is a temperamental, intermittent resource that peaks at midday and vanishes at night. This creates the infamous “duck curve,” where net grid demand plummets during sunny hours and then rockets up as the sun sets. A data center that claims to be solar-powered is, in physical reality, a data center that leans heavily on the grid’s fossil fuel or storage resources for most of the day.

This leads to a stubborn fallacy: that you can “baseload” a data center on renewables. The only way to physically pull that off is through massive overbuilding of generation and an even more staggering deployment of energy storage. The math is sobering. To run a 1-gigawatt data center on solar alone, you wouldn’t just need 1 GW of panels. You’d need perhaps 5 GW of solar capacity and tens of gigawatt-hours of battery storage to cover nighttime, cloudy weeks, and seasonal dips. This isn’t a matter of buying more RECs; it’s a fundamental re-engineering of the grid’s physical assets, a process that takes decades and trillions of dollars.

The Storage Gap

Battery storage gets trotted out as the silver bullet, but the numbers don’t add up yet. The current global installed base of grid-scale batteries is measured in gigawatts, while the need for a fully renewable-powered data center industry would be in the terawatts. Lithium-ion, the dominant tech, is great for short bursts—two to four hours—but it’s not economically viable for the long-duration storage (12+ hours, or even seasonal) needed to bridge the gaps in wind and solar generation. Flow batteries, compressed air, green hydrogen—these are still in their awkward teenage years of deployment. A data center operator can sign a PPA for “24/7 carbon-free energy,” but the physical reality is that the technology to deliver it at scale simply doesn’t exist on the grid yet.

The Thirst Nobody Talks About

Another dimension often left out of the “100% renewable” victory lap is water. Many data centers rely on evaporative cooling systems that guzzle millions of gallons of water a day, especially in water-stressed regions. A single large facility can consume enough to supply a small town. This creates a direct, physical strain on local aquifers and municipal water supplies, a strain that has nothing to do with the carbon content of the electricity. In some communities, data center water use competes directly with agriculture and residential needs, sparking a localized resource conflict that renewable energy certificates do absolutely nothing to address.

Even the renewable energy sources themselves can worsen water stress. Concentrated solar power plants can be water hogs. But more broadly, the land use required for massive solar and wind farms creates its own ecological pressures—habitat fragmentation, the mining of rare earth minerals for batteries and turbines. A data center running on 100% renewable energy is still a massive industrial facility with a physical footprint that extends far beyond its electrical meter.

Aerial view of a large solar panel farm in a desert landscape

The Rebound Effect and the Hunger for More

Here’s the most uncomfortable twist: the availability of “100% renewable” energy can actually accelerate the growth of data center demand, creating a classic rebound effect. When a company believes it has solved the carbon problem, it may feel licensed to expand digital services without restraint. The result is a net increase in total energy consumption, even if the percentage of renewable energy is high. The cloud, AI, streaming, and the Internet of Things are not static industries; their energy appetites are growing exponentially. A 2023 report from the International Energy Agency projected that data center electricity consumption could double by 2026, driven largely by AI and cryptocurrency. If the grid’s total renewable capacity isn’t growing at the same pace, then all this new demand is effectively being met by fossil fuels, regardless of what the certificates say.

Thinking in Systems, Not Spreadsheets

So, if renewable energy procurement is not enough, what is? The answer requires a shift from a carbon-accounting mindset to a systems-thinking one. A data center is a node in a complex network of electrical, hydrological, and ecological systems. Its sustainability must be measured by its actual, physical impact on those systems, not just by its ledger of certificates.

1. Location and Grid Integration

The most consequential decision a data center operator can make is where to build. Placing a facility in a region with an already-clean grid—like the Pacific Northwest with its hydropower, or France with its nuclear—has a far greater immediate physical impact than building in a coal-heavy region and buying offsets. In addition, data centers can be designed as active grid participants, not just passive loads. This means investing in on-site generation, battery storage, and demand-response capabilities that actually help balance the local grid. A data center that can reduce its load during peak hours or provide frequency regulation services is a better physical citizen of the grid than one that simply buys RECs.

2. Radical Efficiency and Circular Design

The cleanest megawatt-hour is the one never consumed. The industry’s focus on PUE (Power Usage Effectiveness) has been a success story, but it only measures the overhead of cooling and power distribution, not the efficiency of the computing work itself. We need to move toward metrics that measure useful computation per unit of energy, incentivizing more efficient code, better server utilization, and a shift away from wasteful “always-on” architectures. Beyond energy, a circular approach to hardware—extending server lifespans, reusing components, and designing for disassembly and material recovery—can dramatically reduce the embodied carbon and resource extraction associated with the relentless churn of IT equipment.

3. Transparent, Granular Accounting

The current system of annual REC matching is too coarse. The industry is moving toward hourly matching of carbon-free energy, a concept known as “24/7 CFE.” This requires data centers to match their electricity consumption with local or grid-delivered carbon-free sources on an hourly basis. While still an accounting framework, it forces a much closer alignment between the data center’s demand profile and the actual generation profile of clean resources, driving investment in the storage and firm clean generation that the grid physically needs. This transparency must also extend to water use, land use, and supply chain impacts, creating a full-system picture of a facility’s footprint.

FAQ

If a data center buys enough renewable energy to cover its annual consumption, isn’t it carbon neutral?

Not in a physical sense. The annual matching system allows a data center to claim carbon neutrality by purchasing certificates from a renewable project that may generate power at different times and in a different location. The actual electricity consumed by the data center at any given moment comes from the local grid mix, which often includes fossil fuels. The certificates represent a financial investment in renewables but do not change the physical source of the electrons powering the servers. True physical carbon neutrality would require the data center to be directly connected to a dedicated renewable source with sufficient storage to cover its 24/7 demand, a configuration that is currently rare.

Why can’t we just build more solar and wind farms to power all data centers?

The limitation is not just the number of solar panels or wind turbines, but the physical capacity of the grid to transmit that power and the ability to store it for when the sun isn’t shining and the wind isn’t blowing. The transmission grid is a major bottleneck, with new high-voltage lines taking a decade or more to plan, permit, and build. Additionally, the variability of solar and wind requires massive amounts of energy storage to provide a stable, 24/7 power supply. Current battery technology is insufficient for long-duration storage, and the scale of deployment needed to firm up a fully renewable grid for a large data center industry is decades away.

What is the single most effective thing a data center operator can do to reduce its real-world environmental impact?

Beyond siting new facilities in regions with already-clean grids, the most effective action is to focus on reducing total energy and resource consumption through efficiency at all levels. This means not just improving PUE, but also optimizing server utilization, investing in more efficient code and hardware, and extending the life of equipment. A data center that uses half the energy has half the physical impact, regardless of the grid mix. Coupling this with on-site generation and storage to actively support local grid stability creates a demonstrably smaller physical footprint than simply buying certificates for a remote renewable project.

The Hidden Cost of Clean Data: Why Renewable Energy Alone Won’t Fix the Internet’s Backbone

When a tech giant announces a shiny new solar farm or a long-term wind contract to power its data centers, it’s easy to feel a little glow of progress. The electrons flowing into the servers are, on paper, clean. But follow those electrons back through the tangled wires of the real grid, and the story gets messy. The idea that a data center running on renewables is an environmental problem solved is not just optimistic—it ignores the stubborn physics of how electricity actually works. Rui Mendes has been poking at the seams of infrastructure and resource flows for years, and the more you dig, the clearer it becomes: matching kilowatt-hours on a spreadsheet is a long way from decarbonizing a round-the-clock industrial beast.

The Intermittency Gap and the Shadow Grid

Data centers don’t nap. They don’t take weekends off. They demand power with a flat, relentless hunger that wind and solar, by their very nature, can’t satisfy alone. A company might ink a deal for a wind farm in Oklahoma and claim its Virginia servers are running on that breeze. But electrons don’t come with name tags. The grid operator has to balance supply and demand in real time, and when the sun dips or the wind dies, that balance is kept by whatever’s spinning—usually a natural gas plant, sometimes coal. The renewable certificate gets filed away, the press release goes out, and the fossil fuel backbone stays right where it is, flexing to keep the servers humming through the night.

This isn’t a flaw in renewables. It’s a flaw in the story we tell about them. A hyperscale data center cluster—think Northern Virginia, where the load rivals a small city—can’t run on good intentions. The grid operator doesn’t care about your corporate sustainability report; it cares about frequency and voltage. When a cloud passes over a solar array or the wind drops, something has to ramp up instantly. That something is almost always a gas turbine. The renewable contract might make the accounting look tidy, but the physical system still leans heavily on fossil fuels, especially during the dark, windless stretches that happen more often than the brochures admit.

Wind turbines and power lines stretching across a rural landscape

Water: The Thirst Nobody Talks About

Carbon gets all the attention, but data centers have another appetite that’s just as worrying: water. Cooling those endless racks of servers can guzzle millions of gallons a day, often in regions already grappling with drought. A solar-powered facility in Arizona might look virtuous on a carbon ledger, but it’s still pulling from the same overtapped aquifers as the local farms and communities. Evaporative cooling systems, which are common because they’re energy-efficient, literally send water vapor into the sky—water that’s gone from the local watershed for good. The renewable energy badge doesn’t cover that loss.

And it’s not just the operational thirst. The supply chain for renewables themselves is waterlogged. Manufacturing photovoltaic panels requires ultrapure water for rinsing silicon wafers, and the factories producing them often sit in industrial zones where water governance is, let’s say, less than rigorous. So a data center running on solar in a desert might be shifting its water burden to a river basin halfway around the world. The math gets uncomfortable when you zoom out.

The Hardware Churn and the Carbon It Leaves Behind

Servers don’t last. In a hyperscale facility, the refresh cycle is brutal—three to five years, then rip and replace. Each new generation of chips promises better performance per watt, and that’s real. But the old gear doesn’t vanish. It’s shredded, smelted, or shipped to a secondary market where it runs less efficiently. And the new gear? It starts its life in a semiconductor fab, one of the most energy-hungry and chemically intense manufacturing processes on the planet. The carbon baked into a single server—from mining rare earths to etching silicon to assembly—can rival years of its operational energy use. When a data center claims it’s “100% renewable,” it’s usually only talking about the electricity that keeps the lights on, not the mountain of embodied carbon that built the place and fills it every few years.

Then there’s the concrete and steel of the building itself. Cement production alone coughs up roughly 8% of global CO₂ emissions. Backup diesel generators sit there, ready to fire up during grid outages—which are becoming more common as climate change strains infrastructure. Those generators get tested regularly, burning fuel, and when a storm knocks out the lines, they roar to life. Renewable certificates don’t touch that reality. The irony is thick: data centers built to serve a digital economy are quietly deepening their reliance on diesel just as the grid they lean on gets wobblier.

Rows of server racks in a modern data center

The Map Doesn’t Match the Demand

Renewable energy is stubbornly place-based. The best wind whips across the Great Plains; the strongest sun bakes the Southwest. But data centers huddle around internet exchange points and population hubs—Northern Virginia, Frankfurt, Singapore. You can’t just pipe sunlight across three states without losing a chunk of it to transmission losses and without building new high-voltage lines that take a decade to permit and build. A data center in Loudoun County can sign a virtual power purchase agreement for a wind farm in Texas, but the actual electrons feeding its servers come from the local grid, which in Virginia is still cozy with natural gas. The renewable energy certificate is a financial tool, not a physical delivery mechanism. It was designed to spur renewable development, and it does that. But it doesn’t rewire the grid.

This geographic mismatch creates a timing problem, too. Data centers run around the clock, but solar panels clock out at sunset. Wind patterns are fickle. Without cheap, massive energy storage—which we don’t have at the scale needed—the gap between renewable generation and constant demand has to be filled by something. In most places today, that something is natural gas. And as data center energy appetite grows, driven by cloud services and machine learning workloads, the gap is widening. The International Energy Agency expects data center electricity consumption to double by 2026, topping 1,000 terawatt-hours. Even with record renewable buildouts, the sheer weight of new demand means more fossil fuel plants will stay online or get built to keep the lights on.

Jevons and the Efficiency Trap

Data center operators love to talk about efficiency gains—better power usage effectiveness, smarter cooling, higher server utilization. These are genuine improvements. But they also risk walking straight into a trap that William Stanley Jevons spotted back in 1865: when a resource gets more efficient to use, total consumption often goes up, not down. Cheaper computation invites more computation. The result is that total energy use climbs even as individual facilities get leaner. This isn’t a theory; it’s the plot of the last two decades. Despite all the efficiency wins, data center energy use has marched steadily upward because our hunger for digital services has grown even faster.

This dynamic pokes holes in the story that we can simply “green” the data center industry by buying more renewables. If the underlying demand keeps surging, even a sector running entirely on wind and solar would still chew up enormous amounts of land, transmission corridors, and mining for battery materials. The physical footprint of renewable energy isn’t zero. A systems-minded view forces a harder question: not just how we power data centers, but why we need so many of them, and which services genuinely earn that resource draw.

Aerial view of a large solar farm in a desert landscape

What a More Honest Accounting Would Look Like

If buying renewables isn’t enough, what would a clearer picture require? First, data center operators would need to report on a wider set of numbers: the hourly carbon intensity of the grid where they actually sit, not just annual certificates matched to total consumption. Google and Microsoft have started nudging toward 24/7 carbon-free energy goals, but those remain aspirational and technically heavy lifts for most operators. Second, it would mean transparent reporting on water consumption—not just in cooling, but across the whole supply chain. Third, it would force a real conversation about demand management. That could mean shifting computation to times when renewables are plentiful, or it could mean questioning whether always-on, low-value computation deserves a permanent place on the grid.

The uncomfortable truth is that a data center is an industrial facility, not a cloud. Its physical demands on land, water, and grid stability are real and growing. Treating renewable energy as a get-out-of-jail-free card hides those demands and postpones the kind of systemic thinking needed to align digital infrastructure with planetary limits. The goal shouldn’t be to make data centers look “green” on a spreadsheet, but to ensure they operate within the actual carrying capacity of the regions that host them. That means sometimes choosing not to build, or to build differently, or to locate where the resource trade-offs are less severe. It means accepting that efficiency and renewables are necessary but not sufficient tools. The real work is in questioning the growth itself.

Frequently Asked Questions

Why can’t data centers just use batteries to store renewable energy for nighttime use?

Battery storage at the scale a large data center needs is still wildly expensive and resource-heavy. A 100-megawatt facility would need hundreds of megawatt-hours of storage to get through a single night, which means a lot of lithium, cobalt, and other materials. The mining and manufacturing for those batteries carry their own heavy environmental and social price tags. For now, batteries are more practical for short-term grid balancing than for shifting a full data center load from day to night.

Doesn’t locating data centers in cold climates solve the cooling problem?

Cold climates cut the energy needed for cooling, but they don’t erase water use or other impacts. Many facilities in cool regions still use water-based cooling for efficiency, and building and running data centers in remote areas can disrupt local ecosystems and strain small-town infrastructure. Plus, the renewable energy available in cold, northern regions is often seasonal—plenty of hydropower in spring, but less solar in winter—creating a different kind of mismatch.

What is the difference between a power purchase agreement and actually using renewable energy?

A power purchase agreement is a financial contract that helps fund a renewable energy project, but the electricity from that project goes into the general grid, not directly to the buyer. The buyer gets renewable energy certificates that can be used to claim “100% renewable” status in carbon accounting. But the physical electricity powering the buyer’s facility still comes from the local grid mix, which may include fossil fuels. The agreement supports renewable development but doesn’t physically disconnect the facility from fossil fuel generation.