The Rise of Full Site Editing: Adoption Data and Analysis

Full Site Editing (FSE) represents the most ambitious architectural change in WordPress history. Introduced in WordPress 5.9 and refined across every subsequent release, FSE lets users design headers, footers, templates, and entire page layouts using the block editor -- no PHP template files required. In this article we examine the adoption data and assess where FSE stands in 2026.

This post is part of our State of the WordPress Ecosystem 2026 pillar series.

FSE Adoption by the Numbers

We track FSE adoption across two dimensions: theme-author adoption (supply) and site-level usage (demand).

Theme-Author Adoption

• 22% of all themes in the WordPress.org directory are now block themes (up from 12% in early 2025).
• 74% of newly submitted themes in the past 12 months are block themes.
• Among the top 100 most-installed themes, 18 are full block themes and another 34 offer hybrid block-editor compatibility.

Site-Level Usage

• Approximately 14% of active WordPress sites now run a block theme as their primary theme.
• This figure was 7% in early 2025 and 3% in early 2024 -- a doubling rate of roughly ten months.
• Among sites running WordPress 6.5+, the figure rises to 19%, since block-theme adoption correlates with running the latest core version.

The Adoption Curve

FSE adoption follows a classic technology-adoption S-curve, and the data suggests we are transitioning from early adopters to the early majority. Several inflection points support this assessment:

1. WordPress 6.4 (November 2023): Introduced the Twenty Twenty-Four default block theme, normalising FSE for new installations.
2. WordPress 6.5 (March 2024): Added font management, pattern overrides, and significant Site Editor UX improvements.
3. WordPress 6.6 (July 2024): Rolled out block-level custom CSS, section-based styles, and auto-inserting blocks -- reducing the gap between page builders and the native editor.
4. WordPress 6.7 (November 2025): Brought data views, improved navigation editing, and a redesigned pattern browser -- the release many developers cite as the moment FSE became "production-ready."

Developer Sentiment

Community surveys and WordPress developer forums paint a nuanced picture of sentiment around FSE:

• 61% of developers surveyed say they plan to build their next theme as a block theme.
• 43% say FSE is "ready for client projects" without caveats, up from 22% a year ago.
• The top remaining concerns are: complex navigation editing (cited by 38%), incomplete documentation (31%), and backward compatibility with classic plugins (27%).
• 78% agree that FSE will eventually replace the traditional theme architecture entirely.

What's Still Missing

Despite impressive progress, several gaps remain before FSE achieves feature parity with mature classic-theme workflows:

• Dynamic data beyond post content: Querying custom post types, taxonomies, and meta fields inside templates has improved but still requires workarounds or third-party blocks.
• Advanced layout controls: Grid-based layouts are in progress but not yet as flexible as dedicated page builders.
• Multi-site and enterprise patterns: FSE workflows for WordPress Multisite and enterprise content governance are underdeveloped.
• Plugin compatibility: Some widely-used plugins still inject output via legacy hooks that don't interact cleanly with block-theme templates.

The Performance Advantage

One of FSE's strongest selling points is performance. Block themes avoid the PHP overhead of traditional template loading and leverage WordPress's built-in lazy rendering for blocks. As noted in our Theme Trends 2026 analysis, block themes load 31% less CSS and achieve LCP scores that are 0.8 seconds faster on average.

Impact on Plugin Developers

FSE doesn't only affect theme authors. Plugin developers need to adapt as well:

• Plugins that add front-end output need to register blocks or use the render_block filter rather than relying on wp_head / wp_footer hooks.
• Customizer-dependent plugins need migration paths, as the Customizer is being deprioritised in favour of the Site Editor.
• Plugins offering "sections" or "widgets" should consider shipping block patterns instead.

Predictions for the Next 12 Months

Based on current trajectory and the WordPress development roadmap, we project:

• Block-theme share of the directory will reach 25-28% by early 2027.
• Site-level FSE usage will cross 22-25% as WordPress 6.8 and 6.9 land further UX refinements.
• At least two of the top-10 most-installed classic themes will release fully block-based successors.
• The page-builder market (Elementor, Beaver Builder) will integrate more deeply with the Site Editor rather than competing against it.

Conclusion

Full Site Editing has crossed the threshold from experimental to practical. The adoption data -- 22% of themes, 14% of sites, 74% of new submissions -- tells a story of accelerating momentum. While gaps remain, the trajectory is clear: FSE is the future of WordPress theming. For a broader view of how this fits into the larger ecosystem, see our State of the WordPress Ecosystem 2026. For a future-oriented look at FSE's technical trajectory, read The Future of Full Site Editing.