You tweaked the theme's files until the site looked perfect, then clicked Update and watched every customization evaporate. The classic WordPress heartbreak, with a permanent cure: child themes.
A child theme layers your changes over the parent theme safely. Here's the twenty-minute setup, by plugin or by hand, and the rules of what goes where.
What trips people up
- Editing the parent anyway because 'just this once': the heartbreak file, page one, same story, child exists on purpose.
- Copying entire template files to change three lines: copied templates miss parent improvements, prefer hooks and targeted overrides where the parent offers them.
Doing it properly
- Understand the two-file minimum. A child theme needs just style.css (containing a header that names its parent) and functions.php (which loads the parent's stylesheet correctly). WordPress does everything else: your child's files override or extend the parent automatically, updates hitting only the parent.
- The painless route: use a generator plugin. Child-theme generator plugins (search the plugin directory for current well-reviewed options) build the folder in clicks: pick the parent, name the child, done. For most site owners this is the entire tutorial, skip to the rules at step five.
- The manual route, for understanding. Create wp-content/themes/yourtheme-child with style.css whose header block includes Theme Name and Template: parent-folder-name exactly; add functions.php with the standard wp_enqueue_style snippet for the parent style (copyable from any current official docs). Activate under Appearance, Themes like any theme.
- Verify the switch cleanly. The site should look identical after activating the child: menus, widgets and customizer settings usually inherit, though menus and widget placements occasionally need re-assignment. Screenshot before, compare after, re-place whatever wandered.
- Learn the overriding rules. CSS customizations go in the child's style.css (or the Customizer's Additional CSS for tiny tweaks); template changes copy the parent template file into the child and edit the copy; functions extend through the child's functions.php. Each follows one idea: parent stays pristine, child carries the signature.
- Adopt the update ritual. Parent updates now arrive fearlessly: click update, glance at the site, move on. Confirm by checking your customizations survived annually, the child's whole purpose is that they do.
Tips that actually help
- Customizer exports: tools exist to export customizer settings between themes, worth an export before structural surgery.
- Theme.json in modern block themes: child-theming block themes follows parallel logic through its own JSON overrides in current WordPress versions.
- Staging sites (one-click from most hosts) let theme experiments fail safely before production ever sees them.
Quick answers
Do page builders remove the need?
Builder-stored design largely lives in the database and survives updates, but CSS additions and template overrides still want a child's home, the habits complement each other.
Will a child theme slow the site?
No measurable difference: one extra stylesheet enqueued, and performance concerns belong to plugin stacks, not children.
Keep reading
- How to Use Public Transit in a New City With Confidence
- How to Remove Candle Wax From Fabric and Hard Surfaces
- How to Prepare Your Dog for a Calm Car Ride Without Stress
The short version
Twenty minutes of setup, and the Update button changes personalities: from villain with a grudge to boring monthly hygiene.
