Pixflow layouts and components can be used in more than one way, depending on how you build sites and which design system you prefer.
Before installing anything, this guide helps you choose the correct Pixflow workflow for your project.
Choosing the right workflow from the start ensures:
- Clean imports
- No missing variables
- No duplicated styles
- No rework later
The Two Ways to Use Pixflow
Pixflow supports two intentional workflows:
- Remote Templates inside Bricks Builder
- Copy & Paste from the Pixflow Website
Each workflow supports different framework strategies.
Workflow A: Remote Templates (Pixflow Framework)
Best for:
- Structured, scalable projects
- Teams or repeatable builds
- Sites built primarily with Pixflow layouts
- Users who want a managed design system
How it works:
- Layouts and components are inserted directly inside Bricks Builder
- Templates are pulled from Pixflow’s remote library
- Assets are inserted as native Bricks elements
Requirements:
- Paid Pixflow plan
- Bricks Builder
- Domain whitelisting
- Pixflow framework styles installed
Important limitation:
⚠️ Remote Templates always use the Pixflow framework
Framework mapping is not supported for this workflow.
Workflow B: Copy & Paste (Framework Choice)
Best for:
- Existing sites using another framework
- Mixing Pixflow layouts with other libraries
- One-off usage or experimentation
- Maximum flexibility
How it works:
- Layouts and components are copied from the Pixflow website
- Pasted directly into Bricks Builder
- Output is always native Bricks elements
Framework options when copying:
- Pixflow Framework
- ACSS
- Advanced Themer
- Core Framework
- Raw CSS
Framework choice is applied at the moment of copying.
Do I Need to Import Pixflow Styles?
It depends on the workflow and framework you choose.
Pixflow Framework selected:
✅ Pixflow framework styles must be installed
Framework mapping selected:
❌ Pixflow framework styles are not required
Pixflow adapts at copy time — it does not force a single design system.
Copy & Paste vs Remote Templates (At a Glance)
| Feature | Remote Templates | Copy & Paste |
|---|---|---|
| Requires Pixflow framework | ✅ | Optional |
| Supports framework mapping | ❌ | ✅ |
| Works inside Bricks UI | ✅ | ❌ |
| Domain whitelisting required | ✅ | ❌ |
| Free plan supported | ❌ | ✅ |
| Rename & Copy available | ❌ | ✅ (paid) |
A Simple Decision Guide
Choose Remote Templates if:
- You want a fully managed Pixflow design system
- You plan to use Pixflow extensively across a site
- You want direct insertion inside Bricks Builder
- You are happy using the Pixflow framework
Choose Copy & Paste if:
- You already use ACSS, Advanced Themer, or Core Framework
- You do not want to import Pixflow styles
- You want Pixflow layouts to match your existing tokens
- You want maximum flexibility
What to Read Next
- Using Pixflow Layouts & Components
Learn how importing, copying, and BEM-safe reuse works. - Using Pixflow with the Pixflow Framework
If you chose the Pixflow framework path. - Using Framework Mapping (Copy & Paste Only)
If you chose the framework-agnostic copy workflow.
Summary
Pixflow does not force a single workflow.
You choose:
- How layouts are imported
- Which framework is used
- How styles are managed
Pixflow adapts at the point of use — so you can build the way you prefer, without compromise.