WordPress.com vs. Self-Hosted WordPress

The confusion is understandable: WordPress.com and self-hosted WordPress (sometimes called WordPress.org) both run on the same underlying software. But one is a hosted platform you sign up for, and the other is free software you install on hosting you choose yourself. That single difference changes what you're allowed to do with the site.

WordPress.com is a managed platform, not just hosting

When you sign up at WordPress.com, the company runs the servers, handles updates, and controls what you can install. Free and lower-tier plans restrict which themes you can use, block most plugins entirely, and place WordPress.com branding on your site. Higher-priced plans loosen these restrictions, but at that point the price often approaches or exceeds what independent hosting plus a domain would cost.

Self-hosted WordPress is software you install yourself

Self-hosted WordPress means downloading the free WordPress software from WordPress.org and installing it on a hosting account, whether that's general shared hosting or a plan built specifically for WordPress. You choose the host, the theme, and any plugin you want. Nothing is blocked by a platform operator, because there isn't one standing between you and the software.

Where the practical differences actually land

• Plugins: blocked or limited on most WordPress.com plans, unrestricted on self-hosted
• Themes: a curated list on WordPress.com, any theme on self-hosted
• Monetization: WordPress.com restricts ads and some e-commerce on lower plans
• Branding: WordPress.com shows its own branding unless you pay to remove it
• Ownership of hosting: WordPress.com controls the server, self-hosted lets you pick or switch providers
• Cost structure: WordPress.com bundles hosting and software into one plan; self-hosted separates domain, hosting, and software

Why plugins and themes matter more than they sound

A huge part of WordPress's reputation comes from its plugin ecosystem: contact forms, SEO tools, caching, e-commerce, membership systems, booking calendars. On a restricted WordPress.com plan, most of that ecosystem simply isn't available to you. If your plan for the site includes anything beyond a blog and static pages — selling products, running a members' area, building custom forms — check whether the plugin you need is even allowed before you commit to a tier.

The cost comparison isn't as simple as the sticker price

WordPress.com's paid plans bundle hosting, a theme, and the software into one monthly fee, which looks simpler than juggling separate charges for a domain and a hosting account. But compare like for like: the tiers that actually unlock plugins and custom themes, usually called Business or Commerce, often cost more per month than an independent WordPress-optimized hosting plan plus a domain bought separately. The bundling isn't a bad deal by default, it just isn't automatically the cheaper option either, and it's worth adding up both paths before assuming one wins on price.

Support means something different on each side

WordPress.com support comes entirely from the platform, since it's the only party responsible for how the site runs end to end. That can be genuinely convenient: there's one company to ask about anything, from a billing question to a broken page. Self-hosted WordPress splits that responsibility between your hosting provider, who handles server performance, uptime, and account-level issues, and you or a developer, who's responsible for the website's own plugins, configuration, and content decisions. Neither model is strictly better, but they answer different kinds of problems, so it's worth knowing which one you're actually signing up for before you need it.

What you're trading for the convenience

WordPress.com's appeal is real: no server to manage, no updates to schedule, no hosting account to configure. That convenience is worth something, particularly for someone who wants to write and never think about infrastructure. The tradeoff is that you're building on a platform whose rules can change, whose pricing tiers gate basic customization, and which you can't simply pack up and move without exporting content and rebuilding elsewhere.

What self-hosted actually asks of you

Self-hosted WordPress puts more decisions in your hands, and with that comes more responsibility. You pick the hosting plan, so you're responsible for choosing one with adequate resources. You install plugins, so you're responsible for keeping them updated. A good WordPress-optimized hosting plan handles server-level maintenance, security, and performance tuning, but core website decisions like which plugins to run and how to configure them stay with you.

SEO and analytics access work differently too

Self-hosted WordPress gives unrestricted access to SEO plugins, custom analytics setups, and direct control over technical details like sitemaps, structured data, and redirects. WordPress.com's lower tiers limit some of this, bundling basic SEO tools instead of letting you choose your own. That's fine for a personal blog, but it can matter more for a business site where organic search traffic actually brings in customers, and where fine control over technical SEO settings isn't optional.

A simple way to decide

If you want to write online with minimal setup, don't need custom plugins, and are comfortable with a platform's rules and branding, WordPress.com's paid tiers can work fine. If you plan to sell anything, need specific plugins, want full design control, or simply want the option to move hosting providers without rebuilding the site, self-hosted WordPress on an independent host is the more durable choice.

• Choose WordPress.com if you want a fully managed writing platform with minimal setup
• Choose self-hosted WordPress if you need specific plugins or full plan flexibility
• Choose self-hosted if you plan to run a store, memberships, or bookings
• Choose self-hosted if switching hosts later without a full rebuild matters to you

Both paths use the same software at their core, which is why the naming trips people up. The real decision is how much control you want over that software, and how much you're willing to hand to a platform in exchange for not managing it yourself.