WordPress.com vs WordPress.org: the difference that matters

Two products share the name "WordPress" and confuse a lot of people as a result, because the difference between them is not obvious from the name alone. It matters more than most naming confusion does, because it affects what you can actually do with the site once you have built it.

WordPress.org: the software

WordPress.org is where the actual WordPress software lives — free, open source, and downloadable by anyone. This is the same software that runs a very large share of the websites on the internet, and it is what people usually mean when they talk about "WordPress" as a piece of software rather than a company.

To use it, you install it on hosting — your own, or hosting bought from any provider — and you have complete control over everything: which theme runs, which plugins are installed, direct access to every file and the database, and the ability to do anything the software allows. Because it is genuinely open source, nobody can take the software away from you or change the terms you use it under.

WordPress.com: the hosted platform

WordPress.com is a company — run by Automattic, one of the largest contributors to the WordPress.org project — offering a hosted platform built on that same underlying software, but packaged as a signup-and-go service rather than something you install yourself. You create an account, choose a plan, and the platform handles the server, updates and infrastructure for you.

The trade is control. On the free and lower-tier WordPress.com plans, you cannot install arbitrary plugins, cannot switch to any theme you like, and cannot directly access the files or database behind your own site. Higher-tier WordPress.com plans progressively remove these restrictions, moving closer to what self-hosted WordPress.org gives you by default — at a corresponding price.

Side by side

Why the distinction actually matters

The practical impact shows up the moment you want to do something the platform was not built to let you do. Want a specific plugin for booking appointments, or a membership system, or a particular payment gateway? On self-hosted WordPress.org, you install it. On most WordPress.com plans, you either cannot, or you have to upgrade to a plan that allows it — and even then, the selection is narrower than what is available to a self-hosted install.

The same is true of themes, of custom code, and of anything requiring direct server access. None of this is a flaw in WordPress.com — it is a deliberate trade, offering less to manage in exchange for less control — but it is worth knowing about before building a site, rather than discovering the restriction later when a specific plugin turns out to be unavailable.

What moving between them actually involves

Content itself is portable in principle — both use the same underlying WordPress export format for posts and pages — but a move in either direction is a genuine project rather than a setting you flip. Moving from WordPress.com to self-hosted WordPress.org means exporting your content, setting up hosting, installing WordPress, importing the content back in, then rebuilding anything that depended on WordPress.com-specific themes or restrictions. Moving the other way is rarer, since it means giving up capability rather than gaining it, but involves the same kind of export-and-rebuild process.

Neither direction is something to plan around doing casually. It is worth thinking through which model actually fits before the site has years of content and configuration built up around one platform's constraints, since untangling that later costs considerably more time than choosing correctly at the outset would have.

A note on cost, since it is not always obvious

WordPress.com's pricing structure bundles hosting, the platform, and increasing levels of capability into tiers, so comparing its cost to self-hosted WordPress.org is not a straightforward like-for-like comparison. Self-hosted WordPress.org has no licence cost for the software itself — hosting is the only recurring cost, bought separately and chosen independently of WordPress at all. Domain registration is a separate cost either way, though it is included more readily in some WordPress.com plans than as a default on self-hosted setups.

Which one to choose

WordPress.com's hosted platform suits someone who wants the absolute minimum to manage and does not expect to need plugins or themes outside its selection — a simple personal blog is the classic case. Self-hosted WordPress.org suits anyone who wants full control over functionality: a business site, a shop, a membership site, or anything likely to need a specific plugin or a custom theme at some point, which describes the majority of commercial websites.

Moving from WordPress.com to self-hosted WordPress.org later is possible but involves an actual export-and-import migration rather than a simple setting change, so it is worth thinking through which route fits before building the site rather than after. See installing WordPress on your hosting for what the self-hosted route actually involves, and managed WordPress hosting if the appeal of WordPress.com is specifically not having to think about maintenance — that particular benefit is available on self-hosted WordPress too, without the platform restrictions.