Google Cloud - Google LLC

The yearly grid carbon intensity and carbon-free energy share of each Google Cloud region, published by Google from Electricity Maps' hourly grid data.

Commercial

Grid mix
Electricity

SpecialistOpen licence

Publisher's page Browse 198 factors

Factors

198

Values

645

One per year and method

Countries

28 regions, sub-national included

Edition

gh-49f3f26b

published 3 Dec 2025 · all versions

Last loaded

16 Oct 2026

Report a newer version

Overview

Google publishes the sustainability figures of its cloud regions on its region carbon page and, in machine-readable form, in the GitHub repository GoogleCloudPlatform/region-carbon-info: one CSV file per year, one row per Google Cloud region, with the region's grid carbon intensity and its Google CFE (carbon-free energy) share. Google derives the figures from hourly grid data by Electricity Maps.

We load the six yearly files for 2019 to 2024 as they stood at commit 49f3f26b (2025-12-03): 44 regions in 28 countries. Google has since added a 2025 file, which is not loaded yet. The latest year of each region is the value served by default.

At a glance

Publisher: Google LLC
Kind: Commercial
Scope: SpecialistOne category holds at least 5% of its factors: Electricity, with 100.0%. A generalist needs 4.
Home region: United States
Edition: gh-49f3f26b
Licence: Open licence (apache-2.0)

Open data

How this works

What open-climate.ai standardised

over the publisher's own fileHow we standardise

One category axis

198 of 198 factor values mapped to one category

Learn more 6 checks behind this

Coded regions

28 regions as ISO or registry codes

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

None is converted: every value keeps the publisher's GWP.

198 factor values left on the publisher's GWP

Learn more 7 checks behind this · 1 known limitation

7 more things standardised

Declared boundaries

5 boundary codes

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

Learn more 8 checks behind this · 1 known limitation

Estimated electricity legs

127 estimated legs the publisher does not print (grid losses, the fuel chain)

Learn more 8 checks behind this

Electricity mix

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

Learn more 5 checks behind this

Data quality

198 of 198 factor values rated on one quality tier

Learn more 7 checks behind this

Languages

English: 100.0% of factor values

German: 100.0% of factor values

French: 100.0% of factor values

Learn more 11 checks behind this

Traceable to the source

205 source rows archived

Learn more 5 checks behind this

Stable addresses

Slugs never break

Learn more

Audit checks

129 passed4 known limitations3 enforced when loadedlast run 22 Oct 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

Separate stages of one activity are linked as parts
Known limitation · 1 in this library
Why it matters Stages served as unrelated factors give no total, so you may use one stage and miss the others.
Values that exclude a carbon pool list the gases behind the total
Known limitation · 653 in this library · 180,272 in all libraries
Why it matters With no breakdown by gas, nothing can confirm that a fossil-only or biogenic-CO2-excluded total really leaves those pools out. The value rests on the publisher's word alone.
An activity's grouping key names only the activity
Known limitation · 1 in this library · 12 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.
Every factor we complete has all of its estimated parts
Known limitation · 5 in this library · 25 in all libraries
Why it matters If one part, such as grid losses, is missing where the others were estimated, a total built from them silently leaves that part out.

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 · 2 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
Known limitation · 1 in this library
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.
Every biofuel counted with its biogenic CO2 says how much
Passed
Why it matters Some publishers count the CO2 a burnt biofuel releases and others leave it out. Search tells the counting ones apart by their biogenic CO2 figure, so a factor without it would be offered to someone who asked to leave that CO2 out.
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.
No burden value hides a credit inside it
Passed · 348 in all libraries
Why it matters When a value that leaves biogenic carbon out is negative, that usually means a credit was subtracted inside it. Used as a burden, it lowers your footprint by a saving that is not yours to claim.

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
Passed
Why it matters Reporting now asks for AR6. Mixing AR5 and AR6 shifts methane-heavy totals by several percent.
CO2e totals leave out what their basis excludes
Passed
Why it matters A value's basis names the carbon pools its total leaves out. When the gas breakdown shows the total counting one of them anyway (biogenic CO2, land-use change, or biogenic methane on a fossil-only value), the label or the total is wrong.
Values that exclude a carbon pool list the gases behind the total
Known limitation · 653 in this library · 180,272 in all libraries
Why it matters With no breakdown by gas, nothing can confirm that a fossil-only or biogenic-CO2-excluded total really leaves those pools out. 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.

Estimated electricity legs

Learn more

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 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.
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.
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 estimated factor carries its description in each language
Passed
Why it matters An estimated factor is one we computed, not one a publisher printed. Its description says so and names the data behind it. Without it, you could not tell the estimate from a published figure.
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.
The text of each estimated electricity total matches its current figures
Passed
Why it matters The description of an estimated electricity total states its year, mix, quality and the parts it adds up. If those moved, the text would explain a different number than the one served.

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
Passed
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
Passed
Why it matters When the publisher rewords a label, an old translation can describe a different activity than the one priced.
Translations follow a corrected source text
Passed
Why it matters When we correct an English label, a French or German label translated from the old wording can still describe what the old wording said.
Recorded translations survive a reload
Passed
Why it matters A reload rewrites a library's labels; a translation we recorded and did not put back leaves that factor without a label in that language.
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 · 24 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
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
Why it matters For example, a purchaser price that leaves out retail or delivery. One of the two claims is wrong, and you cannot tell which.
No energy factor answers a question about packaging or recycling
Passed · 169 in all libraries
Why it matters Packaging and recycling credits belong to goods. On a value per kilowatt-hour they usually mean the boundary was read from the wrong kind of factor. A declared product sold per kilowatt-hour can still carry them, so each case is reviewed.
No factor value the publisher has withdrawn is still served
Passed · 14,762 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

One activity keeps one family across its units
Passed · 8 in all libraries
Why it matters When a publisher prints the same activity per kg and per kWh, the two factors belong to one activity family, with the unit as a choice. Filed as separate activities, they look unrelated, and nothing says they measure the same thing.
An activity's grouping key names only the activity
Known limitation · 1 in this library · 12 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 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.
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.
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.
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.
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.
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.
No total is served when one of its parts is withheld
Passed
Why it matters Where we add up a total from its parts and one part is rated too poor to serve, the total is held back with it. Otherwise you would get a figure that rests on a number we do not stand behind.
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.
Every district-heat factor says whether the network's heat loss is included
Passed · 2 in all libraries
Why it matters Heat is lost in the pipes between the plant and the building. Only the publisher can say whether a factor divides by heat produced or heat delivered, so a factor that leaves it unsaid is listed until its library's method is read.
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.
No estimate sits beside a total of unclear scope
Passed
Why it matters When the publisher does not say whether its total includes a stage, our estimate of that stage may count it twice. These cases are listed for review.
No estimate repeats a stage the publisher's total already includes
Passed
Why it matters If the publisher's figure already covers, say, grid losses, adding our estimate of those losses would count them twice and overstate your emissions.
Every factor we complete has all of its estimated parts
Known limitation · 5 in this library · 25 in all libraries
Why it matters If one part, such as grid losses, is missing where the others were estimated, a total built from them silently leaves that part out.
We only estimate for publishers whose rule allows it
Passed
Why it matters Some publishers print every part themselves, or are deliberately left as they are. An estimate added to them would mix our numbers into theirs, against the rule set for that library.
No estimated total competes with a published one
Passed
Why it matters Where the publisher prints a total for the same activity, region and year, an estimated total beside it would give you two answers to the same question.
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.
The text of each fuel supply-chain estimate matches its current figures
Passed
Why it matters Its description states the year, the figures, the ratio and the quality behind the estimate. If those moved, the text would explain a different number than the one served.
No fuel supply-chain estimate is rated above what its method allows
Passed
Why it matters Each way of estimating a fuel's supply chain has a highest rating it can earn, and an estimate never outranks the combustion figure it builds on. A better rating would lead you to trust it more than it deserves.
Every fuel 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.
Every fuel eligible for a supply-chain estimate is classified
Passed
Why it matters The supply-chain estimate depends on which fuel is burned. A fuel nobody has classified gets no estimate, so you would miss that part of its emissions without knowing why.
No fuel estimate is served where the publisher printed the supply-chain figure
Passed
Why it matters When the publisher states the figure itself, theirs is the one to use. An estimate beside it would give you two answers to the same question.
No supply-chain estimate is served for a fuel we deliberately left out
Passed
Why it matters Some fuels are left out on purpose, for instance when no published supply-chain figure fits them. An estimate on one of them would be a number we decided not to stand behind.
Every fuel supply-chain estimate still matches the figures it was computed from
Passed
Why it matters The estimate scales the publisher's combustion figure by a supply-chain ratio taken from other published data. When either is revised or withdrawn, the estimate is out of date until it is recomputed.
Per-gas values are in CO2e
Passed
Why it matters Each gas line is stored as kg CO2e, so the lines add up to the total. A line stored as a raw gas mass under-states methane and nitrous oxide 27 to 273 times.
Every tagged gas has a known GWP
Passed
Why it matters A kilogram of one named gas is restated in AR6 with that gas's own GWP. A tag the GWP table does not carry would leave the value unconverted, or convert it with the wrong number.
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.
Every publisher has a rule on whether we estimate its missing parts
Passed
Why it matters For electricity and fuels we can estimate parts a publisher leaves out, such as grid losses or the fuel supply chain. Without a rule, a missing part could be a gap or a deliberate choice, so nothing is estimated until one is set.
Factor descriptions describe the factor, not the whole library
Passed · 2 in all libraries
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.
No fossil electricity mix has a zero fuel supply chain
Passed
Why it matters Electricity with fossil emissions always has a supply chain behind it: extracting and transporting the fuel. A zero there means the chain was priced from the wrong mix. Green power is the exception: its chain covers only biomass, and is a real zero on a grid that burns none.
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.
No electricity or heat factor answers network losses against its stage
Passed · 4 in all libraries
Why it matters A figure per unit delivered to the meter or the building includes what the grid or the heat network loses on the way, and one per unit generated at the plant does not. A factor whose library says the opposite of its stage is listed, so the stage can be corrected and the comparison with other grids stays fair.
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.
Only a library cleared for it lists factors without their number
Passed
Why it matters Some publishers' numbers reach us after their factors, so we list the factor and show its value as withheld until the number arrives. Every other library must ship each number: a listed factor without one there is a loading error.
Product footprints headline fossil carbon, like EPDs
Passed
Why it matters EPDs headline fossil carbon and keep biogenic and land-use carbon apart. A product footprint that headlines the net total instead can differ by a few percent, so two steels or two devices no longer compare like for like.
No factor description is too long to display in full
Passed · 5 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.
The library-wide answers on what a factor covers are up to date
Passed
Why it matters Some questions, such as whether a figure includes transport, are answered once for a whole library. If the stored answers fall behind, a factor's details can tell you something we no longer state.
Every library-wide answer applies to at least one factor
Passed · 3 in all libraries
Why it matters An answer about a category or stage the library no longer covers changes nothing you see. It is listed so it can be removed.
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.
Each library's current edition is the one its values come from
Passed
Why it matters Library pages, exports and search read which edition is current from one flag, the factors from another. If the two disagree, a search can serve one edition while the export names another.
No two editions of a library share a release date
Passed
Why it matters The newest edition is picked by its release date. If two editions share one, the pick falls back to the edition label, where 23.6 reads as newer than 23.11, so older numbers can be served as current.
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 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.
Every conservative value carries the same label
Passed
Why it matters Some publishers print each value twice: a typical value and a conservative one, marked up for regulatory use. One shared label lets you pick either across libraries; a second spelling would hide some conservative values from that filter.
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.
Every factor is filed under the most specific category its source allows
Passed · 4,552 in all libraries
Why it matters Some factors sit in a broad category because their source covers several narrower ones. They are listed so a finer mapping can place them more precisely where the source allows it.
Every factor has a category
Passed
Why it matters A factor with no category drops out of every category filter and comparison. Without this check, a library with no category mapping would load unlabelled, and nothing would say so.
Every categorised factor has a GHG Protocol scope
Passed · 2 in all libraries
Why it matters Without a scope, you cannot tell whether the factor belongs in Scope 1, 2 or 3 of your inventory, and you have to place it yourself.
Single-gas values have their AR6 version
Passed · 8 in all libraries
Why it matters A kilogram of one refrigerant is worth its GWP, so it can be restated in AR6 exactly. Blends and untagged gases stay on their published vintage, which can move a leak's footprint by several percent or more.
No factor answers a question that does not arise for it
Passed · 11 in all libraries
Why it matters Some questions only make sense for some kinds of factor. An answer where the question should not arise is either misplaced, or a sign the kind is too coarse for that factor, so each case is reviewed.
No part is larger than the total it belongs to
Passed
Why it matters A part of a total cannot exceed it unless another part is negative. Where one does, either the total or the part is misprinted, and the two give different footprints for the same purchase.
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.
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.
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.
Every device total that includes its use also gives the manufacturing share (embodied emissions)
Passed · 112 in all libraries
Why it matters A device footprint that includes years of electricity use is not the manufacturing number you need for a purchase, and if you also count the device's electricity you count its use twice. Devices whose publisher prints no use share are listed as known gaps.
No plug-in vehicle supply-chain estimate is rated above what its method allows
Passed
Why it matters The supply chain of the electricity a plug-in vehicle draws is estimated from the vehicle's own figure and four grid figures. That estimate has a highest rating it can earn, and it never outranks any figure it is built from. When one of them is withheld, so is the estimate. A better rating would lead you to trust it more than it deserves.
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 · credit the publisher

Your rights

Open licence · apache-2.0

Use it to calculate my own footprint: Yes
Publish my footprint results: Yes, if
you credit the publisher
you say what you changed
you imply no endorsement by the publisher
Share the file with my customers: Yes, if
you credit the publisher
you say what you changed
you imply no endorsement by the publisher
Put the factors in a product I sell: Yes, if
you credit the publisher
you say what you changed
you imply no endorsement by the publisher
Modify it or combine it with my own data: Yes, if
you credit the publisher
you say what you changed
you imply no endorsement by the publisher

Named licence, checked on 14 Oct 2026

Apache License 2.0 §2 grants a perpetual, worldwide, royalty-free copyright licence to reproduce, prepare derivative works of and distribute the Work, commercial use included; §4(a)-(d) require a copy of the licence, a notice in each modified file stating the change, the retained notices and any NOTICE text (the repo has none); §6 grants no trademark rights. Applied by Google to region-carbon-info (google).

Credit line

Google Cloud region carbon data (GoogleCloudPlatform/region-carbon-info), Apache License 2.0. Grid carbon intensity derived by Google from hourly grid mix data by Electricity Maps. Not assured. Normalised by open-climate.ai, https://open-climate.ai/factors/libraries/google/ (CC BY 4.0)

Not legal advice: the publisher's terms prevail.

Full terms Where this answer comes from

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

198factors

Electricity198100.0%

Click a slice to see what is under it. A name opens its category page; its swatch hides it from the ring.

By boundary

198factors

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	Factor	Region	Boundary	Unit

Versions

How this works

Version	Published	Loaded	Status	Source
gh-49f3f26b	3 Dec 2025	16 Oct 2026	Served	Source

Methodology

How this works

From 2021 on, the grid carbon intensity is, in Google's words, "the average operational gross emissions per unit of energy from the grid": the emissions of the power plants as they run, per kWh of grid electricity. We file it on the generation boundary.
The 2019 and 2020 files print a lifecycle grid carbon intensity instead, which covers the plants' whole life cycle. We file it as a separate factor on the energy life-cycle boundary. The two eras measure different things, so each region has one factor per era and the series is never read as one.
Google prints grams of CO2e per kWh; we divide by 1,000. Frankfurt (europe-west3) reads 275.82 g in 2024, served as 0.27582 kg CO2e/kWh. In 2024 the values run from 0.00273 (Stockholm, europe-north2) to 0.679 (Mumbai, asia-south1).
Grid mix and Scope 2 method: we read the values as consumption-based and location-based, an average over the electricity used in the region's grid. This is our reading of the Electricity Maps provenance; Google does not say.
CO2e basis: we read the values as fossil emissions only, the usual convention for operational grid factors, which count no operational CO2 from biomass. Google does not say.
Global warming potential: Google names no GWP set anywhere, so the vintage is unverified. Electricity Maps' methodology says it uses "the 2014 IPCC Fifth Assessment Report emission factors", which names a source of emission factors, not a GWP set.
Google CFE is the average share of hourly carbon-free energy consumed in the region, counting the clean energy Google buys there. We keep it beside each value it was printed with, as a qualifier named google_cfe_share. It is not a market-based factor and never a zero: we never multiply the intensity by the carbon-free share, and we derive no market-based, green or residual value from it.
The year of a value is the calendar year of grid data its annual average covers, not the year Google published it.

Data year: the calendar year of the hourly grid data each region's annual average covers (the file year), not the year Google published it.

What we import

The six yearly files: 205 rows, 71 factors and 205 values, each number read as printed. No row was skipped. 44 operational factors carry 154 values (2021 to 2024), 27 life-cycle factors carry 51 values (2019 and 2020). The share of carbon-free energy rides on the 186 values that print one.
Each factor is named after its region, with Google's city and region code ("Grid electricity - Frankfurt, europe-west3"). The description of an operational factor is Google's definition of the metric. The French and German activity names reuse existing translations, the city and region code stay as printed. The paragraph on what each factor covers and when to use it is written by language models.
Geography is the country: Tokyo and Osaka both read Japan, and the region code in the name tells them apart.
Not imported: the 2025 file, the net carbon emissions column of the early files (all zeros, removed by Google in 2023), and the copy of the data in Google's BigQuery public datasets, whose terms we have not verified.

The operational intensity is generation only. Beside each of the 44 operational factors, open-climate.ai adds three factors Google never printed, each marked as an estimate and rated low quality: the fuel chain (extracting, processing and transporting the fuel the plants burn), the electricity lost in transmission and distribution, and the fuel chain of that lost electricity. For Frankfurt in 2024 they read 0.0561, 0.0153 and 0.0031 kg CO2e/kWh. That makes 127 estimated factors with 448 values. Hong Kong gets none (no loss statistic and no fuel mix), Mexico's 2024 value gets the fuel chain only (no loss statistic), and the 2019 and 2020 life-cycle values need none, since they already cover the chain. How the legs are estimated.

No total adds them up yet: Google's values name no GWP set while the fuel-chain estimates follow IPCC AR5, and we do not add numbers whose GWP basis differs or is unknown.

Licence

How this works

Open. The repository's LICENSE file is the Apache License 2.0, and it covers the data files. It grants "a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works". Its conditions: pass on a copy of the licence, state the changes you made, and keep the copyright and attribution notices (the repository has no NOTICE file). The figures derive from Electricity Maps data. Google is the author of the published aggregate and grants it under its own licence; Electricity Maps' own terms bind its licensees, which is our reading, not a statement from either company. Attribution: "Google Cloud region carbon data (GoogleCloudPlatform/region-carbon-info), Apache License 2.0. Grid carbon intensity derived by Google from hourly grid mix data by Electricity Maps. Not assured." Last verified 2026-10-14.

What can I do with this data?

Credit line: Google Cloud region carbon data (GoogleCloudPlatform/region-carbon-info), Apache License 2.0. Grid carbon intensity derived by Google from hourly grid mix data by Electricity Maps. Not assured.

apache-2.0

Limitations

Google's 205 values are rated low: the data is self-published, revised in place, and carries no uncertainty and no split by gas. Two of them are problematic and withheld: Montréal (northamerica-northeast1) prints 0 g in 2021 and 2022, a rounding rather than a zero, before 2 g in 2023 and 5.48 g in 2024. The 448 estimated values are rated low, six of them problematic and withheld with the Montréal values they rest on. How quality is rated.
Use an operational factor for a location-based Scope 2 figure for a cloud workload in a given region. Do not read the carbon-free share as a market-based factor: it is an hourly matching share, not a linear discount.
The life-cycle values of 2019 and 2020 are not comparable with the operational values from 2021 on.
Google revises past years in place: Jakarta's 2019 value moved from 772 to 647 g in 2021, Melbourne's 2021 value from 746 to 521 g in 2022. Only the edition named above is loaded.
Google's region page, read on 2026-10-14, cites an assurance letter for the Electricity Maps data. Our attribution says "Not assured.", as the page of the loaded edition did; we will reword it with the next edition.

Changelog

2026-10-14: the 2019 to 2024 files loaded (commit 49f3f26b), with the estimated fuel-chain and loss factors beside the 2021 to 2024 operational intensities.

Highlighted factor pages

A selection of Google Cloud factors, with each value, boundary, source and derivation.

Electricity Grid electricity

Grid electricity - Dallas, us-south1 US · kWh · Upstream of transmission and distribution losses
Grid electricity - Stockholm, europe-north2 SE · kWh · Generation
Grid electricity - Melbourne, australia-southeast2 AU · kWh · Generation
Grid electricity - Hong Kong, asia-east2 HK · kWh · Generation
Grid electricity - Warsaw, europe-central2 PL · kWh · Upstream fuel
Grid electricity - Oregon, us-west1 US · kWh · Generation
Grid electricity - Eemshaven, europe-west4 NL · kWh · Upstream of transmission and distribution losses
Grid electricity - Tel Aviv, me-west1 IL · kWh · Upstream of transmission and distribution losses

Know a newer edition?

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