Next. js leads our crawl of 10,242 software websites
In September 2026, directree’s crawler scanned 10,242 software sites, uncovering Next.js on 3,863 homepages—76.3% of sites with a framework signal. The framework tops the list, eclipsing React, Laravel, and Vue. Next.js appears most strongly in AI image & video, video & audio, and directory categor…
In a comprehensive sweep of the software web, directree’s September 2026 crawl uncovered a striking dominance by Next.js. Of the 10,242 distinct hostnames examined, the framework was detected on 3,863 public homepages, representing 76.3% of the 5,060 sites where the scanner found at least one framework signal and 37.7% of all sites that underwent a stack check.
What the Numbers Reveal
directree’s methodology relies on passive detection of clues in HTTP headers, cookies, and page content. For Next.js, the scanner looks for a specific response header and characteristic asset paths. While the tool does not run a full browser session, it can reliably flag a framework when the expected signatures are present.
The data show that nearly half of the 10,242 sites (5,182) yielded no recognizable framework signal. This absence does not prove the absence of a framework; it simply means the scanner did not detect a supported signature. Conversely, 5,060 sites did present at least one framework clue, and Next.js alone accounted for 3,863 of those.
Next.js vs. Other Popular Stacks
When comparing the prevalence of other frameworks, React appears on 830 sites (16.4% of the 5,060 with a signal), Laravel on 235 (4.6%), Vue on 198 (3.9%), Nuxt on 184 (3.6%), Django on 88 (1.7%), SvelteKit on 81 (1.6%), Ruby on Rails on 74 (1.5%), and Angular on 30 (0.6%). These figures illustrate that Next.js leads by a wide margin. It is worth noting that Next.js is itself a React framework, yet the scanner isolates it as a distinct signal, so the 830 React counts represent sites with an independently matched React signature outside of Next.js.
Multiple framework signals were found on 481 sites, indicating that some sites use a combination of technologies. Because of these overlaps, the percentages cannot be summed to produce a market‑share total.
Category‑Specific Adoption
The study also broke down adoption by product category, focusing on groups with at least 200 checked sites. In AI Image & Video Generation, 61.1% of the 488 sites checked had Next.js, while in Video & Audio the figure rose to 52.6%. Directory & Listings saw 51.1% and Design & UI reached 49.2%. Marketing & SEO and Productivity categories had 46.6% and 37.0% respectively, and Developer Tools lagged behind at 30.8%.
Design & UI had the highest share of Next.js among categories that had at least one framework detected, standing at 83.0%. This suggests that sites in this space may favor Next.js for its performance and developer experience.
Implications for Developers and Marketers
For teams building integrations, templates, or documentation, the 3,863 hostnames that use Next.js provide a ready‑made audience. However, the study does not measure performance, revenue, or developer satisfaction, so the counts alone cannot guide a technology decision. The data also do not distinguish between the reasons behind the choice—whether it is due to architectural fit, template availability, or ease of detection.
Directree’s snapshot was compiled from stored observations dated 6–15 September 2026, with 8,944 observations from 6 September alone. The sample includes 10,178 registered domains, covering software broadly, including AI tools. Because the directory membership and detection rules can change, future percentages should be interpreted with caution.
How to Verify Your Own Stack
Developers can use directree’s public‑page scanner to inspect the technology stack of any public website. By comparing the observed signatures against the scanner’s database, teams can confirm whether a site uses Next.js or another framework.
For more detailed data, directree offers downloadable tables of framework counts, complete category breakdowns, and the underlying queries used for counting. The snapshot for this edition has been preserved for reference.
Next Steps
While the study stops short of recommending a framework, it highlights Next.js’s widespread adoption across key software categories. Teams may use these insights to target audiences, benchmark their own stack choices, or explore integration opportunities.
Why it matters
Next.js’s prevalence signals a shift toward server‑side rendered React applications, offering developers a powerful tool for performance and SEO. Understanding its market share helps businesses align technology choices with industry trends.
Key points
- Next.js appears on 76.3% of sites with a detected framework signal.
- Over half of the 10,242 sites show no detectable framework, indicating scanner limits.
- React, Laravel, and Vue trail far behind Next.js in adoption.
- AI Image & Video Generation and Video & Audio categories lead in Next.js usage.
- Directree’s scanner relies on passive detection of headers and asset paths.
- The data can guide teams looking to target Next.js‑based audiences.
- Future studies should account for directory changes and detection rule updates.
Frequently asked questions
What does a "framework signal" mean?
It refers to identifiable clues in a website’s HTTP responses—such as headers, cookies, or specific asset paths—that indicate the use of a particular web framework.
Why is Next.js so dominant?
Next.js combines React’s component model with server‑side rendering, offering performance, SEO benefits, and a robust ecosystem, which attracts many developers.
Does the scanner detect private applications behind logins?
No. The scanner only examines publicly accessible pages; applications behind authentication may use a different stack.
Can I use this data to choose a framework for my project?
The data shows prevalence but does not measure performance or satisfaction, so it should be one of many factors considered.
