WordPress Child Theme: What It Is, When You Need One and How to Create It (2026)

A clear explanation of WordPress child themes, how they inherit from a parent theme, the situations where they are essential and the many cases where you can safely skip them.

Want a parent theme built for clean customization? See GeneratePress plans.

See GeneratePress Plans

What Is a WordPress Child Theme?

Wooden toy rockets built from simple blocks

A child theme is a theme that borrows everything from another theme, the parent theme, and lets you change only the parts you want. The parent provides the templates, styles and features. The child contains your customizations.

The reason child themes exist is updates. When you edit a theme's files directly, the next update replaces those files and your changes disappear. Put the same changes in a child theme, and the parent can update safely while your edits stay in place.

Some products are built around this idea. The Genesis Framework, for example, was designed to be used with a child theme, and older frameworks such as Thesis used a related concept called skins. Our guide to Thesis skins explains how that approach worked.

How Child Themes Work

When a child theme is active, WordPress looks in the child theme first and falls back to the parent for anything the child does not provide.

File How WordPress Handles It
style.css Required in the child; its header names the parent theme
functions.php Both run: the child's loads first, then the parent's
Template files (header.php, single.php, etc.) A child's file replaces the parent's file of the same name
theme.json (block themes) Child settings are merged over the parent's
Templates and parts (block themes) A child's template replaces the parent's template of the same name
Images and other assets Loaded from wherever the code references them

This means a child theme can be tiny. Many contain just a stylesheet and a functions file, and only add template overrides when needed.

When You Need a Child Theme

Use a child theme when you plan to:

  • Edit template files, such as changing the markup of single posts or archives in a classic theme.
  • Add custom PHP functions that belong to the theme's presentation, such as registering a new menu location or changing how the theme outputs certain elements.
  • Override parts of a block theme with your own templates, template parts or theme.json settings, and keep them in code.
  • Build several sites on the same parent with different customizations, such as for client projects.
  • Keep custom code versioned in a theme you control.

When You Do Not Need a Child Theme

For many sites, a child theme adds work without benefit. You can skip it if you only:

  • Change settings in the Customizer or theme options panel.
  • Design with the Site Editor in a block theme. Changes made in the Site Editor are stored in the database, not in theme files, so they survive theme updates.
  • Use a page builder such as Elementor, Divi or Thrive Architect, which stores designs in the database.
  • Add small CSS changes through Appearance → Customize → Additional CSS or the Site Editor's custom CSS option.
  • Add code snippets that are not specific to the theme. A code snippets plugin, or a small custom plugin, keeps them working even if you change themes later.

Theme Code vs Site Functionality

A useful rule: if the code controls how your site looks, it can live in a child theme. If it controls what your site does, such as custom post types, shortcodes or tracking scripts, put it in a plugin. That way, changing themes in the future will not break your site's features. Our guide to changing your WordPress theme shows why this matters.

Pros and Cons of Child Themes

Pros

  • Your customizations survive parent theme updates.
  • You keep the parent's features, fixes and security updates.
  • Custom code is organized in one place.
  • Easy to roll back: switch to the parent theme to see the original.

Cons

  • Another layer to understand and maintain.
  • Overridden templates can fall out of date when the parent changes significantly.
  • Unnecessary for sites that only use settings or a page builder.

How to Create a Child Theme for a Classic Theme

You can create a child theme manually in a few minutes.

Step 1: Create the Folder

Using SFTP or your host's file manager, create a new folder in /wp-content/themes/. Name it after the parent with "-child" added, for example generatepress-child.

Step 2: Create the Stylesheet

Inside the folder, create a file named style.css with this header:

/*
Theme Name: GeneratePress Child
Template: generatepress
Version: 1.0.0
*/

The Template line is the important part: it must match the parent theme's folder name exactly.

Step 3: Create the Functions File

Create functions.php to load the child's stylesheet. Many modern parent themes already load their own styles, so the child only needs to add its own:

<?php
add_action( 'wp_enqueue_scripts', function() {
    wp_enqueue_style(
        'child-style',
        get_stylesheet_uri(),
        array(),
        wp_get_theme()->get( 'Version' )
    );
}, 20 );

Some older parent themes need you to load the parent stylesheet as well. Check the parent theme's documentation for its recommended child theme setup.

Step 4: Activate the Child Theme

Go to Appearance → Themes. The child theme now appears in the list. Activate it. Your site should look exactly as it did with the parent, because nothing has been changed yet.

Customizer settings are stored per theme, so after switching to the child you may need to copy settings from the parent. Some themes offer an import or export tool for this.

Step 5: Add Your Customizations

  • Add CSS to the child's style.css.
  • Add PHP functions to functions.php.
  • To change a template, copy the file from the parent into the child, keeping the same file name and folder structure, then edit the copy.

How to Create a Child Theme for a Block Theme

Block themes can have child themes too. The structure is similar, with theme.json playing a bigger role.

  1. Create a folder, such as twentytwentyfive-child.
  2. Add style.css with a Theme Name and a Template line naming the parent's folder.
  3. Add a theme.json file to override settings such as colors, fonts and spacing. WordPress merges it with the parent's.
  4. Add templates or parts in templates/ and parts/ folders to replace specific parent templates.
  5. Activate the child theme.

The Create Block Theme plugin from the WordPress.org team can generate a child theme of the active block theme from the dashboard and export changes you made in the Site Editor into theme files.

Easier Options: Ready-Made Child Themes

Many popular themes publish a blank child theme or a child theme generator in their documentation, so you do not have to write the files yourself. Check your theme's documentation for a download, install it as a ZIP under Appearance → Themes → Add New Theme → Upload Theme, then activate it. Our guide on how to install a WordPress theme covers the upload process.

There are also plugins that generate child themes for classic themes. They are handy for a quick start, but once the child theme exists, you can deactivate and remove the generator plugin.

A Real-World Example

Two hands holding matching puzzle pieces against the sky

Imagine you use a lightweight classic theme and want three changes: a custom author box under every post, a different layout for one category's archive and a small tweak to the header markup.

  • The author box could be added with the theme's hooks from a child theme's functions file, or with a hook-based element if your theme offers one, such as GeneratePress Elements. No template needs copying.
  • The category layout may be possible through theme settings or a block template. If not, a single archive template copied into the child theme does the job.
  • The header tweak might need the header template copied into the child theme, which you then keep up to date when the parent changes its header.

Working this way, from settings to hooks to template overrides, keeps the child theme small and easy to maintain.

Child Theme Best Practices

  • Back up before activating a child theme on a live site.
  • Override as few templates as possible. Every copied template is one you must maintain.
  • Prefer hooks and filters over template overrides when the parent theme provides them. Themes such as GeneratePress are built around hooks for this reason; see our GeneratePress review.
  • Comment your code so you remember why each change exists.
  • Keep functionality in plugins, not the child theme.
  • Test after parent updates, especially major versions.
  • Use version control such as Git if you manage several sites.

Common Child Theme Mistakes

  • Misspelling the Template line. It must match the parent theme's folder name exactly, including letter case. If WordPress lists the child theme as broken, check this first.
  • Loading the parent stylesheet twice. Some parents already load their own styles and the child's. Follow the parent's documentation to avoid duplicate requests.
  • Copying every template "just in case." Overridden templates stop receiving the parent's improvements. Copy only what you change.
  • Putting site features in the child theme. If you change themes later, those features disappear. Keep them in a plugin.
  • Editing the parent anyway. Once a child theme exists, all edits belong in the child.
  • Forgetting Customizer settings. Settings are stored per theme, so switching to the child can reset them unless you copy them across.

Child Themes and Premium Themes

Premium themes work with child themes in the same way as free ones. The parent theme still needs an active license to receive updates, and the license is tied to the parent, not the child. Some premium vendors also provide official child themes or starter child themes that set things up correctly for their product, including the right way to load styles.

If you use a premium theme that relies on a separate premium plugin, such as GeneratePress Premium or Astra Pro, keep in mind that the plugin's features are independent of the child theme. You can activate a child theme without affecting those modules.

Troubleshooting a Child Theme

Symptom Likely Cause Fix
Child theme listed as broken Template line does not match parent folder Correct the folder name in style.css
Site looks unstyled Parent styles not loading Follow the parent's recommended enqueue code
Changes to style.css not showing Caching Bump the Version number and clear caches
Template edits ignored File name or folder path differs from parent Mirror the parent's exact path and name
Customizer settings lost Settings stored per theme Copy or re-enter settings for the child

Child Theme vs Other Customization Methods

Method Survives Theme Updates Survives Theme Change Best For
Editing parent theme files No No Never recommended
Child theme Yes No Template and presentation changes
Additional CSS Yes No (tied to theme) Small style tweaks
Site Editor changes Yes Partly Block theme design changes
Code snippets plugin Yes Yes Small functional changes
Custom plugin Yes Yes Site functionality
Page builder Yes Yes, if builder stays Visual page design

Final Thoughts

A child theme is the safe way to change a theme's code, because your edits live separately from the parent and survive its updates. But it is not mandatory. If you only use settings, the Site Editor, a page builder or a few lines of CSS, you can skip it and keep things simpler.

When you do need one, keep it lean: a stylesheet, a functions file and only the templates you truly need to change. For more on theme structure, read block themes vs classic themes or browse all our WordPress guides.

Frequently Asked Questions

What Is a Child Theme in WordPress?

A child theme is a small theme that inherits the design and functionality of another theme, called the parent. You put your customizations in the child theme, so they are not lost when the parent theme updates.

Do I Need a Child Theme?

Only if you plan to edit theme files, such as templates or functions.php, or add significant custom code. If you only use theme settings, the Customizer, the Site Editor, Additional CSS or a page builder, you usually do not need one.

Does a Child Theme Slow Down My Site?

Not meaningfully. A child theme usually adds one small stylesheet and a few lines of code. Poorly written custom code inside it can slow a site, but the child theme structure itself has a negligible effect.

Can I Create a Child Theme Without Coding?

Yes. Many popular themes provide a ready-made blank child theme to download, and plugins such as Create Block Theme can generate a child theme of a block theme from the dashboard.

What Happens If I Update the Parent Theme?

The parent theme updates normally and your child theme files stay untouched. Your customizations remain, although a major parent update can occasionally require adjustments to overridden templates.

Can a Child Theme Have Its Own Child Theme?

No. WordPress supports one level of inheritance: a child theme and its parent. A child theme cannot be the parent of another child theme.

Want a Parent Theme Built for Clean Customization? See GeneratePress Plans

Check the current plans, site limits and refund terms on the official GeneratePress website.

See GeneratePress Plans