Full Site Editing (FSE) explained for WordPress

Full Site Editing (FSE) is the set of WordPress features that lets you edit headers, footers, templates and other site parts with blocks via the Site Editor; these capabilities were introduced progressively into core starting with WordPress 5.8 and matured with WordPress 5.9, which shipped a default block theme designed for FSE (sources consulted September 27, 2026).

What is Full Site Editing (FSE)?

Full Site Editing is a set of integrated WordPress features that enable editing of the whole site with blocks through the Site Editor interface. The Site Editor name is the preferred, user‑friendly label adopted by the project (Make.WordPress.org update, consulted September 27, 2026).

FSE shifts site structure and presentation into block units. The Site Editor exposes templates, template parts, global styles and patterns in a single UI. Block themes are designed to be edited via that UI and use theme.json to declare settings and styles (WordPress.org documentation; developer handbook, consulted September 27, 2026).

How FSE changed WordPress: quick chronology

2021: WordPress 5.8 introduced major block editor advances and prepared the ground for site‑level block editing. The WordPress.org news post describes those initial steps and the intended scope of the work (WordPress.org news, consulted September 27, 2026).

January 2022: WordPress 5.9 shipped with the Twenty Twenty‑Two default block theme. Twenty Twenty‑Two was published to support the Site Editor and block‑based theming workflows (Twenty Twenty‑Two documentation, consulted September 27, 2026).

Ongoing: the project refined naming and the UI. The Site Editor label became preferred as the interface matured and community guidance documented the evolving screens and features (Make.WordPress.org update, consulted September 27, 2026). These dated items show a progressive rollout rather than a single release event.

Core concepts

Block themes: themes authored with blocks and theme.json. They declare templates and template parts and use theme.json to define global settings, supported blocks and default styles. Block themes are intended for editing via the Site Editor rather than by editing PHP templates (Block themes documentation; developer handbook, consulted September 27, 2026).

Site Editor: the UI that exposes templates, template parts, global styles and patterns. It centralizes editing of site structure and visual design in the block paradigm and is the interface users access to make site‑wide changes (Make.WordPress.org update; Learn.WordPress lesson, consulted September 27, 2026).

Templates and template parts: templates define page‑level layouts; template parts are reusable areas such as header and footer. Both are editable in the Site Editor. Edits are saved to the database, while themes may provide default template files as starting points (Developer Block Editor Handbook, consulted September 27, 2026).

Global styles and theme.json: theme.json is the configuration file used by block themes to declare global settings and default visual styles. Global styles let site authors set typography, color palettes and spacing at site scope from the Site Editor UI (Block themes documentation; developer handbook, consulted September 27, 2026).

Patterns: reusable block combinations provided by themes or pattern libraries. Patterns speed layout construction by offering composed block groups that can be inserted into templates or content (fullsiteediting.com; block themes documentation, consulted September 27, 2026).

Differences vs classic themes and vs page builders

Classic themes: rely on PHP templates and the Customizer for many global settings. Structure edits often require file changes, child themes or developer work. Classic templates execute server‑side code to generate output and often separate design from the block editor.

Block themes and FSE: move template editing into the editor UI. Templates and template parts are editable visually. theme.json centralizes style control so many global adjustments that once required code can now be done in the Site Editor (Block themes documentation; developer handbook, consulted September 27, 2026).

Page builders: are external plugins that provide visual editing interfaces. FSE is native to WordPress core and does not require a separate plugin for template editing. Native integration reduces reliance on third‑party builders for some sites. At the same time, page builders may still be preferred on legacy projects or where a specific builder offers advanced workflows not yet matched by the Site Editor. Compatibility and feature parity vary; test each case before committing (Learn.WordPress tutorial; How to switch guide, consulted September 27, 2026).

When to choose FSE (profiles)

Solo site builders and small projects: block themes plus the Site Editor reduce the need for custom PHP edits. The visual template and global style controls support no‑code changes to headers, footers and other template parts, which fits projects that prefer visual control over bespoke development.

Small agencies and multisite setups: a mixed approach can make sense. Block themes speed common edits, but agencies should test plugin behavior, multisite handling and theme.json workflow on staging. Pattern management and deployment strategy matter when many sites are involved.

Sites with heavy custom PHP templates or plugin‑dependent layouts: a staged migration or continued use of a classic theme may be safer. When server‑side hooks, bespoke PHP templates or tightly coupled plugins drive layout, keep a fallback and validate critical functionality before switching themes (Learn.WordPress and developer handbook guidance, consulted September 27, 2026).

Practical migration checklist

These steps follow the “how to switch” guidance and developer documentation; consult the Learn.WordPress tutorial and Developer Handbook when performing a migration (Learn.WordPress tutorial; developer handbook, consulted September 27, 2026).

Limits, caveats and common pitfalls

Plugin compatibility: some plugins continue to rely on widgets, server hooks or PHP templates. Those plugins may require configuration changes or replacements when moving to a block theme. Test critical plugins on staging (How to switch guide and Learn.WordPress tutorial, consulted September 27, 2026).

theme.json and global style precedence: global styles can override theme defaults. Misconfigured theme.json entries can create unexpected global styling effects. Review theme.json and test style settings before wide deployment (Block themes documentation; developer handbook, consulted September 27, 2026).

Template persistence and version control: editing templates in the Site Editor writes changes to the database. This differs from editing files in a theme repository. Maintain version control by exporting templates or keeping theme files in a repository when appropriate (Developer Block Editor Handbook, consulted September 27, 2026).

Feature parity and evolution: the FSE ecosystem is still evolving. Some visual features offered by mature page builders may not yet have exact equivalents in the Site Editor. Decisions should be based on current documentation and staging tests rather than on assumptions about parity.

Apply the migration checklist and validate compatibility in a staging environment before any production switch.

FAQ

Is FSE available on every WordPress install? FSE features exist in WordPress core, but to use the Site Editor you need a block theme or a plugin that enables equivalent functionality. Check the documentation for theme requirements (WordPress.org docs, consulted September 27, 2026).

Can I revert to a classic theme? Yes. Switching themes restores the classic theme as active. Content remains, but templates and visual output should be tested after the switch to confirm layout and functionality (How to switch guide, consulted September 27, 2026).

Will my plugins break? Some plugins that rely on widgets, server‑side PHP templates or shortcodes may require configuration, updates or replacements. Test all critical plugins on a staging instance before switching (How to switch guide and Learn.WordPress tutorial, consulted September 27, 2026).

How we made this explainer

This article is based on official WordPress documentation and community resources consulted on September 27, 2026: WordPress.org (news, documentation), Developer Handbook, and Learn.WordPress tutorials. The page summarizes those sources and does not claim hands‑on testing by the site.

What we could not establish from the documentation we reviewed

The following items were not established in the materials provided and are therefore not stated as facts on this page:

Related guides

• Elevate Your Website: Making Accessibility Simple and Effective
• Make Your WordPress Site Speak to the World Without Emptying Your Wallet
• The Hidden Dangers of Using Outdated PHP Versions on Your WordPress Site
• WordPress Themes