What is a Parent Theme in WordPress?

In WordPress, every theme that isn’t a child theme is technically a parent theme. A parent theme is a complete theme: it contains every file WordPress requires, and it installs, activates, and runs on its own. It becomes a “parent” only when another theme declares it as its template, and nothing in its own code has to change for that to happen.

The split exists for update safety. Edit a theme’s files directly and the next update overwrites your work, but skipping updates isn’t an option either: outdated themes can lead to WordPress vulnerabilities. A child theme keeps your changes in its own files, so a parent update never overwrites them. It can still break them in a subtler way, which we cover below.

What a parent theme supplies

A parent theme supplies the templates, the stylesheet, and the functions; in block themes, it also supplies the theme.json defaults. A child theme inherits all of it by default and overrides only the files it replaces. How each file loads is covered on our child theme page, so we won’t repeat the mechanics here.

A child theme is the safest way to customize a parent theme’s code, but you don’t always need one. If the change fits in the Site Editor (for block themes) or the Customizer’s Additional CSS box, WordPress stores it in the database rather than in theme files, so it survives theme updates on its own.

Example: a child of Twenty Twenty-Four

The WordPress Theme Handbook’s walkthrough makes a child of Twenty Twenty-Four, a default theme bundled with WordPress. One line in the child’s style.css header creates the relationship: Template: twentytwentyfour. The value must match the parent’s folder name in wp-content/themes exactly, or WordPress can’t find the parent. Activate the child and the site works and looks just like its parent until you start overriding files. For the exact code, follow our guide, How to Create a WordPress Child Theme.

Choosing a parent theme

The parent can be any complete, installable theme. A child theme can’t serve as a parent, though: WordPress supports only two levels, parent and child. Beyond that rule, choose carefully, because you’re adopting the parent’s code quality and its update schedule. A good parent theme is:

• Actively maintained. Check the last-updated date on its WordPress.org directory listing before you commit.
• Well documented. You’ll read the parent’s templates and hooks every time you override one.
• Built to be extended. A theme framework is a parent theme designed specifically for child-theme customization.

For the full checklist, see WordPress Themes: How to Choose the Right One.

Update risks and abandoned parents

A parent update never overwrites your child theme’s files, but it can restructure the very templates, styles, or hooks those files override. When that happens, your overrides stop matching, and parts of the site fall back to the parent’s new defaults with no error to warn you. After each parent update, skim the parent’s changelog and check the site on a staging copy before pushing it live.

The opposite risk is a parent that stops receiving updates, and with them security fixes. If the parent is abandoned, or your customizations have grown extensive, do what the Theme Handbook recommends for heavily customized child themes: fork the parent into a standalone theme of your own and maintain it yourself.