One question comes up constantly from people evaluating WordPress.com: can you install other software on it? The honest answer depends heavily on which plan you’re on, and understanding the actual limitations matters before committing to the platform for anything beyond a simple blog.
It’s a fair question to ask, and the confusion behind it is understandable. WordPress itself has a reputation for near-limitless flexibility, thousands of plugins, endless customization, and WordPress.com carries the same brand name. The reality on the hosted platform is narrower than that reputation suggests, at least until a certain plan tier.
WordPress.com vs. WordPress.org: The Distinction That Actually Matters
Before getting into specifics, the WordPress.com and WordPress.org difference needs to be clear, since most confusion about software installation traces back to conflating the two.
WordPress.com is a hosted platform. Automattic runs the servers and handles security patches, managing updates behind the scenes. In exchange for that convenience, you give up direct file system and server access.
WordPress.org is the open-source software itself, which you download and install on your own hosting account. Self-hosting this way gives you complete control: any plugin, any theme, any custom code, any server-level configuration.
This guide focuses on WordPress.com specifically, since that’s where the real limitations live.
What You Actually Can and Can’t Install on WordPress.com
Plugins
On the Free plan, and on Personal and Premium above it, third-party plugin installation isn’t available at all. You’re limited to whatever built-in features WordPress.com bundles for that plan tier: basic SEO tools and social sharing, plus a curated set of blocks.
The Business plan and above change this significantly, unlocking the ability to install plugins from the WordPress.org repository, similar to a self-hosted site. This is the plan tier most people actually need if plugin functionality matters to the project.
Themes
Free and lower-tier plans restrict you to WordPress.com’s curated theme library. You can customize colors and fonts, plus some layout options, within a given theme, but you can’t upload a custom theme file.
Business and eCommerce plans allow custom theme uploads, as long as the theme is compatible with the WordPress.com environment (a handful of edge-case incompatibilities exist around certain server-level functions that self-hosted themes sometimes assume are available).
Custom Code
Lower-tier plans offer minimal ability to inject custom CSS, and essentially none for custom PHP or JavaScript. Higher-tier plans (Premium and up for CSS specifically, Business and up for broader code injection) loosen this, but it’s still more restrictive than the completely open code environment a self-hosted install provides.
What the Business Plan Actually Unlocks
The Business plan is the meaningful upgrade tier for anyone who’s hit a wall with the free or lower plans. It includes:
Plugin installation from the full WordPress.org plugin repository, not just a curated subset. This is the single biggest functional change compared to lower tiers.
Custom theme uploads, letting you bring a purchased or custom-built theme rather than working within WordPress.com’s own library.
SFTP and database access, which is a genuinely significant unlock for anyone who wants to work with the site more directly, closer to how a self-hosted install functions, without fully leaving the managed WordPress.com environment.
What This Looks Like for Someone Trying to Build a Community
This limitation shows up most sharply for people planning to build a membership site, forum, or community around a WordPress.com install, since that kind of functionality almost always depends on a specific plugin rather than anything WordPress.com’s built-in toolset covers. A tool like BuddyPress, which turns a WordPress site into a full social network with member profiles and groups, plus a live activity stream, simply cannot run on WordPress.com below the Business tier, since it requires plugin installation the lower plans don’t allow.
This is a common point where someone evaluating WordPress.com for a community project realizes the platform’s simplicity comes at the cost of exactly the functionality they need. For genuinely community-focused builds, this is usually the moment worth stepping back and comparing the total cost of a Business-tier WordPress.com plan against a self-hosted setup, since a self-hosted install running any community plugin has unrestricted access to it from day one.
The same reasoning applies to forums, job boards, event listings, and directory sites, which are all functionality categories that depend on a specific plugin rather than anything a general-purpose managed platform bundles by default. Before settling on WordPress.com for any project with this kind of structured, non-blog functionality at its core, confirm the required plugin actually runs on the plan tier being considered, not just that WordPress.com supports plugins in general at the Business level.
Comparing the Real Costs
The Business plan’s annual cost is worth putting next to a self-hosted alternative directly, since the math isn’t always obvious upfront. WordPress.com Business bundles hosting, the platform’s managed updates, and support into one price. A self-hosted equivalent needs separate hosting (which can range from a few dollars a month on shared hosting to considerably more for managed WordPress hosting with similar support quality), plus the free WordPress.org software itself, plus whichever plugins the project actually needs, most of which have free versions covering core functionality with paid upgrades for advanced features.
For a simple site needing just one or two plugins, the two paths often land in a similar price range. For a site needing extensive plugin functionality (community features, advanced ecommerce, membership gating, multiple integrations), self-hosting tends to come out ahead on cost, since WordPress.com’s Business tier doesn’t get more expensive as you install more plugins, but the overall value proposition shifts once you’re already paying for flexibility you’d get for less elsewhere.
What About Managed WordPress Hosting as a Middle Ground?
Managed WordPress hosting providers (as opposed to WordPress.com itself) offer a genuinely useful middle ground worth knowing about. These are third-party hosting companies that run self-hosted WordPress.org sites but handle much of the technical maintenance burden that scares people away from self-hosting in the first place: automatic backups and security monitoring, staging environments, plus performance optimization tuned specifically for WordPress.
The key difference from WordPress.com: these hosts run the actual open-source WordPress.org software, meaning full plugin and theme access from the start, without needing to hit a specific pricing tier to unlock it. The tradeoff is that you’re managing one more vendor relationship (the hosting provider) rather than everything bundled under one WordPress.com account, and the support experience varies more between providers than it does within WordPress.com’s standardized tiers. For a lot of small to mid-sized businesses that outgrow WordPress.com’s lower tiers, this managed self-hosting middle ground ends up being the actual destination, rather than either WordPress.com Business or fully unmanaged self-hosting.
Why WordPress.com Restricts This in the First Place
The restrictions aren’t arbitrary. They exist because WordPress.com is a shared, managed platform running enormous numbers of sites on shared infrastructure. Unrestricted third-party plugin installation is one of the most common vectors for security vulnerabilities and performance problems on self-hosted WordPress. A poorly coded or abandoned plugin can introduce a vulnerability, slow down a server, or conflict badly with other software. By restricting installation on lower tiers, WordPress.com keeps its shared infrastructure stable and secure without needing every site owner to personally manage plugin security and updates. The tradeoff is control in exchange for that managed stability, which is precisely the value proposition WordPress.com is built around.
Alternatives If WordPress.com’s Limits Are a Dealbreaker
Migrate to Self-Hosted WordPress.org
This is the most complete solution if the site genuinely needs plugin and theme flexibility WordPress.com’s lower tiers don’t offer. Self-hosting means picking a hosting provider, installing WordPress, and taking on the responsibility for updates and security yourself, or via a managed WordPress host that handles that layer for you while still allowing full plugin access. Migration tools exist to move existing WordPress.com content over, though the process needs planning around DNS and URL changes, and around any WordPress.com-specific features that don’t have a direct self-hosted equivalent.
Use External Services Alongside WordPress.com
For specific needs (advanced analytics, email marketing, specialized forms), many third-party services offer WordPress.com-compatible integrations through embeds, widgets, or their own APIs, without needing a plugin installed directly on the site. This can partially close the functionality gap without a full migration.
Upgrade to Business or eCommerce
If the WordPress.com ecosystem otherwise fits (you like the managed hosting, the support, the simplicity), upgrading to a higher tier might solve the specific limitation without needing to migrate anywhere at all.
Working Within WordPress.com’s Constraints on Lower Plans
If migration or upgrading isn’t in the cards, there’s still a fair amount that can be done within the existing limits.
Make full use of what’s actually bundled into your plan. WordPress.com includes a genuinely capable set of built-in blocks and tools that cover more ground than people initially assume, particularly for SEO basics and social sharing, plus simple contact forms.
Review the plugins that are available on your specific tier. Even lower tiers usually include some pre-approved plugin options covering the most common needs, even if the full repository isn’t open.
On Premium and higher, use the custom CSS tool for layout and styling adjustments that don’t require a full plugin, which covers a surprising amount of visual customization without touching the plugin restriction at all.
Keep the site and its bundled tools updated and configured properly, since WordPress.com handles core updates automatically, but plan-specific settings and integrations still need periodic review to make sure they’re set up correctly.
Look into the Jetpack integration specifically, since a meaningful chunk of what would otherwise require a third-party plugin on a self-hosted site is already built into WordPress.com through Jetpack’s feature set, just presented as native platform features rather than something you install separately. This includes things like related posts and basic SEO tools, along with simple site statistics, all without needing plugin access at all.
A Practical Way to Decide Which Path Fits
The decision usually comes down to a few honest questions. Does the project need a specific plugin that WordPress.com’s built-in tools genuinely can’t replicate? Is the budget there for a Business-tier upgrade, or would that cost roughly match a modest self-hosted plan anyway? And is the appeal of WordPress.com really the managed simplicity, or is it just familiarity with the brand name?
If a specific plugin is the blocker and the Business plan’s price is comparable to what self-hosting plus a managed host would cost, the calculus often favors self-hosting, since it removes the ceiling entirely rather than raising it to one specific tier. If the appeal is genuinely the hands-off management and a Business-tier upgrade solves the immediate need, staying on WordPress.com and upgrading is the simpler path.
There’s no universally correct answer here, and that’s fine. The right call depends on the specific project’s requirements and budget, plus how much ongoing technical work someone is realistically willing to take on, not on which platform has the bigger reputation.
A Checklist Before Committing to Either Path
Before signing up for a WordPress.com plan or committing to self-hosting, it’s worth confirming a few specifics rather than assuming based on general reputation.
List the exact plugins the project actually needs, not just a vague sense of “flexibility.” Check each one against WordPress.com’s plugin restrictions for the plan tier under consideration, since the answer is genuinely binary: either it’s allowed on that tier or it isn’t.
Estimate realistic traffic and growth over the next year or two, since WordPress.com’s managed infrastructure scales differently than a specific self-hosted plan would, and the right choice can depend on projected size as much as current size.
Factor in who will actually be doing ongoing maintenance. WordPress.com’s managed update process is a genuine advantage for someone without the time or interest in handling WordPress core and plugin updates themselves. Self-hosting, even through a managed WordPress host, still requires more active oversight.
Check whether the project has genuinely non-negotiable functionality requirements (a specific membership system, a particular ecommerce integration, a community plugin) before signing up for a lower-tier WordPress.com plan and discovering the limitation only after content and design work has already gone in.
Frequently Asked Questions
Can I install WooCommerce on WordPress.com? Yes, but only on the eCommerce plan, which is specifically built around it. Lower tiers don’t support WooCommerce installation at all.
Does upgrading to Business give me full server access like a self-hosted site? Not entirely. You get SFTP and database access, along with plugin and theme flexibility, but WordPress.com still manages the underlying server infrastructure and hosting environment, along with core updates. It’s a middle ground, not full server ownership.
Can I switch from WordPress.com to self-hosted WordPress.org later without losing content? Yes, WordPress.com provides export tools, and migration plugins on the self-hosted side can import that content. Media transfers reasonably well, and so do posts and pages, but some WordPress.com-specific features (certain blocks, built-in stats) don’t have a direct self-hosted equivalent and need a replacement plan.
Is the Business plan worth it just for plugin access? That depends entirely on how much the specific plugin functionality matters to the project, and how that annual cost compares to a self-hosted alternative. For a site that needs one or two specific plugins and otherwise likes the WordPress.com experience, it’s often worth it. For a site that needs deep plugin flexibility, self-hosting usually ends up more cost-effective in the long run.
Can I downgrade from Business back to a lower plan later without losing my installed plugins’ data? Downgrading typically deactivates plugins that aren’t supported on the lower tier, and any data they generated may become inaccessible until you either reinstall on a supporting plan or export it beforehand. It’s worth treating a downgrade as seriously as an upgrade, with a backup taken first.
Does WordPress.com support custom post types, which some plugins rely on? On the Business plan and above, yes, since custom post types are typically registered by a plugin or theme, both of which become available at that tier. Lower tiers don’t support this, since it depends entirely on the same plugin access that’s restricted.
Are there any plugins available on lower WordPress.com tiers at all? Yes. WordPress.com bundles a set of built-in features that function similarly to popular plugins (a Jetpack-powered feature set covering things like basic stats and social sharing, plus simple contact forms) without requiring separate plugin installation. It’s a curated subset rather than the open plugin repository, but it covers more ground than a lot of people expect going in.
Conclusion
WordPress.com offers a more managed, streamlined experience than self-hosted WordPress.org, and that comes with real restrictions on installing external software, particularly on the free and lower-tier plans. The platform is built to trade flexibility for stability and simplicity, which is a reasonable tradeoff for a lot of site owners and a genuine dealbreaker for others.
If WordPress.com’s limitations are blocking something the project actually needs, either the Business plan upgrade or a full migration to self-hosted WordPress.org resolves it, depending on how deep the flexibility requirement actually goes. Understanding exactly which plan tier unlocks what, before committing, saves a lot of frustration down the line.
The mistake to avoid is building content and design on a lower tier, then discovering months in that a genuinely needed plugin simply isn’t available. Test the actual constraint against the actual requirement before that investment goes in, not after.
