Shopify Online Store 2.0 vs Page Builders: Which Should You Use?

What Online Store 2.0 actually changed

Before Online Store 2.0, only the homepage could be assembled from drag-and-drop sections. Now sections and blocks work on every page type, templates are stored as JSON, and app blocks let apps insert their features anywhere in the editor without editing theme code.

• Sections everywhere: product, collection, blog, and custom pages can all be built and reordered in the theme editor.
• Dynamic sources: metafields and metaobjects can feed content into sections, so structured data such as size guides or ingredient lists is edited once and reused.
• App blocks: apps plug into the editor as blocks, and they add no code to the theme when removed.
• Custom templates: marketers can create and assign alternate templates for campaigns or collections without a developer.

How page builders work, and where they cost you

Page builder apps such as PageFly, GemPages and Shogun give you a visual editor with more layout freedom than a stock theme. They typically output their own markup and load their own CSS and JavaScript on the pages they control, on top of your theme.

That extra code is the main trade-off. It can increase page weight and make Core Web Vitals harder to keep healthy, particularly on mobile. Pages built in a builder are also usually tied to that builder: if you uninstall the app or change tools, those pages often need to be rebuilt. Measure your own store rather than assuming, and see our notes on Shopify Core Web Vitals.

Side-by-side comparison

• Speed: Online Store 2.0 sections ship as part of the theme and can be optimised with it. Builder pages carry an additional layer of code that you do not control.
• Design freedom: builders win for one-off, highly custom layouts. OS 2.0 wins when the design is systematised into reusable sections.
• Editing experience: builders are easy for non-technical teams to start with. Well-built OS 2.0 sections, with clear labels and safe defaults, are just as easy to edit, and harder to break.
• Cost: builders add a monthly app fee. OS 2.0 has no ongoing app fee, but custom sections need an upfront development investment.
• Lock-in: OS 2.0 content is stored in Shopify's own format. Builder content is usually stored in the builder's format.
• Consistency: sections enforce your design system. Freeform builders make it easy for pages to drift off-brand over time.

When each option makes sense

Choose Online Store 2.0 with custom sections when performance and long-term maintainability matter, when your team will build many similar pages such as campaign landers, collection pages or product templates, and when you want a consistent brand across them. A custom theme development engagement designs those sections around how your team actually works.

A page builder can still be the right call for a small number of unique, campaign-specific pages, for a team that needs to ship visual experiments without a developer at all, or as a stopgap while a proper theme is built. Keep the builder confined to those pages, and keep the core templates, such as the homepage, product and collection pages, in the theme.

The approach we recommend for most stores

1. Build core templates as fast, performance-first theme sections. See performance-first themes.
2. Expose settings in the theme editor so marketers can change copy, imagery, order and visibility without a developer. Our theme customisation work covers this.
3. Use metafields for structured content so it is edited once and reused across pages.
4. If you keep a page builder, restrict it to a small set of landing pages and review its performance impact regularly.

Frequently asked questions

Is Shopify Online Store 2.0 better than a page builder?

For most stores, custom Online Store 2.0 sections are the better foundation: they load with the theme, cost nothing per month and keep content in Shopify's own format. Page builders remain useful for a few highly custom pages.

Do page builders slow down a Shopify store?

They can. Builders typically add their own CSS and JavaScript on the pages they control, which can increase page weight and affect Core Web Vitals. The impact varies by builder and page, so measure your own store with PageSpeed Insights.

Can I switch from a page builder to Online Store 2.0 sections?

Yes, but pages built in a page builder usually need to be rebuilt as theme sections, since their content is stored in the builder's own format. Plan the migration page by page, starting with the highest-traffic templates.

Can non-developers edit Online Store 2.0 themes?

Yes. Sections and blocks are edited in the theme editor. Well-built custom sections use clear labels and safe defaults so marketers can update copy, images and layout without touching code.