Choosing and installing a theme

Pick a lightweight theme that uses core WordPress features, preview it privately, then activate only after you have checked menus, widgets and styles. Avoid page builders and themes that bundle “plugin” features because they lock you in. If you need code changes, use a child theme so updates do not wipe your work.

This picks up from a WordPress site you can already log in to at wp‑admin with an administrator account. If you host with us on cPanel, you can also reach cPanel File Manager for manual uploads. If you are not sure, open a support ticket.

Before you start

• Know your theme types. Classic themes use the Customizer. Block themes, introduced in WordPress 5.9, use the Site Editor and let you edit headers, footers, templates and styles in Appearance > Editor. The Widgets workflow also differs. Classic themes show Appearance > Widgets. Block themes shift this into the block‑based editors.
• Expect to reassign things after a switch. Posts, pages and media stay. Menus, widgets and theme‑specific settings often need reassigning because every theme exposes different menu locations and widget areas. Additional CSS in the Customizer is stored per theme and may not carry over.
• Test safely. Use Themes > Live Preview to view the new theme privately before activation. For larger changes, use a staging copy or WordPress Playground so visitors do not see half‑done work.
• Watch for lock‑in. The official guidelines prohibit themes from adding plugin‑type features such as shortcodes or custom post types. Many commercial themes and page builders do it anyway. If you deactivate them later you can be left with broken layouts or shortcode text across your pages.
• Mind performance. Heavy themes load large CSS and JavaScript and create deep DOMs. That hurts Core Web Vitals like LCP and INP. Prefer themes that load only what is used.
• Check requirements. Themes declare “Requires at least” and “Requires PHP”. WordPress checks these before activation to prevent fatal errors. Do not force it.
• Have a quick recovery plan. Keep your current theme installed so you can switch back. Take a backup before changing a live site. If you need help on a Hostworld cPanel plan, open a support ticket.

Step 1: Decide classic or block theme

Decide how you want to edit your site day to day.

• Block themes: Use Appearance > Editor to edit templates and parts such as headers and footers with blocks. Styles are centralised and you can make site‑wide changes from the Site Editor.
• Classic themes: Use Appearance > Customizer for settings and Additional CSS. Widgets live under Appearance > Widgets. Templates are PHP files and are not edited in the Site Editor.

If you switch between these types later, expect different menus and widget workflows. Plan a little time to retune.

Undo

If the editing experience is not for you, switch back to your previous theme from Appearance > Themes. Reassign your old menus if needed and remove any blocks or widgets added during testing.

Step 2: Choose a theme that will not trap you

Shortlist themes that keep design in the theme and functionality in plugins.

• Free vs paid: Themes in the official WordPress directory are reviewed for guidelines, code quality and security before listing. Commercial themes sold elsewhere are not reviewed by WordPress.org. You rely on the vendor for updates and support. That is fine if they are reputable, but check their update history before you buy.
• Avoid builder lock‑in: Page builders can store layouts as proprietary shortcodes or markup. Deactivate them and you can get unreadable pages filled with codes. Prefer core blocks. If you do choose a builder, be clear on your exit plan.
• Steer clear of “plugin territory” in themes: If a theme advertises custom post types, shortcodes or sliders baked in, that content may break when you switch themes. Choose themes that leave those to plugins.
• Performance first: Look for light themes that load per‑block styles and minimal scripts. Avoid multipurpose bundles that enqueue everything on every page.

Undo

If you install a builder or a feature‑heavy theme and regret it, deactivate the builder plugin and switch to a lighter theme. You may need to clean up leftover shortcodes or markup. If the cleanup is too big, restore your backup, then migrate page by page using core blocks.

Step 3: Check compatibility and requirements

Before you touch your live site, confirm the theme will run.

• Read the theme’s header or listing. Note “Requires at least” and “Requires PHP”. WordPress validates these before activation to help avoid white screens.
• Check that your editing workflow matches the theme type. If you want the Site Editor, pick a block theme.
• Plan your menu and widget migration. Note your current menu names and widget content so you can reassign them later.

Undo

If activation fails or you see problems, go back to Appearance > Themes and re‑activate your previous theme. If the new theme was uploaded, leave it installed while you troubleshoot or delete it to remove it from the list.

Step 4: Create a safe place to test

• Staging: The WordPress Make/Test team recommends testing major updates and theme changes on staging before going live. If you have a staging copy, use it for theme trials.
• WordPress Playground: Spin up a disposable WordPress in your browser to try a theme with dummy content. No changes touch your site.
• Private preview: At minimum use Appearance > Themes > Live Preview. Visitors do not see the change while you click around.

Undo

Delete the staging copy when finished if you do not plan to maintain it. Close Playground when done. Live Preview changes are not saved to visitors until you activate.

Step 5: Install and safely preview in wp‑admin

1. Go to Appearance > Themes in wp‑admin.
2. Install from the directory: Click Add New, search for the theme, then click Install. Do not activate yet.
3. Or upload a .zip: Click Upload Theme, choose the theme .zip, then Install Now. If the theme already exists, WordPress will offer “Replace current with uploaded” so you can update it without FTP. Use this only if you mean to overwrite the existing version.
4. Use Live Preview: Hover the installed theme and click Live Preview. Click through key templates such as the homepage, a post, category archive and contact page. Check headers, footers, templates and styles. In block themes you will see the Site Editor experience. In classic themes you will see Customizer controls.
5. Check menus and widgets: In the preview, assign your primary menu to the theme’s menu location and place key widgets or their block equivalents. You are testing that you can rebuild your navigation and sidebar within a few minutes.

Undo

Close Live Preview without activating to leave your live site unchanged. If you clicked Activate and want to back out, return to Appearance > Themes and activate your previous theme. Reassign its menus and widgets if WordPress prompts you.

Step 6: Install manually via cPanel File Manager or SFTP

Use this if your theme is not in the directory or you prefer manual control.

1. Prepare the folder: The theme should unzip to a single folder, for example mytheme that contains style.css and templates, not nested within another folder.
2. Upload in cPanel (Hostworld shared, reseller and WordPress hosting use cPanel): In cPanel File Manager, open your site’s document root then go to wp-content/themes. Upload the theme .zip and Extract. Confirm the folder appears directly under themes.
3. Or upload via SFTP: Connect and upload the theme folder to wp-content/themes.
4. Activate from wp‑admin: Go to Appearance > Themes. You will see the new theme. Use Live Preview first, then Activate when ready.

Undo

To back out of a manual upload, delete the theme’s folder from wp-content/themes in cPanel File Manager or SFTP. Deleting a deactivated theme does not change the live site. Do not delete a parent theme if a child theme depends on it.

Step 7: Activate, reassign menus and migrate CSS

1. Activate the new theme in Appearance > Themes when you are satisfied with the preview.
2. Reassign menus: Go to Appearance > Menus or the Site Editor’s navigation area and assign your existing menus to the theme’s locations such as Primary, Footer and Social.
3. Place widgets or blocks: Classic themes use Appearance > Widgets. Block themes use the Site Editor to edit template parts with blocks. Expect names and locations to differ from your old theme.
4. Migrate Additional CSS: The Customizer’s Additional CSS is theme‑scoped. Copy any persistent rules into the new theme’s Additional CSS, or better, into a child theme so they survive updates. Keep the old theme installed while you copy so you can reference it.
5. Check templates: In a block theme, use Appearance > Editor to confirm pages, posts, archives and 404s look correct. In a classic theme, review key templates by visiting those pages on the front end.

Undo

Switch back to the old theme if something is wrong. Reassign its menus and widgets. If you pasted CSS into the new theme, paste it back into the old theme’s Additional CSS. If you changed templates in the Site Editor, revert those or restore from your backup.

Step 8: Measure performance and trim

The theme has a major impact on speed and interaction. Keep it lean.

• Check Core Web Vitals: After activation, test a few representative pages. Large LCP values point to heavy hero images, render‑blocking CSS or JavaScript.
• Reduce render‑blocking: Fewer and smaller CSS and JS files improve load and interactivity. Prefer themes that load per‑block styles and avoid big bundles on every page.
• Watch DOM size: Very deep or large DOM trees degrade interactivity. Heavy page builders often add wrapper upon wrapper. If you see slow input response, simplify the layout.
• Be ruthless with features: Disable sliders and animations you do not use. Remove plugins you enabled to prop up the theme. The fastest asset is the one you do not load.

Undo

If performance worsens after the switch, go back to the previous theme. Alternatively, keep the new theme but turn off heavy options, remove unneeded plugins, and retest until metrics recover.

Step 9: Use a child theme for code changes

If you need to change templates or functions, create a child theme rather than editing the parent. A child theme overrides selected templates and survives parent updates. Keep the parent theme installed. If the parent is missing a child theme will break with “The parent theme is missing”.

• Good use cases: Persistent CSS, small template tweaks, adding functions that are truly theme‑related.
• Bad ideas: Editing parent files in the Theme File Editor. Changes will be lost on update and can white‑screen your site if a syntax error slips in.

Undo

To roll back a child theme experiment, activate the parent theme. Leave the parent installed at all times. If you decide to abandon the child, delete the child theme folder and keep the parent.

Step 10: A quick decision checklist

• Do I want a block theme with the Site Editor, or a classic theme with the Customizer?
• Is the theme in the WordPress directory and reviewed, or will I rely on a vendor for updates and support?
• Does it avoid page builder lock‑in and plugin‑territory features?
• Are “Requires at least” and “Requires PHP” compatible with my site?
• Is the CSS and JS footprint modest and loaded only when needed?
• Have I planned how to reassign menus, widgets and Additional CSS?
• Do I have a staging option or have I used Live Preview?
• If I need code changes, have I planned a child theme?

What next

If you run WordPress on one of our cPanel plans and want help installing a theme or setting up a safe test copy, open a support ticket. Tell us your domain and what you want to try and we will point you at the right route for your account.

If you are weighing up more control over performance, our VPS options give you room to tune PHP versions and caching as you like. See UK VPS and browse our VPS guides for the next steps.

The next step in your site build is to configure your navigation and key templates, then set up a backup before you make further changes.