WordPress Hosting

WordPress.com vs. WordPress.org: The Difference That Actually Matters

They share a name and almost nothing else. Here's who owns the site, who controls it, and what each one actually costs.

Quick Answer: WordPress.org is the free, open-source software you install on hosting you control — full ownership, full plugin and theme access, no platform limits. WordPress.com is a hosted platform built on that same software, but it rents you a version of it: the free tier caps you at a subdomain with no custom plugins, and every paid tier still routes your site through WordPress.com's infrastructure and terms of service rather than giving you an independently owned environment. For a website a business depends on for leads, sales, or credibility, that distinction — ownership versus tenancy — matters more than any feature checklist.

Want the Infrastructure Without Building It Yourself?

Starter gets you a complete self-hosted WordPress foundation — hosting, security, and updates handled — whether you're building new or moving off WordPress.com.

The Name Is the Same. The Product Is Not.

Most confusion about WordPress.com versus WordPress.org starts from a reasonable but wrong assumption: that they're two editions of the same product, like a free tier and a pro tier. They're not. WordPress.org is the software itself — the open-source CMS that powers roughly 43% of all websites — released free for anyone to download and run on hosting of their choice. WordPress.com is a company (Automattic) that took that same open-source software and built a hosted, managed platform on top of it, then sells access to that platform in tiers.

So the real comparison isn't "which WordPress is better." It's "do you want to own and run the software yourself — with a host of your choosing handling the server — or do you want to rent space inside someone else's platform built from that software." Once it's framed that way, most of the individual feature comparisons other guides walk through resolve themselves.

Ownership Is the Actual Dividing Line

On WordPress.org, self-hosted, you own the WordPress installation, the domain, the database, and every file on the server. You can move hosts whenever you want, install any plugin from the official repository or a third party, install any theme, and modify the code directly if you need to. Nothing about the platform can restrict what your site does — the limits are whatever your hosting environment and your own decisions impose, not a platform's terms of service.

On WordPress.com, you're operating inside Automattic's infrastructure under Automattic's terms. The free and lower-tier plans block custom plugin installation and most themes entirely. Higher tiers unlock more, including eventually the ability to install plugins and use a custom domain, but you're still bound by what WordPress.com permits at that tier, and the site itself doesn't move with you the way a self-hosted install does — migrating off WordPress.com later means exporting content and rebuilding the site elsewhere, not just changing a setting.

The Cost Comparison Nobody Runs All the Way Through

WordPress.com's pricing looks simpler on the surface — pick a plan, pay monthly, done. But the comparison usually stops before it accounts for what you actually get at each tier. The free plan carries WordPress.com branding and a subdomain (yoursite.wordpress.com), which is a non-starter for any business. The paid tiers step up from there, and the tier that actually unlocks plugins, a real business use case, and ecommerce functionality is priced well above the entry plans that most comparisons lead with.

Self-hosted WordPress.org has a different cost shape: the software is free, but hosting is not optional — it's just unbundled, so you're choosing your own host and price point instead of accepting one bundled into a platform fee. Basic shared hosting is inexpensive but leaves updates, security, and performance entirely on you. Managed WordPress hosting sits in between — a fixed monthly cost that includes the operational work, while you still own the site outright. The honest comparison isn't "free versus paid." It's "what you're actually getting for the money on each side," and ownership doesn't show up on either price tag.

Monetization and Ads: Where WordPress.com's Limits Actually Bite

This is the one place the platform difference has an immediate, visible business impact. WordPress.com's free and lower-tier plans place WordPress.com's own advertising on your site — ads you don't control and don't get paid for. Running your own ads, affiliate links, or a store requires a specific paid tier, and even then you're operating within WordPress.com's monetization policies rather than making that call yourself. A self-hosted WordPress.org site has no platform-level restriction on monetization at all; whatever the business wants to run, it runs, with no tier gate in the way.

Plugins and Themes: The Feature Gap That Actually Matters

WordPress's real strength — for either version — is its plugin and theme ecosystem: tens of thousands of extensions covering everything from SEO to forms to page building to ecommerce. Self-hosted WordPress.org has unrestricted access to all of it, official repository and third-party alike. WordPress.com restricts this by tier, and even at the tiers where plugin installation is allowed, it's typically capped to certain business or ecommerce plans rather than open the way it is on a self-hosted install. For any business site that will eventually need a specific form plugin, an SEO tool, a booking system, or a custom integration, this is usually where WordPress.com stops being viable and a migration conversation starts.

So Which One Should You Actually Choose?

WordPress.com's case is narrow but real: a personal blog, a hobby project, or someone who wants to publish with zero technical setup and doesn't need a specific plugin, a custom domain identity, or monetization control. If that's the entire use case, the convenience is a legitimate tradeoff.

For anything commercial — a business that needs the site to generate leads, process sales, represent the brand credibly, or integrate with other tools over time — self-hosted WordPress.org is the better foundation almost without exception. The ownership, the unrestricted plugin access, and the absence of a platform ceiling on what the site can become all matter more, long-term, than WordPress.com's setup convenience. The only real objection to WordPress.org is the maintenance workload it creates, and that objection has a direct answer.

The Maintenance Objection Isn't a Reason to Choose WordPress.com

Self-hosted doesn't mean self-managed. This is the part most comparisons of these two platforms skip entirely: the actual tradeoff WordPress.com is selling — someone else handles the server so you don't have to think about it — is available on WordPress.org too, without giving up ownership to get it. Managed WordPress hosting takes on the updates, the security hardening, the backups, and the performance work, while the site, the domain, and every plugin decision stay yours. You get WordPress.com's convenience argument and WordPress.org's ownership, at the same time, instead of trading one for the other.

Martin Van Den Boogerd
Martin Van Den Boogerd
Founder & Owner, CriticalWP — background in cybersecurity and municipal government infrastructure
More about Martin →

Common Questions

WordPress.com has a free tier, but it puts WordPress.com branding on your site, blocks custom plugins and most themes, and gives you a subdomain instead of your own domain. Getting a real domain, removing ads, and unlocking plugins requires moving to a paid WordPress.com plan — at which point you're paying recurring fees for a platform that still limits what you can install and where your site can move to. WordPress.org itself is free open-source software; what you pay for is hosting, which is required either way.
For a business that depends on its website for leads, sales, or customer service, self-hosted WordPress.org is almost always the better choice. It allows full plugin and theme access, direct control over performance and security configuration, and no platform-imposed limits on what the site can do as the business grows. WordPress.com's business-tier plans narrow this gap but still route the site through WordPress.com's infrastructure and terms of service rather than an independently owned hosting environment.
Yes, but it's a real migration, not a settings toggle. Content, media, and (on paid plans) the domain can generally be exported and moved, but themes, page layouts, and any WordPress.com-specific blocks or plugins typically don't transfer and have to be rebuilt on the new host. It's easier to start on self-hosted WordPress.org if there's any chance the site will need to scale, sell, or integrate with other systems later.
No. Self-hosted doesn't mean self-managed. Managed WordPress hosting handles the server, updates, security hardening, and backups, while you keep full ownership of the site, the domain, and every plugin and theme decision. The tradeoff WordPress.com sells — convenience in exchange for platform limits — is available on WordPress.org too, without giving up ownership to get it.
It can be, if it's left unmanaged — someone has to handle core, theme, and plugin updates, monitor for security issues, and keep backups current. That workload is exactly what managed WordPress hosting is built to remove. It's not a reason to choose WordPress.com; it's a reason to choose a managed host on WordPress.org instead of running the server yourself.

Own your site. Skip the maintenance workload.

Starter gives you a complete self-hosted WordPress foundation — infrastructure, security, and updates handled from day one — for a new build or a WordPress.com migration.