Does Hyvä Force a Generic Look? Custom Branding on Tailwind

There is a myth that moving to Hyvä means giving up your brand and accepting a plain, templated look. It comes from seeing a few unstyled demos, and from a criticism you hear in conversation more often than you read in writing: that Hyvä stores all look the same.

The short answer is that Hyvä has no design opinion at all. The longer and more useful answer is that stores do sometimes converge on a similar look, and the reason has nothing to do with Tailwind. It is worth knowing what actually causes it, because that is the part you can control.

Hyvä has no design opinion, and that is documented

Hyvä publishes a technical vision page listing what the project is trying to achieve: reduced complexity, performance, developer experience, delivery speed, fewer dependencies, a lower learning curve. Design and aesthetics are not on that list. Their own description of the goal is the version of Luma they wished Magento had built.

The default theme was built from scratch using a completely blank theme, with all layout XML, all template files and all JavaScript removed. It is a foundation, not a design.

The clearest evidence is what Hyvä does not ship. There is no official Figma file for the default theme. Their own FAQ says so directly. The only Figma they publish belongs to Hyvä UI, which is a separate paid component library. A project that intended everyone to arrive at the same storefront would ship a design file. Hyvä ships a blank one.

Since November 2025 the theme itself has been free and open source under OSL-3.0 and AFL-3.0. Founder Willem Wigman gave lowering the barrier to entry as one reason, and explicitly pointed to premade templates becoming available. Hyvä expects a market of visually different starting points, not one house style.

What Tailwind actually is

Hyvä styles the storefront with Tailwind, a utility CSS toolkit. That is not a fixed design. It is a set of building blocks for any design. The same way a blank page and a full set of pens do not force one drawing, Tailwind does not force one look.

The important difference from a component framework is where the opinions live. A themed framework ships finished buttons, cards and navigation that you then fight to change. Tailwind ships none of that. What it ships is a configuration file, and that file is where your design system goes: your colour palette, your type scale, your spacing rhythm, your breakpoints, your shadows and radii. A designer who fills that file in properly has defined the brand before a single page is built.

This is also why Hyvä gives you more control than a heavy Luma theme, not less. On Luma you inherit thousands of lines of styling written for somebody else’s shop and spend your budget overriding it. On Hyvä there is nothing to override.

So where does the sameness actually come from

Three real causes, and none of them is the theme.

Hyvä UI. This is the optional paid component library, and it is the one thing in the ecosystem that does ship a finished look, complete with a Figma file. It is good, it is fast to build with, and it costs a fraction of designing from scratch. If two agencies both buy it and ship close to stock, their stores will rhyme. That is a procurement decision, not a limitation of Hyvä.

Upgrade economics. This is the real one, and Hyvä states it plainly in their upgrade documentation: the more files are customised, the more work an upgrade becomes. Every template you override is a file somebody has to diff against the new version, every time. An agency that prices upgrades honestly is quietly incentivised to override fewer templates, keep the default markup, and express the brand only through Tailwind classes. Applied without judgement, that pressure is what makes storefronts converge. It is invisible to the merchant and it shows up as a design constraint nobody ever agreed to.

Budget. A blank base means somebody has to actually design the store. If no one is paid to do that, you ship the default. The theme did not force the outcome. The scope did.

The honest version of the criticism is therefore not that Hyvä makes stores look alike. It is that Hyvä makes it cheap to not decide.

The real constraints, named

Design freedom on Hyvä is genuine, but it is not unlimited, and the limits are technical rather than aesthetic. These are the ones that actually affect a design brief.

Templates are the smallest unit

Hyvä uses .phtml templates as its smallest component. There is no atomic component system underneath, so the granularity of your design system is bounded by Magento’s template fallback. If your designer thinks in small reusable parts, someone has to map that onto template files early. Doing it late is expensive.

Tailwind cannot see your PHP

The Tailwind compiler scans your source files for class names. It cannot evaluate PHP, so a class assembled at runtime from a variable silently produces no CSS at all. The page renders, the style is simply missing. The fixes are to drive the variation with CSS custom properties, or to declare the candidate classes somewhere the scanner can find them. Worth knowing before a designer specifies a component with a configurable column count.

Merchant-authored content needs the JIT compiler

Tailwind classes typed into a CMS page or a Page Builder block are not in the build scan either, for the same reason. Hyvä ships a browser-side JIT compiler module to cover this. If your marketing team is going to hand-write layout classes in the admin, that module has to be part of the plan, not a discovery made after launch.

Child themes copy the whole build configuration

The documented way to customise is a child theme, and a Hyvä child theme requires a complete copy of the Tailwind build configuration, pointed back at the parent. The format of that configuration has changed more than once across Hyvä versions. It is a small tax, but it is a real one, and it is the piece most often missed when a team estimates the work.

There is a build step

Tailwind compiles. That means Node on your development and build machines, a compile stage in your deployment, and Magento’s own JavaScript and CSS minification and bundling switched off so it does not undo the work. None of this is difficult. All of it needs to exist before the first design lands.

Branded, fast, and distinct

Distinct design and top performance are not a trade-off on Hyvä. The public Hyvä case study index alone covers stores as unlike each other as a fitness equipment retailer, a boat outfitter, a wine merchant, a garden timber supplier, an audio manufacturer with sites in eight languages and the Amnesty International shop. They share a rendering approach and nothing else.

Our own client stores run on the same base and none of them look alike, because the base is a foundation, not a template. You get a store that is unmistakably yours and still scores 90 to 100 on PageSpeed, the way Vitacom does after its rebuild: from 12 to 100, with server response down from 15,814ms to 12ms. Read the full Vitacom case study.

Where the real limits are

The honest caveat: a design that fights the web will slow any theme down, Hyvä included. Design freedom is real. Design discipline is what keeps the store fast.

The choices that actually cost you speed are specific and predictable. A hero image that is not the first thing the browser is told to fetch. Four font weights when two would do, loaded without a fallback so text stays invisible while they download. Carousels and review widgets injected above the fold by third-party scripts. Components that change height after they render, which shifts the page under the customer’s thumb. Every one of those is a design decision, and every one of them is negotiable while it is still a mockup.

A good partner tells you where a creative choice will cost you speed before you ship it, not after the PageSpeed score comes back. And they tell you which of your existing extensions will survive the move, because a third-party widget you kept can undo the theme’s advantage on its own.

Book a free strategy call

Have a design in mind, or a brand you do not want to compromise? We will show you how it translates to Hyvä without losing speed, and tell you honestly where a choice will cost you performance. Book a free strategy call.