Hyvä Theme Development: What It Is, What Changed in 2025, and How to Plan a Move from Luma
Quick answer: Moving a Magento 2 store to Hyvä means swapping the Luma frontend for a lighter theme built on Tailwind CSS and Alpine.js, while the backend stays put. Hyvä Theme has been free since November 10, 2025. The real work is auditing extensions, rebuilding the design, deciding on checkout and testing properly.
Last updated: November 2026
Hyvä is a frontend theme for Magento 2 that replaces a heavy Luma storefront with a lighter one, while the store’s backend, catalog and PHP templating stay where they are. On November 6, 2025, Hyvä announced that the Hyvä Theme was becoming free and open source, which removed the theme licence fee from the budget. What’s left is the real work: checking your extensions, rebuilding your design, and planning the move properly. This guide walks through all of it in plain words.
What is Hyvä, and is it a new platform?
No. Hyvä is a theme for Magento 2, not a new platform, not a headless build and not a PWA.
Your store still runs on Magento 2 (also sold as Adobe Commerce), and Hyvä replaces what shoppers see and touch in the browser. Magento’s PHP templating stays in place, so your developers are still working in Magento’s template system. The Luma-specific frontend code is what gets replaced. Your products, orders, customers, admin panel and integrations don’t move anywhere.
That’s a big difference from a headless build. With headless you’re running a separate frontend application and talking to Magento through APIs, and that’s a larger project with more moving parts. A Hyvä move is closer to a very thorough redesign of the storefront layer. If you’re weighing options and want the plain version, hyva theme development is the path for stores that want a faster frontend without changing how Magento itself works.
So who is this for? Mostly store owners who look at their Luma storefront and think, “this feels slow, and every change costs us too much.” Luma is the Magento frontend theme that Hyvä replaces. If that sounds like your store, keep reading.
Why do Luma frontends feel heavy?
Because the browser has to download, read and run a lot of files before the page feels ready. The more files and the more code, the longer that takes.
The concept is simple. When a shopper opens a page, their browser has to fetch files and run them. On a phone with a mediocre connection, it takes even longer.
Many Luma storefronts, especially ones that have collected extensions and tracking scripts over the years, can end up asking the browser to do a lot. Extensions often bring their own scripts and styles, and those may add to the weight of a page. Over time it can get heavier, and nobody remembers which piece added what.
Hyvä was built to cut that load down. It’s worth being clear about where the numbers come from, so here they are, labelled properly. Hyvä reports requests cut from 230 to 5, and page weight cut from 3MB to 0.4MB. Those are the vendor’s own figures, and your store will differ. Your results depend on your catalog, your extensions, your hosting and how the theme gets built.
Hyvä also reports more than 7,000 merchants using it. That tells you it isn’t a niche experiment. It doesn’t tell you it will fit your store without work. Keep those two ideas apart.
Want a baseline before you decide anything? Run a Magento performance audit on your current store first. If you don’t know what’s slow today, you can’t prove anything got better later.
What are the Core Web Vitals thresholds?
Google’s web.dev lists three Core Web Vitals: LCP of 2.5 seconds or less, INP of 200 milliseconds or less, and CLS of 0.1 or less. A page counts as “good” when it meets the target for at least 75 percent of visits.
| Metric | What it measures | Good threshold |
|---|---|---|
| LCP (Largest Contentful Paint) | How fast the biggest visible element loads | 2.5 seconds or less |
| INP (Interaction to Next Paint) | How quickly the page responds when someone taps or clicks | 200 milliseconds or less |
| CLS (Cumulative Layout Shift) | How much the layout jumps around while loading | 0.1 or less |
One thing to note. INP replaced an older metric called FID as a Core Web Vital in 2024. If a report you’re reading still talks about FID, it’s out of date.
Why does this matter for a theme choice? Because each of the three is affected by how much code the page ships and how it behaves in the browser. A lighter frontend gives you a better shot at all three. It doesn’t guarantee any of them. Images, fonts, third-party scripts and hosting still count.
If you want a deeper look at the speed side specifically, this page on Hyvä performance optimization covers it in detail.
What do Tailwind CSS and Alpine.js do in Hyvä?
Tailwind CSS handles styling and Alpine.js handles interactivity. You don’t need to be a developer to understand what each one does.
Tailwind CSS is a utility-class styling framework. Developers style elements with small utility classes instead of writing large stylesheets. The build step needs Node.js 20 or higher, which matters for whoever sets up your development environment.
Alpine.js is a small JavaScript library that adds behavior right in the HTML. In Hyvä it handles the interactive parts of the page in the browser. Think of it as the light switch for the page, not the wiring behind the wall.
There’s one detail worth knowing. Different Hyvä Theme versions use different Alpine versions. Per Hyvä’s docs, versions 1.0.x and 1.1.x use Alpine 2, while 1.2.x and 1.3.x use Alpine 3. A single theme can’t mix them. So if an extension’s frontend code was written for one Alpine version, it needs to match the theme you’re on. Ask your developer which version your project targets, and check Hyvä’s current docs for the latest.
Is Hyvä Theme really free now?
Yes, the theme itself is. On November 6, 2025, Hyvä announced that the Hyvä Theme was becoming free and open source. It was relicensed under OSL3 and AFL3, and became freely available from November 10, 2025, through GitHub and free Packagist keys.
For anyone who looked at Hyvä before, that’s a real shift. The cost side of hyva themes development used to include a theme licence fee. That fee is gone for the theme itself. Your budget now goes mostly to people’s time: audit, design, build, testing and launch.
But “free theme” doesn’t mean “free everything.” Hyvä still sells several commercial products. The table below shows the split.
| Hyvä product | Status |
|---|---|
| Hyvä Theme | Free and open source (OSL3 + AFL3) |
| Hyvä UI | Separate product, €250 per store |
| Hyvä Checkout | Separate commercial product |
| Hyvä Commerce | Commercial licence |
| Hyvä Enterprise | Commercial licence |
Prices for Commerce and Enterprise are not listed here because they change. Check Hyvä’s own site for current terms before you budget.
A practical note: a free theme can still carry costs. Someone usually has to install it, build your design on it, test it with your extensions, and keep it updated. How much time that takes depends on your store. The licence fee was only one part of the job, and now it’s gone. That doesn’t make the rest trivial.
Will my existing extensions work on Hyvä?
Not automatically. Extensions built for Luma and the Blank theme don’t necessarily work on Hyvä, and this is where most Hyvä projects either go smoothly or get surprising.
The reason is simple. Any extension that ships its own frontend code for the old theme may not behave properly on the new one.
Hyvä’s answer is compatibility modules. A compatibility module bridges a Luma/Blank extension to Hyvä by reimplementing the parts that don’t work. Hyvä also maintains a Compatibility Module Tracker where you can see which modules already exist. So for some extensions, a module may already exist. Check the tracker.
Work through it in this order:
- List every extension on your store, including the small ones nobody remembers installing.
- Mark what each one does on the frontend. A tax module that only works in the admin is very different from a product configurator that changes the product page.
- Check the Compatibility Module Tracker for each frontend-facing extension.
- Flag the gaps. Anything with no existing compatibility module needs a decision: replace it, rebuild the frontend part, or drop it.
Some of your extensions may turn out to be dead weight. A migration is a good excuse to remove things you stopped using a long time ago. Fewer extensions can also mean a lighter site.
If you buy extensions, ask the vendor directly whether they support Hyvä. Some extension vendors, including WebbyTroops for its own Magento 2 extensions, mark several of their products as Hyvä compatible. Check each product’s listing for the specific status.
Is Hyvä Checkout part of the theme?
No. Hyvä Checkout is a separate commercial product, so it needs its own decision and its own line in the budget.
It’s easy to assume it comes bundled. It doesn’t. Hyvä Checkout is built on Magewire, a server-driven PHP component framework, together with Alpine.js. In plain terms, it lets developers build interactive checkout steps while keeping much of the logic in PHP. Per Hyvä’s docs, it can run on a Luma theme and can be scoped to specific store views.
That second point is useful. You don’t have to treat the theme and the checkout as one all-or-nothing decision. You can decide on them in either order, depending on where your biggest problem is.
Because it’s commercial, add it to your budget conversation early. And don’t assume your existing checkout customisations carry over. They’ll need review.
What does a Hyvä customisation project involve?
Usually five areas of work: brand, layout and UI, extensions, performance and support. Exact scope depends on your store, so treat this as a map, not a quote.
If you hire a team for hyva theme development services, here’s what the work usually covers.
- Brand. Your colors, fonts, logo, spacing and tone need to be carried over, or refreshed, in the new theme. This is a good moment to fix inconsistencies that built up on the old one.
- Layout and UI. Product pages, category pages, the cart, the header and navigation, the footer, search. Each gets rebuilt or adapted in Hyvä’s templates. If your Luma store has custom page sections, they all need attention.
- Extensions. This is the compatibility work covered above. For many stores it’s the part that swings the timeline the most.
- Performance. Once the theme is running, someone should measure it against the Core Web Vitals thresholds and fix what’s still slow. Images, fonts, third-party scripts and hosting often need work even after the theme change.
- Support. Launch isn’t the finish line. You want someone to catch problems in the first weeks, when real traffic shows things testing missed.
How long does a Hyvä migration take?
It depends on your store. WebbyTroops states that a typical Hyvä customisation or migration takes 8 to 12 weeks. That’s their own stated range, not an industry standard.
The time varies with the number of extensions, how custom the design is, and how quickly feedback comes back from your side. A small, clean store can move faster. A store with heavy customisation will take longer.
If you’re specifically thinking about the move itself, there’s a longer walkthrough on moving from Luma to Hyvä.
What should you check in a Hyvä developer or partner?
Check how they handle extensions, Alpine and Tailwind details, checkout, post-launch support, testing and partner status. Many teams mention Hyvä, so it helps to ask how they work.
Here’s what’s worth asking about before you sign anything.
- Do they have a real answer on extensions? A good team will want to audit your extension list before quoting. If someone quotes a fixed number without asking what you run, be careful.
- Do they know the Alpine and Tailwind details? Ask which Alpine version the project will use and why.
- How do they handle checkout? They should be able to explain the difference between the free theme and the paid Checkout product without hedging.
- What happens after launch? Ask what support is included and for how long.
- Can they show how they test? Look for mobile testing, checkout testing and Core Web Vitals measurement, not just “it looks fine on my laptop.”
- Is their status verifiable? Ask them to show proof of any partner status they claim.
When you compare hyva themes developers, also ask how they’d split the work between design and engineering. Some teams are strong at one and thin at the other.
For reference, here’s what WebbyTroops states about itself. It describes itself as an official Hyvä Partner, with Adobe Commerce certified engineers. It also offers two months of free post-launch support with every Hyvä project, as stated on its customisation page. WebbyTroops states its own typical mobile PageSpeed figures as 20 to 45 on Luma and 85 to 98 on Hyvä. Those are WebbyTroops’ own typical numbers, not guarantees, and any team that promises you a specific score before seeing your store is guessing.
What should be on a pre-migration checklist?
Your current Core Web Vitals, a full extension list, a checkout decision, version checks and brand assets. Use this before you ask anyone for a quote. It will make every conversation shorter.
- ☐ I know my current mobile and desktop Core Web Vitals (LCP, INP, CLS) from real data, not just one test run.
- ☐ I have a full list of installed extensions, with notes on which ones affect the frontend.
- ☐ I’ve checked the Compatibility Module Tracker for each frontend-facing extension.
- ☐ I’ve decided what to do about extensions with no compatibility module: replace, rebuild or remove.
- ☐ I know which pages matter most: top landing pages, top product pages, the cart and checkout.
- ☐ I’ve decided whether Hyvä Checkout is in scope now, later or never.
- ☐ I’ve confirmed my Magento version and PHP version against Hyvä’s current docs.
- ☐ I’ve collected brand assets: logo files, fonts, color values and any design guidelines.
- ☐ I know who on my side approves designs and tests, and how fast they can respond.
- ☐ I’ve agreed what “done” means, including what gets measured after launch.
Which Magento and PHP versions does Hyvä need?
Hyvä’s docs list minimum Magento patch levels and a supported PHP range, and they change over time. Always check Hyvä’s current docs before you plan an upgrade around them.
At the time of writing, the docs mention Magento 2.4.4-p9, 2.4.5-p8, 2.4.6-p7 or 2.4.7-p1 and higher, with PHP 8.1 to 8.4. Treat that as a snapshot, not a promise. This guide does not confirm which Magento releases Hyvä supports. Check Hyvä’s docs, including for 2.4.8 and 2.4.9.
Separately, Adobe sets its own support dates for each Magento release line, and Adobe’s dates are the ones to trust. A theme move is also a good time to ask whether your platform version needs attention, because the two projects often overlap. Here is what Adobe’s release page lists at the time of writing.
| Release line | Adobe’s listed support dates |
|---|---|
| 2.4.9 | Released May 12, 2026. Regular support to May 31, 2029 |
| 2.4.8 | Regular support to May 31, 2028 |
| 2.4.7 | Regular support to May 31, 2027. Extended support to May 31, 2028 |
| 2.4.6 | Regular support ended Aug 11, 2026. Extended support ends Aug 31, 2027 |
| 2.4.5 | Regular support ended Aug 12, 2025. Extended support ended Aug 11, 2026 |
| 2.4.4 | Regular support ended Apr 12, 2025 |
Adobe recommends installing the latest patch for each line. If your store sits on an older line, read Adobe’s page directly, then compare it with Hyvä’s requirements before you set a plan.
What mistakes should you avoid on a Hyvä project?
Most problems on Hyvä projects are predictable. These are the ones to watch for.
Leaving Magento’s JS bundling on. Hyvä’s docs recommend turning off Magento’s built-in JS and CSS minification and bundling for Hyvä store views. It’s an easy setting to forget, and it can undo part of what you’re paying for.
Expecting the old captcha to work. Hyvä doesn’t support Magento’s legacy captcha. It uses Google ReCaptcha instead. If your login, contact or checkout forms rely on the old one, plan the swap.
Skipping the extension audit. Covered above, but it’s the number one cause of timeline surprises, so it’s worth repeating. Audit first. Quote second.
Treating the free theme as a free project. The theme costs nothing, but the project still takes people, testing and time. Budget for it.
Assuming Checkout is included. It isn’t. Decide early.
Mixing Alpine versions. A theme can’t mix Alpine 2 and Alpine 3. Make sure every custom script and compatibility module matches the version your theme uses.
Ignoring what’s still slow after launch. A new theme won’t fix oversized images, heavy third-party scripts or weak hosting. Measure after launch and keep fixing.
Skipping real-device testing. It’s usually worth testing on actual phones as well as on a desktop browser, because Core Web Vitals are about how real visits feel. Problems can hide when you only look at one fast machine.
Is a move to Hyvä right for your store?
It’s worth a serious look if your Luma frontend feels slow, costs too much to change, and you don’t rely on a pile of extensions with no Hyvä path. Since the theme is now free, the entry cost is lower than before.
Start with the two cheap steps: measure your current Core Web Vitals, and audit your extension list. Both take little time and make every next decision easier.
If you’d rather talk it through with a team, WebbyTroops offers a free 30-minute call and a free Magento audit, and it states that it is an official Hyvä Partner. A good hyva theme development company will look at your extensions and pages before giving you a plan. Book the call, bring your extension list, and ask the questions from this guide.
Frequently asked questions
Is the Hyvä Theme free?
Yes. Hyvä announced on November 6, 2025 that the Hyvä Theme was becoming free and open source. It was relicensed under OSL3 and AFL3 and became freely available from November 10, 2025, through GitHub and free Packagist keys. Some Hyvä products are still paid, including Hyvä Checkout, Hyvä Commerce and Hyvä Enterprise, and Hyvä UI is sold per store.
Do my Luma extensions work on Hyvä?
Not automatically. Extensions built for Luma or the Blank theme may not behave properly on Hyvä if they ship their own frontend code. Hyvä uses compatibility modules to bridge them, and a Compatibility Module Tracker lists the ones that exist. Extensions with no module need a decision: replace, rebuild the frontend part, or remove.
Is Hyvä Checkout included with the theme?
No. Hyvä Checkout is a separate commercial product. It is built on Magewire, a server-driven PHP component framework, together with Alpine.js. According to Hyvä’s docs, it can run on a Luma theme and can be scoped to specific store views, so you can decide on the theme and the checkout separately.
How long does a Hyvä migration take?
It depends on the number of extensions, how custom the design is and how fast feedback comes back. WebbyTroops states that a typical Hyvä customisation or migration takes 8 to 12 weeks. That is its own stated range, not an industry standard, and a small clean store may move faster than a heavily customised one.
Is Hyvä a headless build or a PWA?
No. Hyvä is a frontend theme for Magento 2 that keeps Magento’s PHP templating. Your catalog, orders, customers and admin panel stay where they are. It uses Tailwind CSS for styling and Alpine.js for interactivity, and it replaces what shoppers see in the browser rather than adding a separate frontend application.
Key takeaways
- Hyvä is a Magento 2 frontend theme, not a new platform, not headless and not a PWA.
- Hyvä Theme became free and open source on November 10, 2025 (announced November 6, 2025), but Hyvä Checkout, Hyvä Commerce and Hyvä Enterprise are still commercial.
- Audit your extensions first. Compatibility modules and the Compatibility Module Tracker decide how much extra work you face.
- Treat vendor-reported numbers, including Hyvä’s and WebbyTroops’, as their own figures, not promises for your store.
- Check Hyvä’s current docs for Magento, PHP and Alpine requirements, and check Adobe’s release page for support dates before you plan.
Sources
- Hyvä, “Hyvä is free and open source”: https://www.hyva.io/blog/news/hyva-is-free-open-source.html
- Hyvä: https://hyva.io
- Hyvä docs, getting started: https://docs.hyva.io/hyva-themes/getting-started/index.html
- Hyvä docs, working with Alpine.js: https://docs.hyva.io/hyva-themes/working-with-alpinejs/index.html
- Hyvä docs, compatibility modules: https://docs.hyva.io/hyva-themes/compatibility-modules/index.html
- Hyvä docs, Hyvä Checkout: https://docs.hyva.io/hyva-checkout/index.html
- web.dev, Web Vitals: https://web.dev/articles/vitals
- Adobe Commerce release versions and support dates: https://experienceleague.adobe.com/en/docs/commerce-operations/release/versions