Block Themes vs Classic Themes in WordPress: Which Should You Use?

A block theme builds every part of a WordPress site, including the header, footer and page templates, out of blocks, and you edit it visually in the Site Editor. A classic theme builds those parts with PHP template files and relies on the Customizer, widgets and the Menus screen. Both kinds use the block editor for posts and pages, and both are fully supported in WordPress 7.1, the current release as of October 2026.

The practical difference is who can change what. With a block theme, a non-developer can redesign the header, rearrange a template or change global colors from the dashboard. With a classic theme, those changes usually need a developer, a page builder or the theme's own options panel. In between sit hybrid themes: classic themes that have adopted some block features such as theme.json or block template parts.

This guide compares the two approaches, explains when each makes sense for a business site, covers the current default theme situation, and lists what to check before migrating.

What a block theme is

Block themes have been part of WordPress since version 5.9. The official block themes documentation defines a block theme as "a theme that uses blocks for all parts of a site, including navigation menus, header, content, and site footer."

Structurally, a block theme is lean. According to the WordPress theme handbook, only two files are required: style.css (theme name and metadata) and templates/index.html, the fallback template that tells WordPress it is a block theme. Most block themes also include:

• theme.json for settings and styles (color palette, fonts, spacing, layout),
• a templates folder for page-type layouts,
• a parts folder for template parts such as header and footer,
• a patterns folder for reusable block layouts,
• a styles folder for style variations,
• an optional functions.php for PHP logic.

Once a block theme is active, you get the Site Editor, global Styles, template and template part editing, and theme blocks such as Navigation and Query Loop. Our Site Editor guide walks through each area.

What a classic theme is

Classic themes are the way WordPress themes were built for most of the platform's history. The official documentation describes them as "built with PHP templates, functions.php, and more that include features like Widgets, a dedicated Menus section, the Customizer, and more." Layout lives in files like header.php, footer.php, single.php and archive.php, following the template hierarchy.

Classic themes still use the block editor for content, so writers get the same editing experience either way. What changes is the frame around the content: to move the header search box or add a section to every product page, you edit PHP or use whatever options the theme author built in. Many popular commercial themes and page-builder setups are classic or hybrid themes. If you are maintaining a custom one, keep changes in a child theme; see why child themes matter.

Side-by-side comparison

Hybrid themes: adopting block features gradually

You do not have to choose all or nothing. The WordPress theme handbook describes hybrid themes as "classic themes that have adopted some modern block-related features, such as global settings and styles or block template parts." Common building blocks of a hybrid approach:

• theme.json in a classic theme. The handbook states that theme.json "works with both block and classic themes." Adding it lets you define a brand palette, font sizes and spacing presets for the editor and lock down options. See theme.json explained.
• Block template parts. Since WordPress 6.1, a classic theme can add block-template-parts theme support and include HTML template parts, so editors can change, say, the footer visually while the rest of the theme stays in PHP.
• Patterns. Classic themes can register patterns, and since WordPress 6.6 their Appearance > Patterns menu opens the Site Editor's Patterns view.
• Style Book. Since WordPress 6.8, the Style Book works with classic themes that have editor styles or a theme.json file.

Hybrid is often the right answer for a business site that works well today but where the marketing team keeps asking a developer to change the footer or the call-to-action strip.

The default theme situation in 2026

Default themes are the ones bundled with WordPress, and they signal where the project is heading. Here is the verified status as of October 2026:

• Twenty Twenty-Five is still the newest bundled default theme. It is a block theme, version 1.5, with 1+ million active installs according to WordPress.org.
• There is no Twenty Twenty-Six. WordPress 6.9 skipped a default theme, and neither 7.0 nor 7.1 added one.
• Ipsum is the proposed default for WordPress 7.2. Work announced in March 2026 as Twenty Twenty-Seven was presented on 16 September 2026 as Ipsum, "planned to be bundled in WordPress 7.2." It is still open for testing, and the 7.2 roadmap notes that planned items do not necessarily make the final release.
• Yearly naming is ending. The announcement says that "going forward, default themes will have their own names and change when the design calls for it, not when the calendar does."

You can read the announcement on the Make WordPress Core blog. If an article tells you Twenty Twenty-Six is the current default, it is out of date.

When to choose a block theme

A block theme is usually the better choice when:

• you are starting a new site and do not depend on a specific page builder,
• non-developers need to change headers, footers, templates and global design,
• you want design decisions centralized in theme.json and Styles rather than scattered across options panels,
• you want to use new features as they land; WordPress 7.0 and 7.1 added per-device visibility, block-level custom CSS, responsive styles and block-built menu overlays, and the Site Editor gets most of the design-tool attention,
• you want a lighter theme without a large framework of theme options.

The WordPress.org theme directory lists 1,886 themes tagged for full site editing as of 1 October 2026, so there is a reasonable range of starting points.

When a classic or hybrid theme still makes sense

A classic theme is still a sound choice when:

• the site works, converts and is well maintained, and a rebuild would cost more than it returns,
• it relies on a page builder, a commercial theme framework or custom PHP templates that would need to be rebuilt,
• developers rather than editors own layout changes, and you prefer code review over visual editing,
• plugins you depend on integrate with the Customizer or widget areas in ways that have no block equivalent yet.

In those cases, consider going hybrid instead of migrating: add theme.json, convert the most-edited areas to block template parts and register a few patterns. Our comparison of custom development vs templates can help frame the budget decision.

Migrating from a classic theme to a block theme

Switching theme type is a redesign, not a settings change. Plan for it:

1. Inventory what the current theme does. List templates, widget areas, menus, shortcodes, custom post type layouts, theme options and any functions.php code. Theme-specific features (sliders, portfolio types, shortcodes) often disappear when you switch.
2. Move functionality out of the theme. Custom post types, shortcodes and tracking code belong in a plugin so they survive the switch.
3. Rebuild on staging. Recreate headers, footers and templates in the new theme, map widgets to blocks and rebuild menus with the Navigation block.
4. Check content. Posts built in the block editor generally carry over. Content tied to a page builder or theme shortcodes needs checking page by page.
5. Protect SEO. Keep URLs, titles, meta descriptions, headings and structured data the same, and crawl the staging site before launch. Our WordPress technical SEO audit guide has a checklist.
6. Test performance and accessibility. Compare Core Web Vitals and keyboard navigation before and after.

The Create Block Theme plugin, published by WordPress.org (20,000+ active installs as of October 2026), can help developers save Site Editor changes back into theme files and package a block theme, which is useful in step 3.

Common misconceptions

• "Classic themes are deprecated." They are not. They are still supported and still receive block features.
• "Block themes cannot use PHP." They can include functions.php and PHP-registered patterns; WordPress 7.0 also added PHP-only block and pattern registration.
• "Switching to a block theme converts my site automatically." It does not. Widgets, menus and theme options need rebuilding.
• "There is a new default theme every year." Not anymore; see the default theme section above.

Conclusion

For new builds, a block theme is now the natural default: it puts layout and design control in the dashboard and gets the newest design tools first. For established sites on a classic theme, a hybrid path often delivers most of the benefit at a fraction of the cost of a rebuild. For more guides, visit the WordPress resource hub. If you are weighing a migration, eSEOspace can plan and build it through our WordPress development services.

Frequently asked questions