What Is a WordPress Child Theme?
A WordPress child theme is a separate theme that inherits the design and functionality of another theme, called the parent, while letting you safely override or add to it. You put your custom styles, template changes, and functions in the child theme, so when the parent theme releases an update, your work is untouched. Without a child theme, editing the parent directly means a single update can wipe out every change you made.
- What it is
- A theme that inherits from a parent theme and holds your customizations
- Minimum files
- A style.css header naming the parent, plus functions.php
- Main benefit
- Customizations survive parent-theme updates (WordPress Theme Handbook)
- Requirement
- The parent theme must be installed for the child to work (WordPress.org)
- Best for
- Any site customizing a third-party premium or marketplace theme
What a child theme is #
A WordPress child theme is a lightweight theme that sits on top of an existing theme, borrowing everything the parent provides and letting you change only the pieces you want. WordPress loads the parent for the bulk of the design, then checks the child for any file or style that should override it. This inheritance is what makes child themes valuable: you get a full, tested theme underneath your customizations, and a clean, separate layer for your own work. A minimal child theme is just two files in its own folder inside wp-content/themes: a style.css header that names the parent, and a functions.php that loads the stylesheets. From there you can copy any parent template, tweak it, and WordPress serves your version instead. Agencies building on WordPress almost always use a child theme so client customizations survive updates. If you run a business site, our /services/wordpress-development team treats the child theme as the standard foundation rather than editing purchased themes directly.
Why parent updates destroy direct edits #
The core reason child themes exist is theme updates. Premium and free themes ship regular releases to patch security holes, fix bugs, and add features. When you install an update, WordPress overwrites the theme's files with the new versions. If you edited the parent theme directly, changing its CSS, a template, or functions.php, every one of those changes is erased the moment you click update. Owners often discover this the hard way: a site that looked perfect suddenly reverts to the stock design after a routine update. The unhappy workaround is to stop updating, which leaves known vulnerabilities in place and is a common reason sites need a /services/website-rescue. A child theme breaks this trap. Because your changes live in a separate folder the parent update never touches, you can keep the parent current for security while preserving all your customizations. You get both safety and stability instead of being forced to choose one. That single benefit justifies the small setup effort many times over.
How inheritance actually works #
Inheritance in a child theme follows WordPress's template hierarchy. When a page loads, WordPress looks in the child theme folder first for a matching template file, then falls back to the parent if it finds none. So if you copy the parent's single.php into the child and edit it, WordPress uses your version; every other template still comes from the parent. Stylesheets work similarly but stack: the parent's CSS loads, then the child's, so your rules can override the parent's because they load later. Functions are different, functions.php files do not replace each other, they both run, letting you add new PHP without copying the whole file. The child theme declares its parent through a Template line in style.css, which tells WordPress which theme to inherit from. Getting the enqueue order right matters for speed, and a poorly wired child theme can double-load stylesheets, worth checking during any /services/speed-optimization review. Understanding this lookup order helps you customize surgically rather than duplicating the entire theme.
Building a minimal child theme #
A working child theme needs just two files in a new folder under wp-content/themes. The style.css header names the parent via its folder slug, and functions.php enqueues the parent stylesheet so styles load in the right order.
/* style.css */
/*
Theme Name: Storefront Child
Template: storefront
*/
// functions.php
add_action( 'wp_enqueue_scripts', function() {
wp_enqueue_style( 'parent-style', get_template_directory_uri() . '/style.css' );
} );What belongs in a child theme #
A child theme is the right home for anything that customizes how a specific theme looks or behaves. Custom CSS overrides go in the child's style.css. Template changes, like a modified header, footer, or product page, belong there as copied-and-edited template files. Theme-specific PHP tweaks, such as adjusting excerpt length or registering a menu, go in the child's functions.php. What should not live in a child theme is functionality you want to keep regardless of design. If you switch themes later, the child theme is discarded along with the parent, so anything you would miss, like tracking scripts, shortcodes, or custom post types, belongs in a plugin instead. A simple rule: presentation goes in the theme, features go in a plugin. Keeping that boundary clean makes future redesigns far less painful, since a /services/website-redesign can swap the visual layer without dragging along business logic that was accidentally buried in theme files. This discipline pays off every time the site evolves.
Child theme versus plugin versus snippet #
Three tools can hold WordPress customizations, and choosing well saves headaches. A child theme is for design and template changes tied to one parent theme. A plugin is for features that should persist across theme changes, like a contact form handler, custom fields, or analytics injection. A code-snippets plugin or must-use plugin can hold small standalone functions without a full plugin structure. The mistake owners make is dumping everything into functions.php because it is convenient. That works until you change themes and lose a critical feature, or a single PHP error in that file takes down the whole site. Separating concerns is more robust: the child theme handles appearance, plugins handle capability, and each can be updated or removed independently. For anything you rely on for revenue, such as booking or e-commerce logic on an /services/ecommerce-development build, keep it in a plugin so it survives every future theme decision. This structure is standard practice on professionally maintained sites everywhere.
Common mistakes and performance pitfalls #
Child themes are simple, but a few mistakes recur. The most frequent is enqueuing stylesheets incorrectly, which can load the parent CSS twice and slow the page. Modern practice is to enqueue only what you need and let the parent's own enqueue logic run, rather than blindly using the old @import method, which blocks rendering. Another mistake is copying far more parent templates than necessary; each copied file must be manually re-synced if the parent changes that template later, so copy only what you actually edit. Some owners also forget the Template line in style.css must exactly match the parent folder name, or WordPress refuses to activate the child. Finally, watch total page weight: a child theme layered over a heavy multipurpose parent inherits all that bloat, so the child does not fix an inherently slow theme. If speed is the goal, a /services/speed-optimization audit or a lighter parent theme matters far more than the child layer itself does.
When you actually need one #
You need a child theme whenever you plan to customize a third-party theme you did not build and want to keep updating. That covers most small-business WordPress sites using a premium or marketplace theme. You do not strictly need a child theme in a few cases: if you are using a theme with a built-in custom CSS box and only changing colors, the theme's own settings may persist through updates safely. If a developer built you a fully custom theme from scratch, that theme is yours and has no upstream parent to overwrite it, so a child theme adds nothing. And builder-driven sites that store most design in the database rather than template files rely less on child themes for layout, though a small child theme is still useful for custom functions. When in doubt, a quick /free-website-audit can tell you how your current site is structured and whether a child theme is actively protecting your work. Knowing which category applies prevents the costly mistake of editing a parent theme with nothing shielding your changes.
What we recommend #
Our recommendation is straightforward: if your site runs a third-party WordPress theme and you have any custom CSS or template edits, those changes should live in a child theme, full stop. It is a small, one-time setup that prevents the painful and expensive scenario of an update wiping your work. If you inherited a site where edits were made directly to a parent theme, migrating them into a child theme is a worthwhile hardening step, often bundled into a /services/care-plans engagement so updates can resume safely. Keep the child theme lean, document what you changed and why, and push anything that is really a feature into a plugin. Done this way, your WordPress site stays both current and stable: you apply security updates the day they ship without fear, and your brand's look holds steady underneath. That balance of safety and control is exactly what a child theme is designed to deliver for a growing business, and it is why we set one up before making any customization to a purchased theme.
FAQ
Do I really need a child theme for small changes?
For a line or two of CSS, your theme's built-in Additional CSS box in the Customizer is often enough and survives updates. But once you edit template files or add PHP, a child theme is the safe home. It costs little to set up and prevents a theme update from erasing your work later.
Will a child theme slow down my website?
Not meaningfully if built correctly. A child theme adds one small stylesheet on top of the parent. Slowness comes from the parent theme's weight or double-loaded CSS, not the child layer itself. Enqueue stylesheets properly and the performance difference is negligible; a heavy parent theme is the real speed concern to address.
What happens to my child theme if I switch themes?
It is discarded along with its parent, because a child theme only works paired with the specific parent it names. Any design or template changes go with it. This is why features you want to keep, like tracking or custom post types, should live in a plugin instead of the child theme.
Can I create a child theme without coding?
Partly. Plugins can generate a basic child theme for you in a few clicks, handling the style.css and functions.php setup. Editing templates afterward still requires some HTML, CSS, or PHP knowledge. For anything beyond simple style overrides, having a developer or a care plan handle the child theme is the safer route.
Does a child theme get its own updates?
No. You maintain the child theme yourself; it has no update button. The parent theme, however, updates normally, and that is the whole point: you can keep the parent current for security while your child theme preserves customizations untouched by those updates over the life of the site.
Is a child theme the same as a page builder?
No. A child theme is a code-level layer that overrides a parent theme's files and styles. A page builder like Elementor or Divi is a visual drag-and-drop tool that stores layouts in the database. They can coexist, but they solve different problems: one protects code edits, the other lets you design without code.
How Local Web Advisor checks this for you
Is your own website getting web dev right?
Our free AI audit scans your site and tells you — in plain English — exactly what to fix for web dev and seven other areas, with the business impact and the fix for each. No login needed to start.
Run my free website audit →Was this helpful?