Which WordPress.com plan you need, and when you have outgrown it

A small architecture practice asked me in February whether its WordPress.com plan was still the right one. Fourteen pages, a project archive of about nine hundred photographs, a contact form, and a blog that gets a post twice a year. The plan had been bought the week the site launched, upgraded once when a plugin turned out to be necessary, and renewed every year since without anybody reading the receipt.

The question was not really about hosting. The site loaded in about a second, the certificate renewed itself, nothing had broken in two years. It was whether a permission paid for monthly was worth more than the money, which is not what the plan page answers and is what most owners arrive at, usually in the week the renewal notice lands.

WordPress.com is unusual among hosts in that what changes between tiers is mostly what the site is allowed to do. The servers are broadly the same, and so are the certificate, the edge cache and the firewall. What moves is the fence, and the price is attached to the fence, which makes the choice narrower than the grid suggests.

Disclosure: some links on this page are affiliate links, and WPSifero may earn a commission if you buy through them. That does not change the price you pay, and it does not change what this piece recommends: the section on when to leave applies to the company linked below as much as to any other.

The four rows that decide a plan

Set aside the rows about premium themes, design tools, priority support and site analytics. Four things change what a site can be.

Plugins. The free tier and the entry paid tier do not allow them. A tier in the middle opens a curated directory: the well-known plugins, installed and updated from the dashboard, vetted by the platform. The top self-serve tier allows a plugin written or bought elsewhere to be uploaded, and adds SFTP and a command line. This is the largest single difference between plans and the row most people misread. They assume plugin access means any plugin, then find the directory does not contain the one they were told about.

Themes. The same ladder. Free themes at the bottom, a wider directory above, and upload of a third-party theme only at the top. A site using a theme from the directory can ignore this row permanently. A site that has bought a theme is choosing its plan with it.

Storage. Measured on media and uploads. A text site uses almost none. A photographer or a site with a project archive uses a great deal, and the tiers differ by multiples. This is the row a site grows through without anybody deciding, which is why it needs checking at renewal.

Advertising. The free tier can carry WordPress.com's own ads; the first paid tier removes them. For a hobby blog that trade is the whole decision. For a business it settles the question the day the site goes live, because an advertisement under your contact form is worse than the fee that removes it.

The four rows above are yes or no. A plugin either installs or it does not, a theme either uploads or it does not, the ads are either there or they are not. Everything else is a sentence with an adjective in it, written to make each tier sound one step better than the one beneath.

WordPress.com's own plan comparison is the only place to check the four against each other, because the labels get renamed on a schedule that has nothing to do with the capabilities underneath them. Read the plugin upload row first. It decides more plans than any other line on the page.

What the grid adds that does not change the answer

Unlimited pages, unlimited posts, a certificate, a CDN and a spam filter are on every tier including the free one. The analytics on the higher plans duplicate whatever the site already runs, or nothing at all if nobody opens the report. The premium theme collection is a count of designs, and the theme that will be used is probably free. Support is a real difference in kind, since a paid tier gets a ticket queue and a free tier a forum, but the row makes each level sound one step better than the last.

Where the money crosses over, and why it happens early

Here is the arithmetic the renewal notice avoids. A small virtual server capable of running that practice's site, one or two cores and a couple of gigabytes of memory, is a modest monthly figure, at the time of writing in the same range as a streaming subscription or below. WordPress itself is free software. The plugins the practice wanted, caching, forms, SEO, an image optimiser, are free. Compared in money alone, the plan price is up against the server price, and the server wins.

The crossover lands at the tier that permits plugins, not at the top of the ladder. It arrives earlier than most people expect, for four reasons.

First, the plugins are free on both sides. The upgrade does not buy software; it buys permission to install software that could be downloaded for nothing. Defensible, since keeping a curated directory patched is work, but it leaves no software value to weigh against the server.

Second, the entry tiers are priced for convenience and the plugin tier is priced for capability. The jump between them is the largest percentage step on the ladder, and it is the step a site makes the moment it stops being a brochure.

Third, one server runs more than one site. The comparison is always made per site and the server is never per site. Two small sites on one box halve the figure the plan is measured against.

Fourth, renewal is the number that matters and the first year is not. Promotional pricing, a bundled domain and a first-year discount flatter the plan at the moment the decision gets made. The honest comparison uses the renewal figure, which arrives when the site is already committed.

The counter-argument belongs in the same paragraph, or this becomes a sales page for servers. That server figure does not include a tested backup with one-click restore, a firewall at the edge, a global cache, somebody applying PHP and core security releases, or a ticket when the database will not start. Assembled honestly, that stack is more money than the plan or several evenings, and the evenings are the expensive half. The plan is not overpriced. It is priced for a different appetite for risk.

One asymmetry runs the other way: a cheap server has a transfer allowance a good day can exhaust, while the tiers people compare do not bill by traffic.

The reasons to stay, which are not marketing

Three of them survive being said plainly.

Somebody else patches it. Core security releases, PHP upgrades, the database, the certificate, the edge rules: none of that becomes a line on the owner's calendar. On a server it is a monthly ritual, and the failure mode of a skipped ritual is not a slow site but a site compromised in a way nobody notices for weeks. The value is not the patch. It is that nobody has to remember the patch.

It cannot easily be broken. With no SFTP and no arbitrary plugin uploads, most of the failures that produce a white screen are unavailable. No .htaccess to corrupt, no PHP memory limit to raise, no way for a helpful editor to install a nulled theme and take the site down on a Friday. The fence is the product, and it is why the top tier is a trade rather than a straight upgrade: it hands over the keys and gives up the protection that made the lower tier safe.

The support is a person with access. When a domain stops resolving mid-migration, or a site goes blank after an update, a ticket reaches somebody who can see the platform from inside. On a server, the provider confirms the box is running and hands the problem back. That is worth the difference on the worst day of the year and worth nothing on the other three hundred and sixty-four, which is why it is easy to dismiss until it is needed.

A fourth reason is organizational. WordPress.com is a place where a site can be handed to somebody who is not technical and still be there in two years. For an agency that is a reason to leave a client on it; for a client, a reason to stay.

The free alternative deserves naming here. The free tier is a real option for a blog that is not a business: a subdomain, the vendor's ads, no plugins and a low ceiling, enough for a first year of writing and not enough for anything that depends on it. Above that, the free alternative is WordPress on a server somebody administers. It is the same software; the difference is who does the work, and the work is what is being priced.

When paying for the plan is the wrong answer

The first case is a site that will never install a plugin: a five-page brochure, a wedding site, a single campaign page. The plugin tier's permission is worth nothing there. The second is a site buying the top tier for the file editor. If the only reason for the upgrade is the ability to upload a plugin zip, the same money buys a server where that ability is inherent, and the managed features go unused.

The third case costs more than it looks. A site whose media library has outgrown its tier does not necessarily need a bigger plan. It needs an image pipeline: resize before upload, serve modern formats, stop the theme requesting the original. The same photographs then occupy a fraction of the storage. Moving up a plan is the easiest way to spend money here and the last thing worth trying.

The signals that it is time to leave

Each of these is a test with an answer rather than a feeling about the dashboard.

• The site needs a plugin outside the curated directory, no tier above the current one allows uploads, and the alternative stack prices below the tier that would.
• The site needs the server rather than the site: a PHP extension, a background worker, a cron, a reverse proxy rule, a second runtime on one box.
• The plan is paid for a permission already exercised on another site, and one box would carry both.
• The top tier is paid for SFTP and uploads alone, which is an expensive way to buy a file editor.
• The site needs a staging copy and database access, and the tier that permits them prices above the alternative stack.

And the one that is not a signal: wanting a plugin. It is the most common reason given for migrating and usually a misreading of the grid. The permission to install plugins sits one tier or two above the tier that feels expensive, and the plugin is waiting there. Moving a site to a server for a plugin the next tier already includes costs a weekend, a migration risk and a year of maintenance, to save a fee a plan change covers in an afternoon.

The decision rule

Choose the lowest tier that permits what the site does today, plus one step of storage headroom, and compare renewal figures rather than first-year ones. Stay while somebody else's patching is worth more than the difference, since the fence matters most to the site that cannot afford a bad week. Leave when the plan charges for a permission a server provides inherently, and the site needs the server: a worker, an extension, a second site, a staging copy with database access. The free tier stays the right plan for a blog that needs nothing the paid ones sell.

Between those two sentences sits the honest advice for the architecture practice and for most sites shaped like it. The plan was not too expensive. It was one tier below what the practice needed, and the upgrade would have cost less than the deliberation. The current tiers and what each one permits are on the plan comparison WordPress.com publishes. Check the price before deciding, and check the renewal price before comparing, because they change it, and the second number is the one that will be charged.