WordPress Development

Child Themes vs Custom Themes: Choosing the Right Foundation for Your WordPress Site

Child Themes vs Custom Themes: Choosing the Right Foundation for Your WordPress Site

One of the first things I check on an inherited WordPress site is whether anyone edited the theme files directly. It happens more often than you’d think. Someone wanted a different footer, opened the theme editor or an FTP client, changed a few lines, and everything looked great. Then the theme updated, and every change vanished overnight.

The fix for that particular problem is well known: use a child theme. But it raises a bigger question I discuss with clients all the time. Should you customise an existing theme at all, or should you build a custom theme designed for your business from the ground up?

There’s no universal answer. It depends on your budget, how unique the design needs to be, how long you plan to keep the site and who will maintain it. Let’s go through both options properly.

How WordPress themes are structured

A theme controls how your site looks: templates, styles, layout and often some functionality. WordPress supports two kinds of themes today.

Classic themes use PHP template files such as header.php, single.php and footer.php. Customisation happens through the Customizer, widgets and code.

Block themes are built from HTML templates made of blocks, with design settings in a theme.json file. Everything, including headers and footers, can be edited visually in the Site Editor.

Both kinds support child themes, though they work a little differently.

What a child theme is

A child theme is a theme that inherits everything from another theme, called the parent, and only overrides what you change. When WordPress looks for a template file, it checks the child theme first, then falls back to the parent.

That means you can update the parent theme to get bug fixes and security patches without losing your customisations, because your changes live in a separate folder.

Creating a child theme for a classic theme

You need just two files. First, a style.css with a header that names the parent:

The Template value must exactly match the parent theme’s folder name, not its display name. This trips people up all the time.

Second, a functions.php that loads the parent styles:

Some parent themes already load their own stylesheet in a way that works with children, so check the parent’s documentation. Loading styles twice won’t break anything, but it wastes a request.

Now activate the child theme. To change a template, copy it from the parent into the child and edit the copy. To add functionality, use the child’s functions.php. Unlike template files, the child’s functions.php doesn’t replace the parent’s. Both run, with the child’s loading first.

Child themes for block themes

Block themes make child themes even simpler. Your child theme can include its own theme.json, and WordPress merges it with the parent’s. You can change colours, fonts and spacing without touching a single template.

Templates and template parts placed in the child’s templates and parts folders override the parent’s versions. There’s also a catch to understand: changes made in the Site Editor are saved to the database, not to theme files. That’s convenient for clients, but it means customisations can live in two places. When I build for clients, I export finished Site Editor changes back into the theme files so the code remains the source of truth.

The limits of child themes

Child themes are great for small to moderate changes. They become a burden when you override so much that the parent is barely recognisable.

Problems I see in heavily modified child themes:

  • Outdated template copies. You copy a template, edit it, and two years later the parent has improved that template ten times. Your copy has none of those fixes, including security improvements.
  • Fighting the parent’s CSS. Huge stylesheets full of overrides, with !important everywhere, trying to undo the parent’s design.
  • Performance overhead. You load all the parent’s features, scripts and styles, then add your own on top.
  • Dependence on the parent’s roadmap. If the parent theme changes direction, gets abandoned or removes a feature, your site is affected.

If your child theme overrides most templates and hundreds of lines of CSS, you’re effectively maintaining a custom theme with extra complications.

When a child theme is the right choice

  • You found a well-made theme that fits about eighty percent of your needs.
  • The changes are mostly visual: colours, fonts, a few layout tweaks, a custom template or two.
  • Budget or timeline is tight.
  • The parent theme is actively maintained by a reputable developer.

When a custom theme is worth it

A custom theme is built specifically for your site. Nothing is inherited, so nothing is wasted.

The design is genuinely unique

If your brand needs a distinctive design that doesn’t resemble any theme on the market, starting from scratch is often faster than bending a general-purpose theme into shape.

Performance matters a lot

Multipurpose themes include code for dozens of layouts and features you’ll never use. A custom theme only contains what your site needs. On sites where speed directly affects revenue, that difference is measurable.

Long-term ownership

With a custom theme, you aren’t dependent on a theme vendor’s updates or business decisions. The code is yours, documented and maintained on your schedule.

Controlled editing experience

A custom block theme lets you design exactly which blocks, patterns, colours and font sizes editors can use. That prevents the slow drift where every page ends up with a different shade of blue.

The trade-offs of going custom

Custom themes cost more upfront and need a capable developer to maintain. You’re responsible for accessibility, browser testing, responsive behaviour and keeping up with WordPress changes. A poorly built custom theme can be worse than a good commercial one. If you go custom, choose a developer who follows WordPress coding standards and documents their work.

A middle path: starter themes and block theme foundations

Many developers, including me, often start from a minimal foundation rather than a blank folder. A lean block theme with a sensible theme.json, a small set of patterns and clean templates gives you a fast start without the bloat of a multipurpose theme. You get the benefits of a custom theme while skipping the repetitive setup.

Where to put functionality

One principle applies regardless of which path you choose: themes should handle presentation, plugins should handle functionality. Custom post types, shortcodes that store content, integrations with outside services and business logic belong in a plugin. If they live in a theme, they disappear the moment the theme changes. I’ve seen sites lose access to hundreds of portfolio items during a redesign for exactly this reason.

Making the decision

I usually guide clients with a few questions:

  1. How closely does an existing theme match the design you want?
  2. How long do you plan to keep this site before a major redesign?
  3. Is site speed critical to your business?
  4. Who will maintain the theme in two years?
  5. What’s the realistic budget, including ongoing maintenance?

A small business with a modest budget and a theme that’s close to right should use a child theme. A growing company that plans to keep the site for years and cares about speed and brand consistency is usually better served by a custom theme.

Don’t forget accessibility and documentation

Whichever route you take, two things are easy to overlook. First, accessibility: a commercial theme may have been tested for keyboard navigation and screen readers, and your overrides can quietly break that. A custom theme needs accessibility built in from the start. Second, documentation: write down which templates were changed, why, and any custom functions added. The next developer, or you in two years, will be grateful.

Frequently asked questions

Will a child theme slow down my site?

Barely. Loading an extra stylesheet adds a tiny amount of work. The real performance cost comes from the parent theme itself, so choose a lightweight, well-coded parent.

Can I switch from a child theme to a custom theme later?

Yes. Your content lives in the database and isn’t tied to the theme. The work is in rebuilding templates and moving any functionality that was stored in the theme into a plugin. Check for shortcodes and widgets that depend on the old theme.

Do I need a child theme if I only use the Customizer or Site Editor?

Not strictly. Settings saved through these tools are stored in the database and survive updates. But as soon as you add custom code, CSS beyond small tweaks or template changes, a child theme is the safe place for them.

Is it safe to edit theme files through the dashboard?

I recommend disabling the built-in file editor entirely. It’s risky for mistakes, since a single typo can take a site down, and it’s a common tool for attackers after a password is stolen. Edit code locally and deploy it properly.

Conclusion

Child themes protect your customisations and are the right answer for moderate changes on top of a quality theme. Custom themes give you speed, uniqueness and full ownership when your site needs more than adjustments. Whichever you choose, never edit a parent theme directly, keep functionality in plugins and think about who will be maintaining the code a few years from now.