Child Themes: Why You Need One So Updates Don't Wipe Your Changes

You opened the theme editor in WordPress, changed a color, added a few lines to functions.php, or tweaked a file until it looked exactly right. It worked. Then, a few weeks later, WordPress told you a new theme version was available, you clicked "Update," and your changes simply vanished.

You didn't do anything wrong as a person. You did something wrong as a method. When you edit a theme's files directly, any theme update overwrites those files with the official version, and your work is gone. The clean fix, used by developers for years, is called a child theme. In this article I'll explain what it is, why it protects you, and how to set one up.

Why your changes disappear on update

A WordPress theme is a folder of files: styles (CSS), templates (PHP), functions. When you edit those files directly, you're changing the very copy installed on your site.

The problem is that a theme update doesn't "keep" your changes. It downloads the new version from the theme's author and completely replaces the old folder. Everything you wrote in there is lost, because WordPress has no way of knowing which lines are the original ones and which are yours.

So it's not a question of "if" but "when." Sooner or later an update arrives — for security, for compatibility — and if you edited the theme directly, you pay for it with your own work.

What a child theme actually is

A child theme is a separate, small theme that "inherits" everything from the original theme (called the parent theme). In effect, you tell WordPress: use the parent theme for everything, but wherever I've written something different, listen to me.

The advantage is clear:

• The parent theme can update freely, without touching your files.
• Your changes live in a separate folder that the update never touches.
• You can deactivate the child theme any time and return to the original, with no damage.

Think of a child theme as a transparent sheet laid over a drawing: the drawing underneath stays intact, you only draw on the sheet, and if you want it gone, you just lift it off.

What a child theme looks like, briefly

A child theme needs its own folder and at minimum two things: a style.css file with a special header and a functions.php file that loads the parent's styles.

In style.css, the header tells WordPress who the parent is:

• Template: the exact folder name of the parent theme
• Theme Name: the name of the child theme

In functions.php you put the code that correctly loads the parent theme's style, then yours. From there on, any file from the parent theme you want to modify, you copy into the child theme and edit it there — WordPress will use yours instead of the original.

It's not much code. The tricky part is respecting the exact names and structure, otherwise the site throws errors. That's why it's worth doing carefully, once, correctly.

When you actually need a child theme (and when you don't)

Not every change requires a child theme. It's important to know the difference so you don't complicate things for nothing.

You don't need a child theme if:

• You change colors, fonts, logo, or layout in the Customizer / visual editor. Those settings are saved in the database, not in files, and survive updates.
• You add CSS in the "Additional CSS" field in the Customizer.

You do need a child theme if:

• You edit the theme's PHP files (functions.php, page templates, header, footer).
• You add custom code that must survive updates.
• You change a page's structure beyond what the editor allows.

The simple rule: if you're touching code in the theme's files, you need a child theme. If you're only using the interface settings, you don't.

How we approach it at MPO Web Studio

On the sites we build, we separate what belongs to the "platform" from what belongs to "your business" from the start. Customizations go into their own layer, exactly like the child theme idea, so security updates can happen without any fear of losing work.

We deliver remotely, anywhere in the country, and we show you a pre-built demo first — you see the result before you pay anything. And when we take over an existing site that's been edited directly "live," the first thing we do is move the changes to safety, so they no longer get lost on the next update.

If you already have a site where you're afraid to press "Update," message us on WhatsApp. We'll look at where things stand together, no obligation.