Quick answer
Page builder apps existed because, before Online Store 2.0, only the homepage could be composed from sections. Now every template supports sections and blocks, so the original reason to install one has largely gone.
A builder still wins for numerous, short-lived campaign pages built without a developer. For anything permanent or repeating, build a theme section: it inherits your design system and speed budget, has no monthly fee, and does not stop working if you uninstall the app.
A page builder app is the fastest way to get an unusual landing page live without a developer, and that is a genuine benefit. It is also a layer of someone else's code between your brand and your customer, on every page you use it on. Both halves are true, so the answer depends on which pages and how often.
01 · History
They solved a real problem.
Before Online Store 2.0, only the homepage could be composed from sections. Every other template was fixed unless a developer edited Liquid. If marketing wanted a campaign page with a different structure, the options were a developer or a page builder. Builders won a lot of stores on that gap alone.
02 · The change
Sections now work everywhere.
Online Store 2.0 put sections and blocks on every template: product, collection, page, blog, cart, search. A marketer can add, reorder and configure them in the theme editor with no code, on any page type. Apps can ship blocks that drop into those sections. Metafields feed them structured content.
In other words, the specific problem builders were bought to solve is now a platform feature. What is left is the size of the section library, and that is a smaller gap than the price difference suggests.
03 · The trade
What a builder costs after the subscription.
- Weight on every page you build with it. The builder's runtime loads whether the page uses one feature or twenty. This is the most common cause of a page that scores well in isolation and badly in the real world.
- Lock-in. Pages built in a builder are stored in the builder. Uninstall it and they do not become theme sections; they stop working. The longer you use it, the more expensive leaving becomes.
- Two editors. Some pages are edited in the theme editor and some in the app. New team members never know which, and the store drifts into two visual languages.
- A design system with a leak. Builder pages tend not to inherit your theme's type scale and spacing, so brand consistency erodes page by page.
Ask the uninstall question before you install: if this app disappeared tomorrow, what happens to the pages I built with it?
04 · Builder
When a builder genuinely wins.
Use one when the pages are numerous, short-lived and structurally unpredictable. High-volume paid campaigns are the honest case: a landing page per ad group, live for six weeks, built by whoever is running the campaign, and never intended to be part of the permanent store.
It is also reasonable while you have no developer at all and a page needs to exist this week. Just keep it to a folder of pages you could lose without grieving.
05 · Sections
When to build sections instead.
Build sections when the pattern repeats or the page is permanent. Anything that appears on the product page, the collection page or the homepage belongs in the theme, where it inherits your design system, your speed budget and your ownership.
This is the approach behind the stores on this site. Muddy Bites has a flavour switcher and pack tiers as theme sections; llano has a tabbed product picker and a filterable review carousel; Nata Concept Store has a searchable stockist map. Each was built once, is edited by the client in the normal theme editor, and carries no monthly fee.
The rule we use: if a non-developer will need to place it more than twice, it should be a section.
Quick check
Before you commit.
- You know which pages would break if the app were uninstalled.
- The page pattern is genuinely one-off, not a repeating layout.
- You measured a builder page on a phone, not only on desktop.
- Permanent pages live in the theme, campaign pages in the builder.
- Your team knows which editor owns which page.
- Builder pages inherit your fonts, colours and spacing.
Rent the campaign, own the store.
A builder is a reasonable tool for pages you expect to throw away. For anything that is part of the store itself, sections cost once and stay yours.
Questions
Questions people ask.
Do I still need a page builder with Online Store 2.0?
Usually not for permanent pages. Online Store 2.0 puts sections and blocks on every template, so a marketer can compose product, collection, page and blog templates in the theme editor without code. Builders still help for high-volume, short-lived campaign pages.
What happens to my pages if I uninstall a page builder?
They stop working. Pages built in a builder are stored by the app, not converted into theme sections, so uninstalling leaves broken or empty pages. Ask this question before installing, and keep builder pages to ones you could lose without grieving.
Are page builders bad for Shopify speed?
They add a runtime that loads on every page built with them, regardless of how many features that page uses. That is a real cost on permanent, high-traffic pages such as product and collection templates, and a smaller one on a short-lived campaign page.