Original Research

State of Magento 2026

In November 2026 we checked more than 1.8 million domains and verified 28,708 live Magento and Adobe Commerce stores among them. This is what they run: which release, which storefront, how fast it is for real shoppers, and how many are on software Adobe no longer patches. And for each finding, what a store in that position can do next.

See the Findings
Isometric icon of a database stack with a blue layer lifted out of it

1.8 million domains checked, 28,708 Magento stores verified

Isometric icon of a clipboard with blue check marks down a list

Every store rechecked in November 2026

Isometric icon of a document on a plate with a blue seal pressed into it

Public pages only, and no store is named

The Short Version

Three Magento Stores in Ten Run Software Adobe No Longer Patches

28,708 stores18.6% on Magento 118.5% on Hyvä

Most numbers quoted about Magento come from a vendor's own customers or from a count nobody can check. This report comes from the stores themselves. We found them, confirmed each one runs Magento, and read what any browser can read: the homepage, the static files and the version the store announces.

Three things stand out. Magento 1 is far from gone: 5,328 of the stores still run it, more than six years after Adobe ended support. Add the Magento 2 stores on lines 2.0 to 2.4.3 and at least 30.5% of the sample is on software with no vendor patches coming.

Hyvä has moved from a specialist choice to a mainstream one in Europe, and much less so in the United States, where 12.2% of Magento 2 stores use it against 34.7% in the Netherlands. Across the whole sample it carries 18.5% of Magento 2 stores, and the Luma stack it replaces still carries 77.7%, so most of the move is still ahead.

And the storefront decides the speed. Hyvä stores pass Core Web Vitals at 68.7%, level with Shopify stores in the same database. Stores on the Luma stack pass at 43.5%.

Key Findings

Magento in 2026, in Three Figures

31%

Past End of Support

At least 30.5% of stores run Magento 1 or a Magento 2 line Adobe stopped patching in 2022 or earlier. A floor, since many stores hide their version.

A laptop open in a dark room with a web page lit on its screen

69%

Core Web Vitals

68.7% of Hyvä stores pass all three measures for real shoppers on phones. On the Luma stack the figure is 43.5%.

A field of fine blue vertical stripes brightening towards the centre

19%

Hyvä Adoption

18.5% of Magento 2 stores run Hyvä. Belgium leads at 41.4% and the United States stands at 12.2%.

Versions and Support

Which Magento Release Stores Really Run

A store's version page gives away only the minor line, and half of the stores hide it. So we also compared a handful of each store's public static files against every release Adobe has tagged since 2.3.0, which places a store on its release line whether or not it announces one.

Magento 2 Stores by Release Line

Share of the stores whose line could be read.

  • 2.4.9Supported to May 2029 10.8%
  • 2.4.8Supported to May 2028 29.3%
  • 2.4.7Supported to May 2027 23.1%
  • 2.4.6Extended support only 13.6%
  • 2.4.5Security fixes only 4.6%
  • 2.4.4Security fixes only 1.6%
  • 2.4.0 to 2.4.3Unsupported since November 2022 6.4%
  • 2.3Unsupported since September 2022 9.7%
  • 2.0 to 2.2Unsupported 1.0%

Base: 20,174 Magento 2 stores placed on a release line, out of 23,380.

Every Store by Support Status

Magento 1 and Magento 2 together.

  • On a supported line2.4.7, 2.4.8 or 2.4.9 44.4%
  • Limited support2.4.4 to 2.4.6 13.9%
  • Magento 2, unsupported2.0 to 2.4.3 12.0%
  • Magento 1Adobe support ended June 2020 18.6%
  • Not readableVersion hidden, files not matched 11.2%

Base: 28,708 stores. Support dates are Adobe's published lifecycle for Adobe Commerce, read in November 2026.

On 2.4.6 or Older?

Every line below 2.4.7 is on reduced support or none. We take a store from any Magento 2 release to the current one as a single planned project: extensions checked first, a staging run, then a cutover outside your trading hours.

See the Upgrade Service

Storefronts

Hyvä vs Luma: Who Has Moved

The Luma stack, meaning the stock theme and every custom theme built on its RequireJS and Knockout front end, still carries more than three Magento 2 stores in four. Hyvä is the only alternative with real share, and where a store is based says a lot about whether it has switched. Hyvä stores are also the better kept: 88.7% of those whose release could be read are on a supported line, against 56.6% on the Luma stack.

Magento 2 Stores by Storefront

  • Luma stackLuma, Blank and themes built on them 77.7%
  • Hyvä 18.5%
  • Breeze 0.8%
  • PWA Studio and other headless 0.2%
  • Not identified 2.8%

Base: 23,380 Magento 2 stores.

Hyvä Share of Magento 2 Stores by Country

  • Belgium 41.4%
  • Netherlands 34.7%
  • Poland 28.6%
  • France 27.5%
  • Germany 25.9%
  • United Kingdom 17.7%
  • Canada 13.7%
  • United States 12.2%
  • Australia 6.6%

Countries with 300 or more Magento 2 stores in the sample. The scale runs to 50%.

Weighing the Move to Hyvä?

We rebuild Luma storefronts on Hyvä, checkout and extensions included, and tell you before work starts which of your modules have a Hyvä version and which need a compatibility layer.

See Hyvä Development

Free, and no store access

Where Does Your Store Stand?

The free Magento audit reads your store the same way this report read 28,708 others, then goes further: speed, checkout, search visibility and security signals, scored and ranked.

Audit My Magento Store

Speed

Core Web Vitals: The Storefront Decides

These are not lab scores. They are Google's Chrome UX Report figures for each store: what real shoppers on phones experienced over 28 days. A store passes when loading, responsiveness and visual stability are all rated good.

Magento Stores Passing All Three, by Storefront

  • Hyvä3,140 stores 68.7%
  • Magento 11,626 stores 60.2%
  • Breeze102 stores 49.0%
  • Luma stack10,137 stores 43.5%

Base: 15,425 Magento stores with enough Chrome traffic for Google to publish field data. Half of them pass.

The Same Measure on Other Platforms

  • Shopware4,431 stores 84.2%
  • Shopify44,643 stores 69.8%
  • Magento on Hyvä3,140 stores 68.7%
  • BigCommerce2,083 stores 55.3%
  • Magento on Luma10,137 stores 43.5%
  • WooCommerce31,055 stores 42.8%

Stores on other platforms that the same scan met and verified. They were not the subject of the search, so read them as context.

Staying on Luma for Now?

A Luma store can pass too: 43.5% of them do. We find what holds yours back, from the JavaScript bundle to the server and the third-party tags, and fix it in order of what shoppers feel first.

See Speed Optimization

Upkeep

How Recently Was the Store Last Deployed

Every Magento 2 store stamps its static files with the time they were last deployed. A full upgrade always moves that stamp, so a store whose stamp is a year old has not taken a full release in a year. The reverse does not hold: a recent stamp says the store is worked on, not that it is patched.

Time Since the Last Static Deploy

  • Under 3 months 81.1%
  • 3 to 12 months 10.1%
  • 1 to 3 years 5.6%
  • Over 3 years 3.3%

Base: 18,943 Magento 2 stores that expose the stamp.

Edition, Where the Store Reveals It

  • Magento Open Source 63.8%
  • Adobe Commerce 26.8%
  • Adobe Commerce with B2B 9.4%

Base: 17,885 Magento 2 stores whose edition could be read. 3,192 stores run on Adobe's own cloud.

No Release in a Year?

That is usually a store without a team, not a store without problems. We take over Magento stores as they stand, start with the patches and the upgrade that are overdue, and keep them current from then on.

See Ongoing Support

What to Do Next

Find Your Store in the Numbers

Each group in this report has a different next step. Pick the one that describes your store.

18.6% of stores

Still on Magento 1

There is no upgrade path, only a move: to Magento 2, or to another platform if the store has outgrown the need for one. We plan the data, the URLs and the search rankings before anything is switched.

Plan the Migration
12.0% of stores

On Magento 2.3 or 2.4.0 to 2.4.3

These lines have had no security fixes from Adobe since 2022, and the PHP versions under them are out of support too. The jump to a current release is larger than a routine upgrade, and it is still one project.

See the Upgrade Service
13.9% of stores

On Magento 2.4.4 to 2.4.6

Security fixes still arrive, and the clock is running: these lines leave support in 2027. Answer a few questions about your store and see what an upgrade from your release involves.

Open the Upgrade Calculator
56.5% of Luma stores fail

On Luma and Failing Core Web Vitals

Hyvä stores pass at 68.7% against 43.5% on the Luma stack. A rebuild on Hyvä replaces the front end and keeps your catalog, your orders and your back office where they are.

See Hyvä Development
44.4% of stores

On a Supported Line

The line is only the start. Adobe ships security releases inside each line several times a year, and a store that skips them is exposed on a supported version. We apply them on a schedule and test before each release.

See Security Patching
Free

Not Sure Where You Stand

The free Magento audit reads your store from outside, the way this scan did, and reports its speed, checkout, search visibility and security signals with the fixes ranked by impact.

Audit My Magento Store

Verified reviews

What Our Clients Say

Methodology

How We Measured It, and What It Cannot Show

The scan read public pages only, one request at a time per store, under a user agent that names ZestIQ. It never touched a cart, a checkout, a customer account or an admin panel, and it sent no request built to test a vulnerability.

FindingHow it was readWhat it cannot show
The sampleCandidate domains came from public web crawl indexes, certificate logs and traffic rankings, more than 1.8 million in all. Each was fetched and kept only when its own pages proved it runs Magento.This is a sample, not a census. Stores whose firewall refused the scanner are not in it, so heavily protected stores are under-counted.
Release lineThe minor line a store announces on its version page, and the hashes of up to twelve public static files compared against every release tagged since 2.3.0.Security releases that changed no public file look alike from outside, and an isolated patch or hotfix leaves no trace at all. No store is called patched or vulnerable.
Support statusEach line was set against Adobe's published lifecycle dates for Adobe Commerce, as they stood in November 2026.Some stores on old lines apply community or third-party fixes, and some Magento 1 stores run a maintained fork. Unsupported by Adobe is all the figure says.
StorefrontTechnical fingerprints in the page source: Hyvä's own markers, the RequireJS and Knockout stack of Luma, Breeze and PWA Studio signatures.A headless store that hides its back end entirely may not be recognised as Magento at all.
Core Web VitalsGoogle's Chrome UX Report for each store's origin: the 75th percentile on phones over 28 days, passing at 2.5 seconds, 200 milliseconds and 0.1.Google publishes data only for sites with enough Chrome traffic, so small stores are missing. The comparison describes stores as they are built, not the theme alone.
CountryA country domain, or for .com stores the address, currency and language the store itself publishes.A store selling into several countries is counted once, where its own pages place it.

Keep reading

More on Magento in 2026

Read all
Read all

FAQ

Questions About the Report

Still have questions?

Tell us about your store and we will come back with straight answers.

Talk to an Engineer

How many Magento stores did you scan?

28,708 live stores that we verified as Magento or Adobe Commerce from their own pages: 23,380 on Magento 2 and 5,328 on Magento 1. Every one was rechecked in November 2026. To find them we checked more than 1.8 million domains and set the rest aside because they run another platform, were offline, or refused the scanner.

What is the latest Magento version in 2026?

Magento 2.4.9, released in May 2026 and supported by Adobe until May 2029. In this scan 10.8% of the Magento 2 stores with a readable release already run it. The most common line is 2.4.8 at 29.3%, followed by 2.4.7 at 23.1%.

Which Magento versions does Adobe still support?

As of November 2026, lines 2.4.7, 2.4.8 and 2.4.9 are in full support, to May 2027, May 2028 and May 2029. Lines 2.4.4 and 2.4.5 receive security fixes only, and 2.4.6 is on extended support. Everything from 2.0 to 2.4.3 has been unsupported since 2022, and Magento 1 since June 2020.

What share of Magento stores use Hyvä?

18.5% of the Magento 2 stores in this scan, 4,329 stores. The share depends heavily on the country: 41.4% in Belgium, 34.7% in the Netherlands, 25.9% in Germany, 17.7% in the United Kingdom and 12.2% in the United States.

Does the report say which stores are unpatched?

No. It names no store, and it does not claim that any store is patched or vulnerable. From outside, a store can be placed on a release line and sometimes within a band of security releases, but an isolated patch or a hotfix changes nothing a visitor can see. What the report does count is stores on lines Adobe no longer patches at all.

Did you test stores for vulnerabilities?

No. The scan requested only what a browser requests: the homepage, the version page and a few static files. It sent nothing designed to trigger or confirm a vulnerability, and it never touched a cart, checkout, customer account or admin URL.

How do you tell a Hyvä store from a Luma store?

By what the page loads. A Luma-stack store loads RequireJS and Knockout and carries Magento's script initialisation blocks. A Hyvä store carries Hyvä's own markers and Alpine.js in their place. The scan reads those technical fingerprints and ignores words in the copy.

Why is your store count lower than other Magento counts?

Because a store is counted here only after its own pages proved the platform and it answered in November 2026. Counts built on a single technology signature run higher, and they include parked and dead domains. Stores whose firewall refused the scanner are also missing here, so this is a verified sample and not a census.

Why do Hyvä stores pass Core Web Vitals more often?

Hyvä replaces the Luma front end, which ships a large JavaScript bundle to every page, with a much lighter one. Less script means faster loading and fewer layout shifts. The figures compare stores as they are actually built, so better-funded teams choosing Hyvä is part of the gap, and the theme is not the whole of it.

Is a store on Magento 2.3 or Magento 1 at risk?

It runs software Adobe no longer writes security fixes for, so every vulnerability found since support ended is open unless someone else has fixed it. Some stores apply community patches or run a maintained fork of Magento 1, which the scan cannot see. For a store owner the practical point is that the cost of an upgrade or a move grows with each year it waits.

My store is on an old Magento version. Should I upgrade or move platform?

It depends on what the store needs. A store that uses Magento's catalog depth, B2B features or custom integrations usually does best upgrading, often with a move to Hyvä in the same project. A small catalog with simple needs may be cheaper to run elsewhere. We do both kinds of project, so the advice does not lean either way. Start with the free Magento audit or tell us about the store through the form below.

Can I quote these figures?

Yes. Quote any figure with a link to this page and the month of the scan, November 2026. If you need a cut that is not shown, such as a country or an industry, ask through the form below and we will run it where the sample is large enough.

Will the report be updated?

Yes. The scan is repeatable, and the stores are rechecked on a rolling basis, so the same measures can be compared over time. This page will carry the newest edition and state the month of its data.

How do I have my store left out of future scans?

Send the domain through the form below and it is removed from the scan list. The report only ever publishes counts and shares, so no single store appears in it either way.

Let’s build something great together!

Want Your Own Store Read Properly?

Tell us your store's address. An engineer reads its release, patches, storefront and speed from the inside, where the real answers are, and replies within one business day.

Reply within 24 hours No long-term lock-in NDA on request Senior engineers only

We've Got Your Request!

We'll reply to {email} within one business day, and it will be an engineer who does the work, not a sales rep.