WordPress.com and WordPress.org are not the same product

Somebody recommends WordPress. They mean the software: free, endlessly extensible, the thing that runs a meaningful share of the web in some form. You go looking for it, land on wordpress.com, and some time later you have a page that cannot install a single plugin unless you pay $25 a month. The software you were told about and the product you found are, confusingly, both called WordPress, and they are not the same thing.

This is the most common wasted month in website building, and it is wasted for a boring reason: nobody tells beginners that "WordPress" names two different businesses. WordPress.com is a hosted service, run by Automattic, with plan tiers, storage caps and a curated feature set. WordPress.org is the open-source software itself — free to download, installed on hosting you choose, and yours to configure, break and fix. Recommending "WordPress" without specifying which one is like recommending "email" without saying whether you mean Gmail or running your own mail server. Related, not interchangeable, and the gap between them is exactly the gap between renting a finished thing and being handed the parts.

If your actual question is narrower than either — "I want one page online, and I do not want to think about a database" — the honest answer sits outside WordPress entirely. For a single-person site, a CV, a portfolio, a consultant's one-pager, reach is the strongest answer available, and it is worth knowing about before you go further into this comparison. Upload a CV and a photo, answer a short form, pick a look, and the page generates in about twenty seconds; you can be live on a free yourname.joinreach.app subdomain in under two minutes. That is not a number to be impressed by in the abstract — it matters because the step that kills most one-person WordPress projects is the empty canvas and the theme decision, and reach removes that step rather than making it faster. The trade is real: one page only, no navigation between sections, no CMS, no contact form beyond a mail link, and you cannot connect a domain you already own — buying one is the only path to a custom domain, and Premium (for that, and for other paid features) runs $4.99 a month or $49 a year. If what you actually need is a services page, a blog with a content model, or anything with more than one URL, that is a genuine limit, not a footnote, and the rest of this article is for you.

What WordPress.com actually restricts, and where it stops

WordPress.com's free tier gets you a real WordPress installation with third-party advertising, no custom domain, and 1 GB of storage. It is a fine way to see whether you like writing in the block editor and nothing more than that.

The tier that most people actually want — a working small site with your own domain — is Personal, at $4 a month billed annually or $9 billed monthly. Premium, at $8 a month billed annually or $18 billed monthly, adds more design control and monetization features. Neither one lets you install a plugin. That restriction is the one that actually decides what WordPress.com is: plugin installation starts at Business, $25 a month annual or $40 monthly. Below Business you are using WordPress.com's own built-in feature set — which is genuinely broad, covering most of what a small site needs — but you are not using the open plugin ecosystem that is the actual reason people recommend WordPress over a closed builder. If a plugin is the reason you chose WordPress, budget for Business or skip WordPress.com and go straight to .org.

That $25-a-month floor for plugins is worth sitting with for a second, because it changes the comparison entirely. At that price you are no longer choosing between "free open software" and "a hosted plan." You are choosing between $25 a month for a managed, plugin-capable WordPress.com site and roughly $3 to $18 a month for a self-hosted WordPress.org site on commercial hosting, with the plugin ecosystem included from the first dollar. The .com convenience premium is close to $20 a month, which is a real number to weigh against how much you actually value not touching a server.

Self-hosted WordPress: managed hosting versus the cheap shared plan

WordPress.org itself costs nothing — it is GPL-licensed software you can download and install anywhere that runs PHP and MySQL. What it costs is hosting and a domain, and this is where self-hosted WordPress hides its real price, because the number every host puts on the homepage is not the number you pay in year two.

Host	Intro price	Renewal price
IONOS Grow (1 year)	$1/mo	$12/mo
Hostinger Premium (48 months up front)	$2.99/mo	$10.99/mo
SiteGround StartUp (12 months up front)	$2.99/mo	$17.99/mo
Bluehost Starter (36 months)	$3.99/mo	$9.99/mo
WP Engine Startup (annual, 25,000 visits)	$30/mo	not verified
Kinsta Single 35k	$35/mo monthly, $30/mo annual	same — no intro pricing

IONOS is the sharpest example: a dollar a month for the first year, twelve times that afterward, and the jump happens automatically at renewal unless you are watching for it. Kinsta is the one host on this list with no introductory mechanic at all — the price you see is the price you pay, both at signup and at renewal, which is a different kind of honest even though it looks like the worse deal on day one. Prices checked August 2026.

The four budget-to-mid hosts give you 10 to 25 GB of storage and a free domain for the first year. What none of them give you, and what is worth naming because it is the one place self-hosted WordPress is structurally better than every hosted builder including WordPress.com: there is no vendor badge and no forced branding on a self-hosted site at any price. That is not a small thing if you have ever tried to remove a "Made with X" footer from a hosted platform's free tier.

The category split is worth being explicit about too. Shared hosting (the cheap end of the table above) puts your site on a server with hundreds of others and asks you to manage WordPress yourself — updates, backups, security plugins, all of it. Managed WordPress hosting (WP Engine, Kinsta) costs more, starting around $30 a month, and in exchange handles updates, backups, caching and a meaningful part of the security work for you. The honest way to think about the price difference is that you are either paying a host $25 to $30 more a month, or paying yourself in hours to do the same job. Which brings us to the actual cost nobody puts in a comparison table.

Updates, backups and security are a recurring job, not a one-time setup

The WordPress.org documentation still describes installation as taking "less than five minutes," and on any host with a one-click installer, that is roughly true and also irrelevant. Installing WordPress is not the work. Maintaining it is, and it does not stop.

The scale of that work has a real number behind it, and it is larger than most people expect. Patchstack's State of WordPress Security in 2026 recorded 11,334 new vulnerabilities across the WordPress ecosystem in 2025, up 42% year on year — 91% of them in plugins, 9% in themes, and six in core, all rated low risk. New holes are typically exploited within about five hours of disclosure. Read that carefully: the problem is essentially never WordPress core. It is what you bolted onto it. Every plugin you install is a second piece of software with its own update schedule, and a site with twenty plugins has twenty things that need checking, not one.

There is no official hours-per-year figure for this — anyone who quotes you one is guessing — but the shape of the job is concrete: applying core updates, applying plugin and theme updates promptly rather than batching them once a quarter, verifying a plugin update did not break something before walking away, and keeping backups current enough that a bad update is a five-minute restore instead of a rebuild. On managed hosting a meaningful share of that is handled for you, which is most of what the extra $25 to $30 a month is actually buying. On shared hosting it is entirely yours, indefinitely, for as long as the site is live. That is the real thesis of this whole comparison: the choice between .com and .org is mostly a choice about whether you want to be the person who does that work, not a choice about features.

What actually moves if you switch

Portability is where WordPress.org has a genuine, structural advantage over every hosted builder in this space, WordPress.com included — but it is worth being precise about what "portable" means here, because it is less than the word implies.

Content moves cleanly. Posts, pages, media and comments export as XML and import into any other WordPress install without much drama; this is the same underlying database structure regardless of host. What does not move cleanly is everything wrapped around that content: a theme built for one host's caching layer, plugins tied to a specific hosting environment, custom code that assumed a particular server configuration. Moving self-hosted WordPress from one host to another is a real, well-trodden process — plenty of hosts will do it for you as a sales incentive — but "moving" a WordPress.com site to self-hosted WordPress.org is closer to a rebuild with a content import than a lift-and-shift, because WordPress.com's plan structure and built-in features have no self-hosted equivalent to move into.

Compare that with a platform switch off WordPress entirely, which is a different and harder problem covered in moving from WordPress to Squarespace: there the content format itself has to change, not just the hosting underneath it. And the underlying economics of why any of this matters — why a $1-a-month intro price is not the real price, why "free" software still costs real money once hosting and time are counted — is the subject of how website builder pricing actually works. The pattern generalizes past WordPress: what platform lock-in actually costs you is rarely the sticker price, it's the rebuild you didn't budget for.

Who neither one is right for

If you have read this far weighing plugin costs against hosting renewal tables, it is worth asking whether you are the audience for either product. WordPress, in both forms, is built for sites that grow: a blog with years of posts, a business site with a service catalog that changes, a publication with an editorial workflow, anything with a genuine content model behind it. That is what the plugin ecosystem and the CMS architecture are for, and for that job WordPress in either form earns the recommendation it gets.

If what you actually have is one person and one page — no blog, no catalog, nothing that needs updating on a schedule beyond a phone number or a project list — WordPress is a disproportionate amount of software for the job, in either form. That is the reader this whole comparison was implicitly written for at the start, and it is the reader for whom the honest answer is not "which WordPress" but "not WordPress." A one-page CV site does not need a database, a plugin update cycle, or a security bulletin to watch. It needs a page that exists and stays online, which is precisely the narrower job reach is built for and WordPress, deliberately, is not.

The people WordPress is right for and the people reach is right for are, mostly, different people asking different questions. The mistake is answering the second question with the first product because the name is more familiar.