You are building a WordPress site in 2026 and you have to make a foundational choice: block theme, classic theme, or Elementor. The choice matters more than it used to. It affects performance, client editing experience, long-term maintenance, WooCommerce compatibility, and how much work you will do every time WordPress releases a major update. This post gives you the honest version of that comparison, no vendor enthusiasm, no false nostalgia, just the real trade-offs for each path.
The short summary before we go deep: block themes are the future and the best default choice for new projects in 2026. Classic themes are still viable for teams with heavy existing investment in them. Elementor remains the most capable visual builder on the market but comes with costs you need to budget for. None of the three is universally wrong, the right choice depends on what you are building and who is maintaining it.
The Three Options, Briefly Defined
Before comparing, it is worth being precise about what each option actually is, because the terms get used loosely.
Block Themes
Block themes are WordPress themes built entirely on Gutenberg blocks and controlled through theme.json. They replace PHP templates with block template files, expose the full site layout to the Site Editor, and define design tokens (colors, typography, spacing) as structured JSON rather than CSS variables scattered across a stylesheet. Every template, header, footer, archive, single post, is editable in the Site Editor without touching code. Block themes have been the official WordPress theme standard since WordPress 5.9.
Classic Themes
Classic themes are the traditional WordPress theme architecture: PHP template files (header.php, single.php, archive.php), a functions.php for hooks and customizations, the WordPress Customizer for front-end editing, and widget areas for sidebar content. They have been the standard for fifteen years and the vast majority of existing WordPress themes, including major commercial frameworks, are classic themes. They use the block editor for post content but not for site-wide layout.
Elementor
Elementor is a page builder plugin that installs on top of any WordPress theme (usually a minimal “Hello Elementor” base theme) and provides a drag-and-drop visual editor for building page layouts. It has its own widget ecosystem, its own template system, its own dynamic content layer, and its own WooCommerce builder. Elementor Pro, the paid version, adds most of the features that make it genuinely powerful. As of 2026, it is installed on over 10 million WordPress sites.
Quick Decision Table
If you are in a hurry, this table covers the most important signals. Detailed breakdowns follow.
| Factor | Block Theme | Classic Theme | Elementor |
|---|---|---|---|
| Page speed (Core Web Vitals) | Best | Good | Requires tuning |
| WooCommerce support | Good (improving) | Mature | Best (Elementor Pro) |
| Client self-editing | Good (Site Editor) | Limited (Customizer) | Best (visual drag-drop) |
| Developer control | High (theme.json) | Very high (PHP) | Medium (proprietary) |
| Long-term lock-in | None (core WordPress) | Low (standard PHP) | High (Elementor markup) |
| Plugin compatibility | High | Very high | High (some conflicts) |
| Hosting cost impact | Low | Low | Medium-high |
| WordPress 7.0 readiness | Full | Partial | Plugin-level |
Block Themes: What You Get and What You Give Up
The Case For
Block themes are where WordPress core investment is going. Every major WordPress release since 5.9 has added new capabilities to the block theme architecture, style variations, pattern overrides, the Connectors API in 7.0. If you build on block themes, you are building on the architecture that will be maintained, extended, and optimized by the core team for the foreseeable future. Classic themes will continue to work but will receive diminishing attention in the roadmap.
Performance is the other strong argument. A properly configured block theme, lean HTML output, no extra JavaScript unless a specific block requires it, system font stack, minimal third-party dependencies, can achieve excellent Core Web Vitals scores without specialized optimization work. The output is clean by default. You are not fighting against a theme framework’s inherited complexity the way you sometimes are with classic themes that have accumulated years of features.
The theme.json design system is genuinely powerful once you understand it. Defining your design tokens, color palette, typography scale, spacing system, in a single structured file and having them automatically available as CSS custom properties across every block is the right architecture for maintaining consistency on large sites. It is the approach modern design system tooling has converged on, applied to WordPress themes.
The Honest Downsides
Block themes are still maturing. The Site Editor has improved significantly but still has UX rough edges that surprise clients who expect a WYSIWYG experience closer to what they have seen in Elementor or Squarespace. Pattern Overrides, which landed in WordPress 7.0, address one of the biggest complaints about synced patterns being too rigid, but the learning curve for clients is real.
WooCommerce support has historically been block themes’ weakest point. WooCommerce’s own block-based cart, checkout, and product templates have improved substantially, but teams doing heavily customized WooCommerce work, custom product types, complex checkout flows, subscription products, will find the classic WooCommerce PHP templates more flexible for those specific use cases. This gap is closing but it is not yet closed.
The developer mental model shift is also real. If your team has ten years of classic theme development muscle memory, child themes, template overrides in PHP, Customizer panels, block theme development requires unlearning some of that and replacing it with new patterns. The migration guide from classic to block themes covers this in detail, but it is worth acknowledging: the switch has a real ramp-up cost.
Classic Themes: Still Viable, But for Whom?
Where Classic Themes Still Win
Classic themes have an enormous ecosystem advantage. If you are buying a commercial theme, for a WooCommerce store, a membership site, a directory, the majority of polished, actively maintained commercial themes in 2026 are still classic themes built on frameworks like Genesis, OceanWP, Astra, or custom proprietary bases. These themes have years of compatibility work with popular plugins behind them. They work with every version of WooCommerce, every major membership plugin, every cache plugin. The compatibility surface area is vast and well-tested.
For agencies and freelancers with large existing client bases on classic themes, there is a pragmatic argument for staying: your tooling, your knowledge, your troubleshooting patterns, and your client training materials all work. Migrating to block themes has a real cost that must be weighed against the benefits for each project. For a stable client site that is working well and needs ongoing maintenance, that migration cost may not be justified yet.
Classic themes also retain an advantage for highly custom PHP-driven layouts, themes that pull from custom post types, use complex query logic in templates, or integrate deeply with server-side rendering. PHP template files give you direct, readable control over the exact HTML output in a way that block templates still feel more indirect about for some developers.
The Honest Downsides
The roadmap argument against classic themes is significant. WordPress core is not investing in improving the classic theme experience. The Customizer is in maintenance mode, there are community discussions about its eventual deprecation. Widget areas are legacy. Future WordPress features, Pattern Overrides, the Connectors API, AI agent infrastructure, are being built for the block architecture. Classic theme developers will either adapt or find themselves increasingly reliant on third-party plugins to compensate for features that are native to block themes.
There is also a performance ceiling. Classic themes, especially commercial framework themes, tend to carry significant CSS and JavaScript payload because they were built to support many possible configurations. A well-built classic theme on a well-configured server performs fine, but the baseline is heavier than a lean block theme. For projects where Core Web Vitals score directly affect SEO rankings or ad revenue, this matters.
Elementor: Why 10 Million Sites Use It and What It Actually Costs
The Real Strengths
Elementor’s dominance is not an accident. For client sites where the client needs to edit the layout, not just the text content, Elementor provides an editing experience that is genuinely closer to what non-technical users expect after using Wix, Squarespace, or Webflow. The drag-and-drop canvas, live preview, responsive controls on a per-element basis, and mobile editing view all reduce the training burden when handing sites to clients who are not technical.
Elementor Pro’s WooCommerce Builder is the strongest argument for Elementor in e-commerce contexts. Designing custom product pages, cart pages, and checkout flows with full visual control, without writing a line of PHP, is a legitimate capability that neither block themes nor classic themes match in terms of visual accessibility. Agencies building WooCommerce stores for clients who want to maintain them without developer involvement have a real reason to choose Elementor Pro.
The widget ecosystem is also vast. Elementor’s own widget library plus the major addon packs (Essential Addons, JetElements, the PowerPack suite) cover almost every UI pattern you might need to build. For rapid project delivery, especially landing pages and campaign sites, Elementor with the right addons is hard to beat for speed of execution.
The Real Costs
Elementor’s output is verbose. The HTML and CSS it generates to render a layout carries significantly more overhead than the equivalent block theme or classic theme output. On a shared hosting environment or a site with no caching, this shows up in page load times. Elementor sites absolutely can achieve good Core Web Vitals scores with proper optimization, caching, image optimization, asset minification, but this requires active work that block themes do not. For agencies delivering twenty client sites a year, this optimization overhead adds up.
The lock-in problem is the one most developers underestimate. A site built in Elementor has its layout data stored as Elementor shortcodes and widget data in the post meta. If you ever need to move away from Elementor, whether because the pricing changes, a conflict with a critical plugin, or a client who wants to take their site in-house, the migration is painful. The content exists only in Elementor’s format. This is the trade-off you make for the visual building experience.
Our earlier head-to-head between block themes and Elementor covers the performance and business case in more detail for those who want to go deeper on that specific comparison.
WooCommerce: Which Option Handles It Best in 2026?
WooCommerce deserves its own section because it is one of the most common reasons developers default to Elementor or classic themes even when they might otherwise prefer block themes.
The current state: WooCommerce’s native block experience, the Cart block, the Checkout block, the Product Grid block, has matured significantly in the past two years. For a standard WooCommerce store (physical products, standard checkout, Stripe or PayPal payment), the native block experience in a block theme is fully production-ready and delivers better Core Web Vitals than an equivalent Elementor-built store.
Where classic themes and Elementor still have an edge is in complex WooCommerce configurations. Subscription products with Woo Subscriptions, membership-gated content with MemberPress or Paid Memberships Pro, complex variable products with a large attribute matrix, and highly customized checkout flows all tend to work more reliably with the classic WooCommerce PHP template system, which classic themes and Elementor both have full access to. Block themes can use these too, but the developer tools for doing so are less mature.
The practical recommendation: for new WooCommerce stores in 2026, start with a block theme and the native WooCommerce blocks. Only reach for Elementor Pro’s WooCommerce builder or a classic framework theme if you hit a specific gap in the native block experience that matters for your project.
The Client Editing Experience: Honest Assessment
This is where Elementor maintains its strongest real-world advantage and it is worth being honest about.
The WordPress Site Editor, the block theme equivalent of Elementor’s visual canvas, has improved significantly. Global styles, template editing, pattern management, and direct block manipulation in a visual context are all much better than they were in 2022. But the learning curve for non-technical clients is still steeper than Elementor’s drag-and-drop experience, and the Site Editor’s interface makes more assumptions about what the user already understands about WordPress.
The classic theme Customizer is, frankly, the worst option for client editing in 2026. It is slow (live preview requires a full page refresh on many configurations), limited in scope (only exposes what the theme developer explicitly adds to it), and being phased out by the WordPress project.
The practical implication: if your clients need to add and move page sections, build landing pages, or rearrange layouts regularly, without developer assistance, Elementor Pro or the block editor in a well-configured block theme are both viable options. Elementor is more intuitive for clients with no WordPress experience. The block editor is better for clients who are willing to invest time learning it and do not want long-term platform lock-in.
When to Use Each: Specific Scenarios
Choose a Block Theme When:
- You are starting a new project and have no existing constraint pushing you toward classic or Elementor
- Performance and Core Web Vitals are a primary requirement
- You are building a content-heavy site (blog, news, documentation) where editorial experience matters
- You want to be positioned well for WordPress 7.0+ features including the Connectors API and AI agent infrastructure
- You are building a standard WooCommerce store without highly complex customization requirements
- You want zero third-party lock-in and maximum future flexibility
Stay on a Classic Theme When:
- You have a large existing client base on a specific classic framework that is actively maintained
- Your site has complex PHP-driven template logic that would require significant re-architecture in blocks
- You have a WooCommerce store with advanced subscription, membership, or variable product configurations that depend on PHP template overrides
- You have a working site that requires no major new development and the migration cost exceeds the benefit
Choose Elementor When:
- Client self-editing of full page layouts is the primary requirement and the client has no interest in learning the block editor
- You are building a heavily visual, campaign-style site that requires granular per-element responsive control
- You need Elementor Pro’s WooCommerce Builder for a custom store design that would require significant PHP work with block themes
- Your agency workflow is optimized around Elementor and the team is already trained on it, the productivity advantage is real for teams that know it well
- You need the specific widget ecosystem (countdown timers, sliders, complex form layouts, animated sections) that Elementor addons provide out of the box
The Migration Question
If you are on a classic theme or Elementor and wondering whether to migrate, the honest answer is: it depends on why you would migrate and what the cost is.
Classic theme to block theme is the migration with the most clear long-term ROI. Block themes will receive core investment and new features; classic themes will not. For a small informational site or blog, the migration is straightforward and worth doing. For a complex application-style site built on a classic framework with many customizations, the migration is a significant project that should be planned and scoped carefully. The complete block themes vs classic themes guide covers the migration path in detail.
Elementor to block theme is the harder migration. Elementor’s proprietary layout data does not translate cleanly to block markup. In practice, an Elementor-to-block-theme migration is often a rebuild rather than a migration, you are recreating the design in the new system, not converting existing content. Budget and timeline accordingly. For complex Elementor sites, the question is usually whether the long-term benefits (performance, no lock-in, lower licensing cost) justify the rebuild cost.
The decision rule we use: if the site is scheduled for a significant redesign anyway, migrate to block themes as part of that work. If the site is stable and the client is happy with it, migration for its own sake may not be cost-justified right now, but plan for it the next time there is a major design change.
Frequently Asked Questions
Can I use Elementor with a block theme?
Technically yes, but it defeats the purpose of both. Elementor works best with a minimal base theme (Hello Elementor) that gets out of its way. Block themes are designed to be built with blocks, not with a separate page builder layer on top. Running both at the same time adds page weight without combining strengths. Pick one approach and commit to it.
Is Elementor Free enough, or do I need Elementor Pro?
Elementor Free covers basic page building for simple sites. For any serious client work, custom WooCommerce templates, form builder, theme builder for headers and footers, dynamic content from custom fields, you need Elementor Pro. Budget for Elementor Pro when evaluating the total cost of the Elementor route. For WooCommerce-specific work, the WooCommerce Builder add-on is included in Pro.
Will classic themes stop working in future WordPress versions?
No. WordPress maintains strong backwards compatibility, and there is no announced plan to deprecate classic themes. Classic themes will continue to work for the foreseeable future. The concern is not that they will break, it is that new WordPress features will be block-theme-first, and classic themes will increasingly require third-party plugins to compensate for capabilities that block themes get out of the box.
Which option is fastest?
Block themes, all else equal. A lean block theme generates minimal HTML with no extra JavaScript by default. Classic themes and Elementor sites can match or approach this with optimization work, but block themes start from a better baseline. For Google PageSpeed Insights scores, block themes typically outperform comparable Elementor sites without specialized optimization. If raw performance is your primary requirement, block themes are the right starting point.
What about Divi, Beaver Builder, and other page builders?
The same analysis that applies to Elementor applies to other page builders with minor variations. They offer visual editing flexibility in exchange for performance overhead and varying degrees of lock-in. Divi’s lock-in is actually more severe than Elementor’s because it uses its own shortcode system throughout content rather than meta-level layout data. Beaver Builder is generally considered more developer-friendly and has a cleaner separation between layout and content. But none of these options change the fundamental trade-off the way block themes do, block themes are built on core WordPress, not a proprietary layer on top of it.