WordPress.org or WordPress.com: The Hosted-vs-Self-Hosted Fork

WordPress.org vs WordPress.com is the fork people hit after they already said “I want WordPress.” The names share a root. The jobs do not.

This page is the Hosted-vs-Self-Hosted Fork. It is not WordPress vs Ghost vs Wix (three platforms). If you are still choosing a CMS family, stop there first.

WordPress.org is software you install on hosting you control. WordPress.com is a hosted product with plan limits. Pick by plugins, ops, and what you will actually renew—not by which logo appeared in a YouTube intro.

Disclosure: CashPilot may earn a commission if you buy hosting or tools through links we add later. Verify current plans on official WordPress pages. No invented speed tests.

Table of contents

1. Who this fork is for
2. The Hosted-vs-Self-Hosted Fork
3. What both still require
4. WordPress.org: when it fits
5. WordPress.com: when it fits
6. Plugin and theme gates without screenshots
7. What the name cannot fix
8. FAQ

Who this fork is for

Use this if you already lean WordPress and someone said “just get WordPress.com” or “just install .org.” Skip it if you need Ghost or Wix—that is a different matrix.

You will still need a domain. Naming mistakes are a separate job: Domain Name Mistakes New Bloggers Still Make.

Official split, last reviewed on WordPress.com’s side in August 2026: WordPress.com vs WordPress.org. Project-side wording: WordPress.org on the two products.

The Hosted-vs-Self-Hosted Fork

Score each line 0 or 1. The higher column is a lean, not a trophy.

     HOSTED-vs-SELF-HOSTED FORK
  ┌──────────────────────────┬─────┬─────┐
  │ Job                      │ .org│ .com│
  ├──────────────────────────┼─────┼─────┤
  │ I will pick my own host  │  □  │     │
  │ I want hosting bundled   │     │  □  │
  │ I need arbitrary plugins │  □  │  ?  │
  │ I want fewer server tabs │     │  □  │
  │ I accept plan feature    │     │  □  │
  │   gates                  │     │     │
  └──────────────────────────┴─────┴─────┘
  ? = only if the current .com plan lists it

Tie? Prefer the path where you can restore a backup without a second YouTube tab. Restores beat launch-day dashboards. Pair with Blog Backup Basics.

What both still require

Both still need a domain people can type, HTTPS, and posts that are worth indexing. Neither product writes your niche for you. Gutenberg exists in both worlds; a heavy page builder is a separate editor split.

WordPress.com’s official table is honest that you own your content on either path. That is not the same as “the move is free in hours.” Export, DNS, and a Restore Kit still take a weekend if you have years of media.

WordPress.org: when it fits

Official software: WordPress.org. You download it, point DNS at a host, and you own the file system—within that host’s rules.

It fits when:

• You already picked a host (or you will, via Web Hosting for Small Blogs)
• You need plugins, mu-plugins, or PHP tweaks the hosted product may still block
• You want a staging clone your host provides

Cost is not “free.” Domain + hosting + extras. Hostinger-class vs SiteGround-class is a later split: Hostinger vs SiteGround for Bloggers. Do not treat this fork as that comparison.

WordPress.com: when it fits

Official product: WordPress.com. Plans bundle hosting. You do not buy a second host for the same site.

It fits when you want fewer server decisions and you can live inside those gates for a year. WordPress.com’s own overview is built around managed hosting: updates, security, and backups as product features, not as a plugin you hunt.

It is a weaker fit when your whole plan is “upload a custom plugin zip and edit PHP on day one.” Check whether that plan even allows it. SEO plugin fit, if you later self-host, is Rank Math vs Yoast.

Plugin and theme gates without screenshots

Do not trust a 2023 blog that said “plugins only on Business.” WordPress.com’s current official comparison says plugins install on paid plans, with automatic updates, and that the platform blocks potentially risky plugins. Custom themes still depend on the eligible plan.

Self-hosted .org can install almost anything that runs on your PHP version. That freedom includes the freedom to break the site. The Restore Kit still applies.

If you later want a WordPress-aware ops product rather than Automattic’s hosted plans, that is Managed WordPress Hosting—an upgrade question after you already chose .org, not this fork.

What the name cannot fix

• A 4 MB hero image
• Thin posts competing for one keyword
• Skipping HTTPS and mixed-content cleanup
• Buying managed WordPress you do not need yet

Fill the fork once. Buy one path for twelve months. Then write posts—not a third “which WordPress” tab.

FAQ

What is the difference between WordPress.org and WordPress.com?

.org is installable software. .com is a hosted product with plans. Confirm both official sites. Same editor family, different ops.

Which is better for a new blogger?

Score the fork. .com is often simpler. .org is more open if you will run your own host.

Is WordPress.org free?

The software is. Hosting and domain are not.

Can I use any plugin on WordPress.com?

Only if the current paid plan says so, and only if the platform does not block it. Verify the live comparison table.

Is this WordPress vs Ghost vs Wix?

No. Different intent. Three platforms vs two WordPress products.

Can I move later?

Yes, with official export/import. Budget time. You own the content; you still do the work.

Do I need hosting on WordPress.com?

Hosting is part of the product plans. Do not pay a second host for the same site.

Where do I verify?

WordPress.org and WordPress.com vs .org support.