Elementor vs Gutenberg vs a custom theme: which should you use?

For most company websites, use the block editor (Gutenberg) with a light, well-built theme. It is part of WordPress, costs nothing extra, ships far less code than a page builder, and will be supported for as long as WordPress is. Choose Elementor when a non-technical team must design new page layouts themselves, often, without a developer, and accepts heavier pages and lock-in in return. Choose a custom theme when your content has a clear structure, such as projects, products or people, and the design has to be exact and stay that way.

The three are not quite rivals. A custom theme is usually built for the block editor, so the real decisions are page builder or block editor, then ready-made theme or custom one.

What is the difference between the three?

Gutenberg is the block editor built into WordPress since version 5.0, released in 2018. Pages are made of blocks: paragraphs, headings, images, columns, buttons. Since version 5.9, block themes also let you edit headers, footers and page templates in the Site Editor. "Gutenberg" is the project's name; inside WordPress it is simply the editor.

Elementor is a page builder plugin. It replaces the editing screen with its own drag-and-drop canvas, with fine control over spacing, colours, animation and responsive layouts. The free plugin covers the basics. As of October 2026, Elementor Pro plans start at about $60 a year for one site, according to Elementor's pricing page, and add theme building, forms, popups and dynamic content.

A custom theme is a theme built for your site by a developer. Today that usually means a block theme: colours, type and spacing defined in theme.json, templates and patterns made from blocks, and a few custom blocks where the core ones fall short. Editors still use the block editor. The theme decides what they can change.

We build WordPress sites with the block editor and a custom theme as part of our website design and development work, and use Elementor when a client's team truly needs to design pages themselves.

How do they compare on speed, cost and flexibility?

The speed row matters most over time. A page builder wraps each element in layers of markup and loads its own styles and scripts. Elementor has cut this down in recent versions, with Flexbox containers and options to load fewer files, but a page built in it is still heavier than the same page in blocks. Is Elementor slowing your site down? shows how to measure the gap on your own site, and the page weight calculator totals what each page loads.

When is Elementor the right choice?

When the people running the site are marketers who build new landing pages every month, care about precise visual control, and have no developer on call. Elementor gives them independence, and for some teams that is worth more than a few hundred milliseconds.

It also suits short-lived sites: campaign microsites, event pages, a site that will be replaced within a year. Lock-in matters less when the site is temporary.

It is the wrong choice when the only reason is "our agency knows Elementor". That benefits the builder of the site, not its owner. It is also wrong for sites where speed drives revenue, and for sites edited by many people, because freedom to restyle every page is also freedom to make every page look different.

When is the block editor enough?

For most company sites, and more often than people expect. The block editor handles columns, media and text, buttons, galleries, tables and embeds. Patterns give editors ready-made layouts to insert. Synced patterns (formerly reusable blocks) let one edit update every page that uses a section. Template locking stops editors from breaking a layout while still letting them change words and images.

It is weaker at fine responsive control and at visual effects such as scroll animations. If the design depends on those, a custom block or a little CSS in the theme usually covers it without a builder.

The official Block Editor Handbook documents patterns, locking and theme.json. It is the reference a developer should build from, and a useful check on any agency's claims about what the editor cannot do.

When is a custom theme worth paying for?

When your content has a shape. A manufacturer with 200 products in families. A consultancy with case studies by sector. A school with departments and staff. That content belongs in custom post types with fields, often built with Advanced Custom Fields, and a custom theme shows every item the same way. Editors fill in a form; the design takes care of itself.

It is also worth it when the brand must look as designed on every page, years after launch. A theme that defines colours, type sizes and spacing in theme.json, and offers editors only those choices, keeps the site consistent whoever edits it.

It is not worth it for a five-page site that rarely changes. A good ready-made block theme, chosen carefully, does that job for far less. How to choose a WordPress theme covers what to check.

What does switching cost later?

Moving between block themes is cheap. Content is stored as standard blocks that any theme can display, so a redesign changes the theme and leaves the pages alone.

Moving off Elementor is expensive. Its layouts are stored in its own format, so deactivating the plugin leaves pages as plain, unstyled content at best. Every page built in it has to be rebuilt. On a 50-page site that is a project in its own right, and it is the most common reason owners stay on a builder they no longer want.

So decide with the next five years in mind, not the launch. If you are unsure, start with the block editor. Adding a builder later is easy; removing one is not. The WordPress for business guide covers the rest of the setup we recommend around this choice.