Skip to main content

Walkthrough · Intermediate · 20 minutes

How to Create a WordPress Child Theme

Customise a theme so the next update rolls through without erasing your work — a hands-on walkthrough in plain words that names the classic mistake before you reach it.

The short answer

The job: customise a theme so the next update rolls through without erasing your work. Time to set aside: 20 minutes. Skill needed: intermediate.

Below is the full run of steps, the error most people trip over, and the short cut worth remembering. On Hosting & Domains plans several steps are already automated away — the guide marks each one.

By the Hosting & Domains team · Reviewed 18 August 2026

Intermediate

Skill rating

20 minutes

Time budget

5

Steps in total

24/7

Support on call

No prior knowledge assumed — a hosting account, a browser and 20 minutes of attention is the whole entry requirement. Every instruction runs on our platform exactly as printed, and carries over to any standard cPanel host.

First rule: read the snag section before you start, not afterwards. It was distilled from the tickets of everyone who tried the other order.

How the work divides up

The work falls into a few clean stages: grasp the problem it solves, create the folder and stylesheet, load the parent's styles, switch over and compare and override deliberately.

No part of this needs code or a terminal unless the guide says so plainly — and where it does, the exact commands are printed. The step-by-step is below, with the surrounding sections supplying the context that makes it hold.

The well-worn snag

Getting the Template line wrong. It has to match the parent's folder name exactly, not the display name in the dashboard, or the child appears in the theme list broken with a missing-parent error against it.

Forewarned is genuinely forearmed here. This one mistake accounts for most of the frustration the topic ever causes — and it disappears entirely once somebody points it out.

A habit worth borrowing

For pure CSS changes, the Customizer's Additional CSS box survives updates too. A child theme repays its setup once you are altering templates or functions, not for twenty lines of styling.

A minute spent now repays itself every time this job comes round again — and like almost every hosting job, come round it will.

What a Hosting & Domains plan spares you

Some steps in this guide exist only because hosting traditionally forced them on you. Here the SSL issues itself, the copy is taken daily without being asked, and one-click installers remove the manual setup. What is left is the part that was always genuinely yours.

Stopped mid-guide at an awkward hour? That is exactly what round-the-clock support is for — say which step you are on and we take it from there.

A developer at the terminal with real SSH access to the box

Why this job is shorter on our plans

Every walkthrough in this library is run on the platform we actually operate — cPanel, LiteSpeed, NVMe, one-click installs — so the instructions match your screen rather than gesturing at it from a distance.

A copy is taken daily on every plan, and putting a file or a database back is one click in the panel rather than a support ticket.

  • Every step checked exactly as published
  • The snag named before it arrives
  • The dull steps taken out of your way
  • People reachable at any hour you stall

Why Hosting & Domains

Standard on every plan

Help that keeps your hours, not ours

Stuck on step three at midnight? Support answers at any hour, mid-walkthrough included.

The dull parts automated

SSL, backups and installs look after themselves here, leaving the guide to cover only what is genuinely yours.

The snag, flagged up front

The classic error for this particular task is named before step one, which is how 20 minutes stays 20 minutes.

5 steps, nothing padded

Each stage is a few minutes of steady clicking, and the fiddly moments are labelled fiddly.

Every undo written out

Any step that could bite is marked, together with the exact way to wind it back.

Honest about how big it is

Customise a theme so the next update rolls through without erasing your work is a intermediate-level job — set aside 20 minutes, with the platform-absorbed steps marked.

Quick Start

Order placed to site online

  1. 1

    Grasp the problem it solves

    Edits made inside a theme are wiped the next time that theme updates. A child theme inherits the parent entirely while your changes sit in a separate folder the updater never opens.

  2. 2

    Create the folder and stylesheet

    Make a new folder in wp-content/themes containing a style.css whose header carries the line Template: parent-theme-folder-name. That one line is the whole inheritance mechanism.

  3. 3

    Load the parent's styles

    Add a functions.php that enqueues the parent stylesheet properly. This replaced the old @import method, which still works but loads more slowly and is no longer advised.

  4. 4

    Switch over and compare

    Change to the child under Appearance, then Themes. The site should look exactly as it did, because a child theme stays invisible until you deliberately override something.

  5. 5

    Override deliberately

    Put CSS in the child's style.css. For template work, copy the parent's file into the child at the same path and edit the copy; WordPress prefers the child's version wherever one exists.

Built In

Fitted to every plan

  • WordPress and 400+ further applications installed in one click
  • Money back within 30 days on hosting plans, 7 on reseller
  • WordPress Toolkit, with the updates seen to for you
  • Staging copies for trying a change before it goes live
  • Spam and virus screening on every mailbox by default
  • Upgrades applied in place, with no migration when you change plan
  • cPanel, which is what most of the industry already runs
  • PHP versions set per site from the control panel
  • Your existing site brought across by our engineers, at no charge
  • No set-up charge at any point, and no joining fee

Frequently Asked

The questions that come up most

Do block themes make child themes unnecessary?

Largely, for everyday changes. Full-site editing keeps your customisations in the database, safely out of an update's reach. For code-level work — custom functions and template parts beyond the editor's reach — the child theme is still the correct tool.

Can a child theme be added to an already-modified parent?

It can, but the direct edits made to the parent have to be found and moved into the child before the next update destroys them. Diff the live theme against a clean download of the same version and every change shows itself.

Does hosting include mail?

Yes — every hosting plan includes mailboxes at your own name, with webmail, IMAP, POP and SMTP plus spam filtering on from the start. There is standalone email hosting too, for a name whose website lives somewhere else.

Where does the hardware physically sit?

The platform runs from a London datacentre with redundant power, cooling and several upstream carriers, with server-level caching in front that keeps cached pages quick for visitors anywhere. For most sites how the platform is built — NVMe disks, LiteSpeed, restrained account density per machine — counts for far more than where it sits.

Keep reading

Changing hosts? Run through our checklist first.

A plain order of work for a move nobody visiting will notice: which files go over first, how to carry the mail across without losing a message, when exactly to repoint DNS, and the two mistakes behind nearly every outage we are asked to rescue.

What arrives is the checklist, and then the occasional note on keeping a site quick. Leave whenever you like; the privacy policy covers the rest.

Do it properly this time.

Every plan carries the essentials other hosts bill as extras — and support that answers.

View Secure Hosting plans