WordPress.com Review (2026): After the plugin restrictions are lifted, is it still worth choosing?

A lot of people still think of WordPress.com as "the cheap plan that won't let you install plugins." That impression is outdated now. On April 2, 2026, Automattic made a policy change that's bigger than it first appears: plugin and theme access opened up across all paid plans, including the entry-level Personal tier. This is the kind of update that deserves its own breakdown, honestly, because it directly undercuts what countless review articles have spent years calling WordPress.com's biggest flaw. I went back and retested the current plan structure. My conclusion: the restriction genuinely loosened, but the gap between WordPress.com and self-hosted WordPress didn't disappear — it just moved somewhere else.

First, Let's Clear Up a Common Confusion

New users fall into this trap every year, so it's worth addressing upfront: WordPress.com is not the WordPress homepage.

WordPress.org is the open-source software itself — free to download, and you find your own server to install it on. WordPress.com is Automattic's managed hosting platform, and conceptually it's actually closer to Wix or Squarespace's product logic. You never touch a server, but in exchange, the platform retains more control over your site than self-hosting would allow.

Both run on the same WordPress core. The operating models, though, are nothing alike.

With Plugin Restrictions Gone, Where's the Real Difference Between Plans Now

This is the question worth actually digging into after this update.

Under the old rules, plugin access was the dividing line between tiers — cheap plans got none, pricier plans got plugins. Now that every paid plan supports plugins, the differentiation shifted to other things:

Verify these numbers on the official site before relying on them — different sources report slightly different figures depending on whether they're quoting monthly vs. annual billing, or capturing a promotional price at a different point in time.

The real dividing line sits at the Business plan — it's the only tier with SFTP/SSH access. In other words, even with plugins unlocked everywhere, if you want direct filesystem access or deeper backend customization, you still need to jump up to Business or above.

Plugins Are Open Now — But Whether WooCommerce Actually Runs Well Is a Separate Question

This is where I think a lot of review content gets sloppy: being able to install a plugin isn't the same as that plugin running well on WordPress.com's infrastructure.

WooCommerce and similar e-commerce plugins are resource-hungry — they lean heavily on server resources and caching strategy, and that's a different question from simple plugin compatibility. The Commerce plan is specifically optimized for WooCommerce, bundling store themes, inventory management, and real-time shipping — and it's currently the most sensible option for running e-commerce on WordPress.com. But the price point is creeping close to dedicated WooCommerce hosting providers at this stage.

If you're serious about building a long-term e-commerce site, here's what I'd actually do: run on Commerce for a few months first, watch how page load speed and checkout flow hold up under real traffic, then decide whether migrating to Cloudways or a specialized WooCommerce host makes sense. Skipping that test period entirely and jumping straight to a self-managed VPS is, for most sellers without ops experience, the riskier move — not the safer one.

Security Is WordPress.com's Underrated Advantage

The platform blocks millions of malicious requests across all sites every single day. Self-hosted WordPress users trying to match that level of protection typically need to add Wordfence or Sucuri subscriptions on top — running $200 to $500 a year. That's a hidden cost people frequently leave out of the math when they're arguing self-hosting is cheaper. Security plugin subscriptions rarely make it into that comparison.

On top of that, every WordPress.com site runs in its own isolated environment — if someone else's site gets compromised, it doesn't spread to yours. That's a fundamentally different risk profile than budget shared hosting, where one compromised site on the server can take down everyone else sharing it. If budget constraints originally pushed you toward cheap shared hosting, this isolation difference is worth weighing again.

Is It Worth It? Depends Which Category You're In

WordPress.com fits: personal blogs, portfolio sites, small showcase sites without deep backend customization needs. With plugins unlocked, even the Personal plan can now run basic plugins — meaningfully lowering the barrier for pure content creators.

The group most affected by this change: anyone who previously walked away from WordPress.com because a specific plugin they wanted was locked behind plan restrictions. Worth a second look now.

Still not recommended for: developers who need direct SSH server access; high-traffic SEO content sites with strict page-speed requirements (caching strategy and server-level tuning freedom still falls short of a VPS); and budget-conscious users with their own ops skills who don't mind handling security and backups themselves — this group gets more freedom for less money on a VPS or Cloudways.

My Take

This plugin rollout is the most substantive product change WordPress.com has made in years, and it earns a fresh look — especially if plugin restrictions were the reason you walked away before. But the things this update doesn't fix are still there: server control, the freedom for deep performance tuning. Those are inherent tradeoffs between managed platforms and self-hosting, and no policy change erases that line entirely.

My advice: figure out whether what you actually need is "convenience" or "control." That question hasn't changed. What's changed is that choosing convenience now costs you a little less than it used to.