Themes and templates, what you are actually buying

A theme or template looks like a design purchase and behaves like a software purchase, and buyers routinely price it as only the first of those two things. Both descriptions are accurate at once, and the second is where the ongoing cost actually lives.

What a theme actually contains

On most platforms, a theme is code that controls how content is displayed — layout, typography, colour, and often a set of pre-built page patterns a site can be assembled from quickly. On a self-hosted CMS in particular, a theme is not inert; it runs alongside the CMS core and any active plugins, and it can be affected by updates to either, which is the direct cause of the visual breakage that occasionally follows an update on WordPress and similar platforms. WordPress is the platform where this dynamic shows up most, purely because more themes exist for WordPress than for any other platform, and because WordPress itself updates more often than most businesses realise. Therefore, checking compatibility before any WordPress update — not just before installing a theme in the first place — is worth building into a standing routine rather than treating as a one-off step.

Why a theme is a software dependency, not just a look

Because a theme is code, it needs to remain compatible with the CMS core as that core updates, and a theme whose developer has stopped maintaining it can eventually become the single reason a site cannot safely update its own core software — the visual layer holding the whole installation back. This is functionally identical to the abandoned-plugin risk covered in plugins and extensions, and the dependency you inherit, and it is worth checking a theme’s update history with the same scepticism applied to any plugin, before treating a purchase as a one-off design decision.

Free versus premium, and what the price difference is actually paying for

A free theme can be entirely adequate, particularly a well-maintained default theme shipped by the platform itself. A premium theme’s price is generally buying a richer set of pre-built layouts, dedicated support from the theme’s own developer, and — this is the part worth checking specifically — an actual commitment to keep the theme updated as the underlying platform changes. A premium theme with no update in two years is a worse position than a free, actively maintained one, regardless of which cost more at the time of purchase.

Page builders change what a theme actually is

Many premium themes today are paired with, or built around, a visual page-builder plugin, which shifts a meaningful part of the layout decisions out of the theme itself and into the builder’s own stored markup. This has a real consequence for portability: content built with a page builder is harder to move to a different theme, or a different platform entirely, than content stored in a CMS’s own native format — a distinction covered in how a CMS stores your content, and why that decides migration cost.

Customisation, and where it stops being cheap

Adjusting colours, fonts and basic layout options within a theme’s built-in settings is usually inexpensive and quick. Genuine structural customisation — changing how a theme behaves rather than how it looks within its own settings — moves the work from configuration into development, at development rates, and is worth pricing as such rather than assumed to be included in a theme’s purchase price.

What to check before committing to one

How recently the theme was updated, and against which version of the platform. Whether the price includes ongoing updates or only the initial purchase. Whether the design is built with a page builder, and if so, which one, since that decision affects portability later. And whether the demo content shown in the theme’s marketing matches what a genuinely new site will look like before any customisation, which is very often not the case.

Why a theme’s demo content rarely matches the eventual result

A theme’s marketing screenshots are typically populated with carefully chosen, professionally shot imagery and tightly edited placeholder text, arranged to show the design at its absolute best. A small business’s own photography, genuine service descriptions and actual content volume are rarely a perfect match for that demo, and the gap between “how the theme looked in the marketplace” and “how the theme looks with this business’s actual content” is one of the more common sources of disappointment in a template-based build — worth expecting and planning content around, rather than assuming the demo is a reliable preview.

Multiple themes on one site, briefly

Some businesses running more than one distinct section — a main site and a separate blog, or a franchise structure covered in multi-site and franchise structures on one platform — consider running different themes for different sections. This is technically possible on most platforms but adds real maintenance complexity, since each theme now needs to be kept updated and compatible independently, and it is generally only worth the added complexity where the sections genuinely need visually distinct treatments rather than simply different content.

Licensing terms worth reading once, properly

A theme’s licence terms occasionally restrict how many sites it may be used on or whether it may be resold or transferred to a new owner — worth a genuine read before purchase rather than assumed to be unrestricted the way a piece of physical equipment would be, particularly for an agency intending to reuse a theme purchase across more than one client site.

Template files, Elementor, Site Editor and how WordPress theme development actually works in practice

A WordPress theme is a folder of template files and stylesheets — PHP files controlling how different page types display, CSS controlling colour and font choices, and increasingly a set of block patterns — rather than a single design file. A website theme is, structurally, this same folder of files regardless of platform, even where the file formats differ. How a theme works with the platform’s own tools has changed significantly: WordPress’s built-in Site Editor and Customizer both let a theme expose specific settings for a non-technical user to adjust, and how much a given wordpress theme actually exposes through either interface, versus locking behind custom code, varies enormously between one theme and another. Elementor and similar page-builder plugins add a further layer on top of the theme development already inside the theme itself — worth knowing which layer a specific setting change is actually happening in before assuming a small tweak is trivial.

How to choose theme options: what separates a good theme from other wordpress themes

A good theme’s template files are cleanly separated from its stylesheets and any bundled scripts, which is what makes the theme maintainable years later rather than an increasingly fragile pile of overrides. Furthermore, a good theme’s update cadence matters more than its initial price. Therefore, checking a theme’s own changelog before purchase, the same way this page has already recommended checking a plugin’s, is worth the two minutes it takes — choosing on appearance alone, without checking how recently its update history shows real activity across current wordpress themes, is the single most common way a business ends up locked into the abandoned dependency described above.

Where to go from here

Whether a template is the right starting point at all, rather than a fully custom design, is a design-process question covered in when a template is the right answer. And what a theme purchase adds to an actual build quote is priced on website design packages.