Updated October 15, 2026. A WordPress block theme lets you edit the site shell—not just the text inside posts—with blocks. From Appearance > Editor, you can change headers, footers, navigation, templates, colors, typography, and reusable layouts without opening PHP template files. Block themes were introduced in WordPress 5.9. This guide explains how to identify one, install it safely, use each Site Editor area, decide whether to move from a classic theme, and understand the developer-facing theme.json file.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
What a WordPress block theme changes
In a classic WordPress setup, the block editor mainly controls the content area of a post or page. The theme’s PHP files, widget areas, menu screens, Customizer controls, and template hierarchy handle much of the surrounding site. A block theme extends block editing to those site-wide areas.
As an Amazon Associate I earn from qualifying purchases.
WordPress defines a block theme as “a theme that uses blocks for all parts of a site, including navigation menus, header, content, and site footer.” In practical terms, the same block-based interface can represent a page layout, a header, a footer, an archive, or a 404 page. The Site Editor is the place where those pieces are assembled.
- Site-wide structure: headers, footers, navigation, sidebars, and other repeated regions are block content.
- Templates: layouts for page types such as a single post, archive, search results, or a 404 page can be edited or created visually.
- Global design: colors, typography, spacing, and layout settings are managed through Styles and, for developers,
theme.json. - Widgets and the Customizer: block themes replace traditional widget areas with blocks. The Customizer is generally unavailable unless a plugin or the theme specifically enables it.
The important scope change is that you are editing the theme’s structure as editable block content. That gives non-developers more direct control, but it also means a template change can affect every page that uses it.
#1 Best Overall
Check compatibility before changing a live site
The Site Editor appears only when an active theme supports the block-theme system. If Appearance > Editor is missing, the active theme is usually a classic theme or a plugin has altered the dashboard. Do not treat the missing menu as a broken editor until you verify the active theme.
WordPress recommends trying a new theme on a test site before changing a production site. A staging copy lets you check templates, navigation, plugin output, and responsive behavior without changing what visitors see. Keep a record of the existing theme’s Customizer settings, widgets, menus, and custom CSS; those settings do not automatically become equivalent block-editor content.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →- Confirm that your WordPress installation and hosting environment support the block theme you intend to use.
- Check whether important plugins add widgets, Customizer panels, or theme-specific settings that your new theme will not reproduce.
- Make a backup and test the change on staging first.
- Plan who may edit templates. A person changing a shared header is changing a site-wide resource, not one page.
How to install and activate a block theme
The official directory identifies themes that support the Site Editor. Use the following path in the WordPress dashboard:
- Open Appearance > Themes.
- Select Add New.
- Choose the Block Themes filter to browse compatible themes.
- Open a theme’s details, then select Install. After installation finishes, select Activate.
- Open Appearance > Editor. The Site Editor should now load. If it does not, confirm that the block theme is the active theme and temporarily check for a plugin that changes the dashboard.
Activation may change the site’s layout immediately. Do the first pass on staging, then review the homepage, a single post, an archive, search, and the 404 page before switching production traffic.
Learn the Site Editor areas
The Site Editor’s labels and arrangement can change between WordPress releases, but its main jobs remain consistent. Begin with the areas below in the order most site owners encounter them.
Styles: control the visual system
Open Appearance > Editor > Styles to set global design rules. Depending on the theme, you can adjust the site’s color palette, typography, layout dimensions, spacing, and styles for individual blocks. You can make these changes while viewing a template or template part, so you can see how the design behaves in context.
- Colors: set the global palette and, where offered, background, text, link, and accent colors.
- Typography: choose available font options and set text properties such as size, appearance, and line height.
- Layout and spacing: define content width, padding, margins, and block alignment when the theme exposes those controls.
- Block-specific styles: target a supported block type so buttons, headings, or other repeated elements stay visually consistent.
Use Styles for rules that should apply broadly. If you change one heading block directly, you are making a local exception; if you change the heading block’s style in Styles, you are defining a system for every matching block.
Navigation: manage menus with the Navigation block
The Navigation area manages menus represented by the Navigation block. You can select an existing menu, add page or custom links, reorder items, and create submenu relationships using the controls presented by your installation and theme.
Because navigation is normally placed in a header template part, a menu edit can appear across many templates. After saving, check the desktop and mobile presentations supplied by the theme. A menu that fits on a wide screen may need a different arrangement at smaller widths; the available responsive controls depend on the theme and WordPress version.
Templates: edit layouts for content types
Templates define the arrangement used by a class of pages or posts. Typical entries include a single-post template, page template, archive, search results, and 404 page. Select a template from Appearance > Editor > Templates to inspect its blocks and edit the layout.
A template commonly contains a header template part, a main content area, post or page metadata, a comments area, and a footer template part. You can insert, remove, reorder, or configure blocks just as you would in a page editor, while remembering that the result applies to the whole content type.
When you save a template in the editor, the saved editor version takes precedence over the template file bundled with the theme. If the theme later updates its bundled file, your saved customization remains the version WordPress uses until you reset or replace it.
Template parts: reuse structural regions
Template parts are reusable structural regions such as headers, footers, and sidebars. Manage them from the Site Editor’s template-part controls or by selecting a part while editing a template. Use a template part when the same region should stay synchronized across multiple templates.
For example, place the site logo, Navigation block, and utility links in a header template part. Place the copyright notice, secondary links, and footer navigation in a footer template part. Editing that part then updates every template that includes it, so check the list of affected templates before saving a substantial change.
Patterns: save reusable sections and layouts
A pattern is a reusable arrangement of blocks for a section or layout. Examples include a call-to-action section, a feature grid, an author biography, or a repeatable pricing-information layout. Manage patterns at Appearance > Editor > Patterns.
WordPress distinguishes theme-supplied patterns from patterns you own:
- Theme patterns: supplied by the active theme and locked in their original form. Duplicate one to create an editable copy.
- User patterns: created or copied by you. You can edit, rename, duplicate, export as JSON, or delete them.
- Imported patterns: a JSON file can be imported when you need to move a reusable arrangement between sites.
Choose a pattern when editors may insert the section in different places or when it is a reusable content composition. Choose a template part when the region is part of the site’s repeated structural frame.
Pages and site identity
The Site Editor also exposes page management and site-identity controls in its navigation. The exact labels vary by WordPress release and theme. Use these areas to move between editing the site’s content and editing the framework that displays that content. If a setting is not present, look at the block selected in the current template or at the theme’s available Styles options rather than assuming the feature has been removed globally.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Editing a header, footer, or complete template
To change a shared header or footer, open Appearance > Editor, choose Templates or Template Parts, and open the relevant item. You can also select the header or footer while viewing a template. Make the block changes, preview the result, and select Save.
- Identify whether you are editing a template or a template part. A template controls a page type; a part is a reusable region inside one or more templates.
- Select the block you want to change. Use list view when nested groups, columns, or navigation items make the canvas difficult to inspect.
- Adjust block settings and, for broad design changes, use Styles instead of repeating local overrides.
- Preview representative content: a page, a post, an archive, and a narrow viewport if your preview tools provide one.
- Save only after checking which templates or parts are included. WordPress may present a confirmation listing the changes.
If the same header appears on every post and page, edit the header template part once. If only archive pages need a different arrangement, edit the archive template instead of creating a separate header for every page.
Templates, template parts, and patterns: which one should you use?
| Use this | It controls | Typical examples | Effect of editing |
|---|---|---|---|
| Template | The complete layout for a content type | Single post, page, archive, search, 404 | All content that uses that template receives the change |
| Template part | A repeated structural region inside templates | Header, footer, sidebar | Every template containing that part can change |
| Pattern | A reusable section or block arrangement | Hero section, feature grid, call to action | Insert the pattern where needed; editing its saved copy depends on how it was created and managed |
This distinction prevents two common mistakes: putting a site-wide header into a one-off pattern, or building the same footer separately in several templates and allowing them to drift apart.
Rank #4
What theme.json does
For developers and advanced site builders, theme.json is the central configuration file for editor settings and global styles. It lets a theme declare which controls appear in the editor and how those controls map to the front end.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsDocumented top-level areas include settings, styles, customTemplates, templateParts, and patterns. Depending on the theme and WordPress version, configuration can:
- enable or limit color, typography, spacing, and layout controls;
- define color palettes, gradients, duotone filters, and font options;
- add custom CSS properties used by the theme;
- declare styles that appear consistently in both the editor and the front end;
- register custom templates, template parts, and patterns.
Editing the file directly requires basic JSON and CSS knowledge. A malformed JSON value can prevent the theme configuration from loading, while an overly broad style rule can affect every matching block. Keep a backup, validate syntax, and make one small change at a time. Site Editor changes are often safer for non-developers because WordPress exposes the supported settings and stores the resulting customization without requiring file access.
Block themes versus classic themes
| Decision area | Block theme | Classic theme |
|---|---|---|
| Site-wide editing | Blocks in the Site Editor can edit headers, footers, navigation, templates, and styles. | PHP templates, widgets, menus, and Customizer workflows do most of the work. |
| User workflow | Visual editing from Appearance > Editor. | Theme settings, template files, widget screens, and Customizer panels. |
| Best fit | People who want direct control of the whole site and are comfortable with block editing. | Sites or teams that depend on classic PHP, widget, or Customizer behavior. |
| Development model | HTML block templates plus configuration such as theme.json. |
PHP, JavaScript, CSS, and classic theme APIs. |
“Better” depends on the work you need to do. A block theme is a strong fit when editors must adjust the site shell without a developer. A classic theme may be the lower-risk choice when a site’s workflow is tightly coupled to PHP template overrides, widget areas, or Customizer settings that have no equivalent in the new theme.
Moving an existing site to a block theme
Theme switching changes presentation, not the underlying posts and pages, but it can change where menus, widgets, and customizations appear. Treat migration as a mapping exercise rather than a one-click redesign.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11- Inventory the current site: record menus, widget areas, Customizer values, custom CSS, template overrides, and plugin-generated components.
- Create a staging copy: install and activate the candidate block theme there first.
- Map navigation: confirm that existing menus are available through the Navigation block and rebuild missing relationships if necessary.
- Rebuild repeated regions: create header and footer template parts instead of duplicating blocks in each template.
- Recreate page-type layouts: review single, page, archive, search, and 404 templates. Do not assume a classic theme’s PHP hierarchy will produce the same visual order.
- Reapply design rules: use Styles for global colors, typography, layout, and block-level defaults; add local exceptions only where needed.
- Test plugin output: check forms, commerce components, memberships, and any plugin that supplied widgets or Customizer controls.
- Review content types: inspect representative posts, pages, archives, search results, and error pages before scheduling the production switch.
- Document editor permissions: decide who may save templates and template parts after launch.
Common problems and practical fixes
“Appearance > Editor” is missing
Confirm that a block theme is active. The Site Editor is not available with an ordinary classic theme. If a block theme is active and the menu is still absent, check whether a plugin or custom code is altering the dashboard, then test with nonessential plugins disabled on staging.
A theme update did not change my template
An editor-saved template takes precedence over the theme’s bundled template file. Your saved version can therefore remain in use after the theme updates. Review the template’s saved customizations and reset or replace them deliberately if you want to adopt the newer bundled layout.
Best Value
A header or footer change appeared everywhere
That is the expected behavior of a shared template part. Open the list of templates that include the part and decide whether the region should remain global. If only one content type needs a variation, edit that template or create a separate part instead of altering the shared one.
A theme pattern cannot be edited
Theme-supplied patterns are locked in their original form. Duplicate the pattern, then edit and rename the user-owned copy. Manage the copy from Appearance > Editor > Patterns.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →The design looks inconsistent between editor and front end
Check whether a local block override is defeating a global Style, whether the selected template is the one used by the page type, and whether a plugin adds its own CSS. A theme.json rule is intended to configure styles for both editor and front end, but custom CSS or plugin styles can still change the rendered result.
A classic widget or Customizer option disappeared
Block themes replace traditional widget areas with blocks, and the Customizer is generally unavailable unless specifically enabled. Recreate the function with blocks, a supported plugin interface, or a theme that provides an equivalent control. Preserve the original site until you confirm the replacement behaves correctly.
Best practices for a maintainable block-theme site
- Use global Styles for global decisions: define the palette, typography, spacing, and layout once instead of hand-tuning every block.
- Keep shared structure in template parts: one header and one footer are easier to audit than many duplicated copies.
- Use patterns for editorial reuse: give content creators ready-made sections without turning every section into a site-wide structural dependency.
- Name user patterns clearly: include the purpose and, when useful, the placement, such as “Author bio—posts.”
- Limit template editing permissions: a saved template changes every item that uses it.
- Test after each structural change: inspect a single item, a listing, search, and the 404 view rather than relying on the editor canvas alone.
- Keep a staging workflow: export or document reusable patterns and record intentional template customizations before theme updates.
- Use
theme.jsondeliberately: define the controls and design tokens your team actually supports; avoid exposing settings that create inconsistent combinations.
Is a block theme right for you?
Choose a block theme when the people maintaining the site need to change headers, footers, navigation, templates, and global styling from the WordPress interface. It is also a good fit for a team willing to adopt a block-based design system and to document which templates and parts are shared.
Stay with a classic theme, at least for now, when critical workflows depend on classic widget areas, Customizer panels, PHP template overrides, or plugin integrations that have not been mapped to the Site Editor. You can evaluate a block theme on staging without committing your production site, then make the decision after testing real content and plugins.
Recommended Free Tools
What to remember
- Block themes make the whole site editable with blocks, not only post content.
- Activate one, then open Appearance > Editor to use the Site Editor.
- Use Styles for global design, Navigation for menus, Templates for page-type layouts, Template Parts for repeated structure, and Patterns for reusable sections.
- Saving a template affects every post or page that uses it, and the saved editor version overrides the theme’s bundled template file.
theme.jsongoverns editor settings and global styles for developers who are comfortable with JSON and CSS.- Block themes began in WordPress 5.9; pattern and template-part management through the Site Editor sidebar is documented as available since WordPress 6.3. Interface details continue to evolve, so verify labels on the WordPress version you run.
Frequently Asked Questions
Can I use the Site Editor without changing themes?
No. The Site Editor is available after a block theme is active. A classic theme normally uses its traditional template, widget, menu, and Customizer workflows instead.
Why did my template change affect every post?
You edited the template assigned to that post type. Templates define layouts for a class of content, so WordPress applies the saved layout to every item using it.
Should a reusable section be a pattern or a template part?
Use a pattern for an insertable content or layout section. Use a template part for a repeated structural region such as a header or footer that should stay synchronized across templates.
Do I need to edit theme.json to build a block-theme site?
No. Site owners can use the Site Editor. Direct theme.json editing is an advanced option for configuring editor settings and global styles and assumes basic JSON and CSS knowledge.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
