Overview
Components are reusable blocks you create once and use in multiple emails. They help maintain visual consistency and speed up email creation. Think of them as email “Lego blocks” with a shared design system.Component vs Email
Component (Master)
Stored in component library
- Fixed design structure
- Reusable across multiple emails
- Editable from the library
- Changes propagate to all emails using it
- Single source of truth for design
Email (Instance)
Individual email template
- Contains component instances
- Can override content via overrides
- Complete email structure
- Design inherits from component master
- Can have multiple component instances
Creating a Component
You can create components in two ways:1
From email editor
Select multiple elements in an email, then convert them to a component. The selected elements become the component’s structure.
2
From library
Create a new empty component in the library, then add elements to it using the editor.
Component Structure
A component contains:- Properties: Metadata (name, type, visual properties like background, padding)
- Children: Hierarchical element structure (same as emails)
- Style Library: Uses the same design tokens as emails
Using Components in Emails
When you insert a component into an email, it becomes an instance of that component:The instance references the master component. You can override content (text, links, image URLs, alt text, and background images), but layout and styling stay linked to the master component. See Component Overrides.
Example: Newsletter Header Component
Component Master (in library):- Logo image
- Title text (“Weekly Newsletter”)
- Navigation menu
- Uses master design (logo, colors, spacing)
- Override: Title text → “Product Updates”
- Uses master design (same as Email 1)
- Override: Title text → “Monthly Digest”
- Override: Logo image → Different logo
Component Types
Components can contain any type of element:Simple elements
Simple elements
Text, buttons, images, separators, and social links all work inside components.
Structural elements
Structural elements
Groups, multi-columns, and sections can be part of a component structure.
Components inside components
Components inside components
A component can contain groups, multi-columns, and simple elements, but not an instance of another saved component. Component instances live in emails, where you can place them inside groups and columns alongside your other content.
Best Practices
🎯 Single purpose
Each component should have a clear, single purpose (e.g., “Header”, “Footer”, “CTA Button”).
🎨 Use design tokens
Build components using tokens from your Style Library, not manual values.
📝 Name clearly
Use descriptive names like “Product Card” or “Newsletter Header” instead of “Component 1”.
🔄 Keep reusable
If you find yourself copying elements often, it’s a good candidate for a component.
Component Library
Before saving a shared component, review its usage and the emails affected by the change. Saving the master updates the linked design in those emails; it does not automatically sync their exported HTML to a sending tool. Your component library is accessible from:- The main navigation menu
- The email editor (insert component button)
- The component editor (for editing existing components)
Components are account-wide, so all your emails can use any component you’ve created.
