WordPress.com has enabled WordPress.com plugins on every paid plan, starting at the Personal tier, and it was overdue. For anyone who has been in this ecosystem a while, the plugin lockout was the one thing that pushed small businesses onto the $25/month Business plan long before they needed anything else that came with it.
What actually changed
The walled garden on the lower tiers used to be a recurring argument with clients. You either found a hacky workaround or explained why one contact form plugin tripled their hosting bill. The gate is open now, but there is still a hierarchy underneath it, and it is worth understanding before you rethink which plan you put people on.
You get the 50,000+ plugins from the directory, but the lower tiers still run in a shared environment. SFTP, SSH and WP-CLI stay locked until the Business tier. So when a plugin takes a site down with a white screen of death, a Personal plan leaves you leaning on the WordPress.com automated recovery tools instead of a quick wp plugin deactivate in a terminal.
Global styles and custom CSS
The second half of the change matters as much as the WordPress.com plugins part: Global Styles and Custom CSS are included too. Instead of loading extra stylesheets for small tweaks, you work with the site’s theme.json logic directly. If you would rather write CSS than drag blocks around, having it at the code level is what keeps the markup clean.
A spacing override is a good example of something the Global Styles UI will not quite cover:
/* Custom CSS for refined layout control */
.wp-block-group.custom-container-padding {
padding-top: clamp(2rem, 5vw, 5rem);
padding-bottom: clamp(2rem, 5vw, 5rem);
margin-inline: auto;
}
/* Ensure accessible focus states for custom plugins */
.custom-plugin-form input:focus {
outline: 2px solid var(--wp--preset--color--primary);
outline-offset: 2px;
}Where the Business plan still wins
If you manage high-traffic WooCommerce sites or complicated integrations, the Personal plan will not cover you. Staging and the developer tools are still limited to the Business and Commerce plans, and shipping code without testing it somewhere first is how professional workflows break.
For agencies, the higher plans are mostly about infrastructure: automated backups with one-click restores, plus uptime monitoring. I have watched enough “managed” hosts fall over during a traffic spike to value that. The Business tier also performs better, with 8x the storage and dedicated resources for heavy PHP work.
I have written more about why managing servers is often a trap for agencies and how to put together a smarter agency stack with these tools.
If this kind of work is eating your dev hours, I can take it on. I have been working with WordPress since the 4.x days.
Which plan to pick
Opening the plugin directory to the cheaper plans makes WordPress.com competitive for the prosumer market. It does not remove your job of telling clients where the lower tiers stop. Anyone who needs Git integration or a real CI/CD pipeline is still on the Business plan. Pick the plan that fits the workflow rather than the one with the longest feature list.
