Style Guide FAQs
Get all the questions related to setting up your style guide in Maker answered here
Privacy & Access
Where is the imported data stored, and who on my team can see it??
Anyone who is a member of the organization can see all fonts used across the style guides.
How are licensed fonts and brand files handled so they aren’t shared outside our team??
Font URLs must be publicly accessible in order to load on a website. But they are not shared outside of an organization unless DevTools is used to inspect the AI-generated page to extract those URLs.
Saving & Updates
If I already have a style guide, does this update it or create a new one? Can I choose?
You can choose. While working on a project, Maker will also prompt you to save recent design changes to a style guide if it detects you asked it to make changes to a design element. When you ask Maker to “save to style guide,” it knows if the project is already linked to a style guide and only updates the linked style guide, and will not create a new style guide unless asked explicitly.
If names or settings clash with my current guide, how do I pick which one to keep?
Maker will decide which one to keep and which one to omit.
Speed, Limits & Reliability
How long does a typical import take? Is there a progress bar?
The amount of time it takes depends on the size of the context given to Maker. Large files and too many screenshots can slow it down. It can take several minutes. There is no progress bar at the moment.
Are there limits on the number of pages or asset sizes Maker's Style Guide can handle?
The real limit is the context window, which is 200,000 tokens. We have no limit on asset size.
General Questions
If I update my Style Guide, will existing projects update automatically?
No. Existing AI-generated projects never auto-update, and republishing won’t apply new styles. To use the latest Style Guide, Remix the project with the current style guide—this creates a new copy so the original stays intact while you test and fix any compatibility issues from the updated Style Guide.
If a font is a Google Font, will it be available automatically, or do I still need to upload files?
No need to upload Google Fonts; you can ask Maker to use the Google Font of your choice in the style guide instruction doc or the context field. For example, add “Use Playfair for the headings and Inter for the body text,” and Maker will know how to do that.
If I import into a project and then “save as style,” does that update the current style or create a new style?
It depends on how the project was created. Projects started with a style guide can modify the style guide they’re linked to. Projects created without a style guide will be saved to a new style guide.
If a new style is created, is there a way to merge it into the existing guide?
Currently, there is no option to merge two style guides.
Are there versions or changelogs for style guides so one can roll back after an import?
There is no versioning at the moment for style guides.
If some font uploads fail, can I still proceed with the project and fix items later?
Yes, you can fix those later by uploading font files and regenerating the style guide.
When a font is missing, what is the fallback?
Fallback fonts are defined by Maker automatically and we will try to use system fonts as a fallback.
What happens when a font is missing—do I get a prompt to add it?
Yes, you’ll see a button “Missing fonts” in the project preview.
Are there any limits on the number/size of font files and assets per style guide?
There’s no limit to the number of fonts or assets you can add, but each uploaded file is limited to 5 MB.
Where are uploaded fonts stored? Is it per style guide or account?
Fonts are stored in an S3 bucket at /fonts/{orgId}/theme/{themeId}. They’re shared within a style guide, keeping them organized by the style guide.
Can I continue adding assets (screenshots, palettes, logos) to the same style guide to incrementally upload additional fonts and brand details, or do I need to create a new guide each time?
Yes, you can continue adding assets and regenerate existing style guides at any time.
NOTE: Regenerating or editing a style guide doesn’t automatically update projects created from an older version. To apply changes, remix the project with the theme; fix any incompatibilities in the new remix while the original remains intact.
For custom fonts, which file formats are supported?
Supported font formats: TTF, WOFF, WOFF2, and OTF.
How are weights/styles mapped from Figma text styles to the Style Guide?
We import the style names (family + weight/italic) as text tokens, but Figma doesn’t provide the actual font files—so they come in as Missing. Upload the correct fonts to your Style Guide, then use Missing Fonts in the project to map each style to the matching family/weight. Once mapped, all tokens resolve; if an exact weight isn’t available, we fall back to the closest weight.
If the imported Figma designs conflict with my Style Guide, which wins?
Imported layouts remain intact; Style Guides govern AI-generated and edited outputs. To enforce a new style across an imported project, Remix it and reapply the Style Guide
Can I make a Style Guide the default for all new projects?
Yes. Set it as the default in Settings → Style Guide; new projects will start with it.
How can I make a new page match the design style and fonts of an existing project?
There are two good options, depending on what you are trying to do:
Option 1: Duplicate Project 1 (fastest way to match the design exactly) If you want Project 2 to inherit the exact same look and feel, duplicate Project 1 and use it as your starting point. Then replace the content and adjust sections as needed. You can duplicate from the top-left dropdown menu.
Option 2: Save Project 1 as a Style, then apply it to Project 2 (best when Project 2 already exists) If Project 2 is already built but you want it to adopt the same style as Project 1, save Project 1 as a Style and then apply it to Project 2 using Remix.
How to apply a saved style to Project 2 (while keeping structure and content):
Open Project 2.
Click the top-left dropdown menu.
Select Remix.
Choose the saved style from Project 1.
Run Remix to update the project’s styling (fonts, visual language, design system) while keeping the existing content and structure.
Tip: If your goal is a perfect visual match and you have not built Project 2 yet, duplicating Project 1 is usually the simplest. If Project 2 is already created, Remix is the best way to switch it to the saved style.
Last updated
Was this helpful?