The common advice is “use a block theme”. Nobody explains what to check before you buy one. If a developer, a freelancer, or a forum thread told you to switch, you probably have no way to tell a solid block theme from a weak one.
This post gives you a plain definition, a clear view of what changes for you and what you give up, and a checklist you can apply to any theme from any seller. It is the entry point to the topic. The deeper technical coverage lives in the 3-part series on block themes (Part 1, Part 2, Part 3), so this post stays practical.
What a block theme is, in plain terms
A block theme is a WordPress theme built from blocks all the way through, not only the post content. Its header, footer, and page templates are made of the same blocks you use to write a post. You edit those parts in the Site Editor, inside the WordPress dashboard, instead of changing code files. You will also see this setup called full site editing, and both names point to the same thing.
The practical difference is where the pieces live. In a classic theme, the header, footer, and templates sit in PHP files, so changing them means editing code or paying someone who can. In a block theme, those same parts live in the Site Editor, and you change them on your own. A page builder theme works differently again, because the builder’s own editor controls the layout.
| Classic theme | Block theme | Page builder theme | |
|---|---|---|---|
| Header, footer, templates | Edited by a developer in PHP files | Edited by you in the Site Editor | Edited by you in the builder’s editor |
| Where changes happen | Code files, plus some options in the Customizer | The Site Editor in WordPress | The page builder’s interface |
| Page content | Block editor | Block editor | Page builder interface |
This is the short version. Part 1 of the series covers the full explanation, so this post does not repeat it. Read it first if you want the technical detail. Keep going here if you want to decide what to buy.
What actually changes for you
You can edit headers, footers, and templates visually, without code. Open the Site Editor, click the header, and change it the way you would change a paragraph. A common mistake is forgetting that a template applies to every page that uses it. If you edit the single post template, every post changes, not just the one you had in mind.
Global styles let you set colors, fonts, and spacing in one place. Behind them sits theme.json, a single settings file in the theme that stores those choices and feeds them to the Site Editor. The observable result is that you change a color once and it updates wherever the theme uses it. The limit is that you can only change what the theme exposes, so a theme with few style options gives you few controls.
Patterns and template parts make layouts reusable. A pattern is a saved arrangement of blocks that you insert onto a page, such as a hero section. A template part is a reusable section such as the header or footer. Site owners who skip patterns often rebuild the same section by hand on five different pages, then fix the same detail five times.
You also need fewer plugins for basic layout work. A custom header or a different footer no longer requires an extra plugin. That applies to basic layout only, and more specialized needs can still call for plugins.
Much stays the same. Your posts, pages, and content carry on as before, and so do the plugins that do not depend on a classic theme’s setup. Day-to-day writing and publishing look the same as they did.
What you lose or give up
Compared with a page builder, a block theme gives you fewer design controls. Some editing tasks feel less polished in the Site Editor than in a mature builder, and you will spend time learning it. If you already build pages quickly in a builder, expect a slower first month.
Compared with a classic theme, some plugins and Customizer-based workflows do not carry over. If your site relies on a plugin that hooks into a classic theme’s templates, or on options you set in the Customizer, test them before you commit. Finding out after a switch means rebuilding that part of the site.
Migration has a cost when you move an existing site. Your content comes along, but your layouts do not rebuild themselves, and every template needs attention. The Elementor-to-block-theme migration guide walks through what that work involves.
A block theme is the wrong choice in three situations. It is wrong if your site depends on plugins or Customizer workflows that will not carry over. It is wrong if you need page-builder-level design control and have no reason to give it up. It is also wrong if you have an existing site and no time or budget for the migration work.
How to choose a block theme: the buyer’s checklist
Run every theme through the same ten checks. Each one has a “what to look for” line and a “red flag” line, so you can score a theme in an afternoon.
1. Real block theme or a hybrid?
- What to look for: A Site Editor entry in the dashboard, a theme.json file, and block templates.
- Red flag: No Site Editor under Appearance, or a demo that needs a page builder to look right.
2. Quality of the demo’s patterns
- What to look for: Patterns you can insert and edit from the editor, matching what the demo shows.
- Red flag: Demo layouts that exist only as screenshots and cannot be rebuilt from the theme itself.
3. Template types included
- What to look for: Templates for single posts, archives, 404, and search, plus any others your site needs.
- Red flag: Only a homepage and a page template, which leaves you building the rest yourself.
4. Global style variations
- What to look for: Several style variations that change colors and fonts from the Site Editor without code.
- Red flag: Custom CSS as the only way to change the look.
5. Plugin dependencies
- What to look for: A short list of required plugins, named before you buy.
- Red flag: A bundle of extra plugins needed to make your site look like the demo.
6. Performance and accessibility basics
- What to look for: A demo that loads quickly in a free speed test such as PageSpeed Insights, and works when you press the Tab key to move through it.
- Red flag: A slow demo, or a page where you cannot see which element is selected as you Tab.
7. Documentation and update history
- What to look for: Public documentation and a changelog with dated entries.
- Red flag: No changelog, or a last update date long in the past.
8. Support terms and license
- What to look for: A written statement of what support covers and for how long, plus license terms in plain text.
- Red flag: Support length left unstated, or no clear license terms.
9. Fit for your site type
- What to look for: Demos and templates close to your type of site: municipal, editorial, portfolio, directory, or restaurant.
- Red flag: A demo built for a different site type, which means rebuilding most pages.
10. How to test before you commit
- What to look for: A demo import, a staging copy where you can try it, and a refund policy.
- Red flag: No refund policy, or no way to try the theme before you pay.
Which route fits your situation
New site. Choose a block theme. You carry no migration cost, and you can use the checklist above from the start.
Existing site on a classic theme. Stay put unless you pay for header or footer changes. If you do, move to a block theme, and test it on a staging copy first.
Existing site on a page builder. Stay with your builder for now. Migration takes real work (see the guide), so move only when the builder is the problem you want to solve.
Heavy design customization needed. Pick a page builder theme. A block theme gives you fewer design controls, and you will notice it quickly.
Closing and next steps
The decision rule is short. Choose a block theme when you want to edit your own layouts without code and your plugins carry over. Choose a page builder when you need design control beyond what the Site Editor offers.
- Read the 3-part series in order: Part 1, Part 2, Part 3
- Read the Elementor-to-block-theme migration guide
Last modified:
