How often developers use AI tools

Daily use accounts for 47.1% of responses. Adding daily, weekly and monthly or infrequent use gives 78.5% current use. A further 5.3% plan to begin, while 16.2% report no plans to use AI tools.

Combining present use with future intention answers a broader question than current adoption. Both can be useful, but a headline should make the distinction visible. A plan to try a tool does not establish that it is already part of someone's workflow.

Citation's interpretation is that frequency should be paired with a description of the task. A developer may consult AI every day for a small question while completing most work independently. Another may use it weekly for a larger assignment. The frequency categories cannot distinguish those patterns.

For a research or writing team, record the steps where an assistant is used: discovering sources, organizing notes, drafting, editing or checking references. This creates a more useful picture than a single count of active users because it connects the tool with a specific piece of work.

A local adoption study could follow a progression from access to first use, repeated use and completion of a useful task. Each stage needs a clear definition. Keeping them separate helps a team see whether a difficulty concerns setup, relevance or the quality of the result.

That progression is a proposed measurement approach. The survey is a snapshot of reported frequency, not a record of how the same people move between stages. It should not be used to predict an individual's future behavior.

The question received 33,662 responses in Stack Overflow's 2025 survey. Recruitment was primarily through Stack Overflow channels rather than a random draw of all developers. The chart uses the All Respondents group and preserves the published decimal percentages, which sum to 100%.

The original report provides the published figures and question wording. The chart and downloadable data use the same values; labels are shortened for readability.