How to choose a WordPress theme without regretting it later

Pick for code quality and upkeep, not the demo. Block or classic, where to look, seven checks before you install, and how to test with your own content.

By Sohail Hussain21 November 20265 min read

Choose a theme for how it is built and maintained, not for how the demo looks. A good theme is light, updated regularly, uses the block editor properly, does not force a page builder or a bundle of plugins on you, and stores content in a way any other theme can display. Shortlist two or three, test each on a staging copy with your own content, and pick the one that is quickest to edit and lightest to load. The demo's photography and copy will not survive contact with your real content anyway.

Should you pick a block theme or a classic theme?

For a new site in 2026, a block theme, unless you have a specific reason not to.

Block themes are built entirely from blocks. Headers, footers and page templates are edited in the Site Editor, and colours, fonts and spacing are defined in a theme.json file that the editor reads. Editors see the real design while they edit, and global changes, such as a new brand colour, happen in one place.

Classic themes use PHP templates for layout and the Customizer for settings. The block editor only handles the content area. Many good classic themes are still maintained, and if you have one that works, you do not need to switch. But new WordPress features arrive in the block system first.

The main reason to choose a classic theme today is a dependency: a plugin or workflow that has not caught up with block themes.

When no ready-made theme fits, we build custom block themes as part of our website design and development work. For many small sites, though, a well-chosen ready-made theme is the better use of money.

Where should you look, and what should you avoid?

Start with the WordPress.org theme directory. Every theme there passes a review against the directory's requirements, is GPL-licensed and updates from your dashboard. Use the feature filters: "Full Site Editing" for block themes, "Accessibility Ready" for themes that passed an extra accessibility review, and "RTL Language Support" if you will ever add Arabic or Urdu.

Commercial theme shops and marketplaces are fine too, with more care. Avoid these:

  • Multipurpose themes with dozens of demos. They ship code for every possible kind of site, plus a page builder, a slider and a list of "required" plugins. You use a fraction and load the rest.
  • Themes that bundle premium plugins. Bundled licences often cannot be updated directly, so you wait for the theme author to ship each plugin update.
  • Nulled themes from download sites. They are pirated, often contain malware, and never get updates.
  • Themes that put content in shortcodes. Switch themes later and your pages fill with bracketed codes instead of content.

What should you check before installing a theme?

Seven checks, a minute or two each:

  1. Last updated. Within the last six months is good. More than a year is a warning.
  2. Compatibility. It should support the current WordPress release, which is 7.1 as of October 2026, and PHP 8.3 or newer.
  3. Support. On WordPress.org, open the support forum. Are questions answered, and by the author?
  4. Demo weight. Run the demo through PageSpeed Insights on mobile. If the demo is slow with the author's own tuned content, your site will be slower.
  5. Required plugins. Note what the theme asks you to install on activation. Each one is a dependency you inherit.
  6. Editing experience. Does it use the block editor and patterns, or its own builder?
  7. Licence and renewals. For paid themes, what do you get after the first year, and what happens to updates if you stop paying?

For checks 4 and 5, list what the demo homepage loads and total it in our page weight calculator. A light theme adds little on top of your own images; a heavy one can add a megabyte before any content.

How do you test a theme with your own content?

On a staging copy, never on the live site. Install each shortlisted theme, then:

  • Add your real homepage text, a real service page and real images. Long product names and short Arabic headings break layouts in different ways; test with what you will actually publish.
  • Build one new page the way your editor would, and time it. If it takes an hour to make something presentable, it will take an hour every time.
  • Look at the result on a mid-range phone, not only a desktop screen.
  • Check the colours against your brand, and the contrast of text on its backgrounds.
  • Switch to another theme and back. Note what was lost: widgets, menus, Customizer settings, anything the theme stored instead of your content.

How do you customise a theme without losing changes?

Never edit the theme's own files. The next update overwrites them.

In a block theme, design changes made in the Site Editor, such as colours, fonts and template edits, are saved in the database, not in the theme's files, so they survive updates. Code changes, such as extra templates or custom CSS files, go in a child theme. A child theme needs only a folder and a style.css whose header names the parent theme's folder:

css
/*
Theme Name: Example Child
Template: twentytwentyfive
*/

Template must match the parent's folder name exactly. Block themes generally do not need a functions.php to load the parent's styles; classic themes usually do. The child themes chapter of the Theme Handbook covers both.

Features that should survive any theme change, such as custom post types or tracking code, belong in a small site plugin, not in the theme or the child theme.

When is a ready-made theme the wrong choice?

When your content has a strong structure, such as products in families, projects by sector or people by department, and every item should be displayed the same way. A ready-made theme gives you pages; a custom theme gives you a system. Elementor vs Gutenberg vs a custom theme covers that decision.

It is also the wrong choice when you would end up overriding half its templates. At that point you are building a custom theme on top of someone else's, and inheriting their updates as well. For the rest of the setup we put around a theme, see WordPress for business websites.

Was this guide useful?

Questions

Frequently asked.

Should I pay for a premium theme?

Only for something the free options lack, such as a specific design, priority support or features you will actually use. Many of the best-built themes are free in the WordPress.org directory. Price says little about code quality; the seven checks in this guide say much more.

Will I lose my content if I change themes?

Posts, pages and media stay. What can be lost is anything the theme stored itself: widget areas, Customizer settings, theme-specific shortcodes and any custom post types registered inside the theme. Check for those on a staging copy before switching, and move post types into a plugin first.

Sohail Hussain

Founder, MSH Technologies

Sohail has designed and built websites, web apps and AI products for over 12 years, for clients from Singapore-based industrial groups to early-stage SaaS startups. He writes about what actually worked.

Keep reading

Related guides.

All posts

Your next move

Like what you see? Tell us about it.

A process that takes too long, a website that undersells you, or an idea ready to take shape. Tell us where you are and we will suggest a useful next step.

India · Working with clients worldwide

Sohail, Founder, replies within 1 working day (Mon–Sat, IST). Free and no obligation.