How Much Does a WordPress Website Cost?

The software is free. Nothing else is. WordPress itself costs nothing and never will, which is why "how much does WordPress cost" is the wrong question. The right one is: what does running this particular site cost, this year and every year after.

There are four buckets, and only the first is optional to think about.

The four cost buckets

Most budgets get the first three roughly right and forget the fourth entirely. Maintenance is the one that decides whether the site is still working in three years.

Hosting

The widest range and the most consequential choice. What separates tiers is not disk space, it is what happens when something goes wrong and how fast pages are served under load.

• Budget shared hosting is genuinely cheap and genuinely slow, and it is shared — a busy neighbour is your problem. Fine for a brochure site with light traffic.
• Managed WordPress hosting costs several times more and absorbs updates, backups, caching and often security. For a business site that is a staffing decision priced as a hosting bill.
• VPS or cloud is cheaper than managed at the same performance and assumes you are the sysadmin.

Two traps in the pricing. Introductory rates are typically for the first term only and renew at a much higher figure — budget the renewal, not the promotion. And the cheapest plan that technically runs WordPress often cannot run a store; a store's requirements are different from a blog's. What to compare is set out in hosting services for WordPress.

A domain is a small annual cost by comparison, with the same renewal caveat — see how to pick a domain name.

Themes and plugins

This is where "free WordPress" quietly becomes a subscription.

Themes. A free theme from the official directory costs nothing and is a legitimate choice. A premium theme is a one-off or annual licence — what that buys is covered in premium WordPress themes.

Plugins. The pattern is a free tier that does the basics and a paid tier that does the thing you actually needed. The ones that most often end up paid:

• a page builder's pro tier, if you use one — choosing a page builder;
• forms, once you need conditional logic or payments;
• a backup plugin with off-site storage — backup plugins;
• a security plugin's paid firewall — security plugins;
• caching, though free options are strong;
• anything that syncs with an external service, which usually charges per record.

Count these as annual, not one-off. Five licences at a modest yearly price is a real recurring line, and it is the line that surprises people most.

Store costs are different

A WooCommerce store adds categories a brochure site never sees:

• Payment processing — a percentage of every sale, forever. Over any meaningful revenue this dwarfs every other cost on this page.
• Extensions for shipping, subscriptions, bookings — often per-site annual licences. WooCommerce subscriptions is one example of a capability that is usually paid.
• Hosting that can run a store. Cart and checkout cannot be page-cached, so a store needs real server capacity rather than a good cache.
• Transactional email through a proper service, because receipts that do not arrive cost more than the service does.

Build cost

If you build it yourself, the cost is your time and it is not small — plan on a real project, not an afternoon. How to use WordPress to make a website is the order to do it in.

If someone else builds it, the range is enormous and driven by four things: how many unique page designs exist, whether the design is bespoke or a customised theme, whether anything integrates with an external system, and how much content someone has to write and migrate. Content migration in particular is routinely underestimated and routinely the biggest line.

Maintenance: the cost everyone forgets

A WordPress site is not a purchase, it is a running system. Every month it needs:

• core, theme and plugin updates applied safely;
• backups that are verified, not just scheduled;
• a check that forms still send and the checkout still completes;
• occasional real repair work when a plugin conflict or a PHP version change breaks something.

You either pay someone for this or you do it. A site with no maintenance budget is a site that will eventually be broken, hacked, or both — and recovering a hacked site costs more than a year of prevention.

Where money is genuinely wasted

• Paying for plugins that duplicate each other — two caching plugins, two SEO plugins.
• Licences for plugins nobody uses, still renewing years later. Audit annually.
• A premium theme bought for one feature a small snippet would have provided.
• Over-provisioned hosting for a site with modest traffic, and under-provisioned hosting for a store.
• Rebuilding instead of fixing, because nobody documented the first build.
• Nulled themes and plugins, which are free and cost you the whole site.

How to arrive at your number

Answer five questions and the budget writes itself: Is it a store? Will it need plugins beyond the free tiers? Are you building it or paying someone? How much traffic, honestly? And who is responsible for it in month eighteen?

The last question is the one that decides whether the number you write down is the number you actually spend. If the answer is "nobody", add the cost of the rebuild.