Explainers · Explainer
What Is a Child Theme? A Plain Explanation

Short answer
A child theme is a small theme that borrows everything from a parent theme and holds only the changes you make. One line in its style.css file, the Template field, names the parent folder. Parent updates replace the parent folder but never touch the child, so your changes survive.
Key takeaways
- A child theme holds only your changes and borrows everything else from its parent.
- Parent theme updates replace the whole parent folder, so direct edits to it are lost.
- The Template field in style.css must match the parent folder name exactly.
- A child theme needs only one file: style.css with a Theme Name and Template field.
- The child functions.php loads before the parent one, and both files run.
- There are only two theme levels, parent and child; no grandchild theme exists.
What is a child theme?
A child theme is a small theme that borrows everything from another theme, called the parent, and holds only the changes you make.
The Theme Developer Handbook defines it in one line: child themes are extensions of a parent theme, and they let you modify an existing theme without directly editing that theme's code. The parent stays complete and untouched, while the child holds your overrides.
That split is the whole point. A parent theme gets updates from its author, and every update replaces the whole theme folder. If you edited the parent files directly, those edits would vanish with the next update.
A child theme keeps your work in a separate folder that updates never touch.
Learn WordPress makes the same point with a plain example: a child theme lets you extend or modify any part of the parent theme without making any changes to the parent theme code. You can change a color, a template, or a function, and the parent keeps working as before.
How does a child theme work?
A child theme works because WordPress looks in the child theme first for every file, and falls back to the parent when the child has no copy.
One line in the child's style.css file makes the link: the Template field names the parent theme's folder.
The handbook states that this field must be a 100% match of the folder name of the parent theme, relative to the wp-content/themes folder. For Twenty Twenty-Four, the folder is twentytwentyfour, so the line reads Template: twentytwentyfour.
When you activate the child theme, the site looks exactly the same as before. Learn WordPress notes that this is expected, because all the theme elements are inherited from the parent theme. Your changes appear only when you add files to the child.
There is one more layer above the child. The handbook lists the style layers for block themes as WordPress itself, the parent theme, the child theme, and then user customizations, which can override theme.json, templates, and patterns.
Those user changes are stored in the database, not in files, which is why the handbook calls them a “grandchild” of sorts. There is no standard installable grandchild theme: only 2 levels exist, parent and child.
What files does a child theme need?
A child theme needs only 1 file to exist: a style.css file with a theme header that names the parent.
The handbook states that style.css is the one absolutely necessary file for a child theme to exist. Its header must carry at least a Theme Name and the Template field.
WordPress reads the first 8 kilobytes of style.css to find that header, according to the handbook page on the main stylesheet, and Theme Name is the only field required for WordPress to recognize any theme.
| File | What it does | Needed? |
|---|---|---|
style.css | Names the theme and the parent with the Template field | Yes, always |
functions.php | Loads stylesheets and adds custom functions | Often, for classic parents |
theme.json | Overrides parent colors, fonts, and layout | For block parents |
| Template files | Replace parent templates with the same name | Only for files you change |
screenshot.png | Shows a preview image on the Themes screen | No, but helpful |
For a classic parent theme, you usually add functions.php as well. The child's functions.php loads before the parent's, and both files run, so the child file adds to the parent rather than replacing it. For a block parent, styles mostly come from theme.json, so the stylesheet step is often not needed at all.
Themes submitted to the WordPress.org directory use the GPL license, and the handbook example header lists the GNU General Public License version 2 as the license. A private child theme on your own site does not need that field, but the license line is required if you ever submit a theme.
How do you create a child theme?
You create a child theme by making a folder, adding a style.css header that names the parent, and activating the child under “Appearance” then “Themes”.
The manual route has 4 steps. First, create a folder inside wp-content/themes, using a kebab-case name such as grand-sunrise for a child of Twenty Twenty-Four. Second, create style.css in that folder with a header like this, written as plain text:
/*
* Theme Name: Grand Sunrise
* Template: twentytwentyfour
*/
Third, if the parent does not load the child stylesheet, add a functions.php file that loads it with wp_enqueue_style() on the wp_enqueue_scripts hook.
The handbook notes that Twenty Twenty-Four loads no stylesheet at all, so a child of it needs that step. Fourth, go to “Appearance” then “Themes” in the admin area and click “Activate” on the child theme.
The plugin route is faster for block themes. Install and activate the Create Block Theme plugin, make your changes in the Site Editor, open the plugin menu at the top of the editor, and pick “Create Theme” then “Create Child Theme”.
The plugin writes the child folder with your changes included. Its current version is 2.10.2 as of November 2026, and it needs WordPress 6.8 or newer.
What can you change with a child theme?
You can change almost any part of the parent theme: templates, template parts, patterns, styles, and functions.
To replace a template, copy the parent's file into the child at the same relative path and edit the copy. The handbook states that a file you add to the child theme with the same name as a parent file overwrites the parent's version, and patterns must also share the same registered slug.
To add something new, such as an extra template or pattern, just add the file: the child can hold files the parent never had.
Functions work differently. The child's functions.php does not replace the parent's file. Both load, with the child first, so you can add new functions or replace pluggable ones.
The handbook warns against copying code directly from the parent's functions.php into the child, because duplicate function names will cause fatal errors.
For paths and URLs, use the child-aware functions. get_theme_file_path() finds a file in the child first, while get_parent_theme_file_uri() points at the parent folder. Mixing them up is a common source of missing styles.
Our guide on how to add theme support in WordPress shows the kind of small feature you would add through a child theme's functions.php.
How is a child theme different from editing the parent directly?
Editing the parent directly is faster once, and a child theme is safer every time after that, because updates wipe direct edits and leave child edits alone.
A theme update replaces the entire theme folder with the new version. The Learn WordPress lesson states this plainly: during a theme update, the entire theme is replaced with the updated version, so any changes you make to specific files will be lost. That single fact is the reason child themes exist.
The child theme also keeps your work portable. The handbook lists the benefits as making changes portable and replicable, keeping customizations separate from the parent, allowing parent updates without losing changes, and saving development time since you only write the code you need.
You can copy the child folder to another site that runs the same parent and get the same changes.
There is a limit, though. The handbook notes that very large customizations can become a management headache, and for those projects it is often better to fork the original theme and build a full parent theme of your own. A child theme fits small and medium changes, not a full rebuild.
How do you check if your child theme works?
Activate the child theme and confirm the site looks the same as it did with the parent, then make one small change and check that it appears.
Start at “Appearance” then “Themes” and activate the child. The front end should look unchanged, since the child inherits everything. If the site looks broken or unstyled, the Template field is the first thing to check: it must match the parent folder name exactly, including case.
Then add one visible change, such as a new CSS rule in the child's style.css or a small text change in a copied template.
Load the front end as a logged-out visitor and confirm the change shows. If it does not, check whether the parent loads the child stylesheet, and add the enqueue step in functions.php if it does not.
Also check the parent theme's update status. Our guide on how to check if a WordPress theme is safe covers what to look for before you build on any parent.
Our guide on fixing a theme that broke a site after an update covers recovery if an update goes wrong.
What mistakes should you avoid with child themes?
Do not copy the parent theme's whole stylesheet or whole functions.php file into the child, because that creates duplicates and errors.
Copy only the rules and functions you change. The handbook warns that copying parent functions.php code directly will likely lead to fatal errors from duplicate function names. The same idea applies to CSS: add only your overrides, and let the parent supply the rest.
Do not use CSS @import to load the parent stylesheet. That old method makes the browser download stylesheets one after another and slows the page. The handbook teaches enqueueing with wp_enqueue_style() instead, which loads both sheets in the right order.
Do not build a child theme for changes the Customizer or Site Editor already handle. Small color or font changes belong in the Site Editor styles panel, where they are stored in the database and survive updates without any files.
Reserve the child theme for template changes, PHP functions, and theme.json overrides that the editor cannot do.
Our guide on themes vs plugins in WordPress helps you decide whether a change belongs in a child theme at all.
Our guide on free vs premium WordPress themes helps you pick a parent worth building on.
Frequently asked questions
Do I need a child theme for small color changes?
No, and you should not. The Customizer and the Site Editor handle small color, font, and layout changes, and those changes survive updates on their own. Build a child theme only when you need to change template files, add PHP functions, or override theme.json.
Do I need to keep the parent theme installed?
Yes. The child theme only works when the parent theme is installed, because it borrows everything it does not override. If you delete the parent, the child has nothing to borrow and WordPress will mark it as broken.
Can I make a child theme of a child theme?
It will not be a grandchild. WordPress supports only two levels, parent and child. Your Site Editor changes sit in a layer above the child and are stored in the database, but they are not an installable theme you can copy to another site.
My child theme shows as broken. What went wrong?
The Template field in the child style.css file must match the parent folder name exactly, including case. A mismatch is the most common cause. Also check that the parent theme is installed and that the child stylesheet is loaded through functions.php when the parent needs it.
Can I use a child theme for a large redesign?
Yes, but only when you keep your changes small. Copy only the files you change, add only the CSS rules you need, and never copy the parent functions.php file. Large rebuilds belong in a full parent theme of your own, not in a child.
Sources
- Child Themes WordPress Developer Resources
- Child themes Learn WordPress
- Main Stylesheet (style.css) WordPress Developer Resources
- Create Block Theme WordPress.org
- Version 7.1.5 WordPress.org
- GNU General Public License, version 2 GNU Project
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


