WordPress.com to Self-Hosted: Your Real Options in 2026

You signed up for "WordPress" years ago, and now you're hitting walls: no plugins, ads you didn't ask for, or a pricing tier that keeps climbing. The fix is moving from WordPress.com to self-hosted — and you have more options than you think.

TL;DR: WordPress.com is a hosted service run by Automattic. Self-hosted WordPress (WordPress.org) is free software you install anywhere. If WordPress.com's limits are squeezing you, there are two exit paths: (a) export your content via XML and move to self-hosted WordPress, or (b) skip the WordPress baggage entirely and move to a modern self-hosted CMS. Both paths use the same export file. Both let you keep your domain, your URLs, and your search rankings — if you handle redirects properly. This guide walks through the differences, the costs, and the exact migration steps.

WordPress.com vs self-hosted WordPress: what's the actual difference?

WordPress.com is a commercial hosting service that runs WordPress for you, with restrictions that vary by plan. Self-hosted WordPress is the open-source software from WordPress.org, installed on hosting you control. Same core software, completely different ownership model — and many site owners don't realize they're on the restricted version.

Here's the confusion in one sentence: both products are called "WordPress," but only one of them is fully yours.

WordPress.com (run by Automattic):

• They host it, patch it, and back it up
• Plugin and theme installs are locked behind higher tiers
• The free plan shows their ads on your site — and you don't get the revenue
• You agree to their terms of service; they can suspend sites that violate them

Self-hosted WordPress (from WordPress.org):

• Free, open-source software (GPL)
• You pick the hosting, install any plugin or theme, edit any file
• You handle updates, security, and backups — or pay someone to
• Nobody can suspend you except your own host

If you've ever typed your site's address and seen yoursite.wordpress.com, you're on the hosted service. If you tried to install a plugin and got told to upgrade first, same thing.

Why do people leave WordPress.com?

Three reasons come up over and over: plugin restrictions on lower tiers, a pricing ladder that funnels everyone toward the expensive plans, and ads on the free plan. None of these are bugs — they're how the hosted business model works. The frustration starts when your site outgrows the tier you're paying for.

The plugin wall. As of 2026, installing your own plugins on WordPress.com requires the Business plan (around $25/month billed annually, more if billed monthly). That means SEO plugins, custom forms, redirect managers, membership tools — all locked until you're paying roughly $300/year. The Free, Personal (~$4/month), and Premium (~$8/month) tiers can't install plugins at all.

The pricing ladder. Each tier solves one annoyance and introduces the next. Free has ads and a .wordpress.com subdomain. Personal removes ads but won't let you monetize properly. Premium adds some design control. Business finally unlocks plugins. Commerce (~$45/month as of 2026) is the only tier with full store features. Most growing sites end up at Business or above — and at that price, self-hosting starts to look cheap. We broke down the full math in the hidden costs of WordPress.

Ads you don't control. The free plan displays WordPress.com's ads to your visitors. You can't remove them without paying, and you don't share in the revenue unless you join their separate ad program on a paid tier.

There's also a quieter reason: you don't fully own the platform. Your site lives under someone else's terms of service. For a hobby blog, fine. For a business, that's a dependency worth removing.

Your two exit paths

Path A is self-hosted WordPress: same software, your server, every plugin unlocked. Path B is a modern self-hosted CMS: you leave WordPress entirely and import your content into something newer. Path A is the familiar move; Path B trades familiarity for less maintenance and a cleaner stack. Both start from the same XML export.

Path A: Self-hosted WordPress

This is the classic move, and it's the right one if you depend on specific WordPress plugins (WooCommerce, a particular membership plugin, a page builder you love). You get:

• Full plugin and theme freedom from day one
• Hosting from ~$5–15/month on shared hosting, as of 2026
• A one-click WordPress importer that reads your WordPress.com XML export natively

The trade-off: you inherit WordPress's maintenance load. Core updates, plugin updates, plugin conflicts, security hardening, backup configuration — it's all on you now. The plugin freedom you wanted is also the attack surface you'll be patching.

Path B: A modern self-hosted CMS

If your site is mostly content — blog posts, pages, a contact form — you don't actually need WordPress. You need a CMS. Modern self-hosted options give you the ownership of Path A without the plugin treadmill, because features like SEO management, redirects, and an API ship in the core product instead of as third-party add-ons.

Full disclosure: we build UnfoldCMS, one of those options, so weigh our take accordingly. But the category is real and growing — we covered the broader movement in why teams are moving off WordPress in 2026.

The trade-off here: no one-click importer from WordPress.com (you'll convert content via the XML export or paste/import it through an API), and you leave the WordPress plugin ecosystem behind. For plugin-heavy sites, that's a dealbreaker. For content sites, it's usually a relief.

Want to see what the modern path looks like before committing? Compare your options on our migration page — it maps WordPress features to their modern equivalents.

Comparison: WordPress.com plans vs self-hosted WP vs modern self-hosted CMS

The short version: WordPress.com trades freedom for convenience, self-hosted WordPress gives you freedom plus a maintenance bill, and a modern self-hosted CMS gives you freedom with less to maintain. Prices below are approximate, as of 2026, billed annually.

If "self-hosted" itself is new territory for you, start with our complete guide to self-hosted CMS platforms — it covers hosting requirements, backups, and what "owning your stack" actually means day to day.

How to migrate from WordPress.com to self-hosted: step by step

The migration has five core moves: export your content as XML, set up the new home, import the content, point your domain, and set up redirects for any URLs that changed. Done carefully, your readers and your Google rankings come along with you.

1. Export your content. In WordPress.com, go to Tools → Export → Export All. You'll get a ZIP containing an XML file (WXR format) with your posts, pages, comments, and category structure. Media files are referenced by URL, not embedded — note that for step 3.
2. Set up the new home. Path A: install WordPress on your new host (most hosts have a one-click installer). Path B: install your chosen CMS — for example, UnfoldCMS runs on standard shared hosting with no queue workers or background processes required.
3. Import the content. Path A: Tools → Import → WordPress, upload the XML, and check "Download and import file attachments" so your images move too. Path B: convert the XML to your CMS's format — for UnfoldCMS that means creating posts through the admin or pushing them via the /api/v1/admin/posts REST endpoint, which supports full create/update/publish operations with a Sanctum token. Re-upload images to the new media library either way.
4. Move your domain. If you registered the domain through WordPress.com, either transfer it to a registrar you control or update its DNS to point at your new host. Domain transfers take a few days and your registration must be older than 60 days. Keep the WordPress.com site live until DNS settles.
5. Set up redirects and verify. Map every old URL to its new equivalent. Same permalink structure? Little to do. Changed structure (say, /2024/03/post-name/ to /blog/post-name/)? Every post needs a 301 redirect. Then crawl your site, fix broken internal links, and resubmit your sitemap in Google Search Console.

A few honest warnings:

• Themes don't migrate. The XML export carries content, not design. You'll rebuild or replace your theme on either path.
• WordPress.com-specific features don't migrate. Stats history, followers from the WordPress.com Reader, and built-in email subscriptions stay behind. Export your subscriber list separately before you close the account.
• Set up "Site Redirect" if you used a free subdomain. WordPress.com sells a paid Site Redirect upgrade that 301s yoursite.wordpress.com to your new domain. If you had real traffic on the subdomain, it's worth a year of it while Google reindexes.

What the redirect work looks like in practice

Redirects are where migrations live or die for SEO: every old URL that 404s leaks authority, and a structure change without 301s can drop your traffic for months. Whatever platform you land on, you need a way to create, import, and monitor redirects in bulk — not edit server config files one line at a time.

On self-hosted WordPress, you'd install a redirect plugin. On a modern CMS this should be built in. Using UnfoldCMS as the worked example (our product, disclosed above): the redirect manager supports 301 and 302 rules, CSV import for bulk migrations — export your old-URL-to-new-URL mapping from a spreadsheet and load it in one move — plus hit counters so you can see which redirects still get traffic, and an optional expiry date for temporary rules. Slug history is automatic on top of that: if you rename a post's slug after migrating, the old URL keeps resolving without you creating anything.

The same logic applies to the rest of the SEO surface. Sitemaps, robots.txt, JSON-LD structured data, and per-page meta titles and descriptions should regenerate themselves on the new platform — in WordPress that's typically a plugin's job; in UnfoldCMS those ship in core, alongside scheduled publishing, threaded comments, role-based access control, automatic WebP image conversions, and database-backed site search. Pricing depends on tier, so check the current plans rather than trusting a number in a blog post.

Ready to map your own migration? Start with the WordPress migration guide and get a realistic checklist before you export anything.

FAQ

Is WordPress.com the same as WordPress.org?

No. WordPress.org distributes the free, open-source WordPress software you install on your own hosting. WordPress.com is a commercial hosting service by Automattic that runs that software for you, with plan-based restrictions on plugins, themes, and monetization. The naming is genuinely confusing, and it trips up site owners constantly.

Will I lose my Google rankings when I move from WordPress.com to self-hosted?

Not if you keep the same domain and set up 301 redirects for any URLs that change. Expect some ranking wobble for a few weeks while Google recrawls. The risky cases are changing domains and changing permalink structure at the same time — do one move at a time if you can.

Can I export my WordPress.com site for free?

Yes. Tools → Export is available on every plan, including Free. You get a WXR XML file with posts, pages, and comments. What you can't export: your theme customizations, WordPress.com stats history, and Reader followers. Email subscribers can be exported separately as CSV.

Do I need to know how to code to self-host?

For self-hosted WordPress or a shared-hosting-friendly CMS, no — one-click installers and standard cPanel hosting cover it. You do take on light admin duties: running updates, keeping backups, and renewing your domain. If even that sounds like too much, managed hosting splits the difference between WordPress.com and full self-hosting.

Sources

• WordPress.com plan pricing — official tier list; prices referenced as of 2026
• WordPress.com support: Export your content — official WXR export documentation
• WordPress.org: Importing content — the importer used on the self-hosted path
• WordPress.com support: Site Redirect — redirecting a free subdomain after migration
• Google Search Central: Site moves with URL changes — redirect best practice for preserving rankings

Related: Why move from WordPress to a modern CMS in 2026 · The hidden costs of WordPress · Self-hosted CMS: the complete guide