This question gets answered with ideology far more often than with analysis. Builder people think custom is over-engineering; custom people think builders are technical debt. Both are sometimes right.
What page builders are genuinely good at
- Speed to first version. A small marketing site can exist in days rather than weeks.
- Non-technical editing. Someone with no development background can build a landing page.
- Low upfront cost. No design system to build before the first page ships.
For a five-page site for a small business, a builder is frequently the correct answer, and telling that client they need a custom theme would be selling them something they do not need.
Where the cost appears
The trade-offs are real and they show up later, which is what makes them easy to underestimate at the start.
- Page weight. Builders ship a generic framework that has to handle any layout you might create, so every page carries CSS and JavaScript for features it does not use.
- Editing gets slower, not faster. Simple pages are quick. Complex nested layouts become genuinely painful to edit, and only the person who built them knows where anything is.
- Consistency drifts. When every element is individually stylable, they eventually will be. Fourteen button styles is a builder site symptom.
- Content lives in builder markup. This is the big one.
The lock-in question
Most builders store content as shortcodes or their own serialised markup rather than as clean HTML. Deactivate the plugin and your pages become unreadable fragments.
That is not a conspiracy, it is just how they work — but it means leaving is not a migration, it is a rebuild. Before choosing one, deactivate it on a staging copy and look at what is left. That is your exit cost, and it is worth knowing before you are five years and two hundred pages in.
What a custom theme actually gives you
Not “better code” in the abstract. Specific things:
- Only the CSS and JavaScript your site actually uses
- A content model shaped around your business — products, locations, case studies — rather than everything forced into pages
- Editors filling in meaningful fields instead of rebuilding layouts
- Content stored as standard WordPress data, so it outlives any theme
The cost is a longer, more expensive start. There is a design system to build before the first page ships.
Block themes: the middle ground
This is where most of the market is heading and it is genuinely a good answer for a lot of sites. A block theme with custom blocks gives your team visual editing and layout control, while content stays in core WordPress format and page weight stays under your control.
You get most of the editing freedom of a builder without the exit cost. The trade-off is that some older extensions have not caught up, so your plugin stack partly decides whether this is available to you.
How to actually decide
Four questions, and the answers point clearly:
- How long will this site live? Under two years, builder. Five-plus, the lock-in matters.
- How many pages, and how similar? Many similar pages want a content model. A handful of unique ones do not.
- Who edits it? A marketing team publishing weekly needs a system. An owner updating quarterly does not.
- Does performance affect revenue? If a slow page costs you sales directly, the weight is not an abstract concern.
If you already have a builder site
Do not rebuild for purity. If it works, your team can maintain it, and it is fast enough, leave it alone — a rebuild is a large cost for a benefit you may not feel.
Rebuild when you are actually feeling the pain: pages nobody can edit safely, performance you cannot fix, or a redesign that is coming anyway. The redesign is the natural moment, because you are paying for the pages to be rebuilt regardless.