- asks a short set of design questions about color, typography, and layout, or
- builds directly when the visual direction is already clear.
Key benefits
- Steer the visual identity. Choose the color palette, typography, and layout before Lovable writes any code.
- Decide visually. Options appear as color swatches, font samples, and layout wireframes, so you compare looks instead of describing them.
- Fewer revisions. Lovable applies your choices from the first build, so you spend less time correcting the look afterwards.
- Stay in control. Pick an option, write your own preference, or skip the questions. Lovable builds either way.
Design questions
When your prompt leaves the look open, Lovable shows a question card in chat before it builds (in Plan mode, before it writes the plan). The card has up to four questions. Three of them are design questions, each with up to four options that Lovable picks to fit your project:- Color palette
Palettes shown as color swatches, from dark and moody to light and clean, warm and earthy, bold and vibrant, soft pastel, nature-inspired, and professional. - Typography
Heading and body font pairs, each shown in its own fonts, such as a geometric pair for a tech product or an editorial serif pair for a magazine. - Layout
Page structures shown as wireframes: hero grid, single column, split screen, sidebar, masonry, bento grid, magazine, dashboard, full-width sections, zigzag, card grid, asymmetric, broken grid, feed, or gallery.
When design questions appear
Lovable asks design questions when your request involves visual design but leaves the direction open. This is common for landing pages, portfolios, blogs, marketing sites, and other visually expressive apps. Prompts like these lead to design questions:When Lovable builds directly
Lovable skips design questions and builds directly when:- your prompt gives a specific design direction, such as named fonts, colors, a brand, or a style like “minimal black and white with Swiss typography”,
- the request is purely functional, such as a to-do app, a calculator, or adding authentication,
- the app type has standard defaults, such as dashboards, admin panels, and apps that mainly manage records,
- the project was created from a template, including design templates, or is connected to a design system, because the design is already set.
FAQ
Can I bring my own typeface or palette?
Can I bring my own typeface or palette?
Yes. Write the font or colors in the text field under the question instead of picking an option, or name them in your prompt. To share fonts, colors, and components across projects, connect a design system.
What happens if I skip the design questions?
What happens if I skip the design questions?
Lovable continues with reasonable defaults for the work you asked for. It does not start additional work because you skipped. You can change the look at any time by describing the change in chat.
Can I change the design after the build?
Can I change the design after the build?
Yes. Describe the change in chat, or use the preview toolbar to select an element and describe what to change. To keep the design consistent in later prompts, save your fonts, colors, and style keywords to your project knowledge.
Does this work for dashboards or internal tools?
Does this work for dashboards or internal tools?
Lovable asks design questions where the look matters most, such as landing pages, marketing sites, blogs, and portfolios. Dashboards, admin panels, and apps that mainly manage records use Lovable’s standard build flow. You can still request a specific look for them in your prompt.
What happens if I'm using a design system or template?
What happens if I'm using a design system or template?
Lovable skips design questions and builds with the existing tokens, components, and visual rules from the template or design system.
Does this cost extra credits?
Does this cost extra credits?
No. Design questions are part of the message you send and do not add credit costs beyond that message.