Bricks is installed and activated as a WordPress theme, not a plugin. Download the ZIP from your Bricks account, upload it through Appearance > Themes > Add New > Upload Theme, activate the theme, then enter your license under Bricks > License. After setup, learn the builder in the order that mirrors a real site build: interface navigation, pages, templates, theme styles, global classes, responsive layouts, dynamic data, and query loops.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
What Bricks Builder is—and what it is not
Bricks is a visual site builder for WordPress delivered as a theme. That distinction determines how you install, update, troubleshoot, and remove it. You do not upload Bricks from the Plugins screen. The official installation process is the same WordPress theme workflow used for any other theme: upload a ZIP, install it, and activate it.
As an Amazon Associate I earn from qualifying purchases.
Once active, Bricks provides a visual editing interface for constructing pages and templates while still using WordPress content. You can design layouts, connect elements to dynamic data, build query loops, reuse remote templates, and extend the builder with custom elements. The result is a site assembled from WordPress content and Bricks templates rather than a separate publishing system.
Think of the product in three layers:
- Theme layer: the installed and activated Bricks theme that powers the builder and front-end rendering.
- Builder layer: the visual interface where you add elements, set layout and typography, and create responsive rules.
- Content layer: WordPress pages, posts, custom content, and fields that can be inserted into designs as dynamic data or repeated through query loops.
Understanding those layers prevents two common beginner mistakes: looking for Bricks in Plugins, and treating every design as a one-off page instead of separating reusable templates, site-wide styles, and content.
Check these requirements before installing
Confirm that your WordPress hosting environment meets the current Bricks requirements before uploading the theme. The important checks cover PHP, the database, available memory, the maximum upload size, and browser support. The exact values can change with Bricks and WordPress versions, so verify the requirements that apply to the version you intend to install rather than relying on an old server checklist.
- PHP: your host must provide a PHP version supported by the Bricks release you are installing.
- Database: use a database engine and version supported by your WordPress installation and the current Bricks release.
- PHP memory: the site needs enough memory for the WordPress admin and visual builder to load reliably, especially on complex pages.
- Upload limit: the server’s upload limit must allow the Bricks ZIP file to be uploaded from the Themes screen.
- Browser: use a current, supported browser for the builder interface. An outdated browser can look like a Bricks problem when it is actually an editor compatibility issue.
Also prepare administrator access to WordPress and the account credentials used to obtain your Bricks download and license key. If you are replacing another theme, make a backup and confirm how that theme stores templates or settings before switching; changing themes can affect the presentation of existing content.
Install Bricks as a WordPress theme
The normal installation takes place entirely in WordPress’s theme uploader. Keep the downloaded ZIP intact; WordPress expects the theme archive rather than an extracted folder.
- Sign in to your Bricks account. Open
my.bricksbuilder.ioand download the latest Bricks ZIP that your account provides. Do not unzip the file before uploading it. - Open the WordPress theme installer. In the WordPress dashboard, go to Appearance > Themes, select Add New, and choose Upload Theme.
- Select the archive. Use the file picker to select the downloaded
bricks.zip, then choose Install Now. WordPress uploads and unpacks the theme. - Activate Bricks. When installation completes, select Activate. Bricks is now the active theme and its builder is available for your site.
- Open the license screen. In the dashboard, go to Bricks > License. Paste the license key from your Bricks account and choose the activation control shown there.
Uploading the ZIP under Plugins > Add New will not install Bricks correctly because Bricks is not a plugin. If WordPress reports that the package is too large or cannot be installed, check the server upload limit, confirm that you selected the original ZIP, and ask the host to verify file permissions and available disk space.
Activate and manage the Bricks license
License activation is separate from theme activation. The site can be running the theme while the license is still unentered, but an activated license is needed for the account-linked update service and any license-controlled features.
Dashboard activation
Copy the key exactly as displayed in your Bricks account, open Bricks > License, paste it into the license field, and submit it. If activation fails, check for leading or trailing spaces, confirm that the key belongs to the account you used to download the ZIP, and make sure the site’s URL is reachable by the licensing service.
Configuration-managed activation
For blueprint-driven or code-managed sites, the official license documentation also describes defining BRICKS_LICENSE_KEY in wp-config.php. Use that method only after checking the instructions for the exact Bricks version on the site. A constant name or placement that is correct for one release should not be assumed to be unchanged in another.
What happens after activation
Activated sites receive Bricks update notifications in the WordPress dashboard. License validation and update checks send the site’s URL or domain and the installed Bricks version to the licensing service. Treat that exchange as part of your site’s operational and privacy documentation, particularly when a staging domain is publicly reachable.
Find your way around the builder before designing
Open a page in Bricks and spend a few minutes identifying the main working areas before changing styles. The exact control names can evolve, but the concepts remain consistent:
- Structure or element tree: the hierarchy of sections, containers, blocks, and content elements. Selecting the right parent is essential when spacing or width appears wrong.
- Canvas: the visual preview of the page. Use it to confirm hierarchy and responsive behavior, not as a replacement for checking the published page.
- Settings panels: controls for layout, spacing, typography, colors, borders, backgrounds, visibility, and interaction states.
- Responsive controls: breakpoint-specific values that let a desktop layout adapt to smaller screens.
- Data and template controls: options for inserting WordPress fields, choosing a template context, or repeating content through a query.
Start with a blank test page or a disposable draft. Learn how to select a parent element, duplicate an element, undo a change, and preview the page at different viewport widths. These small operations save more time than immediately copying a complex design.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →A beginner learning path that scales to a full site
The most efficient sequence follows the progression of the official Getting Started curriculum. Each stage introduces a concept that the next stage depends on.
1. Builder navigation and element hierarchy
Practice adding a section, placing a container inside it, and adding text, image, button, and layout elements inside the container. Learn to distinguish the element’s own settings from the settings inherited from its parent. When a child appears misaligned, inspect the tree first: an unexpected parent width, display mode, gap, or padding is often the cause.
Use meaningful labels for major sections while you build. A tree that says “Hero,” “Features,” and “Signup” is easier to maintain than one filled with anonymous containers.
2. Build a simple page
Create a home-page draft with a header area, a short value statement, a primary call to action, a feature section, and a footer call to action. Concentrate on structure rather than polish. Keep content in normal WordPress fields where possible so it can be edited without rebuilding the layout.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Save regularly and view the draft outside the editor. The editor canvas is a design aid; the front end reveals real font loading, content wrapping, link behavior, and interactions with the active WordPress environment.
3. Create templates
Pages are appropriate for unique content; templates are appropriate for repeated structures. Use templates for items such as a site header, footer, single-post layout, archive layout, or a reusable callout. Decide which parts belong to the template and which belong to the content record before you start styling.
A useful test is to change one piece of content. If changing a post title requires editing a template, the title was placed in the wrong layer. If every post needs the same structural change, it belongs in the template.
4. Set theme styles
Establish the site’s base visual rules before styling every element individually. Define the typography, color palette, spacing approach, and other global defaults available in the theme-style controls. Then build pages on top of those defaults.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesGlobal defaults reduce drift: a later type or color change can update the system rather than requiring a search through every page. Keep exceptions deliberate and document them in your naming conventions.
5. Use global classes
Global classes are reusable style definitions for patterns such as buttons, cards, labels, and content wrappers. Create a small vocabulary with names that describe purpose rather than appearance—for example, a class for a primary action rather than a class named “blue-button.” Purpose-based names survive a redesign.
Apply classes consistently and avoid combining many near-duplicate classes. When a component needs a one-off adjustment, add a clearly named modifier instead of silently overriding several unrelated rules.
6. Design responsively
Build the wide layout first only when that matches your content strategy, then check every breakpoint available in the builder. Reduce columns, adjust gaps, resize type, and change alignment where the content needs it. Do not assume that a layout that looks balanced on a large monitor will remain readable on a phone.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Check long headings and buttons for wrapping.
- Confirm that navigation remains usable when the available width shrinks.
- Inspect images for cropping and excessive download dimensions.
- Look for horizontal scrolling caused by fixed widths, large gaps, or overflowing content.
- Test real links and forms at each important viewport size.
7. Connect dynamic data
Dynamic data lets a design pull values from WordPress instead of hard-coding them. Use it for titles, excerpts, featured images, author information, dates, and other fields available in the current context. A single template can then present many records while each record supplies its own content.
Before inserting a dynamic value, identify its context: a single post, an archive, a page, or an item inside a loop. A field that exists for one context may be empty in another. Preview with representative content, including records with missing images or unusually long titles.
8. Build query loops
Query loops repeat a design for a selected set of WordPress records. Use them for post grids, related content, product-like listings, team directories, or any repeated collection. Define the query first—post type, ordering, limits, and any available filters—then design the repeated item inside the loop.
Keep the repeated card self-contained: image, title, supporting data, and link should all refer to the current loop item. Test an empty result, a single result, and a full result set so the surrounding layout does not collapse unexpectedly.
Move from a first page to a maintainable site
Separate content, templates, and presentation
Put editorial text and media in WordPress content fields, repeated structures in templates, and reusable visual rules in theme styles or global classes. This separation makes it possible to change content without redesigning the page and to redesign the site without rewriting every post.
Use remote templates deliberately
Bricks supports remote templates, which can make a design available across sites or installations that are configured to retrieve it. Treat a remote template as a dependency: record where it comes from, what content context it expects, and what happens if it is unavailable. Keep a local fallback for critical site areas.
Plan custom elements only after mastering native elements
Custom elements can extend the builder when a project needs a component that the standard element set does not provide. Before commissioning or writing one, confirm that the requirement cannot be met with a template, global class, dynamic data, or a query loop. Custom code adds another update and testing responsibility.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Bricks pricing and license limits in 2026
The following are the listed Bricks plans in 2026. Annual plans renew yearly; the lifetime option is a one-time payment. The figures are in U.S. dollars and should be treated as the listed prices for that period, not as a guarantee of future pricing or taxes.
Free tools Windows power users keep installed
One-click scans. No signup required.
| Plan | Price | Production websites | Payment term | Local and staging sites |
|---|---|---|---|---|
| Starter | USD 79 per year | 1 website | Annual | Do not count toward the license limit |
| Business | USD 149 per year | 3 websites | Annual | Do not count toward the license limit |
| Agency | USD 249 per year | Unlimited websites | Annual | Do not count toward the license limit |
| Ultimate Lifetime | USD 599 once | Unlimited websites | One-time payment | Do not count toward the license limit |
Choose by the number of production websites and the payment model you can support, not by assuming that a higher tier automatically adds a builder feature. The listed plan information establishes site counts and billing terms; it does not establish an affiliate benefit or any feature not shown on the official pricing page.
Local and staging URLs are excluded from the production-site limit. You should still label those environments clearly and avoid treating a publicly accessible staging site as a production deployment when reviewing license usage.
Updates, staging, and common setup problems
The theme ZIP will not upload
Check that you selected the original bricks.zip, that the server upload limit is large enough, and that the account has administrator privileges. A full disk or restrictive file permissions can produce an installation error even when the ZIP is valid.
Bricks is missing from the dashboard
If you uploaded the archive under Plugins, remove the failed plugin installation and repeat the process under Appearance > Themes > Add New > Upload Theme. Bricks appears in the dashboard after the theme has been installed and activated.
Recommended Free Tools
The license key is rejected
Re-copy the key without extra spaces, verify the site’s domain, and confirm that the key is active in your Bricks account. If the site was cloned from another environment, check whether the clone retained the original domain or license state. For a code-managed deployment, compare your BRICKS_LICENSE_KEY declaration with the version-specific documentation.
No update notification appears
Confirm that the license is activated, the WordPress site can make outbound HTTPS requests, and the installed version is recognized by the licensing service. Remember that update checks use the site’s URL or domain and Bricks version; a blocked connection or altered domain can prevent the notification from appearing.
The builder is slow or unstable
Start with the environment rather than changing design settings at random. Verify the PHP and memory requirements, update the browser, disable conflicting extensions for a test, and check whether the problem occurs on a new blank page. A very large page tree, heavy media, or another WordPress component can also make the editor difficult to use.
The published page differs from the canvas
Clear relevant caches, view the page while logged out, and inspect responsive settings at the viewport where the difference occurs. Then check inherited styles and template conditions. A front-end difference can come from caching or from a template rule that is not obvious while editing a single page.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11A practical first-session checklist
- Confirm PHP, database, memory, upload-size, and browser compatibility.
- Download the current ZIP from
my.bricksbuilder.io. - Upload it through Appearance > Themes > Add New > Upload Theme.
- Activate the theme, then open Bricks > License.
- Activate the key and record which production domain uses it.
- Create a disposable page and learn the element tree, canvas, and responsive controls.
- Build one simple page before creating a full set of templates.
- Define theme styles and a small set of global classes before detailed styling.
- Test a template with real WordPress content, including missing and unusually long fields.
- Use dynamic data and query loops only after you understand the content context they will read.
- Check the front end at desktop and mobile widths, logged in and logged out.
- Keep staging and production domains clearly separated and monitor update notices.
What to learn next
After the first session, repeat the learning path on a small, realistic site rather than a collection of isolated experiments. Build a page, turn its repeated parts into templates, move recurring visual rules into theme styles and global classes, then replace hard-coded text with dynamic data where the content model calls for it. Finish by converting a repeated listing into a query loop and testing it with several content records.
This order gives you a working mental model: Bricks supplies the visual design system, WordPress supplies the content, templates supply reusable structure, and queries supply repetition. Once those relationships are clear, advanced work such as remote templates or custom elements becomes a deliberate extension instead of a workaround for a missing foundation.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
