Survey Shows Software Developers Want Sustainable Practices
Software developers want help cutting the carbon cost of their code. That is the core finding from a joint survey published by GitHub and Yale University in 2026, which reveals that many developers are actively concerned about climate change and see software efficiency as part of the solution.
The research surveyed 1,039 GitHub users across the United States between June and August 2026. Results show that developers are asking for practical tools to measure and reduce the environmental impact of their work. Moreover, they expect employers and platform providers to take sustainability seriously.
For UK businesses relying on software development, procurement, or cloud infrastructure, this shift in developer expectations has commercial implications. Sustainability is moving from compliance checkbox to operational requirement. Consequently, companies that build or buy software may soon face new questions about energy efficiency and emissions from their technology teams.
Developer attitudes diverge from the general public
The Yale Program on Climate Change Communication conducted the survey using questions validated against its long-running Climate Change in the American Mind research. This allows direct comparison between GitHub users and US adults overall. The gap is substantial.
Among surveyed GitHub users, 86% said global warming is happening. By comparison, only 68% of US adults agreed. Similarly, 82% of GitHub users described climate change as personally important, compared with 65% of the general population. Furthermore, 68% of developers expected climate change to harm them personally, against 45% of all adults.
These figures suggest that software developers as a group are significantly more climate-aware than the wider public. Importantly, that awareness translates into professional expectations. Three-quarters of respondents said it was important that their employer actively works to reduce environmental impact.
The survey also found that 79% of GitHub users were worried about global warming. Additionally, 71% expressed concern about the environmental impact of AI systems, including energy use, water consumption, and carbon emissions. This concern about AI is particularly relevant given the rapid expansion of machine learning workloads in business operations.
Strong demand for measurement and efficiency tools
Beyond attitudes, the survey revealed clear demand for practical support. Developers want tools and guidance that help them write greener code and understand the environmental footprint of their work.
Specifically, 80% of respondents were interested in tools that help them write more energy-efficient code. Meanwhile, 78% wanted best practices for reducing software's environmental footprint. In addition, 74% wanted ways to measure the environmental impact of their software or development process.
These are not abstract preferences. They point to a skills and tooling gap that businesses will need to address. If your organisation employs developers or commissions software, you may soon face requests for carbon measurement capabilities, efficiency benchmarks, or sustainability training.
The survey also found that 70% of respondents were interested in contributing to open source projects focused on sustainability. This suggests a willingness to invest personal time in environmental goals, reinforcing the idea that sustainability is becoming central to professional identity for many developers.
GitHub described the central takeaway as "strong demand for tools, measurement, and practical guidance that can help developers reduce wasted compute." The platform noted that these results should not be treated as representative of every developer, since the sample was drawn from GitHub monthly active users in the US who had opted into marketing communications. Nevertheless, the scale of interest is striking.
Why software efficiency is becoming a business issue
Software efficiency has always mattered for performance and cost. However, it is now also becoming a sustainability issue. The energy consumed by cloud infrastructure, data centres, and AI workloads translates directly into carbon emissions. As a result, inefficient code has an environmental cost that businesses are starting to measure and manage.
This shift is being driven by several factors. First, AI adoption is increasing computing demand substantially. Training and running machine learning models requires significant energy, particularly for large language models and other data-intensive applications. Second, regulatory pressure is growing. UK businesses face carbon reporting requirements under frameworks such as the Streamlined Energy and Carbon Reporting scheme. Third, procurement is changing. Public sector suppliers must demonstrate carbon reduction plans to meet requirements such as PPN 06/21.
For SMEs, this creates both risk and opportunity. On the risk side, clients and procurement teams may start asking about the carbon footprint of your software, cloud usage, or digital services. If you cannot answer those questions, you may lose tender opportunities or supplier status. On the opportunity side, businesses that can demonstrate energy-efficient software practices may gain a competitive advantage in bids and client relationships.
The survey also highlights expectations around employer responsibility. Three-quarters of developers said it was important that their employer actively works to reduce environmental impact. This is not just about corporate social responsibility. It affects recruitment, retention, and employee engagement. Consequently, businesses that ignore sustainability may struggle to attract or keep skilled technical staff.
Additionally, the research shows that developers expect action from cloud providers and platforms. If you rely on cloud infrastructure, your suppliers may come under pressure to offer carbon measurement tools, energy-efficient services, or transparent emissions reporting. Therefore, your own ability to report and manage software-related emissions will depend partly on what your cloud provider makes available.
Carbon reporting and software-related emissions
One of the more challenging aspects of this shift is measurement. Many businesses do not currently measure the carbon footprint of their software development or cloud usage. However, that is starting to change.
Carbon accounting frameworks distinguish between Scope 1, Scope 2, and Scope 3 emissions. For most businesses, software-related emissions fall into Scope 2 or Scope 3. Scope 2 covers purchased electricity, so energy used by your own servers or offices would be included here. Scope 3 covers indirect emissions in your value chain, including cloud services provided by third parties.
Measuring Scope 3 emissions from cloud usage is not straightforward. It requires data from your cloud provider about the energy mix, data centre efficiency, and resource consumption associated with your usage. Not all providers offer this data in a usable format. Consequently, businesses often struggle to include cloud emissions in their carbon reports.
The Yale-GitHub survey suggests that developers are aware of this gap. Their demand for measurement tools reflects a recognition that sustainability requires data, not just good intentions. Furthermore, it points to a role for platforms and employers in making that data accessible.
For UK businesses, this has implications for carbon reporting compliance. If you are required to report emissions under SECR or other frameworks, you may need to account for cloud and software-related energy use. Similarly, if you are working towards net zero targets or responding to client sustainability requirements, you will need to understand and reduce emissions from your digital operations.
What this means for procurement and supply chains
The survey findings also have implications for procurement. If developers are asking for greener tools and practices, procurement teams may soon be asking the same questions of software vendors and cloud providers.
Public sector procurement already includes carbon reduction requirements through PPN 06/21, which requires suppliers to publish carbon reduction plans and report emissions. While this applies to contracts above certain thresholds, the principle is spreading. Private sector clients are increasingly asking suppliers about their environmental impact as part of tender evaluation.
For businesses that sell software or IT services, this means sustainability is becoming a commercial differentiator. If you can demonstrate energy-efficient code, transparent emissions reporting, or active carbon reduction, you strengthen your position in competitive bids. Conversely, if you cannot answer questions about the environmental impact of your services, you may be excluded from consideration.
The survey also suggests that sustainability is becoming a procurement criterion for developer tools themselves. If 80% of surveyed developers want tools to help them write energy-efficient code, then platforms and vendors that offer those capabilities may gain market share. Therefore, businesses should consider sustainability features when selecting development tools, cloud providers, or software platforms.
What UK businesses should consider now
The Yale-GitHub survey is US-focused, but the trends it identifies are not limited to American developers. UK businesses are facing the same questions about software efficiency, cloud emissions, and the environmental impact of AI.
Here are several practical steps to consider. First, start measuring software-related emissions. This requires collecting data on cloud usage, data centre energy consumption, and development workflows. Our compliance team helps businesses integrate software and cloud emissions into carbon reporting frameworks.
Second, engage with your technology teams about sustainability. If your developers are concerned about climate change, they may welcome the opportunity to work on energy efficiency. However, they need tools, training, and management support to act on that concern. SBS Academy offers training on carbon literacy and sustainability practices for technical and non-technical staff.
Third, review your cloud and software procurement. Ask vendors about energy efficiency, carbon reporting, and sustainability features. Include environmental criteria in your supplier evaluation and contract terms. Our sustainable procurement support helps businesses integrate environmental requirements into purchasing decisions without compromising on performance or cost.
Fourth, consider how sustainability affects your competitive position. If you provide software, digital services, or IT support to clients, be prepared to answer questions about the carbon footprint of your offerings. Building capability in this area now may give you an advantage in future tenders and client relationships.
Finally, align software efficiency with broader net zero strategies. Reducing wasted compute is not just an environmental goal. It also reduces cloud costs and improves system performance. Therefore, energy-efficient software practices can deliver financial and operational benefits alongside carbon reduction. Our net-zero programme for carbon reporting compliance helps businesses integrate technology emissions into their overall carbon reduction plans.
Key details from the survey
- The survey interviewed 1,039 GitHub users aged 18 and older across the United States, with fieldwork conducted online between June 30 and August 9, 2026.
- 79% of respondents said they were worried about global warming, and 71% expressed concern about the environmental impact of AI systems.
- 80% were interested in tools to help them write more energy-efficient code, while 78% wanted best practices for reducing software's environmental footprint.
- 74% wanted ways to measure the environmental impact of their software or development process, and 70% were interested in contributing to open source sustainability projects.
- GitHub users were significantly more likely than US adults overall to believe global warming is happening, consider it personally important, and expect it to cause them harm.
- The sample was drawn from GitHub monthly active users in the US who had opted into marketing communications, so results should not be treated as representative of all developers.
How carbon and software efficiency connect to compliance
Understanding the carbon footprint of software and cloud infrastructure is becoming essential for compliance. UK businesses subject to SECR must report energy use and emissions annually. While many focus on buildings and transport, digital operations also consume energy and generate emissions.
Cloud services, data centres, and software development all have an energy cost. As reporting requirements evolve, businesses may need to include these emissions in their disclosures. Furthermore, voluntary frameworks such as the Science Based Targets initiative encourage comprehensive Scope 3 reporting, which includes purchased services like cloud computing.
The survey findings suggest that the technical community is ready to engage with these requirements. Developers want measurement tools and efficiency guidance. Therefore, businesses that provide those resources may find it easier to meet reporting obligations and achieve carbon reduction targets.
For businesses working towards net zero, software efficiency is a practical lever. Reducing unnecessary compute, optimising code, and choosing energy-efficient cloud services all contribute to lower emissions. These actions also reduce costs, since cloud billing is typically based on resource consumption.
Consequently, there is a commercial case for greener software practices that goes beyond compliance. Businesses that integrate sustainability into their technology strategy can reduce costs, meet client expectations, and strengthen their position in tenders that include environmental criteria.
Further information and resources
The full survey report is available from the Yale Program on Climate Change Communication, which conducts regular research on public attitudes towards climate change and publishes data and analysis for policymakers, researchers, and businesses.
For guidance on carbon reporting requirements in the UK, visit the Streamlined Energy and Carbon Reporting guidance published by the Department for Energy Security and Net Zero. This resource explains who must report, what must be included, and how to calculate emissions.
Information on public sector procurement requirements, including PPN 06/21 on carbon reduction plans, is available from gov.uk. This guidance sets out the expectations for suppliers bidding on government contracts above certain thresholds.
For businesses seeking to measure and reduce emissions from cloud infrastructure, the guidance on measuring and reporting environmental impacts provides a framework for understanding Scope 1, 2, and 3 emissions and integrating them into business reporting.