Bricks Builder Review (2026): The Theme That Replaces Your Page Builder

Who sells Bricks, and how long has it been around?

Bricks is sold by Codeer Limited, a company registered in Cyprus (registration HE 383869, based in Paphos), with Thomas Ehrig named as its representative on the legal page. Version 1.0 shipped on March 15, 2021. Version 2.4 arrived on September 16, 2026, and 2.4.2 followed on September 28, the current release at our October 6 check. That is five and a half years from launch to a major release with AI-assisted editing, which tells you something about the pace.

It is also a closed shop in the old sense. Bricks is not on wordpress.org, so there is no public install count, no star rating and no free download. Files and license keys come from my.bricksbuilder.io, and updates come from Codeer, not from the WordPress directory. That is common for premium tools and not a warning sign by itself. It does mean the only public record of how Bricks behaves is the vendor's changelog and its own forum, which we read for this review.

The forum is busy, and in 2026 much of the traffic concerns new territory: threads about the Abilities API and about disabling MCP features in a local ddev setup sit beside the usual layout questions. Bricks is clearly building for developers who work with AI tools. Whether that suits you depends on who will be clicking inside the builder, a question this review keeps returning to.

Is Bricks a theme or a page builder?

Both, and that is the point. You install Bricks as a theme, and the theme contains a full visual site builder written in VueJS 3. There is no separate page builder plugin and no theme options panel to reconcile with it. Headers, footers, archives and single templates are all Bricks templates, created under Bricks, Templates. The pricing page lists more than 110 elements, plus builders for query loops, menus, popups and WooCommerce, and conditions and interactions in every plan.

The working vocabulary is a developer's. Global classes and variables hold the design system. Components let a team build a card or a call-to-action once and reuse it everywhere. The Query Loop builder pulls posts, terms or users into any layout. Bricks 2.4 added AI-assisted site editing and the Bricks Browser. A designer who thinks in classes will feel at home in an hour. An owner who wants to drag a photo onto a page and leave will find the canvas strangely empty.

Where other builders and the block editor fit

Bricks replaces page builders rather than hosting them, and the vendor makes no statement about running Elementor or Divi alongside it. Its Gutenberg story is more interesting. Bricks can load standard blocks, save its own data as block-editor data, and offer its components as blocks, and you choose per page whether WordPress or Bricks renders it. The vendor is clear about the limit: conversion works with standard WordPress blocks only, not third-party ones. Teams arriving from Elementor should read Bricks vs Elementor before committing.

What does Bricks cost, and what if you stop paying?

As of October 2026, Bricks sells four plans, and every one carries the full feature set. The only differences are how many sites and for how long.

• Starter: $79 a year for one site.
• Business: $149 a year for three sites.
• Agency: $249 a year for unlimited sites, and eligibility for a Bricks Expert Listing.
• Ultimate Lifetime: $599 once for unlimited sites, with all future updates, features and support, plus Expert Listing eligibility.

Local and staging sites do not count against any plan's limit, which makes testing updates free. New purchases carry a 60-day money-back guarantee; the Terms of Service exclude renewals and upgrades from that window and give renewals a 30-day grace refund instead. The lifetime plan costs about two and a half years of Agency, so any agency planning to stay on Bricks past 2028 should run that number.

Our Bricks pricing guide works through which plan fits a freelancer, an agency and an in-house team, and what the plugins around Bricks add to the yearly bill.

How fast is a Bricks site, and does it help SEO?

Bricks makes confident, specific speed claims. Its performance page says sites earn top A grades in Lighthouse and GTmetrix out of the box, displays a 98 percent performance score with 100 for SEO, accessibility and best practices, and promises clean, semantic HTML with an ever smaller DOM. Those are the vendor's numbers. We have not reproduced them, and your plugins will have a say.

The mechanisms behind the claims are real. The front end runs on vanilla JavaScript with no jQuery. Lazy loading covers images, background images and videos. The Font Manager can download Google Fonts to serve them from your own server, and custom fonts use font-display: swap. The frontend stylesheet uses CSS cascade layers by default.

One default deserves changing. Out of the box, Bricks prints its generated styles inline: page settings, element styles, global CSS, theme styles, palettes and classes. Under Bricks, Settings, Performance, setting CSS Loading Method to External Files writes per-page CSS files, switches to a lighter frontend stylesheet and adds a Regenerate CSS files button. If a style change refuses to appear afterward, Bricks CSS not updating explains the cache layers. The full tuning order is in our Bricks speed guide, and reading PageSpeed Insights shows how to test without fooling yourself.

And search?

Lean markup and fast pages are what a theme can contribute to rankings, and Bricks contributes both. Sitemaps, redirects and site-wide structured data are still jobs most WordPress sites hand to an SEO plugin, so plan for one. A watch item: the Font Manager's Download from Google option has an open report of fetching every unicode-range variant, which adds font files you may never use. Check the fonts folder after downloading.

Can Bricks run a WooCommerce store?

Yes, and more completely than most themes. Bricks has a visual WooCommerce builder with dedicated elements and templates for the product archive, the single product, the cart, the checkout (including a multistep Checkout v2), the account area, quick view, variation swatches and notices. Version 2.4 added modular Cart, Checkout and My Account v2 elements and a Woo Setup Wizard. Every store feature is included on every plan, so a $79 license builds the same shop as the lifetime one.

The trade is responsibility. Because Bricks templates every store page, a store owner relies on Bricks and WooCommerce agreeing after each update. One 2.4-era report describes a critical error in the Account Page V2 element on PHP 7.4, a reminder to keep PHP current and test account and checkout flows on staging. When a store page breaks, WooCommerce layout broken covers the general causes, and our WooCommerce repair team takes over when orders are at stake. For larger catalogs, compare WooCommerce against a Next.js store.

Why does a Bricks menu vanish on phones?

Headers in Bricks are templates of type Header, built visually like any page. The modern menu tool is the Nav (Nestable) element, part of the Menu Builder since version 1.8. It has its own setting for the breakpoint at which the hamburger toggle appears, and the mobile menu reuses the desktop markup rather than printing a second copy, which keeps the page lighter.

That design has one trap. Remove the toggle from a Nav (Nestable) element and nothing shows at the mobile breakpoint, unlike the older flat Nav Menu element. Users reported it as a bug; staff marked it not a bug, because the toggle is required. If your menu disappears on a phone, check for the toggle before anything else. Bricks mobile menu not working covers the remaining causes.

Breakpoints are flexible. The defaults are desktop as the base, a portrait tablet below 992 pixels, a phone held sideways below 768 and an upright phone below 478. Custom breakpoints can be switched on in Bricks, Settings, General and edited in the builder's breakpoint manager, a level of control few themes in this price range offer.

What has gone wrong with Bricks lately?

Bricks releases often, and 2.4 was a large release. The forum logged a cluster of regressions in the weeks after it, several marked solved, others still open at our check.

• SVGs stopped appearing in the new media manager in 2.4.1, and other users reported images not loading since 2.4.
• The experimental CSS Sync feature deleted or merged Custom CSS edits when a style control was clicked afterward, and clashed with child selectors.
• Bricks theme styles leaked into the Gutenberg editor, resetting body styles and links and removing paragraph spacing.
• Taxonomy delimiter options broke, and the 2.4.x dynamic data parser could hang on strings that looked like CSS.
• The Account Page V2 element threw a critical error on PHP 7.4.

None of that makes Bricks fragile. It makes it a fast-moving product installed on live sites, and the cure is the same routine every time: update staging first, which costs nothing because staging sites do not count against your license. If the builder will not open at all, start with Bricks builder not loading, then theme plugin conflicts. Our theme repair service handles the cases that need rolling back, and our Bricks developers maintain sites built on it.

Speed is what Bricks sells. A staging site is what keeps it.

So, should you buy Bricks?

How does Bricks compare with Elementor, Divi, GeneratePress, Kadence and Next.js?

Against other builders, Bricks trades a gentler learning curve for leaner output. Bricks vs Divi is the clearest contrast, since both install as themes and both want to own the whole site. Against lightweight themes, the question is whether you need a builder at all: GeneratePress vs Bricks and Kadence vs Bricks compare it with the two themes developers most often pick instead. The full list sits under theme comparisons.

Bricks is also the WordPress tool that comes closest to how a coded site is built: components, variables, queries. That makes the three-way Bricks vs Elementor vs Next.js worth reading, and Bricks vs Next.js covers what changes when the builder and WordPress both go away. If you are already planning the move, Bricks to Next.js maps each Bricks part to its replacement.

Every theme we reviewed is collected in the WordPress themes section. Not sure whether your Bricks site needs tuning, repair or replacing? A free site audit answers that with a fixed quote, and WordPress financing is available for bigger jobs.