Adobe Commerce development
Storefront design
Performance & SEO
AI & agentic commerce
Release tracker
For most Magento stores in 2026, the choice comes down to this: Hyvä when you want the fastest, most maintainable frontend and can budget for a rebuild; Breeze when you need a speed boost on an extension-heavy Luma store with less rework; and Luma only when you must change as little as possible right now. Since November 2025 the core Hyvä Theme has been free and open source, which removed the main cost objection, but rebuild effort and extension compatibility still decide the right answer.
The three options in one paragraph each
Luma
Luma is the default storefront theme shipped with Adobe Commerce and Magento Open Source. It is built on RequireJS, jQuery, Knockout.js and LESS. Almost every Magento extension supports it out of the box, which is its main strength. Its weakness is weight: many JavaScript modules load on every page, which tends to hurt Interaction to Next Paint and Largest Contentful Paint on mid-range phones. Note that Adobe Commerce as a Cloud Service (the SaaS edition) does not support Luma storefronts, though Luma remains the default on PaaS and Open Source.
Hyvä
Hyvä replaces Luma's frontend stack entirely with Alpine.js and Tailwind CSS, while keeping Magento's server-rendered architecture, layout XML and PHP templates. Because it removes RequireJS, Knockout and jQuery from the storefront, third-party extensions with frontend features need a Hyvä compatibility module; many exist, and others must be written. Hyvä announced on November 6, 2025 that the theme is relicensed under OSL3 and AFL3, and it has been freely available since November 10, 2025 through GitHub and free Composer keys from the Hyvä Portal. Hyvä Checkout, Hyvä Enterprise and Hyvä Commerce remain commercial products, and Hyvä UI became a separately sold component library.
Breeze
Breeze, from Swissup, is a free frontend that keeps Luma's templates and replaces its JavaScript layer. According to the Breeze documentation, it does not load RequireJS; it provides its own lightweight define and require functions and maps jquery to Cash, a much smaller alternative. Many Luma extensions work with little or no change; others need to be registered in a breeze_default.xml file or adapted. Swissup also offers free Breeze themes such as Breeze Blank and Breeze Evolution.
Side-by-side comparison
| Factor | Luma | Breeze | Hyvä |
|---|---|---|---|
| Frontend stack | RequireJS, jQuery, Knockout, LESS | Luma templates with a lightweight JS layer (Cash instead of jQuery) | Alpine.js, Tailwind CSS |
| Licence (as of Nov 2026) | Included with Magento | Free | Theme free (OSL3/AFL3); Checkout, UI and Enterprise paid |
| Extension compatibility | Native for nearly all extensions | Many work as-is; some need registration or fixes | Needs a compatibility module per extension with frontend code |
| Rebuild effort | None | Low to medium | Medium to high (new theme) |
| Performance ceiling | Lowest without heavy tuning | Clear improvement over Luma | Highest of the three in typical setups |
| Developer skills | Magento frontend (Knockout, LESS) | Magento frontend; Luma knowledge transfers | Tailwind, Alpine.js, Magento templates |
| Checkout | Luma checkout | Luma-based checkout (check Breeze docs for how checkout pages are handled) | Hyvä Checkout (paid) or Luma checkout fallback |
The performance row is a general pattern, not a benchmark. Results depend on images, third-party scripts and hosting as much as on the theme, so measure your own field data before and after.
Decision matrix
Find the row that matches each of your constraints. If most of your answers land in one column, that is your likely choice.
| Your situation | Stay on Luma | Choose Breeze | Choose Hyvä |
|---|---|---|---|
| Extensions with frontend features: under 10 | Only if nothing else changes | Good fit | Strong fit; few compatibility modules needed |
| Extensions with frontend features: 10–30 | Possible | Strong fit | Good fit if compatibility modules exist for most |
| Extensions with frontend features: 30+ or many custom ones | Possible | Strong fit | Plan carefully; budget for custom compatibility work |
| Budget: minimal this year | Strong fit | Good fit | Defer |
| Budget: moderate | Not recommended | Strong fit | Good fit for small catalogs and few extensions |
| Budget: full redesign planned | Not recommended | Possible | Strong fit; rebuild anyway |
| Team skills: Luma, Knockout, LESS | Comfortable | Strong fit | Training needed |
| Team skills: Tailwind or modern JS | Frustrating | Fine | Strong fit |
| Timeline: weeks | Strong fit | Good fit | Unlikely unless the store is simple |
| Timeline: a quarter or more | Missed opportunity | Good fit | Strong fit |
| Moving to Adobe Commerce as a Cloud Service soon | Not supported there | Not supported there | Not supported there; plan Commerce Storefront instead |
"Extensions with frontend features" means extensions that add JavaScript, templates or styling to the storefront, such as product sliders, reviews widgets, one-step checkouts and search autocomplete. Back-office extensions (ERP connectors, export tools) usually do not affect the theme decision.
How to count your extension risk
- List all enabled modules from
app/etc/config.php, ignoring Magento's ownMagento_modules. - Mark each one that adds storefront templates, layout XML, JavaScript or CSS.
- For Hyvä, check whether the vendor or Hyvä's compatibility module tracker lists a compatibility module.
- For Breeze, check Swissup's compatibility list and test on a staging copy.
- Count the gaps. Each gap is either a custom compatibility task, a replacement extension, or a feature you drop.
What about headless?
A headless storefront (for example a Next.js or React frontend talking to Magento's GraphQL API) is a fourth option. It suits brands with strong content needs, a dedicated frontend team, or plans to combine commerce with a separate CMS. It also moves more work onto your team, since many Magento extensions have no headless frontend at all. Our headless CMS guide explains when that architecture pays off.
Budget notes
Licence fees are now a small part of the decision. The Hyvä Theme is free; Hyvä UI, Hyvä Checkout, Hyvä Enterprise and Hyvä Commerce are paid products, so see hyva.io for current pricing before you budget. Breeze and its free themes cost nothing to license.
The real costs are development time: building or adapting the theme, compatibility work for each extension, testing every storefront feature, and the checkout. A meaningful estimate needs the extension count from the steps above.
Frequently asked questions
Is Hyvä really free now?
The core Hyvä Theme is, under OSL3 and AFL3 licences, since November 2025. Hyvä Checkout, Hyvä UI, Hyvä Enterprise and Hyvä Commerce are separate commercial products.
Can I switch from Breeze to Hyvä later?
Yes, but Breeze work does not carry over to Hyvä, because the two use different frontend stacks. If Hyvä is the long-term goal and budget allows, going straight there avoids paying twice.
Does the theme alone fix Core Web Vitals?
No. A lighter theme removes a large source of JavaScript, but images, fonts, third-party scripts and server response time still matter. See our list of Magento speed optimization fixes ranked by impact.
Which Magento versions does Hyvä support?
As of November 2026, Hyvä's getting-started documentation lists Magento 2.4.4-p9, 2.4.5-p8, 2.4.6-p7 or 2.4.7-p1 "or higher" as minimums, recommends 2.4.6 or later on the latest patch, and says 2.4.4 and 2.4.5 will no longer be supported from 2027. It lists PHP 8.1 to 8.4 and does not name 2.4.9 or PHP 8.5, so confirm support with Hyvä before you move to 2.4.9.
Getting the choice right
Mistri can audit your extension list and field data and recommend a frontend path as part of our Magento performance optimization work. For full theme builds or a move to a new frontend, see our Adobe Commerce development services.
Sources
Hyvä Theme is now open source and free (Hyvä blog, 6 Nov 2025); Hyvä getting started documentation; Breeze RequireJS documentation (Breezefront); Adobe Commerce as a Cloud Service overview (Adobe Experience League).
