In this guide7 sections
Most widely quoted “vibe coding” statistics do not measure vibe coding. They measure use of AI tools somewhere in a development workflow—a much broader category that includes autocomplete, chat, code review, testing and agents.
This page retains only figures that can be traced to an original survey or company source. Each entry records the date, population, sample and wording needed to interpret it. It does not publish a market-size estimate because we did not find a transparent primary dataset defining that market.
First: AI-assisted coding is not the same as vibe coding
For this tracker, AI-assisted coding means any use of an AI tool during development. Vibe coding is the narrower prompt-led practice in which a model generates substantial implementation from intent described in natural language. A respondent who uses autocomplete or asks a chatbot one syntax question belongs in the first group, but not necessarily the second.
None of the surveys below asks a representative population how often it practices that narrower workflow. Their results are useful adoption context, not a measured vibe-coding adoption rate.
Verified developer survey results
| Finding | Population and sample | Definition | Original source |
|---|---|---|---|
| 84% use or plan to use AI tools | 2025 Stack Overflow Developer Survey; 33,662 responses to this question | AI tools in the development process; not specifically vibe coding | [Stack Overflow 2025 AI results](https://survey.stackoverflow.co/2025/ai) |
| 51% of professional developers use AI tools daily | 2025 Stack Overflow Developer Survey; professional-developer segment of the same survey | Daily AI-tool use; the published summary does not equate this with prompt-built apps | [Stack Overflow 2025 AI results](https://survey.stackoverflow.co/2025/ai) |
| 92% had used AI coding tools at work or personally | GitHub-sponsored US survey published June 2023; 500 developers at companies with 1,000+ employees | Ever/then-current use in either setting—not daily use and not a 2026 estimate | [GitHub survey report](https://github.blog/news-insights/research/survey-reveals-ais-impact-on-the-developer-experience/) |
Sources rechecked September 6, 2026. Survey populations and question wording differ, so these percentages should not be combined into a trend line.
Company milestones are not market adoption
Wix announced its acquisition of Base44 on June 18, 2025 and described the product as a natural-language app builder. That verifies the acquisition and product positioning, but the announcement does not establish how many active developers use vibe coding or how frequently they ship production software.
Vendor revenue, registrations and project counts use different definitions and often come from company announcements. We therefore exclude them from the adoption table unless the source publishes the measurement period and definition. Read the Wix acquisition announcement (opens in a new tab) directly.
What these sources do not establish
- They do not estimate the size of a consistently defined “vibe coding market.”
- They do not show that 92% of developers use AI tools daily; the GitHub figure covers use at work or personally.
- They do not prove an average MVP takes one to three days or costs 90–95% less.
- They do not measure production reliability, security defects, maintenance cost or business outcomes.
How to cite this data accurately
Name the survey, year, population, response count and behavior measured. The defensible summary is that AI-tool use is common among survey respondents, while autonomous-agent use and the narrower practice of vibe coding remain separate questions.
We will update this page when a survey publishes a representative vibe-coding question with a reproducible definition. Until then, broader AI adoption numbers should not be relabeled as vibe-coding adoption.
Key takeaways
- The strongest public statistics measure broad AI-tool use, not vibe coding specifically.
- Stack Overflow reports 84% using or planning to use AI tools and 51% of professional developers using them daily, with 33,662 responses to the main question.
- GitHub's 92% result came from 500 US developers at large companies in 2023 and measured use at work or personally—not daily usage.
- No retained source supports a $4.7B market estimate, universal one-to-three-day MVP timeline, or 90–95% cost reduction.
Frequently asked questions
No source in this review measures the narrower practice with a representative 2026 developer sample. Stack Overflow measures broader AI-tool use: 84% of respondents use or plan to use such tools, while 51% of professional developers report daily use.
