The Style manager changes how a whole family of elements looks. It is the difference between editing one button and editing every button on the site.
Last updated
Open Style manager from the top bar. The styles are grouped by category: buttons, typography, dividers, menus, images, forms, and so on.
Each card shows a live preview, the style name, and its internal name. Use the light and dark button on the preview when a style is hard to see against the default background.
The three-dot menu on a card has the actions for that style. Show advanced at the bottom reveals the less common categories.
The Style manager is project-wide. A change there affects every page, not just the page you were editing.
Changes appear in the editor right away after you save. They go live with the next publish.
There is no undo history for Style manager changes. Built-in styles can be restored. Custom styles cannot.
A base style is the shared foundation behind a kind of element, such as a button.
A variation is a named version of that base. A button can have a primary variation, a soft variation, and an outline variation. They share the button base but set some properties differently.
This means a change to the base reaches every variation, unless a variation sets the same property itself. If a variation still looks different after a base change, edit that variation too.
The Style manager lists both kinds. Some shared bases, such as Base button, are in the advanced Base styles category, so choose Show advanced to see them. Others, such as Paragraph and Heading 1, appear in their own category.
When you change a built-in, it has a project override until you restore it. Custom variations can be renamed or deleted.
Editing the base button changes every button. Editing the primary variation changes only primary buttons. Use Merge styles into base style when you have already styled one element and want to move those classes into either target.
Read Variations for that workflow.
Open the action menu on a built-in style or variation and choose Edit classes.
Add or remove classes in the Classes field, then save. The card preview and the editor update.
This does not destroy the original. A customized built-in gets a Restore default action. Restoring brings back the original look.
To edit the shared button base, choose Show advanced, open Base styles, and edit Base button. That reaches every button, including all its variations.
Built-in styles and variations cannot be deleted. Only custom variations and custom base styles can be deleted.
Variations are created from the editor, not from the Style manager.
Select an element that supports variations, open the palette button in its floating toolbar, and choose New variation. Give it a name. It captures the current look of the element and adds it to the picker and the Style manager.
Read Variations for the full flow and for switching between variations.
Sometimes you style one element until it looks right, then decide every similar element should look the same.
Select the element, open the palette button in its floating toolbar, and choose Merge styles into base style. The dialog that opens is called Apply styles everywhere.
This action is available for elements that support variations, such as buttons, headings, and images. For a section or row, edit the shared style in the Style manager instead.
The dialog shows the extra classes on that element. Choose the classes you want to share, then choose the target:
A variation target, such as the primary button, changes only that variation.
A base target, such as the button base, changes every element using that base.
After you apply, the shared classes live in the style and are removed from the one element.
This is the usual way to make every base item look the same when the base has no card of its own.
Read Variations for the target choice and an example.
New base style creates a named bundle of classes. It is not a variation and does not appear in the variation picker.
This is an advanced feature. You give the bundle a name such as x-card, add classes, and then apply it by adding that name to an element's class list.
Read Custom classes (advanced) for the class list workflow.
Use the Style manager when the change should apply everywhere:
All primary buttons should be a little rounder.
All headings should use a different weight.
All menu links should have more space.
All form fields should have a softer border.
Use the Box and Text tabs when the change is only for one block.
If a shared change is too broad, make a variation instead and apply it only where you need it.
To make every primary button match your brand:
Open the Style manager.
Find the Button category.
Select the primary variation.
Choose Edit classes.
Change the fill, text color, radius, and padding.
Save.
Check a page with a primary button.
Publish.
Then check mobile. A button that looks good on desktop can be too small to tap on a phone.
To change every button, not just the primary one, add the common classes to the base with Merge styles into base style, or edit each variation.
A website builder that works like a document. CMS, forms and EU hosting included.
© 2026 Remake. All rights reserved.
