The most-used developer tools
Based on sample data between Jun 2025 and Jun 2026.
Editor and tool debates are a developer pastime, usually settled with opinion rather than evidence. This report settles a narrower question with data: among people who write code, which tools do they actually spend time in?
It looks only at people who actively used a development tool, then ranks those tools by reach, the share of that group active in each one. Because it is based on real usage rather than stars or survey responses, it reflects the tools that hold a place in daily work.
Executive summary
- The most-used developer tool is Windows Terminal, used by 54.3% of developers.
- The three most widely used tools are Windows Terminal, Visual Studio Code, Notepad++.
- Most developers use several tools at once, so the shares overlap rather than add up to 100 percent.
Key findings
Share of developers, people who actively used a development tool, who were active in each tool.
Interpretation
Reach shows how widely a tool is used, not how heavily. A lightweight editor that many people open for quick edits can rank above a heavyweight IDE that fewer people live in all day.
Because developers routinely mix tools, an editor, a terminal, a database client, and a version-control app, the picture is one of overlapping toolkits rather than a single winner.
Methodology
- Source: anonymized WhatPulse application activity, recorded per user per application.
- A developer is defined here as a user who actively used at least one application classified as a development tool, such as an editor, IDE, or programming utility, in the window. Tools are ranked by reach, the share of that group active in each one.
- Applications merged under a single canonical name are combined. Because most developers use several tools, the shares do not add up to 100 percent.
Limitations
- The definition of a developer is a proxy: using a development tool once in the window is enough to count, so the group is broader than full-time engineers.
- WhatPulse users are enthusiasts and power users, so this reflects an engaged community rather than the whole software industry.
- Tool classification relies on community tags and is not perfect, so a runtime, updater, or occasional mis-tagged application can appear, and a niche tool can be missed.
Frequently asked questions
As a user who actively used at least one application classified as a development tool in the window. It is a usage-based proxy, so the group is broader than full-time software engineers.
Applications tagged as editors, IDEs, or programming and development utilities, for example code editors, integrated development environments, terminals, and version-control or API tools.
Because most developers use several tools. Each percentage is the share of developers who used that tool, and the same person is counted in every tool they used.
It is close to it, but based on real usage rather than sales or survey responses. It measures the share of developers who were active in each tool, which is a usage-based view of popularity.
No. Reach measures whether a tool was used at all. A tool many people open briefly can outrank one that fewer people use intensively all day.
It may not be tagged as a development tool, it may fall below the others in reach, or closely related tools can be split or merged by naming. Classification relies on community tags and is not perfect.