Bricks vs Elementor: What You Own and What You Only Rent

The renewal email that settles this comparison

Most builder reviews end at launch day. The bill arrives a year later. With Bricks, the email asks whether you want another year of updates and support; if you say no after a paid, non-refunded year, the terms let you keep using the builder you have. With Elementor on Hello, the email is about Pro. Say no, and Elementor's help center says Pro stops updating, new Pro widgets cannot be added, and existing Pro features may only be partly available.

So the useful question is not which editor is nicer. It is which parts of your site you will own outright and which you will rent, and what happens to the rented parts if the card on file expires during a busy quarter. The table below lays out both products, and the sections after it follow the money: what is included, what drifts, what each page weighs and who should buy which. For the version that puts Next.js in its own column, see Bricks vs Elementor vs Next.js.

Bricks and Elementor on Hello, line by line

Every cell comes from the vendors' own pages, checked on October 6, 2026, and vendor speed claims are labeled as claims. Elementor means the free plugin plus Elementor Pro, with Hello as the theme, because Hello is the theme Elementor builds for its editor and the one its help center suggests switching to when diagnosing a slow site.

Two rows deserve a second look. The WooCommerce row hides a price: an Elementor store needs at least Advanced Solo, $84 a year as of October 2026, because Essential lacks the WooCommerce Builder. The payments row hides a behavior that the rest of this page keeps returning to. Full plan tables and fine print are in Bricks pricing.

One product, whole, against a free core and a paid layer

Bricks sells four plans, as of October 2026: Starter at $79 a year for one site, Business at $149 for three, Agency at $249 for unlimited sites, and Ultimate Lifetime at $599 once for unlimited sites. Every plan has every feature, from the 110+ elements to the query loop, popup and WooCommerce builders; only the site count and the term change. Local and staging sites do not count against the limit. Nothing is held back for a higher tier, which means nothing on the site depends on staying subscribed to one.

Elementor splits the product in two. Hello and the core plugin are free and carry the editor, containers and V4 Atomic elements. Pro is billed yearly at list price: Essential $60 for one site, Advanced Solo $84 for one site, Advanced $108 for three and Expert $204 for 25. Essential includes the Theme Builder and the form widget but leaves out the Popup Builder, custom code and CSS, stored form submissions, ACF and Pods dynamic data and the WooCommerce Builder. Each of those is a rented feature, and some sites rent a third-party widget pack on top.

• Bricks refunds: a 60-day money-back guarantee on the first purchase. Renewals get a 30-day grace refund instead, and plan upgrades fall outside the 60 days.
• Elementor refunds: 30 days on initial Pro purchases, handled automatically from the My Elementor dashboard. Plan upgrades and AI add-ons are non-refundable.
• Many sites: 25 client sites cost $204 a year on Elementor Expert, against $249 a year or $599 once on Bricks with no ceiling on site count.
• Who holds the key: Bricks licenses come from my.bricksbuilder.io, and Elementor Pro activates through a my.elementor.com account. Both should belong to the business. If activation fails, see Elementor Pro license not activating.

The drift problem: a free half that keeps updating

Here is the scenario Elementor itself warns about. Pro lapses in year three. The free Elementor plugin keeps updating, as free plugins do, and so does WordPress. Pro stays frozen at its last version. Elementor's help center says plainly that updating the free version without the Pro version can lead to compatibility problems. The site does not go dark on renewal day. It drifts, one update at a time, until a Theme Builder header or a popup misbehaves and nobody connects it to an invoice from two years ago. Elementor update broke layout is often where that story surfaces.

Bricks cannot drift that way, because there is only one package. If you stop paying, the whole builder stops changing at once, which is stable but not risk-free: you also stop receiving fixes, and a builder frozen in 2026 will meet PHP and WordPress versions it never saw. Bricks' own risk is the opposite of drift. It ships fast. Version 2.4 arrived on September 16, 2026, with AI-assisted site editing, and the forum logged hidden SVGs, images not loading and an experimental CSS Sync feature deleting custom CSS edits before 2.4.2 followed. Owning the tool means rehearsing its updates on staging.

Bricks freezes whole when you stop paying. Elementor freezes in half, and the halves drift apart.

Features you would otherwise rent: loops, popups, shops

The included-or-rented question shows up again in how each builder works. In Bricks, styles can live on global classes reused across every page. Query Loop turns any element into a repeater for posts, terms or products. Conditions decide what shows to whom, and components let you build a card once. A directory, a location network or a resource library can be built with what is already in the box. Our Bricks developer page explains how we structure classes so the next developer can read them.

Elementor starts from the widget: drop it in, style it in the panel. Flexbox containers replaced the old section and column nesting, and V4 Atomic elements, on by default in Elementor 4.x according to its help center, add CSS classes, variables and CSS Grid to the free plugin, with synced components for Pro users. That narrows the gap with Bricks on paper. The catch is the rental again: dynamic data from ACF, popups and Woo templates sit behind tiers, and effects the tiers lack often come from third-party packs, each with its own renewal. Our Elementor developer page covers replacing a pack that was installed for one carousel.

The third option

Athena CMS, with AI agents on staff.

Not a theme and not a blank Next.js repo. The content system we put behind every custom site: plain fields, a real preview, every version kept, and AI agents that handle the chores a plugin only nags you about.

• PPicassoImages
• AApolloSite analysis
• AAresCompetitor watch
• PPrometheusContent holes
• AAtlasPage depth and structure
• DDelphiAI search visibility

ZDAOAand 12 more agents. Two come with Athena; the rest are monthly add-ons.

Meet the agentsTake the Athena tour

PPicassoWeekly · ImagesAApolloWeekly · Site analysis

Page weight starts in different places

Bricks is the theme, so the theme's weight and the builder's weight are one number. The front end runs on vanilla JavaScript with no jQuery. Generated styles print inline by default. Switch Bricks > Settings > Performance > CSS Loading Method to External Files and it writes a CSS file per page and loads a lighter frontend stylesheet, with a Regenerate CSS files button for when edits refuse to appear. The Font Manager can download Google Fonts to serve from your domain. Bricks claims top 'A' grades in Lighthouse and GTmetrix out of the box; that describes its test page. The Bricks speed guide shows where real sites gain weight.

Hello really is small: three stylesheets between roughly 5.8 and 7.5 KB each in version 3.5.1, and a settings page that can deregister two of them. Elementor even publishes two different size claims for it, 6KB in its help center and under 30KB on the product page. The theme is not the bottleneck. The page is drawn by Elementor, so speed work happens in its Performance and Features tabs: an external CSS file, Optimized Image Loading for the LCP image, Lazy Load Background Images, Inline Font Icons, and Element Caching, which is still labeled experimental. The Hello Elementor speed page goes through each setting.

To compare fairly, build the same real page in both, on the same host with the same caching, and run several mobile tests each in PageSpeed Insights. Count requests and DOM nodes as well as the score. If either version flickers or refuses to show an edit, read Hello Elementor CSS not loading or Bricks CSS not updating before blaming the builder.

Buy-once owners and pay-as-you-go teams

One caution for each. A Bricks owner who stops paying should still plan a renewal before the next big PHP or WordPress release, because a frozen builder meets new server software eventually. An Elementor owner should put the Pro renewal on the same calendar as the domain and hosting. The Elementor repair hub and the Bricks review list the failures we see most often.

Six kinds of site, six verdicts

The neighboring contests are argued on other questions: Divi vs Elementor on two rebuilt engines, Bricks vs Divi on lifetime deals and exits, and Avada vs Elementor on bundles against tiers. All of them are listed in the theme comparisons hub.

When the site has outgrown visual builders of any brand

Some sites lose this comparison on both sides. A contractor who needs a page for every service in every suburb, a clinic with a patient portal, a distributor with quote calculators tied to a price list: each can be forced into Bricks query loops or Elementor templates, and each will keep asking for one more plugin. A Next.js build writes those features into one codebase, prerenders pages for a CDN and sends the browser only what each page uses. It costs more up front and needs a developer for structural change. Page builders vs Next.js sets out the trade, with theme versions for Bricks and Hello Elementor.

There is no builder license to renew on a Next.js site, and editing does not go away. Athena CMS comes with every site we build: plain fields, a real preview, every version kept, and agents with one job each. Argus watches for broken links and failing forms, and Iris keeps search titles and social cards in order. The moves are mapped in Bricks to Next.js and Elementor to Next.js, and they start with a free site audit.