← Back to Blog

Block Editor vs Site Editor

The Block Editor and Site Editor use the same block system, but they control different layers of a WordPress website.

Veyra Admin

5 min read

  • Guide
  • Beginner
  • 5 minutes read
  • Reviewed August 5, 2026
  • WordPress themes and templates

The Block Editor and Site Editor use the same block system, but they control different layers of a WordPress website.

The Block Editor is primarily used to create the content of an individual post, page or other supported post type. The Site Editor is used to edit site-wide styles, templates and template parts when a block theme is active.

Understanding the boundary prevents accidental template changes and helps teams decide where a design belongs.

The Block Editor Controls Individual Content

The Block Editor opens when you edit a post, page or compatible custom post type.

It is used for content such as:

  • Headings and paragraphs.
  • Images, galleries and media.
  • Lists and tables.
  • Buttons and calls to action.
  • Columns and groups.
  • Embedded content.
  • Reusable patterns.
  • Custom blocks provided by plugins.

The editor also exposes document settings such as status, author, taxonomy terms, featured image and excerpt when supported by the content type.

Changes normally affect only the current content item, although synced patterns can update every location where the same pattern is used.

The Site Editor Controls the Site Structure

The Site Editor is available under Appearance → Editor when a block theme is active.

It provides tools for:

  • Templates.
  • Template parts such as headers and footers.
  • Global Styles.
  • Style variations.
  • Site navigation.
  • Patterns.
  • Site-wide custom CSS.

A change to a template can affect many pages at once. Editing the Single template, for example, may change the layout of every post that uses it.

The Template Editor Sits Between Them

WordPress can also provide a Template Editor while editing a post or page.

It allows authorized users to edit or create templates associated with content. It is available with block themes and can also be enabled by compatible classic themes.

This interface looks similar to the content editor, so verify whether you are editing the page content or the template around that content.

Shared Blocks, Different Contexts

Many blocks can appear in both editors, but their purpose changes with context.

A Paragraph block in a post stores the actual paragraph. A Post Content block in a template acts as a placeholder that outputs the current post's stored content.

Theme blocks such as Post Title, Query Loop, Site Logo and Navigation are designed for dynamic site structures. They may be available only in template contexts or make little sense inside ordinary content.

How to Decide Where a Change Belongs

Use the Block Editor when the change is unique to one content item.

Use a pattern when a layout should be reused as a starting point or synchronized component.

Use a template when every item of a type should share the structure.

Use a template part when a region such as the header or footer appears across several templates.

Use Global Styles when colors, typography, spacing or block defaults should apply across the site.

Permissions and Governance

The Site Editor gives users significant control over the public website. Not every content editor should necessarily be able to change templates or global styles.

Plan roles and workflow around the risk of site-wide changes. On managed projects, designers or administrators may own templates while editors work only with content and approved patterns.

Common Mistakes

  • Building repeated site structure inside every page.
  • Editing a template when only one page should change.
  • Placing unique content inside a global template.
  • Duplicating a pattern instead of updating a synced version.
  • Giving unrestricted design access without review or recovery procedures.
  • Assuming every theme provides the Site Editor.

Frequently Asked Questions

Why can I not see Appearance → Editor?

The full Site Editor requires an active block theme. A classic theme may provide the Customizer or other theme-specific tools instead.

Does changing a template edit my post content?

No. The template changes the structure around content. The Post Content block outputs the stored body of each item.

Can the same block be used in both editors?

Many blocks can, but theme blocks and dynamic placeholders are intended mainly for templates and site structure.

Applying Block Editor vs Site Editor in a Real WordPress Project

Separate content, presentation and permanent functionality. Test the editing workflow as well as the public output, because a theme decision affects templates, design controls, accessibility, performance and future redesign work.

A connected concept is WordPress Templates and Template Parts. Reading the two together helps separate the immediate task from the wider WordPress responsibility.

A useful implementation begins by writing down the current state, the intended outcome and the evidence that will prove the change worked. This prevents a configuration screen, plugin recommendation or code snippet from becoming the entire strategy.

Decision Matrix

| Question | Block Editor | Site Editor | |—|—|—| | Primary responsibility | Identify what this option owns | Identify what this option owns | | Data and portability | Review what remains if the option changes | Review what remains if the option changes | | Editing workflow | Test the interface with real users | Test the interface with real users | | Maintenance | Check updates, compatibility and support | Check updates, compatibility and support | | Exit path | Define migration or replacement steps | Define migration or replacement steps |

How to Make the Decision

Do not choose from a demo or feature list alone. Build a short requirements list, test the highest-risk workflow and compare the complete operating cost. The correct choice is the one the team can maintain while preserving the required data and user experience.

Review Editor and Frontend Behaviour

A block feature has at least two user experiences: the editor used to create it and the frontend used to consume it. Dynamic data, responsive behaviour and accessibility can differ between the two.

Test insertion, selection, keyboard operation, saved markup, server rendering, theme styles and backward compatibility with previously saved content.

Official Reference Context

The Block Editor Handbook is the primary version-specific reference for this topic. Use the current documentation to verify interface labels, supported APIs and behaviour before applying instructions to a production site.

How to Verify the Result

  • Test representative templates on mobile and desktop.
  • Check keyboard navigation, headings, contrast and focus.
  • Switch editing contexts and confirm that the team knows where each design decision is stored.

Sources and Further Reading

Continue Learning