How Many Websites Use WooCommerce? 3.34M Stores and the Version Matrix Behind Them
As of November 16, 2026, webatla counts 3,344,511 websites running WooCommerce, 1.03% of the 325.8 million websites it tracks. That is roughly one site in 97, and the live figure sits on webatla's WooCommerce technology
As of November 16, 2026, webatla counts 3,344,511 websites running WooCommerce, 1.03% of the 325.8 million websites it tracks. That is roughly one site in 97, and the live figure sits on webatla's WooCommerce technology page, which is updated daily.
That is the short answer to how many websites use WooCommerce. The rest reads the same data for people who build and maintain these stores, and leaves growth curves and country tables to the longer WooCommerce statistics write-up on webatla's blog.
How to check a single store from your terminal
According to its technology page, webatla's scanner finds WooCommerce from front-end traces in the storefront each domain serves, so each of the 3,344,511 sites is a domain where those traces turned up. Your terminal sees the same public HTML and assets. The difference is that on one site you can keep digging, into the REST API or a product page. None of the checks below is webatla's detection method. They are quick signals you can look for yourself on a store you are about to take over or audit.
The plugin lives under /wp-content/plugins/woocommerce/, and on a default setup its stylesheets and scripts load from that folder with a ver query string that usually carries the plugin version. WordPress also serves a REST API index at /wp-json/, and when WooCommerce is active that index normally lists wc/ namespaces such as wc/v3 or wc/store/v1.
curl -sL https://example.com/ \
| grep -oE 'plugins/woocommerce/[A-Za-z0-9/._-]+\?ver=[0-9.]+' \
| sort -u | head -n 5
curl -sL https://example.com/wp-json/ | jq -r '.namespaces[]' | grep '^wc/'
Replace example.com with the store you are checking. The first command pulls the home page and prints up to five distinct WooCommerce asset paths with their version strings. The second asks the REST index for its namespaces and keeps the ones that start with wc/. It needs jq, and it fails loudly if the site returns HTML instead of JSON. That can mean the API is blocked or rewritten, or that the site uses plain permalinks, in which case try https://example.com/?rest_route=/ instead.
The technology page names aggressive page caching, heavily customised themes and headless builds as the ways a real store slips past a scan, and each one has a counterpart in the terminal. An asset optimiser that merges and renames files removes the plugin path from the HTML. Hardened sites often block or filter the REST index. WooCommerce also prints its own generator meta tag with its version, right after the WordPress one, but many sites strip both. A headless build is the hardest case. A separate application renders the shop, so the public domain may serve no /wp-content/ paths at all, and if WordPress runs on a subdomain the REST check on the main domain finds nothing. Every one of these hides a working store, which makes the count, like any WooCommerce usage statistics built from public pages, a floor.
Errors also run the other way. A shop that stopped taking orders long ago can keep serving the same markup and still counts, and no public page shows revenue, order volume or catalogue size. An empty result from the commands above proves nothing. A hit on the plugin path is a strong sign, and the ver value is usually the installed release, though a cached page can lag behind an update.
Market share inside the open source PHP world
Measured against the whole web, WooCommerce market share is the 1.03% above. A peer group says more to a PHP developer. The blog post on webatla compares the 20 largest store platforms on its technology list. Six of them, WooCommerce, Magento, OpenCart, PrestaShop, EasyDigitalDownloads and Shopware, show both PHP and an open source licence on their technology pages. Together they run 3,648,193 sites.
Sites on the six open source PHP store platforms among the 20 largest store platforms, November 16, 2026.WooCommerce holds 91.7% of that group, about eleven installs in every twelve. The other five combined run 303,682 sites, so WooCommerce has 11 times as many as all of them together. Magento is the largest of the rest at 128,122 sites and grew 34% over the last 12 months according to its page, while PrestaShop fell 25% and OpenCart 7% in the same period.
If you write PHP for self-hosted shops, most of the stores you meet will be built on WordPress actions, filters and template overrides. EasyDigitalDownloads is a WordPress plugin too, so the WordPress side of this group is larger still. Magento is the one other codebase in the group with a six-figure site count.
2,748 version strings and the test matrix behind them
According to webatla, there are 2,748 distinct WooCommerce version strings in the wild, and about 3.0 million stores, close to nine in ten, expose one. The most common build is 11.2.1, found on 734,109 stores, which is 24.5% of those with a visible version. The chart groups the 25 most common builds by release line.
The 25 most common WooCommerce builds grouped by release line, as a share of stores that show a version.The 11.2 line covers 33.4% through three builds. 10.7 is the second largest line at 8.1%, and in the top 25 it is a single build, 10.7.0.
WordPress core versions sit far closer together.
Share of sites with a visible version covered by the most common builds, WordPress core vs the WooCommerce plugin.It takes ten WooCommerce builds to reach 58.8% of versioned stores, about the share that two WordPress releases cover on their own (57.8%). By default WordPress installs minor core releases by itself, while plugin auto-updates stay off unless the site owner or the host switches them on. That is a likely reason the plugin's installed base is spread so much wider.
- WooCommerce extensions declare
WC requires at leastandWC tested up toin the main plugin file header. A floor of 10.0 still leaves at least 115,940 stores on five 9.x builds outside it, plus some part of the 25.8% of versioned stores that run builds outside the top 25. Pick the floor on purpose and run your tests on the oldest line you claim. - Testing only against the newest release covers a minority of real stores. The 11.2 line plus 10.7.0 already accounts for 41.5%, so those two belong in any matrix.
- Theme template overrides age with the plugin. The System Status report in the WooCommerce admin lists the templates a theme overrides and flags the ones that are out of date, which is worth a look before and after you move a store up several release lines.
- A version string is a hint. It can trail the real install on a cached page and it can be removed. Use it to prioritise work across many sites, then confirm on the site itself.
Which payment plugins sit next to the cart
Payment code is where version drift turns into incidents, because gateways retire API versions and tighten authentication over time. The four WooCommerce payment plugins below are tracked by name on webatla's technology list.
Sites where each WooCommerce payment plugin was detected, November 16, 2026. All four counts are floors.WooCommerce PayPal Payments shows 86 distinct versions on its page. Among the roughly 21,800 installs that show one, 4.2.0 (27.7%) and 4.1.3 (26.5%) together cover more than half, and the nine 4.x builds in the top 25 cover about 78%. Behind them sits a tail of 1.x, 2.x and 3.x builds. The plugin is the official PayPal extension, first released in 2021, and runs on 133,653 sites. If you support stores that use it, the 1.x installs are the ones to look at first.
The legacy WooCommerce PayPal gateway, the third card above, has 28 recorded versions, yet 83.0% of its installs that show one sit on a single build, 2.1.3. Its page says it is no longer the recommended path. It still runs on 17,842 sites, one for every 7.5 installs of the newer extension. A plugin frozen on one old build across thousands of shops is a clear migration ticket waiting for an owner.
WooCommerce Stripe Payment Gateway, published by Automattic, runs on 55,956 sites. Its page has no dependable release string for it, so it can say where the plugin is installed but not which version. The third party WebToffee Stripe Payment Plugin for WooCommerce adds 3,102 more.
The four add up to 210,553 detections, 6.3% of the WooCommerce count, which is low partly because a gateway often loads its scripts only on the final payment step, where a scan of public pages may never go. A hit also does not prove the gateway is switched on.
Extensions that are thinning out
MailChimp for WooCommerce runs on 94,488 sites after a 27% drop in the last 12 months. WooCommerce Multilingual is on 48,241 sites, down 15% over the same period, with 213 version strings and 5.6.3 the most common at 30.7%. If you inherit a store with either one, check that the integration still does its job before you update WooCommerce on that site.
Where the migration work comes from
Over the last 12 months WooCommerce's technology page reports 721,000 brand new sites and 386,000 switchers arriving, against 604,000 sites that went offline and 602,000 that stayed online but stopped showing the plugin, for a net change of -2.8%.
The 602,000 is the figure most likely to turn into developer work. Each of those domains stayed online after its WooCommerce traces disappeared. Some may have moved to another platform, some may have closed the shop and kept the rest of the site, and some may still run WooCommerce behind a headless front end or a cache that hides its traces, which shows up in the counts as a drop. The counts do not say which.
Each case leaves a different job behind. A move to another platform starts with the URL map. On a default setup WooCommerce puts products under /product/ and categories under /product-category/, and every one of those paths needs a 301 to its new home or it turns into a 404 for old links and search results. Products, customers and orders need an export the new platform can import. Saved cards are usually tokens held by the payment provider, which has to be part of any plan to keep them.
A shop closed inside a site that lives on is quieter work. Deleting the plugin leaves its tables and options in the database unless WC_REMOVE_ALL_DATA is set to true in wp-config.php beforehand, so old customer and order data stays there until someone removes it on purpose. A headless rebuild keeps WooCommerce as the back end, and the Store API (wc/store/v1) from the terminal check is one of the interfaces the new front end can call. For maintenance that store is still a WooCommerce site, plugin updates included, even though the counts file it under drops.
The history model behind webatla's pages estimates active sites month by month (early years are approximate), and its yearly figures for 2019 and 2025 show how the balance between switching in and dropping out turned.
Yearly flows into and out of WooCommerce in webatla's history model, 2019 vs 2025, thousands of sites.In 2019, sites switching to WooCommerce outnumbered sites dropping it by 538,000 to 419,000. By 2025 the order had flipped, with 413,000 switching in and 605,000 dropping it. New launches reached 785,000 in 2025, so setup work has not dried up. Drops rose while switch-ins fell, and for an agency that adds up to more export and redirect projects than a few years ago.
Questions developers ask about these numbers
Is 3,344,511 the number of active shops?
No. It counts domains where the WooCommerce plugin showed up in the storefront when webatla last scanned them. Dormant shops that still serve pages are included, and stores hidden behind caching or a headless front end are missed.
Why do the yearly figures not line up with today's count?
They come from different sources. Yearly and monthly figures come from the history model, which ends at 3.36 million in October 2026. The 3,344,511 is today's count. Compare model months only with other model months, and use the page's own change figures for trends.
Which WooCommerce release should an extension support first?
11.2.1, on 24.5% of stores that show a version, and the rest of the 11.2 line next to it. 10.7.0 follows at 8.1%. Testing only on the latest release leaves most of the installed base untested.
Can I tell which gateway a store uses?
Sometimes. The plugin counts above are floors because payment scripts often load only at the last step. For a site you maintain, the Network tab in your browser's DevTools on the final payment page shows which payment domains it calls, which beats reading the home page HTML.
Sources
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.



