eGRID - U.S. EPA Emissions & Generation Resource Integrated Database (eGRID)

The US Environmental Protection Agency's eGRID output emission rates for electricity generation, by eGRID subregion and for the United States as a whole, in kg CO2e per kWh.

Government

Grid mix
Electricity

SpecialistOpen licence

Publisher's page Browse 299 factors

Factors

299

Values

299

One per year and method

Countries

28 regions, sub-national included

Edition

eGRID2023 rev2

published 12 Jun 2025 · all versions

Last loaded

18 Aug 2026

Report a newer version

Overview

eGRID, the Emissions and Generation Resource Integrated Database, is EPA's database of emissions and generation for the US power sector. Its subregion output rates are location-based factors for electricity used in the United States.

EPA publishes a new edition roughly once a year on the eGRID site, and often one or two revisions after it. A revision restates values without flagging which regions changed.

At a glance

Publisher: U.S. EPA Emissions & Generation Resource Integrated Database (eGRID)
Kind: Government
Scope: SpecialistOne category holds at least 5% of its factors: Electricity, with 100.0%. A generalist needs 4.
Home region: United States
Edition: eGRID2023 rev2
Licence: Open licence (us-gov-public-domain)

Open data

How this works

Standardised file

U.S. EPA Emissions & Generation Resource Integrated Database (eGRID), standardised by open-climate.ai

The publisher's file, re-cut into the schema every library on open-climate.ai shares: one category axis, coded regions, canonical units, AR6 warming potentials, the source row kept beside each value. What is in the file

Edition eGRID2023 rev2xlsxen159 rows · built 2026-09-01 · 26d88763a681free account required
Edition eGRID2023 rev2csven159 rows · built 2026-09-01 · fd758dd6f20dfree account required

What open-climate.ai standardised

over the publisher's own fileHow we standardise

One category axis

299 of 299 factor values mapped to one category

Learn more 6 checks behind this

Coded regions

28 regions as ISO or registry codes

11 take the publisher's default region, stated rather than assumed

Learn more 3 checks behind this

Canonical units

1 canonical unit in 1 unit families, raw unit kept

Learn more 4 checks behind this

Warming potentials

131 factor values recalculated on AR6

0 factor values already on AR6

168 factor values left on the publisher's GWP

Learn more 7 checks behind this · 1 known limitation

8 more things standardised

Declared boundaries

5 boundary codes

112 factor values state in, out or varies for each scope term

Learn more 7 checks behind this

Parts and parents

140 factor values grouped under 159 parents

Use a part on its own, or the parent when you want the whole.

Learn more 3 checks behind this

Summed totals

140 totals summed from their printed parts

Learn more 3 checks behind this

Electricity mix

299 electricity factors state their instrument; one default, market first

Learn more 5 checks behind this

Data quality

299 of 299 factor values rated on one quality tier

Learn more 7 checks behind this · 1 known limitation

Languages

English: 100.0% of factor values

German: 100.0% of factor values

French: 100.0% of factor values

Learn more 9 checks behind this · 1 known limitation

Traceable to the source

177 source rows archived

149 rows skipped, each with a reason

Learn more 4 checks behind this

Stable addresses

Slugs never break

Learn more

Audit checks

89 passed3 known limitations3 enforced when loadedlast run 25 Sept 2026

Checks we run on every load to keep the data above trustworthy. Counts are for this library; the grey figure is the same check across all libraries. Point at the i to see why a check matters.

What the statuses mean How checks are counted Why we check How checks are grouped

Needs attention

Every convertible value has its AR6 version
Known limitation · 28 in this library
Why it matters Reporting now asks for AR6. Mixing AR5 and AR6 shifts methane-heavy totals by several percent.
No default value is withheld for poor quality
Known limitation · 28 in this library
Why it matters A default rated too poor to serve is hidden from search and exports, so that factor is missing for you even when it is the right one.
Translations match the current source text
Known limitation · 28 in this library · 286,941 in all libraries
Why it matters When the publisher rewords a label, an old translation can describe a different activity than the one priced.

One category axis

Learn more

Every source category maps to our vocabulary
Enforced when loaded
Why it matters A factor with no category drops out of every category filter and comparison. The load stops rather than serve one.
The publisher's classification is kept
Passed
Why it matters You can still find a factor the way the publisher filed it, and check our mapping against theirs.
Every classification level has a valid parent
Passed
Why it matters A broken tree hides factors from browse and puts them in the wrong category totals.
Every product code comes with the codes above it
Passed
Why it matters In product codes like HS or CPC, a search for a chapter should reach every code inside it. A missing level hides the factor from that search.
A publisher's own classification is used only by that publisher
Passed
Why it matters A publisher's own tree only makes sense inside its library. Filed under another publisher's codes, a factor would show up in categories that do not describe it.
A standard classification code has one label in every library
Passed
Why it matters Codes like NACE or NAICS are meant to link libraries. If one code carries two labels, you cannot tell whether both libraries mean the same activity.

Coded regions

Learn more

Every region is a known code
Enforced when loaded
Why it matters Free text like “France continentale” cannot be filtered or joined to your own data. A code can.
No named region is filed under a broader one
Passed
Why it matters A French factor filed as World would be applied to the wrong country, or lose to a global value in a search for France.
Every region sits in the world hierarchy
Passed
Why it matters A search for Europe has to reach France. A region outside the hierarchy is invisible to broader searches.

Canonical units

Learn more

Every unit is a known code
Enforced when loaded
Why it matters Activity data only multiplies correctly when the unit is exact. An unknown unit stops the load.
One source unit maps to one unit
Passed
Why it matters If one of the publisher's units were read as two different units, factors that share it would give inconsistent footprints.
A unit label means the same in every library
Passed
Why it matters Comparing two libraries is only safe when a label like t.km means tonne-kilometre in both.
A unit label that names no basis folds one way
Passed · 1 in all libraries
Why it matters A label like GJ says nothing about the heating value behind it. If the same bare label folds to two different units, two factors that look alike are not comparable.

Declared boundaries

Learn more

Every boundary states what it includes
Passed
Why it matters Cradle-to-gate and full life-cycle values can differ several times over. Without a stated boundary you cannot tell which you are adding up.
Boundary scope terms are known codes
Passed
Why it matters Consistent terms let you keep exactly the life-cycle stages your inventory needs.
No two factors for the same activity partly overlap in scope
Passed
Why it matters Two totals that share some stages but not all cannot safely be added or swapped: adding them counts the shared stages twice.
Separate stages of one activity are linked as parts
Passed
Why it matters Stages served as unrelated factors give no total, so you may use one stage and miss the others.
Every part of a factor states its boundary
Passed
Why it matters A part with an unknown boundary cannot be told apart from the other parts, so you cannot pick out, say, the combustion share of a total.
Each biofuel follows one convention for biogenic CO2
Passed · 12 in all libraries
Why it matters Burning a biofuel releases CO2 that some publishers count and others leave out, so the same fuel can differ many times over between libraries.
No recycling credit is hidden inside a life-cycle total
Passed
Why it matters A negative total may be a credit for avoided emissions. Filed as a life-cycle burden, it would quietly subtract emissions from your footprint.

Warming potentials

Learn more

Methane and nitrous oxide figures match the stated GWP
Passed
Why it matters If a gas's CO2e is not its mass times the stated GWP, the GWP label is wrong, and converting the value to another GWP version would give a wrong result.
Every convertible value has its AR6 version
Known limitation · 28 in this library
Why it matters Reporting now asks for AR6. Mixing AR5 and AR6 shifts methane-heavy totals by several percent.
CO2e totals agree with their gases
Passed · 3,229 in all libraries
Why it matters A value labelled fossil-only should carry no gas other than CO2 and not exceed its own CO2. When it does, the label or the total is wrong.
Fossil-only values list the gases that back the label
Passed · 19,942 in all libraries
Why it matters With no breakdown by gas, nothing can confirm the fossil-only label. The value rests on the publisher's word alone.
Standardised figures keep every gas the publisher lists
Passed
Why it matters The comparable figure we serve must carry each gas the publisher reported. A lost gas makes the breakdown disagree with the total and hides that gas from you.
Every value states what its CO2e total includes
Passed
Why it matters For a biofuel, a total with or without biogenic CO2 can differ widely. Without that convention you cannot tell which one you are comparing.
A library with no AR6 version at all has a recorded reason
Passed
Why it matters Values that cannot be converted to AR6 cannot be compared with AR6 figures. That has to be a documented decision, not something missed at load.

Parts and parents

Learn more

Every part links to a valid parent
Passed
Why it matters A part that points nowhere gets summed twice or dropped when you use the parent total.
No factor is an unlinked part of another factor
Passed
Why it matters If one stage of a total is also served on its own, beside that total, adding both counts the same emissions twice.
Every factor points to its top parent
Passed
Why it matters Search groups parts under their top factor. A stale link shows a part as a stand-alone result.

Summed totals

Learn more

Summed totals equal their parts on every gas
Passed
Why it matters Where a total is the sum of its parts, the two must agree on every gas. Otherwise your footprint changes depending on whether you use the total or the parts.
Every summed total has a classification when its parts do
Passed
Why it matters A total with no classification drops out of every category filter, even though its parts are filed there.
Summed totals keep their parts' classification
Passed
Why it matters A total takes a classification only when all its parts share it. Otherwise it lands in a category its parts do not support, or misses one they all share.

Electricity mix

Learn more

Every electricity factor states its mix
Passed
Why it matters Without its mix you cannot tell a location-based figure from a market-based one, and Scope 2 reporting needs both side by side.
The market-based value is the default
Passed
Why it matters The default then matches the figure most Scope 2 reports lead with, and a green-tariff zero is never the default when another figure exists.
One default value per factor and year
Passed
Why it matters Two defaults for one year give two answers to the same lookup.
Every green-electricity zero is a market-based value
Passed
Why it matters A zero from a green contract only holds for the buyer of that contract. Filed as location-based, it would put a zero on the physical grid.
Green-electricity zeros are not rated below market-based peers
Passed
Why it matters A green-contract zero is the contract's own figure. Marked down for being zero, it would lose to less relevant values when you look up contracted supply.

Data quality

Learn more

Quality ratings fall inside their scale
Passed
Why it matters An out-of-scale rating cannot be compared, so the value would be ranked arbitrarily.
Every zero value is explained
Passed
Why it matters A zero can be real (contracted renewable power) or a gap in the data. A gap read as real erases emissions from your total.
No default value is withheld for poor quality
Known limitation · 28 in this library
Why it matters A default rated too poor to serve is hidden from search and exports, so that factor is missing for you even when it is the right one.
No implausibly high per-kilogram value is rated reliable
Passed
Why it matters Above 1,000 kgCO2e per kg is often a unit slip, such as grams read as kilograms. Rated reliable, such a value could inflate a footprint a thousandfold.
Every quality level gives a recognised reason
Passed
Why it matters The reason explains why a value got its quality level. An unrecognised one cannot be filtered on or explained to you.
A zero that is only a gap in the source is withheld
Passed
Why it matters A zero with no quality signal, or an implausible regulatory default of zero, is more likely missing data than a real zero. Served, it would erase emissions from your total.
The library is not rated entirely on one fallback quality level
Passed
Why it matters When every value gets the same level because the publisher gives no quality signal, the level tells you nothing and cannot rank one value above another.

Languages

Learn more

Every factor has an English name
Passed
Why it matters Every factor can be searched and cited in one shared language, whatever the publisher's.
Translations match the current source text
Known limitation · 28 in this library · 286,941 in all libraries
Why it matters When the publisher rewords a label, an old translation can describe a different activity than the one priced.
Every served factor has a name
Passed
Why it matters A factor with no name in any language shows as a blank row: you cannot search for it or tell what it measures.
Factors are searched on their English name where one exists
Passed · 7 in all libraries
Why it matters Search matches your query against one name per factor. A name kept in the publisher's language, when an English one exists, is harder to find in English.
Every language with a main name also has a full name
Passed
Why it matters Without the full name, the detail that tells similar factors apart is missing in that language, so two different factors can look identical.
Full names are built from their parts in the same language
Passed
Why it matters A full name must read as the main name followed by its detail. Translated separately, it can drift and describe a slightly different activity.
Every text is labelled with its real language
Passed
Why it matters A French name labelled English would be shown to English readers and matched against English searches.
Every description is available for display and translation
Passed
Why it matters A description missing from the per-language text store is not shown in your language, and never gets translated.
Every usage note is available for display and translation
Passed
Why it matters Names and notes are served from one text store per language. A note missing from that store is not shown, and never gets translated.

Traceable to the source

Learn more

Values traced to one source row agree with each other
Passed
Why it matters Each value traces back to one source row. When values that disagree share a row, it can back only one of them, which weakens that audit trail.
No duplicate factors are served
Passed · 302 in all libraries
Why it matters Identical duplicates split search results and invite counting the same factor twice.
No factor value claims two things that cannot both be true
Passed · 5,836 in all libraries
Why it matters For example, a purchaser price that leaves out retail or delivery, or packaging on an energy unit. One of the two claims is wrong, and you cannot tell which.
No factor value the publisher has withdrawn is still served
Passed · 556 in all libraries
Why it matters The publisher's end date for the value has passed. The figure may be out of date, so look for a newer one before you use it.

Other checks

An activity's grouping key names only the activity
Passed · 6 in all libraries
Why it matters If the key also carried the unit, country or scope, one activity would split into several, and search would not show you its other versions side by side.
A Creative Commons credit names its licence
Passed
Why it matters CC BY asks you to say which licence applies. A credit that leaves it out makes your attribution incomplete when you copy it.
No note of ours appears in the credit or licence notice
Passed
Why it matters Our own notes on how we handle the data would end up in the credit you reproduce, as if the publisher had written them.
The credit line carries no terms of use
Passed
Why it matters You copy the credit line as it stands. Terms of use belong in the licence notice, which you read rather than reproduce.
Every impact assessment method is a recognised code
Passed
Why it matters Free text in place of a code splits one method into several spellings, so filtering by method misses some of its values.
An avoided credit is linked to the burden it belongs to
Passed
Why it matters Served on its own, a credit reads as a factor in its own right. Linked beside its burden, it applies only where it belongs and is never subtracted twice.
Every value is typed as specific, generic or average
Passed
Why it matters The type says how closely a figure fits the product you bought. Any other word would be invisible to a filter on it.
Validity dates are the publisher's own, never guessed
Passed
Why it matters A start date we invented looks just like one the publisher printed, and would hide correct factor values from a search for what applied on a given date.
Quality breakdowns use their scheme's axes
Passed
Why it matters A score on an axis the scheme does not define, or off its scale, cannot be read, so the breakdown behind a rating would mislead.
No battery-electric vehicle carries tailpipe emissions
Passed
Why it matters An electric vehicle has no tailpipe. A non-zero combustion figure means its electricity emissions sit in the wrong place, or are counted twice.
The text of each estimated factor matches its current figures
Passed
Why it matters An estimated factor's description states the year, shares and quality behind it. If those moved, the text would explain a different number than the one served.
A total built on an estimated part is marked as estimated
Passed
Why it matters If the total lost the mark, you would read a figure we partly computed as one the publisher printed.
Every estimate is built only from data we may redistribute
Passed
Why it matters An estimate derived from restricted data would pass that data on under our open licence, which its owner never allowed.
No estimated factor is rated above the data it was built from
Passed
Why it matters An estimate cannot be more reliable than its inputs. Rating it higher would lead you to trust it more than a published figure.
No estimate is served where the publisher printed the figure
Passed
Why it matters When the publisher states the number itself, theirs is the one to use. An estimate beside it would give you two answers to the same question.
Every estimated factor still matches the inputs it was computed from
Passed
Why it matters When an input is revised or withdrawn, the estimate built on it is out of date until it is recomputed.
Every factor with a current value has a default
Passed
Why it matters A factor with values but no default is left out of the served catalogue, so you would never find it in search or exports.
Every factor has a value, in a library that publishes values
Passed
Why it matters A factor listed with no number looks like a match in search but gives you nothing to calculate with.
Every fixed group of regions lists what it covers
Passed
Why it matters A group like “Europe outside the EU” with no member list cannot be placed, so its factor values never match a search for any country in it.
Where both exist, the residual mix is shown before the green-tariff zero
Passed
Why it matters Green electricity counts as zero only for buyers who hold the matching certificates. Showing zero by default would understate everyone else's emissions.
The newest edition of each value is the one marked current
Passed
Why it matters If an older edition stayed marked as current, you would get superseded numbers, or two answers for the same factor.
Factor descriptions describe the factor, not the whole library
Passed
Why it matters When the same long text is repeated on every factor, it tells you nothing about the one you are looking at and hides what is specific to it.
Every library's licence has its rights recorded
Passed
Why it matters Without them, the library page cannot tell you what you may do with the data: share it, change it or use it commercially.
Every green-electricity zero is exactly zero and says why
Passed
Why it matters A green-tariff factor is zero by rule. Any other number, or a zero with no stated reason, would mean the rule was applied wrongly.
Green-electricity zeros cover power generation only
Passed
Why it matters Certificates cover the power plant's emissions, not grid losses or the upstream fuel chain. A zero on those stages would understate your Scope 2 and Scope 3 figures.
Only a total we computed may mix GWP vintages
Passed
Why it matters A published row states one GWP vintage. A mix of AR5 and AR6 can only come from a total assembled out of several rows, and saying so tells you the number was computed, not published.
Spend factors state their price year and basis
Passed
Why it matters A 2019 euro is not a 2024 euro, and a purchaser price includes margins a basic price does not. Without both, spend footprints drift.
Every value has a number, a GWP version and a reference year
Passed
Why it matters Without the number there is nothing to multiply. Without the GWP version or the year, you cannot tell whether two values are comparable.
No factor description is too long to display in full
Passed · 4 in all libraries
Why it matters Text beyond the limit is cut short on the factor page, so part of what the publisher wrote shows only in the download.
Every excused arithmetic disagreement is stated
Passed
Why it matters Where a publisher's own total does not equal its parts and we serve it anyway, the exception is listed on every audit run rather than left in code where nobody sees it.
Every reference year falls between 1960 and next year
Passed
Why it matters A year outside that range points to a typo or a misread column, and would put the value in the wrong period when you filter by year.
The parts of a total are never listed twice under one label
Passed
Why it matters A group that repeats a part label is a list of terms, not a split of the total, so adding its rows up would count some emissions twice.
Every residual mix has its green-tariff counterpart
Passed
Why it matters Market-based Scope 2 reporting needs both: the residual mix for ordinary contracts and a zero for certified green power. With one missing, you have to find it elsewhere.
Every publisher's quality rating system is read
Passed
Why it matters If we do not read a publisher's rating system, its values are treated as unrated and marked down, although the publisher rated them.
A supplier named in the source is linked to the factor
Passed
Why it matters If the supplier is named but not linked, you cannot filter by supplier or tell a company's own figure from a generic one.
A part covering the same scope as its total is linked to it
Passed
Why it matters When a part and the total beside it cover exactly the same scope, nothing in the numbers tells them apart. Linking them stops you adding a part to the total that already contains it.
A year in a factor's name matches its reference year
Passed
Why it matters A name like “Grid 2019” on a 2023 value usually means a yearly series was flattened, so you could apply one year's figure to another.

How the audit works

What can I do with this data?

Open licence

Your rights

Open licence · us-gov-public-domain

Use it to calculate my own footprint: Yes
Publish my footprint results: Yes
Share the file with my customers: Yes
Put the factors in a product I sell: Yes
Modify it or combine it with my own data: Yes

Statute, checked on 5 Aug 2026

eGRID FAQ Q25: "eGRID data is produced by the United States Environmental Protection Agency (EPA) under the public domain and is available for use both non-commercially and commercially."

Credit line

Data: United States Environmental Protection Agency (EPA). (2025). Emissions & Generation Resource Integrated Database (eGRID), 2023. Washington DC: Office of Atmospheric Protection, Clean Air and Power Division. https://www.epa.gov/egrid. Normalised by open-climate.ai, https://open-climate.ai/factors/libraries/egrid (CC BY 4.0)

Not legal advice: the publisher's terms prevail.

Full terms

How to read these answers

Coverage

What the library covers, by category and by boundary. Click a slice to drill in, then a sub-category or a boundary to filter the factors below.

By category

159factors

Click a slice to see what is under it. Click a name to hide it from the ring.

By boundary

159factors

Click a slice to see what is under it. Click a name to hide it from the ring.

Browse factors

Currency

top 0 matches

Saved	Unfold	Activity		Sub-category	Region	Boundary			Unit	GWP

Versions

How this works

Checked for updates 18 Sept 2026: the publisher still shows the edition we serve (2 signals watched)

Version	Published	Loaded	Status	Source
eGRID2023 rev2	12 Jun 2025	18 Aug 2026	Served	Source

Methodology

How this works

Rates are emissions divided by net generation, at the stack of the generating plant. Transmission and distribution losses and upstream fuel supply are outside the boundary.
CO2e uses IPCC AR5 100-year GWPs without climate-carbon feedbacks, as eGRID applies them: 28 for CH4 and 265 for N2O. We also compute an AR6 value by re-weighting the CH4 and N2O legs.
Biogenic CO2 is subtracted from the plant totals; biogenic CH4 and N2O stay in.
EPA publishes lb per MWh. We convert to kg per kWh with the exact factor (1 lb = 0.45359237 kg). EPA's own metric workbook rounds to 0.4536, so our values sit a constant 0.0017% above it.
The reference year is the data year, 2023.

Data year: the eGRID data year, not the edition label.

What we import

eGRID2023 revision 2, released 2025-06-12, data year 2023.
The 27 eGRID subregions and the US national total: 187 factors.
Total output rates for all fuels, coal, oil, gas and all fossil fuels, and combustion output rates. A fuel rate is skipped where the region generates none of that fuel, so there are 22 coal and 26 gas factors.
Non-baseload rates are loaded but not served, carrying EPA's warning that they "should not be used for assigning an emission value for electricity use in carbon-footprinting exercises or GHG emissions inventory efforts".
Not imported: input rates per MMBtu, plant, unit, generator, state and balancing authority figures, and the NOx, SO2, mercury and ozone-season series, which are not greenhouse gases.
French names are machine translated.

eGRID prints generation only. Beside each all-fuel total output rate, for the 27 subregions and the United States, open-climate.ai adds three legs eGRID never printed, each as its own factor marked as an estimate: grid losses, the fuel chain (extracting, refining and transporting the fuel the plants burn) and the fuel chain of the losses, plus a delivered total. They are computed by a stated rule from eGRID's own grid gross loss and resource mix, with Ember's mix for the United States as a whole. They are rated low quality, and very low for Puerto Rico (PRMS), whose loss share is the national one. How the legs are estimated.

Licence

How this works

Open. The data is US government public domain. EPA states: "eGRID data is produced by the United States Environmental Protection Agency (EPA) under the public domain and is available for use both non-commercially and commercially." Commercial use and redistribution are allowed, with no ShareAlike. EPA suggests citing: "United States Environmental Protection Agency (EPA). (2025). Emissions & Generation Resource Integrated Database (eGRID), 2023. Washington DC: Office of Atmospheric Protection, Clean Air and Power Division."

What can I do with this data?

Credit line: United States Environmental Protection Agency (EPA). (2025). Emissions & Generation Resource Integrated Database (eGRID), 2023. Washington DC: Office of Atmospheric Protection, Clean Air and Power Division. https://www.epa.gov/egrid

us-gov-public-domain

Limitations

These are generation rates: eGRID's own values include no grid losses. The loss leg we add is an estimate; use it, or your own loss adjustment, for a consumption figure.
The fuel-specific rates are alternatives to the all-fuel rate, never parts of it. Do not sum them.
Some fuel rates are extreme and are EPA's own numbers: the oil rate reaches 19.0 kg CO2e per kWh in SPSO and 18.4 in RMPA, where oil units burn fuel for startup and testing with almost no generation.
Revisions restate every region. From revision 1 to revision 2 all 27 subregions moved, NYCW by -11.3%, with no marker.
EPA states no uncertainty for the rates.
Only eGRID2023 is loaded. EPA announced eGRID2024 for January 2026; it was not published as of August 2026.

Changelog

2026-09-25: estimated legs for grid losses and the fuel chain, and delivered totals, added beside the all-fuel rates.
2026-08-17: eGRID2023 revision 2 loaded.

Know a newer edition?

If eGRID has published an edition we do not serve yet, tell us where to find it.