WordPress Site Editor theme export lets you package important design and structural changes made to an active block theme in a downloadable ZIP file. This is useful when a site owner, freelancer, designer or agency wants to preserve a customized theme or test the same theme adjustments on another site. The workflow focuses on changes made through the Site Editor rather than on a complete website migration.
Before exporting, set the right expectation: WordPress documents the package as containing updated templates, template parts and style settings. That makes it a practical theme-customization package, but not a confirmed full-site backup. Content, media, plugin settings, WooCommerce configuration, user accounts and other database data should not be assumed to be included. The following guide explains the export scope, the steps to create the ZIP and the checks to complete before using it elsewhere.
What the Site Editor Theme Export Actually Contains
Theme files versus full-site data
The documented export is available when a block theme is active. From the Site Editor, WordPress can generate a ZIP containing the theme with the relevant customizations made to templates, template parts and style settings. In practical terms, the package represents the visual and structural work performed in the block-theme editing workflow.
This scope is different from a complete site backup. The reviewed documentation does not provide an exhaustive inventory of every object excluded from the ZIP, so the safest description is limited to what it confirms: theme-related templates, template parts and styles. Do not present the exported file as a verified restore package for the whole website, and do not assume that it carries all site data or third-party configuration.
The role of templates and template parts
Templates define layouts for specific page types. They determine how a particular type of page is structurally arranged in the block theme. Template parts are reusable structural areas, such as headers, footers and sidebars. Editing one of these areas can affect the presentation of multiple parts of a site.
Because both types of objects are part of the documented export scope, a customized ZIP can package more than a single page design. It can include the relevant layout changes and reusable structural edits made in the Site Editor. This does not mean that every integration connected to those layouts is preserved; the confirmed scope remains the block-theme customization itself.
Prerequisites and Compatibility Checks
Check the source site
Start by confirming that the source site uses an active block theme. The documented full Site Editor workflow depends on that context, so the same export process should not be assumed for a classic theme. Open Appearance > Editor and verify that the Site Editor is available for the active theme.
Before exporting, review the changes you intend to preserve. Check the templates, template parts and style settings that were edited through the Site Editor. This helps you understand what the resulting package is expected to contain and separates theme customizations from changes made elsewhere in WordPress or by plugins.
Check the destination environment
If the ZIP will be used on another site, assess that destination before installation or activation. It should have a compatible block-theme setup, and the required blocks or plugins used by the customized templates should be available. Missing dependencies may result in incomplete layouts or editor warnings.
Also consider the destination WordPress and theme context. An exported theme should not be assumed to work unchanged on every site. The exact appearance and menu labels can vary across WordPress versions, active themes and interface updates, so treat the documented navigation as a practical guide rather than a permanently universal interface.
How to Export a Customized Block Theme
Open the export command
With the block theme active, open Appearance > Editor to enter the Site Editor. Open the editor’s tools or options menu near the available editor controls and choose Export. WordPress then generates a downloadable ZIP file containing the theme with the relevant current Site Editor customizations.
The command packages the documented theme-related changes together. You do not need to export every template and template part separately to create the block-theme package. The export is generated from the current templates and template parts in the Site Editor, while the documented style settings are included as part of the theme export scope.
Retain the ZIP for testing
Download and retain the generated ZIP in a controlled location. Treat it as a version of the customized block theme, not as proof that the entire website has been backed up. If the package is intended for another site, use it first in a staging environment.
Create an independent backup of the destination before installing or activating the exported theme. This separate backup is important because the documented export concerns theme-related files and settings and is not presented as a complete website backup. Avoid replacing a production design until the package has been checked in a controlled test.
How Templates and Template Parts Are Handled
Finding template parts in the Site Editor
In current WordPress documentation, template parts are accessed through Appearance > Editor > Patterns. They may be listed alongside other patterns rather than appearing as a separate top-level template-parts area. This explains why a user may not see a standalone menu item named Template Parts.
Look for the reusable structural areas used by the theme, including headers, footers and sidebars. The export command is separate from this browsing location: after the relevant Site Editor changes have been made, the theme export packages the applicable templates and template parts together. Each template part does not need an individual theme-export command.
How saved edits are synchronized
There is a technical reason why Site Editor changes can become part of an exported theme. When a user edits a block template or template part, WordPress keeps the original theme file and stores the edited version as a site-level template entity. The edited version is then used by the site.
During export, the relevant edited templates and template parts can be synchronized back into theme files in the generated package. This explains the relationship between the changes visible in the Site Editor and the ZIP produced by the export process. It also reinforces the scope limitation: the process packages the relevant theme structures, not every type of data stored by the website.
How Global Styles Are Included in the Export
What Styles can change
Yes, global style customizations can be included in the exported theme. The documented export includes style settings saved through the Site Editor. The Styles interface covers site-wide typography, colors and layout, and it can also provide style controls for individual block types across the site.
When reviewing the source site, inspect these settings alongside the templates and template parts. Typography, colors, layout rules and block-level styles are part of the visual system that the customized block theme presents. Including them in the export helps keep the theme package connected to the design work performed in the Site Editor.
Limits of the style export claim
The inclusion claim should remain precise. It applies to style settings documented within the Site Editor workflow. It should not automatically be extended to plugin-specific CSS, external font services, custom code or every external asset that may influence the appearance of a site.
For that reason, test the exported theme rather than assuming that every visual dependency will transfer. A destination site may need the same required blocks, plugins, fonts, images or custom functionality used by the original design, and the reviewed documentation does not guarantee that all such dependencies are packaged in the ZIP.
Testing the Exported Theme on Another Site
A practical staging checklist
Use the ZIP on staging before applying it to production. First create a separate backup of the destination site. Then confirm that the destination supports a compatible block-theme setup and that the required blocks and plugins are available. These checks reduce the risk of testing a package in an environment that cannot reproduce the source site’s editing context.
After installing or activating the exported theme in the test environment, review both structure and appearance. Check the following areas:
- Templates: confirm that the expected page layouts and template assignments are present.
- Template parts: inspect reusable areas such as headers, footers and sidebars.
- Global styles: review typography, colors, layout and styles applied to individual block types.
- Navigation and site identity: verify the elements that visitors use to identify and move through the site.
- Responsive layouts: inspect how the design behaves across the relevant screen sizes.
- Dependencies: confirm that required blocks, plugins, fonts, images and custom functionality are available.
Review the result after activation or import instead of assuming that the source design has transferred unchanged. Missing dependencies can produce incomplete layouts or editor warnings. Keep the independent destination backup until testing is complete, and do not treat the theme ZIP as a substitute for a separate backup of site data.
Theme export versus pattern export
Full block-theme export should also be distinguished from exporting an individual custom pattern. Current documentation describes a separate pattern workflow. User-created patterns can be exported individually as JSON files, while a bulk pattern export produces a ZIP containing JSON files. This is useful when the goal is to transfer selected reusable patterns rather than the broader customized theme.
Patterns bundled with a theme are locked and cannot be exported in the same way. Therefore, choose the workflow based on the object you want to transfer:
- Use the Site Editor theme export when you need a package of the customized block theme, including relevant templates, template parts and style settings.
- Use the separate pattern export when you need individual user-created patterns as JSON files or a ZIP containing those JSON files.
Neither workflow should be described as a complete website migration without separate verification. The theme export is centered on theme files and Site Editor customization, while the pattern export targets selected pattern data. Keeping these purposes separate makes it easier to plan testing, backups and any additional transfer work required by the destination.
WordPress Site Editor theme export provides a focused way to package customizations made to an active block theme. The generated ZIP contains the documented changes to templates, template parts and style settings, including global typography, colors, layout and relevant block-level styles saved through the Site Editor. Templates control page-type layouts, while template parts organize reusable structural areas.
Use the export as a theme-customization transfer, not as a confirmed full-site backup. Before using it elsewhere, create an independent backup, test the ZIP on staging, confirm the block-theme context and required dependencies, and review the resulting templates, styles, navigation and responsive behavior. For tools that support your wider website workflow, Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.