Last week, we announced PCF Studio, our new tool for manufacturers to quickly and reliably calculate product carbon footprints.
PCF Studio provides a clear cradle-to-gate PCF result, with emissions broken down across materials, manufacturing, and freight. In turn, you can deliver the carbon visibility your customers need across your product range.
Features of PCF Studio:
This feature is currently in beta. Contact our sales team to get access →

Sometimes, you might need to change some of the processes in your PCF calculation, for example if you change supplier, start using a different energy source, or new data becomes available. To handle this, version control has been introduced in the PCF API so you can update your PCF. You can now add an optional product_id parameter in the request, which signifies an updated estimation of the given product. Each estimate response has a version_id field, which serves as the identifier for this specific estimation.
The new list products endpoint gives you the option to retrieve a list of PCFs previously calculated with Climatiq. The endpoint returns the latest version of each product estimated, which is stored in Climatiq, and ordered by date and time.
You now also have the option to manually specify the data quality indicators (DQIs) for your PCF. As Climatiq cannot know how well a given emission factor matches your processes, it is recommended that you override the data quality rating when you know it’s a good match. You can then adjust the score based on technological representativeness, geographic match, and time accuracy of the emission factor (e.g. whether the correct year is used). This gives you more flexibility and control to get a more representative data quality rating.
Additionally, the location parameter for heat & steam manufacturing processes is now optional and defaults to the manufacturing location.
This feature is still in private beta. Reach out to our sales team to get access →
Previously, you had to manually add transport modes for each leg of your freight journey, which is a difficult task when granular activity data is missing. The underlying logic in Freight v3 has now been improved so that only specifying start and end location is enough for automatic routing to provide a plausible route. In this case, Climatiq can use heuristics to determine a likely transportation mode.
To perform automatic routing and transport mode selection, Climatiq will intelligently pick between sea transportation, which is the most common type of shipping, and road transportation for shorter routes. If Climatiq determines that sea shipping is the most likely transportation mode, but your locations are not close to sea ports, road legs will automatically be added to transport the cargo to the closest port. Read more here →
Freight v3 also supports the new transport mode inland_waterways. Current supported options include Duisburg, Antwerp, Rotterdam, and Genk. This adds new options for you to more accurately reflect your freight journeys.
Data release 31, including new additions:
And updates:
AND data release 32, including new additions:
And updates:
For a full overview of data updates, please visit our data release notes.
/suggest now returns a notice for each suggestion, e.g. to tell you whether region fallback was used to find that suggestion
Our product carbon footprint (PCF) API lets you integrate product-level emission insights into your platform to estimate PCFs at scale.
New updates to the PCF API include:
metadata field is added at the top-level and on each manufacturing component to allow for recording of data like internal IDs, qualitative statements, etc.location is now optional for input componentsThis feature is currently in private preview. Contact our sales team to try it out →
We have significantly improved the user experience in Climatiq for Google Sheets, with revamped UI and simplified formula workflows — following on from last year’s updates in Climatiq for Excel.
Some of the features of the add-on:
For existing users of Climatiq for Google Sheets, you don’t need to do anything — the add-on will automatically update to the newest version.
For new users, you can download it here →
If you’ve logged into your Climatiq account this week, you probably noticed we’ve made some big changes to how the dashboard looks.
We’ve restructured the navigation and improved the look and feel of our interface to streamline your access to Climatiq’s data, unifying the features you need in one easy-to-navigate workspace that allows you to source emission factors and deliver calculations.
It’s where you can:
(If you look closely, you’ll see a lot of tools now live in Data Studio. Keep an eye out for some exciting features coming there soon.)
Data release 30, including new additions:
And updates:
For a full overview of data updates, please visit our data release notes.
We recently released version 2 of our Excel add-in, with a significantly improved user experience through an easier installation flow, revamped UI, and simplified calculation workflows. If you're a carbon accounting professional working with emissions data in spreadsheets, V2 makes it easier than ever to use Climatiq calculations and data directly within Excel.
Some of the features of the add-in:
This lets you transform business activity data into compliant CO2e estimates without leaving your existing spreadsheets or learning a new tool.
For existing users on v1 of the Excel add-in, you need to migrate to the new version before 1st March 2026 to ensure there are no interruptions to your workflows.
Download the new add-in from Microsoft Appsource here →
Watch our how-to series on YouTube to learn how to use the add-in →

Our newest feature preview allows you to get emission factor matches and calculate emissions by simply uploading a .csv of your business activity data. You can even customize results by filtering for premium data sources, dataset, and LCA activity for more precise and targeted results, or calculate emissions across energy usage, business travel, and freight shipments.
Manual emission factor mapping creates huge headaches and swallows hours of carbon accountants’ time. Our new tool saves this time by automatically matching your business data to the right emission factor—just drag and drop the .csv file.
This makes it easier and faster than ever to access our emission factors and calculations—you don’t even need to search the database or apply a factor!
For automatic calculations, simply drag and drop your file to calculate emissions for electricity, heat and steam, fuel consumption, freight shipments, and business travel based on spend or distance.
While in its preview phase, all Climatiq users can calculate or match up to 200 rows of business data for free—including community users.
You can try it out by logging into your Climatiq account and clicking on the links under “Data Studio” in the left sidebar.
.gif)
Previously, when using any endpoint that accepts a location, you had to explicitly specify whether your location was a LOCODE {location: {locode: "DE-BER"}}, an IATA code {location: {iata: "JFK"}}, or a free-text {location: query: "Berlin, Germany"}}.
We’ve now simplified this so you can simply pass in a string as the location parameter, and we'll automatically detect the type. For example, the above examples would be {location: "DE-BER"}, {location: "JFK"}, and {location: "Berlin, Germany"}, simplifying your workflows.
This works in all endpoints where location is used to map to a fitting emission factor.
Data release 28, bringing us to over 639,000 factors, including:
Plus data release 29, including new additions:
For a full overview of data updates, please visit our data release notes.
Our new product carbon footprint (PCF) API lets you integrate product-level emission insights into your platform to estimate PCFs at scale, allowing manufacturers to meet their customer and regulatory requirements.
The PCF API includes:
For software platforms, the API cuts the complexity of PCFs so you can support calculations in a few sprints rather than a few quarters. Check our website and API documentation to learn more about our new PCF tools and what they can unlock for development teams.
If you’re a manufacturer who would be interested in exploring PCF calculations beyond our API, you can get in touch here about our co-innovation program.
See a screenshot from Celonis’ PCF solution, which is built on top of the PCF API, below.

We’ve made major updates to Autopilot, hugely expanding its breadth and usability for mapping activities to emission factors. The latest version, preview-4, adds support for all reporting scopes, expanding its capabilities beyond procurement, and allows multilingual inputs.
This means you can now use Autopilot for any emission factor matching, cutting the time and investment needed to map activity data and deliver full scope reports.
preview4 limits its search to scope 3 emission factors by default; we’ve therefore added a new scopes filter to support scope-specific filtering. You can expand your search to all scopes by adding scopes: ["1", "2", "3"] in your request, or scopes: ["3.1", "3.2"] to filter by scope categories. We now also display the scopes field for emission factors returned by the /suggest endpoint as well.
Autopilot now also supports multilingual inputs, identifying the language of incoming queries to expand its usability and the accuracy of results.
The languages with full support are Bulgarian, Czech, Danish, Dutch, Estonian, Finnish, French, German, Hungarian, Irish, Italian, Latvian, Polish, Slovak, Spanish, Swedish, and Mandarin Chinese. Note that Autopilot still accepts inputs in other languages, but the model has not been optimized to support them and therefore match quality may be compromised.
Read more about Autopilot here →
Climatiq users with an EXIOBASE subscription can now view emission factor values in Data Explorer—meaning it can act as your single source for emission factors.
If you have a subscription for this dataset, simply log in to Data Explorer and use the Source filter to start browsing factors (the ones in the screenshot below of course aren't the real values).
If you’re interested in purchasing the latest EXIOBASE data through Climatiq, you can reach out to our sales team for more info →

The Energy endpoint automatically calculates the greenhouse gas emissions associated with consumed energy based on relevant emission factors. The most recent version, v1.2, now incorporates the latest data version, data release 27. This expands coverage for new regions, including Singapore, updates existing data, and brings improvements to quality. See changelog here →
V1.1 is now deprecated, with a removal date set for November 2026.
Read more about the Energy endpoint →
Data release 27, including new additions:
For a full overview of data updates included in this release, please visit our data release notes.
Intermodal Freight v3 is the most up-to-date version of the freight endpoint, and is fully compliant with the latest version of the GLEC Framework (v3.1).
Freight v3 now falls back to Google Maps for geocoding locations if HereMaps fails to find the location, improving reliability. If you have journeys through countries such as China, Korea, Argentina, Colombia, and others where routing was previously challenging, the new version should have a significant impact on routing accuracy.
v2 and v3-preview1 have now been deprecated, the former after one year of support and the latter after three months. The only change from v3-preview1 to v3 is a fix to recognize transition point type overrides. If you use v3-preview1, you should therefore be able to simply change the URL you are using to use the latest version.
Intermodal Freight v1 has reached its end-of-life. Any remaining users must therefore move to a newer version; anyone still using v1 has the perfect chance to hop straight over to v3. The upgrade from older versions is explained in the changelogs →
Read more about the Intermodal Freight endpoint here →
Every emission factor in Climatiq now comes with scope information, making it easier than ever to find and use the right data that corresponds to the scope you need. Many factors are linked to multiple scopes, helping you understand exactly where and how they can be applied across your value chain.
You can now search for emission factors by scope directly through the Search API, whether you’re looking for scope 1, 2, or 3 data, including individual scope 3 categories such as 3.1. This makes it simpler than ever to align your calculations with the GHG Protocol and meet your reporting needs.
This is currently available via the Search endpoint, and will be available in Data Explorer soon.
Suggest and One-shot Estimate have two new optional filters to help you narrow down the results you receive in Autopilot preview4. This makes it easier to filter out paid datasets if you don't have a license, are looking for results from specific datasets, or only want to receive private emission factors in Autopilot. The new filters:
source_dataset allows you to select a list of datasets to include; source is the name of the dataset provider and dataset is the dataset and version provided by that source e.g. "source_dataset": ["EXIOBASE 3.10 - Industry"]access_type allows you to filter between dataset types (input can be public, premium, or private, where public includes openly available datasets, premium refers to paid datasets (ecoinvent, EXIOBASE 3.10, and IEA), and private is for emission factors you have uploaded yourself) e.g. "access_type": ["public"]Both of these filters accept a list of values.
Read more about Suggest and One-shot Estimate here →
Both Autopilot and Procurement now use industry-specific and country-specific inflation rates for 2023 and 2024.
As spend-based factors are usually published a few years after the time period they cover, it is best practice to adjust your expenditure amount for inflation to match the emission factor's year. With the addition of inflation data for 2023 and 2024, Autopilot and Procurement can now use the most recent data to automatically make inflation adjustments in spend-based calculations.
This means you may see your numbers shifting as estimates now use the most recent, and therefore accurate, inflation data.
Learn more about inflation adjustment →
We’ve released a new version of the Travel endpoint, Travel v1-preview3, which includes the latest 2025 flight and vehicle emission factors from BEIS.
Travel v1-preview3 also supports "Premium Economy" as an option for flight classes. This offers you extra customizability in your requests to more accurately reflect the type of journey taken.
Data version 26, including new additions:
For a full overview of data updates included in this release, please visit our data release notes.
Inflation adjustment for spend-based estimations
As spend-based factors are usually published a few years after the time period they cover, using this data on new spending won't give you an accurate result. It is therefore best practice to adjust your expenditure amount for inflation to match the emission factor's year. However, this step is often skipped due to its complexity. To simplify the process, Autopilot can now handle inflation adjustment for you automatically.
To use this feature when making estimations using a money emission factor, include an inflation_adjustment parameter in the request. Inflation will be calculated using the emission factor's region and the spend_year or year in the request. This is available through either the Estimate or the One-shot Estimate endpoint. Inflation adjustments are calculated using country-specific inflation data using rates provided by the World Bank.
This is a backwards compatible update to the preview4 release—there are no breaking changes. Find the documentation here →
EXIOBASE 3.10 in Autopilot
The latest data from EXIOBASE is now available in Autopilot, offering you access to the most up-to-date spend-based data through our AI-powered search. EXIOBASE 3.10 includes spend data up to 2022, with now-casts to 2024.
You can get these premium emission factor matches via the Suggest endpoint. To use them via Estimate or One-shot Estimate, you need to contact your customer success manager for access →
In order to better serve the thousands of people who use our Data Explorer every day, we’ve made some new usability updates.
You can now filter search results by “Lifecycle Activity”, allowing you to more easily find emission factors that match the specific phase within the process or product lifecycle that you want to measure. For example, for spend-based estimates you can select “cradle-to-gate” to receive factors which incorporate all emissions from the beginning of the product’s lifecycle through to when it leaves the factory gate.
We’ve also added a “Copy” button to emission factor results pages, which allows you to copy the emission factor as plain text, JSON, or directly into an Excel spreadsheet.
This follows last month’s update to improve search function and results, plus our recent introduction of AI search powered by Autopilot. Try the new updates here →
.gif)
The Intermodal Freight API endpoint generally routes a shipment following the most likely and commonly used passage. However, actual shipping routes may differ from standard pathways due to operational decisions. Examples include avoiding the Suez Canal due to security risks, bypassing the Panama Canal during capacity constraints, or routing around areas with piracy concerns or seasonal weather disruptions.
You can now use the parameter avoid_zones to exclude selected passages from sea routes in Intermodal Freight. This allows you to use routes that more accurately reflect your actual shipments. Find out more and see the list of passages you can exclude in the docs →
Climatiq’s database includes thousands of emission factors from many sources. In most cases, these cover what is needed for emissions calculations. Where there are specific data gaps or our customers require tailored calculations, Climatiq has now developed a small selection of emission factors called Climatiq Composite. This ensures the database can meet customer needs, providing the most comprehensive collection of emission factors available.
The new emission factors are based on UK Government data and cover three use cases:
You can explore the new factors here or read more in our Methodology Hub →
Data version 25, including new and existing datasets:
For a full overview of data updates included in this release, please visit our data release notes.
model name, model_version, and the data_version used by the model in Suggest and One-shot Estimate responses. This means you can now identify the model and data version used to generate the match and prioritize results from newer versions when they become available. There are also improvements to model accuracy.
The Cloud Computing endpoint will be deprecated in September 2026. You can replace the emission calculations from this endpoint using the energy feature, plus you will still be able to access any cloud computing emission factors as usual via Climatiq →
If you require any support transitioning from this endpoint, please reach out to your customer success manager.
The latest version (preview-4) of Autopilot, our AI-powered emission factor matching engine, comes with multiple updates to simplify searching, provide better matches, and enhance usability.
Private emission factors
Autopilot can now return your private emission factors among its matching results. This allows you to use Autopilot as the single source of reference when considering which emission factor to use for scope 3 calculations, simplifying the search for a fitting factor.
Please note that in order to use this, you need to re-upload your private factors (plus relevant metadata); emission factors uploaded in the past will not be supported by Autopilot.
To activate this feature, contact your customer success manager →
Updated evaluation scores
We've streamlined how you evaluate AI-generated emission factor matches. Previously, our system provided two separate scores (confidence_score and similarity_score) which required interpretation.
In this release, we've replaced both with a single, actionable label field. This simplified system gives you clear guidance on what to do next:
Accept indicates high match confidence — the suggested factor is ready to useReview means the match is likely relevant but should be verified before useThis makes it easier to act on AI recommendations while maintaining accuracy in your carbon calculations. As we continue improving our matching models, this simplified approach will help you work more efficiently with increasingly accurate suggestions.
Renamed domain to model
We have also renamed the domain parameter in Autopilot to model.
The updates above are available with the new preview-4 release. Find the documentation on Autopilot preview-4 here →
Climatiq’s custom mapping tool allows users to map any identifier they choose to a Climatiq activity ID, which can then be used for emission calculations via the custom mapping endpoint.
Previously, custom mappings only worked with our standard datasets. It now accepts estimations for items mapped to premium datasets such as EXIOBASE or ecoinvent.
Data version 24, including new data:
For a full overview of data updates included in this release, please visit our data release notes.
The latest EXIOBASE release, v3.10, is now available via Climatiq as a premium data source. This version updates underlying economic tables with core data up to 2022 and now-casts up to 2024 for the most up-to-date emission factors and improved accuracy.
EXIOBASE is the leading provider for spend-based emission factors, and is codeveloped by Richard Wood—a member of the Climatiq Scientific Advisory Board.
Explore EXIOBASE 3.10 here →
Please contact your Climatiq customer success manager if you'd like to access the new version.
(NOTE: version 3.8 of EXIOBASE will remain available.)
To simplify configuration and improve usability and matching results, we’ve merged our two existing Autopilot ML domains into the General model.
This means you no longer need to select between our General or Manufacturing domains, making it easier to set up Autopilot for any use case.
If you currently use the General domain, no action is required since you’ll automatically have access to the new updated model. The Manufacturing domain will remain available for the time being, and you can switch to General through the domain parameter settings.
Additionally, we’ve enabled regional fallback logic in Autopilot. For example, Belgium will fall back to Europe, enabling you to get a fitting match if there is no emission factor specifically for Belgium. To enable region fallback, set “region_fallback” to “true” in your API request.
Try the updated version of Autopilot in our Data Explorer or through our API.
We’ve updated our Energy API to version v1.1. This release improves calculation accuracy through updated methodology, enhances coverage with 20 new countries (80 in total), and includes the most recent emission factors available, now covering up to 2024. To improve transparency, this update introduces new notifications for production mix emission factors, and exposed calculation constants in the source trail.
This is the first minor version release of a Climatiq API. While the API schema is backwards-compatible, calculation results in the new version may differ due to changes in data and methodology.
You can opt in to use the new version by updating the API URL in your implementation.
Find the documentation here →
Data version 23, including new datasets:
Plus additions and updates to existing datasets:
For a full overview of data updates included in this release, please visit our data release notes.
(Climatiq.Search_ByID(id)). This returns the relevant metadata and helps with auditing.This new AI-powered experience, currently in beta, makes finding emission factors in the Data Explorer easier, more intuitive, and less dependent on knowing the exact search terms.
Powered by our AI recommendation engine, Autopilot, this feature suggests relevant emission factors for purchased goods, even from generic inputs, brand names, or ambiguous product terms. Instead of relying on exact keyword matches, it uses machine learning and Natural Language Processing to interpret your input and return better matching results.

Try it now in the Data Explorer →
Autopilot, which currently works best for physical goods in Scope 3.1, automates the mapping of business data to emission factors and can easily be embedded in your own tools via API. Siemens SiGREEN, launched their AI-driven emissions estimator with Autopilot in under six weeks.
You can also use Autopilot directly in spreadsheets with our Excel add-in.
We have released a new version of our Freight API, delivering more reliable freight emission calculations across geographies.
It uses the latest emission factors provided in version 3.1 of the GLEC framework, which includes updated and new emission factors for all transport modes and new factors specific to road transport in China. To support this, we've added API parameters that let you define China-specific settings within the leg_details object, enabling more accurate emission estimates for transport activity in the region.
This version also introduces a new rail routing mechanism that improves route accuracy, extends geographic coverage to six continents, and avoids generating routes where none exist (e.g., across impassable terrain).
Our Freight API is aligned with the ISO 14083 standard and GLEC framework developed by the Smart Freight Centre, so you can confidently build solutions that meet industry accounting standards.
Read more about the changes here →
The IEA (International Energy Agency) provides two types of emission factors: provisional and final. Provisional factors are estimated values that provide an early indication of emission intensity before final, verified data, becomes available for a given reporting period.
For users with licensed IEA data, we offer the option to use provisional factors in the energy endpoint via a new API parameter (allow_iea_provisional). A notice is now shown when provisional factors are used. This enhancement improves calculation consistency across reporting periods and increases transparency about the type of emission factors used in your energy calculations.
When opting out of provisional factors, the calculation engine will use IEA's final factors for the requested year, or the most recent available final data if that year hasn't been published yet.
See documentation for details →
Data version 22 includes the following datasets:
Data version 21 is our most significant data release to date. We’ve expanded our emission factor database to over 190,000+ emission factors, adding 100,000+ new entries from 12 sources across 16 sectors.
These additions expand coverage for scope 1, 2, and 3 emissions, support both activity-based and spend-based methodologies, and reinforce global scope coverage with additions from the GHG Protocol (refrigerants) and the Covenant of Mayors (alternative scope 2 factors).
It also deepens regional granularity with new data for the Netherlands (CO2-Emissiefactoren), Canada (OpenIO), UK (electricity supplier-level data via Electricity Info), and France (full food chain coverage via Agribalyse).
Read about our vision and what’s next for our emission factor database.
The release includes the following new datasets:
Data version 21 also brings expanded coverage across existing datasets:
passenger_km or container_mi as input parameters in calculations cargo objects now support setting the number of containers to improve emissions accuracy for maritime hub emission calculations US if no results are found for US-CA)