BricksSync turns your Bricks templates and settings into versionable files, so you never have to manually import and export again.
BricksSync solves the pain of managing Bricks Builder templates, components, styles, and settings across different environments and sites.
Instead of working inside the database, it saves your Bricks data as clean, structured JSON files, that can be synced and versioned (using GIT for example) between local, staging, and live, or even different websites.
Whether you’re a solo builder, an agency, or running a WordPress multisite and want to have a Bricks-based master theme, BricksSync gives you control, clarity, and a proper dev workflow — without touching code.
BricksSync v1.1.1 released!
Lifetime license available!
Full Components support!
Full Bricks 2.0 compatibility!
Full WordPress Multisite support!
- Sync between local, staging & live
- Use Git to version your Bricks work
- Reuse templates across projects
- Full Multisite support (Master Theme ready)
- No post content — just clean Bricks data
Features
Find out about BricksSync’s unique features.

Professional development workflow
Make your changes in Bricks Builder on your development environment, commit and push to GIT and release via CI/CD, or however you want it to work. Even manual uploading through FTP works!
File based theme and template migrations
BricksSync can generate and synchronize template files with Bricks Builder and you can configure your ideal workflow.
Automatic or manual synchronisation
For some use cases automatic synchonisation makes sense, for other you will want to use manual synchronisation. Configure BricksSync however you want to work.
Non-invasive integration
BricksSync merely adds file-based theme migration functionality to the website and keeps the existing database driven workflow intact. You can add or remove the plugin whenever you want, and you won’t loose anything on your website, except for the file-based template migration functionality of course. But since Bricks Builder works Database First, it stays Database First, you will just get some extra options.
No more database migrations
No more database migrations for theme and/or template changes. Just transfer the theme files in whatever way you see fit and import them manually or automatically.
Full Multisite support (Master theme)
With the BricksSync v1.0 release, full multisite support has been added. So you can now have one, or multiple Bricks powered master themes inside a WordPress Multisite. Very Powerful!
Quick demo's of BricksSync
Use cases
BricksSync adds file-based template migrations to Bricks Builder, these are some examples how it can be used.
Do you have other use cases or questions?
Bricks powered Multisite Master themes
With the BricksSync v1.0 release, full WordPress Multisite support has been added. So you can now have one, or multiple Bricks powered master themes inside a WordPress Multisite. Very Powerful!
Build ready-to-use Bricks Child themes
Build your own themes on Bricks, and easily use it on other sites or even distribute it to your clients.
GIT or CI/CD Workflow
Make your changes on your development environment, commit and push to GIT and release via CI/CD, or however you want it to work.
Manual FTP Workflow
BricksSync can generate and synchronize template files with Bricks Builder which you can transfer through FTP between sites/environments
Setup a centrally managed base theme
Because it’s so easy to transfer templates between sites, you can now use your Bricks Builder theme as a central base theme for all your websites and decouple design and content as you should.
You could even use it as a base for your WAAS (Website-as-a-service).
Separate backups of your templates
Since BricksSync generates and synchronizes a template file for every template in Bricks Builder, you can make and restore backups of your templates and/or themes without touching the database.
Easily reuse templates between sites
Since the templates are not coupled by ID, you can transfer and share single or multiple templates between different sites. For example, if you have a header you always use as a base, just copy the template file to your project.
Pricing
- Solo3 site activations$99
- Recurs yearly
- Price locked in for life
- Pro9 site activations$129
- Recurs yearly
- Price locked in for life
- AgencyUnlimited site activations$149
- Recurs yearly
- Price locked in for life
- Developer Lifetime LicenseUnlimited site activations$199
Frequently Asked Questions
We try to answer the most asked questions here, if your question isn’t listed here, please let us know!
What kind of files are generated?
Every template will be exported as separate JSON files. The settings, components and global styles will be exported as a single settings JSON file, as these are global as per Bricks’ design.
Can I make a static website with BricksSync?
No, BricksSync doesn’t generate HTML files. It’s a developer tool to easily transfer Bricks Builder templates, themes and/or settings to another Bricks Builder website. Please see the use cases to get a better idea of what it does.
Will this work for pages built in Bricks?
Currently BricksSync doesn’t support separate posts, pages and other custom posts that are individually built with Bricks Builder. It only works with templates (and settings). It doesn’t touch content to have a clear separation between content and theme.
Does it synchronize Media?
Currently BricksSync doesn’t support media migrations. It only works with templates (and settings). As media is generally seen as content, it doesn’t touch media to have a clear separation between content and theme.
Does it use ID's for synchronization?
BricksSync does not use database ID’s to synchronize the templates, because this can cause conflicts between sites.
Are the templates available publicly?
The generated templates are not available publicly in the standard configuration, but because BricksSync is a highly configurable development tool, you can make them available if you want.
Where are the generated files saved?
In the standard configuration, your files will be saved inside a protected directory of your child theme. Because BricksSync is a flexible developer tool, you can override this file location inside the settings page of BricksSync or inside the BricksSync configuration file.
What happens when I remove BricksSync?
When you remove BricksSync from your website, your website will stay alive just as it was. Nothing changes to the way Bricks Builder or your WordPress website works, except for the file-based template synchronisation functionality. It’s a true non-invasive add-on to Bricks Builder.