Does Lovable Follow Your Design System? What 154 Sites Kept and Rewrote
Lovable loads your fonts and paints your colours. What it often does not keep is the design system behind them. Here is what we measured on 154 sites and the wording that fixes it.
7
min read

Table of Contents
Your Lovable site looks like your design. Underneath, on 82 percent of sites, it is still running the default theme.
Lovable follows your design almost exactly as far as anyone can see. It loaded the requested fonts on 97 percent of sites and painted a background matching the prompt on 88 percent. What it often does not keep is the design system underneath. On 82 percent of sites the default theme was still running underneath, with your colours copied into it by value.
Key findings
Lovable loaded 282 of the 291 font families our prompts asked for, which is 97 percent, and 95 percent of sites received every font they named.
The painted page background was visually indistinguishable from a prompt colour on 82 percent of sites and a close match on 88 percent.
Only 33 percent of the 493 colour values in the prompts appear in the compiled CSS as written. The rest were converted, often to
oklch(), which 52 percent of sites use.82 percent of sites still carry the default shadcn/ui theme variables, such as
--popover-foreground, so your colours usually live under the theme's names rather than yours.The fix is one paragraph in the prompt: tell Lovable to redefine the existing theme variables with your values and to use no colour outside your tokens.
That difference is invisible on launch day and expensive a few months later. This article shows what we measured, why it happens, and the four sentences that make Lovable use your tokens instead of its own.
How we measured it
We have 154 websites where we know exactly what the prompt asked for, because we wrote the Lovable prompts ourselves, and exactly what was built, because each site is published. Every prompt specifies its fonts and a colour palette as CSS custom properties. Across the set that is 291 font families and 493 colour values. It is the same set of sites behind our studies of Lovable page weight and Lovable credit costs.
Fonts were checked by what the page actually loaded. Colours were checked two ways: by searching the compiled stylesheet for the exact values from the prompt, and by loading each site in a browser, reading the colours it paints on its surfaces and buttons, and comparing them with the prompt in Lab colour space. A difference below about 2.3 is the point where two colours stop being distinguishable side by side.
The figures were measured on the published sites at the end of September 2026. The four examples in this article were checked again on 16 October 2026: we read the custom properties defined on :root in each live stylesheet, compared them with the :root block in the prompt, and read the painted colours by letting the browser draw each one to a single pixel and comparing the result with the prompt in Lab space.
Does Lovable use the fonts in your prompt?
Of 291 requested font families, 282 were loaded. 95 percent of sites received every family they asked for, including the fussy cases where a prompt wanted a display face, a body face and a separate monospaced face for small labels. This is close to perfect and needs no caveat. If you name a font, you get it.

Star Lanes, built from our bowling alley prompt. The prompt asks for Alfa Slab One on the headings and Space Grotesk for body text, and those are the two families the page loads and uses.
Does Lovable use the colours in your prompt?
Measured by what the browser paints, the palette arrives on almost every site:
The page background is visually indistinguishable from a prompt colour on 82 percent of sites, and a close match on 88 percent.
87 percent of sites show at least one prompt colour essentially exactly.
Only 4 percent of sites show none of the palette at all.
The median site displays half of the colours it was given. The rest are mostly states and details the prompt never covered.

What arrives on 154 sites built by Lovable, measured in the browser. Fonts and the overall colour scheme come through almost every time.

Good Boy Supply Co., built from our pet store prompt. The four numbered colours are painted exactly as the prompt defines them: each prompt value converts to the hex the browser painted, a Lab difference of 0. Look at the last column, though: the prompt's blue and pink tokens now live on the site under new names, cobalt and bubblegum.
Why Lovable rewrites your CSS variables
Search the compiled stylesheet for the exact values you wrote and the picture changes. Of 493 specified colours, only 161 appear as written, which is 33 percent. The colour is on the page, but not in the form you defined it.
The reason is in the stylesheet itself. These builds start from a template with a complete design system already wired in, and its fingerprints are on almost every site:
82 percent of sites carry the standard component theme variables, recognisable by names like
--popover-foregroundthat none of our prompts ever mentioned. This is the shadcn/ui theme that Lovable projects start from.52 percent store colours in
oklch(), the modern Tailwind default, rather than the hex values in the prompt.The median compiled stylesheet is 75 kB, most of it theme and utility classes rather than anything specific to the design.

What is actually in the compiled stylesheet. The colour you asked for is usually there, but rewritten into the default theme in a different notation.
So when you paste a :root block with your paper, ink and accent colours, you usually do not replace that system. Lovable reads your intent, produces the right colour and writes it into its own theme in its own notation. The page looks correct, but the components often reference the theme's names rather than yours. On some sites your names survive next to the theme. On others they disappear completely, as in the car wash build below.

Gleam Auto Spa, built from our car wash prompt. The prompt defines 20 colour tokens, 7 of them shown here. The live stylesheet holds the same values to the digit, but under the default theme names, and none of the 19 custom names exists. Colours without a theme slot were hard coded instead: the page code contains 111 colour classes with a raw hex value, such as text-[#648caa].
Why that costs you later
None of this shows up when you first publish. It shows up in three predictable ways once you keep working on the site:
Changing a colour is a search, not an edit. To change your accent you have to find every place the value was copied to, rather than changing one definition.
New parts come back generic. A section or component added later inherits the template default instead of your palette.
The details you never named stay default. Focus rings, form borders, disabled states and chart colours were never part of what you specified, so they keep the template look. This is why a site can match your design and still feel slightly off the moment someone clicks around.
Our accessibility audit of the same 154 sites found the same pattern from another angle: the colours the model picked on its own, outside the palette, were behind 70 percent of the contrast failures.
How to make Lovable use your design system
Three changes, in order of how much they matter:
Override the theme tokens by name. Do not only define your own variables like
--paperand--ink. Say that the existing theme variables must be redefined to your values, and name them: background, foreground, primary, secondary, muted, border, ring.Say it must replace, not extend. One sentence: the default theme is overwritten rather than supplemented, and no component keeps a default colour.
Ask for something you can check. Require that no colour appears anywhere in the code except your tokens. That turns a matter of taste into a search you can run.
A wording that works, placed directly under your colour block:
Fonts need no special wording, because they already arrive. Name them with weights and where each one is used, as in our guide on how to write an AI website prompt, and Lovable will load them.
How to check if Lovable used your tokens
Open the published site, view the stylesheet and search for --popover. If it is there and your token names are not, the original theme is still in control, however right the page looks.

The compiled stylesheet of the pet store site from the palette example above. The stock shadcn/ui theme block is still there, --popover included, and the prompt's palette is written over it in a second block. Anything the prompt did not cover, such as popover and chart colours, keeps the default value.
This is a better test than searching for your hex value. A missing hex value tells you very little, because it may simply have been converted to oklch(). Missing token names tell you that you have a picture of a design system rather than a design system.
What we have not measured
We measured the colours of surfaces and buttons, not of every element. Text colours, borders and icon fills are not in these figures, and the accessibility audit suggests the muted text colour is the least faithfully carried part of a palette.
Layout is not measured either. We can only count sections reliably on prompts that list them in a fixed format, which is a minority of the library, and we would rather leave that open than publish a number we do not trust. These figures describe Lovable specifically. Bolt and v0 start from different templates and we have not tested them.
Update, 30 September 2026. An earlier version of this research claimed that AI ignores the colours in your prompt, based on the 33 percent string match alone. Measuring the colours actually painted showed the palette usually does arrive. What goes missing is the token structure, which is what this article is now about.

