Greenpixie and Google Cloud Carbon Footprint calculate the impact of your cloud usage in different ways. Their methodologies differ in approach, granularity, timeliness and data sources, so which one to use depends on the outcome you need and the use case in front of you.
How does Google Cloud Carbon Footprint work?
Google Cloud Carbon Footprint starts from the total electricity carbon footprint of each Google Cloud product and allocates it to customer accounts, so the figure is a share of Google's own data centre footprint and not a measurement of the customer's own resources.
The allocation works in four steps:
- Google records each machine's power draw and the internal service using it every hour, and spreads overhead such as cooling and power systems across the machines in the same way.
- They then multiply that energy by hourly Electricity Maps grid factors for the location-based figure and by annual factors for the market-based figure.
- Then they allocate each product's footprint to customers by SKU usage, weighting the SKUs within a product by quantity and list price, and by internal cost for services with no usage data.
- Finally they roll the result up to a monthly total, so no hourly figure reaches the customer.
Google's own researchers, Schneider and Mattia, write that "In carbon accounting, a cost-based approach is typically less desirable than a resource-based approach" and that customers "do not receive a signal about how switching from SKU A to SKU B can reduce their actual emissions".
Market-based emissions use annual factors and include Google's carbon-free electricity purchases, while location-based emissions ignore them. Google amortises equipment embodied carbon over 4 years and facilities over 20 years, and excludes downstream end-of-life emissions. Coverage is a published list of services which includes Vertex AI and the Gemini API. Services not on the list are not covered, and GPU instances and Marketplace software are not itemised on it. The export has one row per service, project, location and month, with no resource, SKU, label or usage quantity column.
Customers receive emissions in kgCO2e for scopes 1, 2 and 3 on location-based and market-based methods, by billing account, project, service, region and month, through a dashboard in the Google Cloud console and a BigQuery export. Per-customer energy consumption is available to customers participating in a private preview, and neither the dashboard nor the export contains a kWh or water figure. The tool is free, the BigQuery export incurs minimal fees, no set-up is needed, and "it can take up to 21 days for data of the previous month to become available".
What is Google Cloud Carbon Footprint good for?
Google reports scope 2 on both methods. The dashboard gives an annual total for the past 12 complete months.
Google publishes its covered services list, which includes Vertex AI, the Gemini API, Cloud TPU, Compute Engine, Kubernetes Engine and BigQuery. A BigQuery export lets you query the figures next to your other data.
What can't Google Cloud Carbon Footprint be used for?
Below are some common use cases our customers have told us they struggle to accomplish with the native tool.
| Use case | Why Google Cloud Carbon Footprint falls short | With Greenpixie |
|---|---|---|
| Confirming that rightsizing reduced emissions | You get one figure per service, project, location and month, and it changes when Google upgrades its carbon model. Scott Logic notes that although the data is matched hourly, the dashboard updates monthly. A 10% saving from rightsizing, for example, can be masked by a model upgrade that restates the same months. | Per resource, by hour |
| Measuring electricity per workload | The dashboard, export and schema contain no kWh column, so electricity per workload cannot be read from them. | kWh on every line item |
| Reporting emissions per customer | Software vendors who need to report what their product emitted for one customer can split the figure by project but not by tenant, product line or label. | By tag or project |
| Comparing Google Cloud with other cloud providers | The FinOps Foundation notes that Google's emissions are apportioned to each customer and reported as the customer's scope 3 emissions. Robin Lemesle observes that "those tools don't all measure the same things". | One method across AWS, Azure and Google Cloud |
| Planning a workload for lower emissions | The report describes what already happened. Google's region picker shows Google CFE%, the share of carbon-free energy consumed in a region averaged hourly, as an annual figure per region. That gives no granular view of a single workload or hour, and Google offers no forecast. The published cases of shifting compute to cleaner hours describe Google moving its own internal workloads with Electricity Maps forecasts, not a customer tool. | Hourly grid intensity per region |
| Choosing an architecture for lower impact | Because the weighting follows list prices, a cheaper SKU can look lower carbon without using less electricity. For idle projects, the Unattended Project Recommender estimates the location-based reduction from removing them. | Model a change from the rate card |
| Reporting water use | The dashboard, export and schema have no water column. | Two water columns per line item |
| Measuring AI emissions | Vertex AI and the Gemini API appear as service lines with no model or token dimension. Google allocates previously unallocated AI inference model emissions to the associated Google Cloud services, mainly Vertex AI. | Per instance, model and token type |
| Choosing between AI models | Choosing a model on its footprint needs energy per token by model and inference region, which Google Cloud Carbon Footprint does not provide. | Energy per token for 500+ models |
What Greenpixie adds
Greenpixie adds energy, carbon and water columns to every line of the billing data your FinOps team already works with, and leaves the annual disclosure to Google Cloud Carbon Footprint.
For AI, every GPU instance family is included, and the AI token methodology gives energy, carbon and water per token, across scopes 1, 2 and 3, for over 500 open and closed models in varying configurations. The methodology is built on hardware benchmarking and published as a white paper.
Finding which workloads emit the most
Greenpixie calculates at the individual SKU and rate code level, the same granularity as the Google Cloud billing export, joined on SKU code. It typically covers 99% to 100% of relevant SKUs by spend, and you can allocate carbon to a team, product or customer in the same way as cost.
Reading electricity in kWh per line item
Each line item carries total electricity in kWh.
Reporting water use
Each line item has two water columns, one for cooling water and one for the water used to generate the electricity.
Scheduling batch jobs and choosing regions by hour
Greenpixie applies grid carbon intensity at hourly resolution for the grid area supplying each region, so the same instance gets a different carbon figure at 2pm and 2am.
Modelling a change before making it
The Greenpixie API serves rate cards with energy, carbon and water per unit for each SKU. You join them to your own billing data on the SKU code at whatever refresh rate you want, up to every 6 to 12 hours, and swapping the SKU models a change before you make it.
Seeing the data inside FinOps tools
Greenpixie's energy, carbon and water columns are generally available inside Flexera, CloudHealth, Cloudability, and Umbrella.
How Google Cloud Carbon Footprint and Greenpixie fit together
| Question | Google Cloud Carbon Footprint | Greenpixie |
|---|---|---|
| What was our Google Cloud footprint last year, for the annual report? | Yes, both methods, not yet third-party assured | Supporting detail |
| Which projects and regions carry the most carbon? | Yes, monthly | Yes, down to the resource |
| How many kWh did this workload use? | No | Yes, per line item |
| How much water did it use? | No | Yes, two columns per line item |
| Did last month's rightsizing reduce emissions? | Not reliably, because of model upgrades and monthly totals | Yes, per resource, by hour |
| What would changing machine type or region do? | By region, as an annual average | Yes, from the rate card |
| When should this batch job run? | No | Yes, hourly intensity |
| What did our AI usage and GPU instances emit? | Service lines such as Vertex AI, monthly | Per instance, and per model and token type |
| Can we report it to a customer, per tenant? | By project, not by tenant | Yes, by tag or project |
FAQs
Which services does Google Cloud Carbon Footprint cover?
It lists 81 services. Google's known issues page says "Carbon Footprint does not cover all Google Cloud services", and Marketplace software is not on the list.
Does Google Cloud Carbon Footprint include scope 3?
Yes, it reports scopes 1, 2 and 3. The amortisation periods and the end-of-life exclusion are set out in the methodology.
Is Google Cloud Carbon Footprint assured?
Google's methodology states that the reports have not yet been third-party verified or assured. The product page cites a third-party review of the methodology, which covers the method and not the reported figures, so check with your auditor before relying on them in a disclosure.
How different are Greenpixie's and Google's numbers for the same project and period?
Google Cloud Carbon Footprint allocates a share of Google's reported footprint to you by usage and list price, while Greenpixie estimates what each resource drew from the grid, hour by hour, so the figures can vary a lot depending on what you run. Greenpixie provides an audit trail for every number, by resource ID, usage type and hour of the day.
Which carbon intensities does Google Cloud Carbon Footprint use?
Google uses hourly emission factors from Electricity Maps for location-based emissions and annual factors for market-based emissions, and falls back to a country-specific annual average where Electricity Maps data is unavailable.
Learn more
To learn more about Greenpixie's methodology and work with the data, take the Greenpixie Data Explorer course at the Greenpixie Academy.
For the other clouds, read AWS Sustainability vs Greenpixie and Azure carbon optimization vs Greenpixie. For an open-source option, read Cloud Carbon Footprint and its alternatives.
Measure your cloud emissions
See the energy, carbon and water behind your cloud bill
GPX Cloud adds energy, carbon and water data to AWS, Azure and Google Cloud billing data, line by line.
Sources
All statements about Google Cloud Carbon Footprint were checked against the sources below and are accurate as of Nov 10, 2026.
- Google Cloud Carbon Footprint product page. Google Cloud
- Carbon Footprint documentation. Google Cloud documentation
- Methodology. Google Cloud documentation
- Export Carbon Footprint data to BigQuery. Google Cloud documentation
- Data schema. Google Cloud documentation
- Covered services. Google Cloud documentation, updated October 2026
- Release notes. Google Cloud documentation
- Known issues. Google Cloud documentation, updated October 2026
- Region picker. Google Cloud
- Schneider and Mattia, Carbon accounting in the Cloud: a methodology for allocating emissions across data center users. Google research paper, June 2024
Third parties
- FinOps and sustainability teams collaborate to optimize carbon. FinOps Foundation, June 2024
- Tools for measuring Cloud Carbon Emissions, updated for 2025. Scott Logic, May 2025
- Carbon Dashboards in 2025: AWS vs Google vs Azure, a Reality Check. Robin Lemesle, August 2025
- Google data centers shift their computations to cleaner times and locations. Electricity Maps case study, undated
Greenpixie
- Methodology overview. Greenpixie documentation
- AI token methodology. Greenpixie documentation
- Greenpixie's AI Token Methodology: assessing the energy, water and CO2-eq impact of AI tokens. arXiv white paper
- Grid and regions methodology. Greenpixie documentation
- CUR enrichment. Greenpixie documentation
- Greenpixie API. Greenpixie documentation
- GPX Cloud. Greenpixie product page
- Flexera bolsters FinOps offering with Spot Eco, Ocean and Greenpixie partnership. Flexera press release, May 2025
- Greenpixie Data Explorer course. Greenpixie Academy

