Bad Sector

Do you need a child theme?

When should you use a child theme with fully native WordPress block themes in late 2026? Use this guide to decide which design changes can live in WordPress’s Site Editor and database and which need to be more portable in files you can review and deploy from a code repository.

Risograph-style illustration: a translucent pink sheet laid over a blue page layout, changing only a few of its blocks, beside a checklist of five boxes, three of them ticked.

Block themes let you change almost anything in WordPress’s Site Editor, so the old advice to always use a child theme no longer holds so firmly. That doesn’t mean child themes will become irrelevant to WordPress users. Whether a child theme is worth adopting depends less on the theme than on who builds and maintains a site, how they need to go about it, and the requirements they and the site owner or end users have.

This is the short, practical companion to “Three themes, one question: where should your design live?,” which examines Ipsum, the new core default theme, and Mētis, the new flagship theme. Both have a lot in common with the already established Ollie theme. All three can be used with or without child themes, but they offer different levels of support for child theming, especially in relation to AI.

Does your design need to leave the database?

My old rule of thumb about child themes asked whether you’d ever need to change the active theme’s code. If you needed to customize a theme, you were better off building or adopting a third-party parent theme as a foundation that is separately maintained, and a child theme you maintain to hold all your unique code. Child themes inherit everything the parent does unless they explicitly change or remove it, so they can add their own unique elements. A key, long-term benefit to this arrangement is that a well-maintained parent will take updates, which you can apply without overwriting your customizations, which would be the case if you modified the parent theme code. Changes to a parent theme might still break or interfere with your changes at the level of the child theme, but this can be reviewed and managed as a normal maintenance process.

Today, the modern WordPress site and block editor stores changes made through the admin user interface in the database along with your content. This includes global styles, page templates, template parts, and block patterns — and they will augment or override whatever the active theme does by default.

This makes the decisive question to ask about child themes much simpler: Do your design customizations need to exist anywhere other than their site’s database? If yes, it needs to live in files, and if you want to keep those files out of the parent theme for the maintenance value I noted above, that means using a child theme. If you don’t need your design modifications to travel beyond their site, keeping them in the Site Editor and WordPress database with good backups will be fine.

How to decide

The following non-technical decision tables will help you answer the key question of how portable your design changes need to be.

If…Your design has to exist…
There’s a staging site, local copies, or a test environmentOn every copy, in sync. Syncing theme files is much easier than moving design stored in the database.
The same design runs on more than one siteOn every site, from one shared foundation. The same header on six client sites is all the reason you need.
Someone else edits the design, or will take the site over from youIn a state you can hand over, with a record of who changed what.
Changes need review or rollbackIn a shared history. The Site Editor keeps revisions, but version control gives a team a history it can review, branch, and deploy across environments.
AI agents edit the designIn a diff a person can approve before it goes live. An agent working in the Site Editor changes the live site the moment it saves.
You answer to a compliance teamIn an approval record and a reproducible deployment. “The agent did it in the Site Editor” won’t satisfy anyone.

Custom PHP doesn’t change the answer. The Site Editor can’t write PHP no matter where your design lives. Theme-specific PHP can go in a child theme; functionality that should survive a theme switch belongs in a plugin.

What I’d do

This decision table is a bit more technical and reflects how developers will look at the question of whether to use a child theme. Notice it’s not really a binary choice — you have some options between a single (childless) theme and a fully developed child theme that might also involve one or more custom plugins. It’s beyond the scope of this post, but you can also run more than one parent and/or child theme on the same site by using a theme switcher plugin that assigns different themes to different pages and sections of a site.

If this describes your siteWhat I’d use
One site, with design changes made and maintained thereA maintained block theme, the Site Editor, and regular database backups.
A few overrides need to travel between environments or go through reviewA thin child theme in Git for templates, parts, and patterns. Leave Global Styles open in the Site Editor for colours and type.
Several sites need the same design, or you need a formal approval workflowA versioned child or custom theme, a staging site, and reviewed deployments. Put reusable patterns or functionality in a plugin when they need to move independently of the theme.
You’re replacing much of the parent and can own its maintenanceA custom theme or fork, with a named maintainer and a plan for upstream fixes.

A custom parent or a fork never changes under you unless you say so. That’s the appeal and also the catch. You now own every upstream fix you want, and someone has to follow, test, and port them. AI tooling makes that far more feasible than it was a few years ago, especially if you fork a solid, supported parent whose updates you can review and port with an agent’s help. It’s still work, and it doesn’t happen by itself.

Choosing a parent

If you do use a child theme, check the parent for compatibility before you commit to it, and pick it for how it will age, not by how it looks today. Maintainability is the key to longevity.

  • Stable colour slugs. Colour slugs in the WordPress editor serve as abstract ID tags (like “primary” or “secondary”) so we don’t need to hardcode raw hexadecimal RGB colour codes (#345C00) into page markup. If a parent theme renames a slug, blocks that use it lose their colour. The “slug” term comes from the history of hot metal printing; in WordPress, it refers to the unique human-readable text identifier associated with a single content item, taxonomy term, and now design patterns.
  • Pattern slugs you can override. If a child theme registers a pattern with the same slug a parent uses, it overrides and replaces the pattern a template references, which is the easiest way to change a template without copying it. Copies of a pattern already inserted into pages stay as they were.
  • No explicit "theme" attributes on template-part blocks. The attribute pins the template-part lookup to the named theme, which can bypass a child’s override or stop headers and footers from rendering at all. Search the parent’s templates/, parts/, and patterns/ folders for "theme":", then activate a bare child theme and check that the header and footer render.
  • Careful versioning. A changelog, and a habit of not redesigning in place, make updates safe to take.
  • Dependencies. What else is packaged with the theme? Who maintains it? What about upstream dependencies like JavaScript libraries?
  • AI Instructions. Are there included files with instructions for AI agents? How do the theme’s developers want AI tools to work with it?

If your design is already in the database

You can move it into files. The Create Block Theme plugin, from WordPress.org, can save Site Editor changes to the active theme, create a child theme from the active one with your changes included, or export the whole theme as a zip.1 Then work in this order:

  1. Back up the database.
  2. Export the changes and commit them.
  3. Deploy the files to a staging site and reset the matching Site Editor customizations there.
  4. Compare the affected pages.
  5. Only then reset the same customizations on the live site.

The order matters because WordPress prefers the database. A template or template part saved there takes precedence over the theme file with the same name, so until you reset the saved copy, the file you just deployed sits there, correct and ignored.

After that, decide what the database is allowed to hold. A common split is content and small Global Styles tweaks in the database. Templates, template parts (or “partials”), and (block) patterns go in files.

Then check for drift now and then. On Ipsum, the theme’s own design guide for agents reports which templates have been customized. On any site, the Site Editor marks customized templates, and WP-CLI or the REST API can list them.

Where to start

Start with the next change you’ll have to make twice. If you find yourself rebuilding the same header on staging and then again on the live site, that header belongs in a child theme. Decide which edits people can keep making in the Site Editor, and check that your next deployment leaves them alone. Then write it down where the next maintainer will find it. That may well be you, a year from now, wondering why the footer won’t change.

Notes

  1. WordPress.org, Create Block Theme, version 2.10.2, accessed November 14, 2026, https://wordpress.org/plugins/create-block-theme/. ↩︎

How this article was researched & written

This guide distils the decision section of “Three themes, one question.” Claude and I drafted it from that post and from a conversation about maintainability for agencies, enterprises, and simpler use cases. Claude checked up on the Create Block Theme plugin’s current features on WordPress.org, since it’s been a few months since I last used it. After several editorial reviews, we settled on the final decision tables and reworked the advice on choosing a parent and moving designs out of the database.

Last updated:

Leave a Reply

Your email address will not be published. Required fields are marked *