Who Pays for Data Center Power Costs in 2026?

The short answer is: usually the utility ultimately recovers the cost of serving a data center, but the bill is spread among the data center operator, the utility’s ratepayers, taxpayers, and sometimes generators or contracted customers. The allocation depends on the grid connection, utility tariff, local tax agreements, demand charges, energy-efficiency performance, and whether new generation and transmission are built specifically for the project. It is therefore misleading to say that data centers either pay every cost themselves or receive electricity entirely for free.

Also worth reading: How Should Cities Zone AI Data Centers for Growth, Infrastructure, and Community Protection? · What does the future of smart city planning look like with artificial intelligence and data-driven infrastructure? · How Are Cities Changing Data Center Permitting Rules in 2026?

Large data centers use electricity for servers, cooling, power conversion, backup systems, and network equipment. AI facilities generally have a higher electrical load than ordinary web-hosting centers because they run dense accelerator racks and often operate near full capacity around the clock. A utility may purchase several megawatts for a facility that appears modest on a citywide demand chart, yet that load can require expensive substations, transmission lines, backup generation, and new supply. The operator may pay for some of those upgrades, while residential and business customers may bear part of the system cost through rates.

The public debate intensified by 2026 because several states and communities confronted proposals for very large campuses alongside rising electricity prices. Oregon considered legislation intended to protect consumers from data-center power costs, while California tightened oversight of data-center energy use and grid costs. These disputes show that “data center power costs” can mean three different things: the electricity bill paid by the operator, the utility’s cost of serving it, and the broader household effect on electricity rates. Planning discussions should identify which cost is being discussed before comparing projects.

How Large Data Centers Change Electricity Demand

A data center adds demand, but its effect on power prices is not automatic or identical everywhere. The impact depends on local demand growth, the time of day when servers operate, available generating capacity, transmission constraints, weather, fuel prices, and the utility’s rate design. If a new data center connects to a grid with spare capacity, the immediate system cost may be limited. If it arrives in a constrained region, its sudden load can require upgrades that serve future customers but are initially paid for through tariffs, contracts, or public financing.

Demand charges are especially important. A commercial customer may pay a fee based on its highest 15-minute demand interval during a billing month, rather than only on the amount of electricity consumed. This encourages data-center operators to smooth their load where possible, but it does not remove the need for infrastructure. A 100-megawatt facility with a carefully managed peak still requires substantial generation and delivery capacity, even if it shifts some computing work to hours when renewable output is higher. Operators can also use batteries, thermal storage, or workload scheduling, although these measures add capital cost and may not fit every technical workload.

The connection process can be lengthy. A project may need environmental review, equipment procurement, transmission studies, substation construction, utility filings, and local approvals. Those tasks can take months or years, and the planned commercial operation date may not match the date when new transmission becomes available. Utilities consequently face a forecasting problem: they must reserve equipment and capital before customer revenue is guaranteed. In a high-growth area, waiting until every permit is complete can delay a data center, but committing too early can leave the utility responsible for costs if the project is cancelled.

How Utilities Decide Who Pays

The most common arrangement is that the data center signs an electricity service agreement or tariff and pays ordinary energy charges, demand charges, and the costs of service-specific facilities. The utility may also recover shared network investment through a special charge, a negotiated contribution, or a general rate increase. In some cases, the operator deposits funds or agrees to take a minimum amount of power. In others, the project receives a customized rate that spreads fixed costs over a longer period or reduces charges if the facility meets efficiency and load-management targets.

There is no universal rule saying that a data center must pay 100% of the transmission and generation costs caused by its arrival. Rate designs differ by jurisdiction, and public policy can change over time. Some utilities use “large-load” tariffs for customers above a specified capacity, often expressed in megawatts rather than as a percentage of total utility demand. A threshold does not mean that every customer below it is subsidized; it is mainly a mechanism for identifying large loads that require separate planning and cost allocation. Conversely, a customer above a threshold may still participate in costs for upgrades that benefit the wider system.

Taxes and public incentives create a second layer. A local government may offer a property-tax abatement or infrastructure support in exchange for investment, job commitments, or restrictions on the site. Such agreements are not necessarily free energy, because the utility and the municipality are separate entities, but they can shift public expenditure and political risk. A city may also pay for roads, water, sewer, or emergency-service capacity associated with a campus. These costs should be included in an honest project comparison rather than described only as construction spending.

The Role of Energy Prices and Power Contracts

Data center power costs are determined by more than the retail electricity rate. Operators may use a utility tariff, a power-purchase agreement, an on-site generation contract, or a combination of these. A power-purchase agreement can provide long-term price certainty, while a utility rate can provide network access under regulated terms. Large buyers may also invest in renewable generation, natural-gas generation, battery storage, or fuel cells, but each option brings different costs and emissions profiles.

The economics should be separated into three categories. The first is the energy commodity, which can vary with wholesale prices and hourly demand. The second is delivery infrastructure, including substations, lines, transformers, and demand charges. The third is the site’s own consumption, including cooling and power-conversion losses. Cooling is a major operating factor: a more efficient cooling system can reduce total electricity use, but the savings depend on climate, humidity, rack design, and how much heat must be removed. The frequently discussed chip-cooling improvements could lower power or cooling requirements, but they do not eliminate the need for grid capacity because the servers still consume substantial energy.

Operators can reduce exposure through efficiency, flexible workload scheduling, backup-generation design, and long-term supply contracts. They cannot simply treat all AI computing as interruptible if customers require continuous service. The economic benefit of shifting work also depends on software architecture: many training or inference tasks may tolerate some movement, but latency-sensitive services may not. A cooling breakthrough should therefore be evaluated by measured facility-level savings, not by a laboratory percentage applied automatically to the entire campus.

Comparison of Data Center Power-Supply Options

FeatureUtility-grid connectionBehind-the-meter generationHybrid supply
Main advantageUses existing network and supports a staged connectionControls some fuel or generation costsCombines grid reliability with dedicated capacity
Main limitationMay add demand charges or require new infrastructureFuel, emissions, equipment, and permitting can be expensiveMore complex contracts and engineering
Cost exposureUtility rate and possible demand chargesFuel price, maintenance, and capital costMix of grid and generation costs
Reliability roleProvides normal and emergency grid service where supportedCan provide backup or firm capacityAllows workload shifting between sources
Planning questionWho funds network upgrades?What emissions and fuel rules apply?Which costs are shared or avoided?
A behind-the-meter project may be attractive where the grid is congested or where on-site generation is economical, but it is not automatically cheaper. A data center may value a utility connection because it avoids operating its own large power plant, but that choice can expose the project to interconnection delays. Hybrid systems can provide resilience and cost control, yet they also require more sophisticated controls. A city or county should ask operators to show annual energy cost, peak demand, infrastructure contribution, backup fuel, emissions, and the assumptions behind any 10-year or 20-year price estimate.

For comparison, the urban alternative is not usually “no data center.” It is a smaller facility located in an existing industrial area, a campus developed in phases, or a project that uses underused substations and existing buildings. Those options can reduce some infrastructure pressure while preserving the economic activity associated with computing. They may also impose higher land, noise, traffic, or water costs, so the tradeoff must be measured rather than assumed. A smaller center can be more compatible with a neighborhood, while a larger site can be more efficient per unit of computing once fully built; neither outcome is guaranteed.

Practical Steps for Communities and Operators

The first practical step is to obtain a transparent load forecast. It should distinguish IT load from cooling, backup, and auxiliary loads, and it should state the expected annual energy use, maximum demand, ramp-up schedule, and planned expansion. A forecast that presents only the first building can understate campus-wide demand. For example, a 50-megawatt initial phase followed by 200 megawatts of later capacity should not be evaluated as if 50 megawatts were the permanent load.

The second step is to request a utility cost-allocation study. The study should identify substations, feeders, transformers, generation adequacy, and transmission elements required by the project. It should distinguish costs that serve only the data center from upgrades that improve reliability for other customers. Communities should ask whether the operator is contributing to those costs through a connection charge, monthly tariff, minimum bill, special contract, or tax agreement.

The third step is to set measurable operating requirements. These can include annual kWh limits, a maximum demand, efficiency targets, renewable matching, backup-runtime requirements, water-use limits, and restrictions on new fossil generation. A target should have a reporting method. A statement that the facility will use “clean energy” is incomplete unless it identifies whether the claim concerns annual renewable procurement, hourly matching, on-site generation, or avoided grid emissions.

The final step is to build an exit or revision plan. Construction can be delayed, company priorities can change, and grid forecasts can become wrong. Agreements should address cancellation, unused capacity, equipment removal, and the treatment of advances paid for shared infrastructure. A phased permit or staged connection can preserve flexibility, but it may also increase total project costs. The appropriate choice depends on the project’s technology, local market, and expected expansion.

Common Mistakes in Data Center Cost Debates

A common mistake is to equate a large electricity bill with a large increase in everyone’s electricity bill. The two are related through the utility’s cost structure, but they are not identical. If a data center pays ordinary rates and the utility has spare capacity, the added revenue may reduce the utility’s fixed-cost burden per customer. If new infrastructure is financed through general rates, the result can be different. The evidence should therefore include the utility’s projected revenue requirement, not only the operator’s annual power bill.

Another mistake is to treat demand charges as proof that the project is subsidized. Demand charges fund capacity that the customer reserves, and they can encourage operational efficiency, but their design varies by utility. Conversely, relying on a cheap energy rate while ignoring the cost of a new substation is incomplete. A low commodity price does not mean that every delivery component is inexpensive.

A third mistake is to use a single global percentage to describe AI growth or power consumption. The research context reports that about 70% of global computer memory production in fiscal year 2026 had been purchased for AI data centers, but that statistic concerns memory purchasing, not electricity use or total data-center capacity. It is useful for showing supply-chain pressure, not for calculating grid costs. Similarly, claims that space-based data centers could become cost-effective relative to terrestrial facilities are forward-looking projections, not evidence for a current city project.

Communities should also avoid assuming that opposition to data centers is automatically a decision against jobs, tax revenue, or digital infrastructure. A well-run project can bring investment and a larger tax base while still imposing costs on schools, households, and the grid. Conversely, approval does not guarantee that the promised jobs will materialize at the stated scale. The appropriate comparison is the project’s net public benefit after infrastructure, service, environmental, and fiscal costs are included.

When Communities Should Act

A community should seek early review when a proposal appears likely to exceed the utility’s ordinary planning assumptions, especially when it is above a local large-load threshold. The threshold is jurisdiction-specific, so a number such as 25, 50, or 100 megawatts should not be presented as a universal trigger. The decisive question is whether the project changes the utility’s capital plan, requires a new generation resource, or materially affects the timing of transmission and substations.

Immediate scrutiny is also warranted when several projects arrive together. Individually, each may appear manageable, but a combined 500-megawatt pipeline can change grid investment and household rates. A later campus phase should be included in the first environmental and fiscal review whenever the site plan and utility study make that phase reasonably foreseeable. Reviewing only the initial tenant or first building can produce a misleading estimate of long-term demand.

There is no need to freeze every digital project because one large facility has raised concerns. A targeted process is better: require load disclosure, cost allocation, infrastructure commitments, emergency planning, water and noise studies, and a public explanation of who will pay when costs change. Communities that wait until the project is fully permitted may have fewer options, but communities that impose premature bans may lose investment without solving the underlying grid issue. The best timing is usually during site selection, utility interconnection, and permitting, while the project can still be modified.

How to Judge Whether the Arrangement Is Fair

A fair arrangement should make the financial effects visible before approval and should not rely on one party assuming an unpriced obligation. The operator should know the demand charge, energy rate, connection contribution, construction schedule, backup obligations, and consequences of expansion. The utility should know the project’s load profile and whether the facility can reduce demand during system peaks. Residents should know which costs will be recovered through rates and which may be covered by taxes or public funds.

The review should also consider distributional effects. Schools may face higher electricity bills even when they do not benefit directly from the project, while a tax abatement may reduce the public revenue that would otherwise offset those bills. Municipalities should compare the value of property taxes, payroll or construction activity, and infrastructure spending with the cost of road improvements, water, emergency services, and grid charges. A project can be economically attractive and still require a stronger contribution from its operator to protect the public.

For AI Urban Planner, the relevant planning question is not simply whether a data center is “good” or “bad.” It is whether the project fits the electrical, fiscal, environmental, and physical capacity of the place. The most defensible answer as of September 27, 2026 is that data centers generally pay substantial direct electricity and infrastructure costs, but public ratepayers and taxpayers may also carry part of the system cost when new capacity is added or when policies spread upgrades broadly. Utilities, operators, and local governments must disclose the allocation and update it as projects expand. Until they do, claims that data centers will either save consumers money or destroy affordability are unsupported.