PUBLISHING · RESPONSIBILITY · PORTABILITY
WordPress.org vs WordPress.com: Choose Your Operating Model
Choose where your WordPress website runs by matching the publishing work, maintenance responsibilities and exit requirements to the people who will operate it.
This is a researched comparison, not a hands-on hosting benchmark. No speed, uptime or support-quality winner is claimed. The source links below are direct references, not affiliate tracking links.
Software and hosting are different decisions
WordPress.org is the home of the open-source WordPress project. It is not a hosting subscription. With a self-hosted installation, you choose a separate provider to run the software.
WordPress.com’s official comparison describes its service as managed WordPress hosting. Both options use WordPress. Independent hosts can also offer managed services; “self-hosted” does not automatically mean maintaining a server yourself.
Compare a specific WordPress.com plan with a specific external host and its service agreement. A generic contest between two names hides the actual limits, renewal terms and division of work.
Start with the person responsible for the site
You want to concentrate on publishing
Shortlist WordPress.com and an independently managed WordPress host. Ask each candidate to demonstrate your editor’s normal workflow. A service is a suitable candidate only after you confirm the required integrations, recovery process and support scope. Convenience is valuable when it removes work your team would otherwise struggle to cover.
You have a custom workflow and a technical owner
Start with the non-negotiable requirement: a particular plugin, deployment process, integration or access level. Investigate an external host when control over the hosting arrangement matters. Still compare the exact WordPress.com plan if it appears to meet the requirement. The presence of a technical owner makes maintenance feasible; it does not make maintenance free.
You are learning before committing money
A limited experiment can help you discover what you need. Write down what the experiment cannot validate, particularly paid features and a production domain setup. Do not base a long-term business decision on a free demonstration that excludes the workflow you expect to use.
Compare responsibility, not just features
The hosting distinction follows the official overview. The questions below are our decision framework; they are not measured service-quality ratings.
| Area | Independent WordPress hosting | WordPress.com |
|---|---|---|
| Hosting relationship | Select a separate hosting provider. | Hosting is part of the service. |
| Maintenance owner | Ask which updates, backups and recovery work the host covers. | Ask where managed hosting coverage ends and site-specific work begins. |
| Customization | Verify host restrictions and your required workflow. | Verify the plan and plugin compatibility before committing. |
| Support | Identify who handles hosting, theme and plugin problems. | Confirm support access and whether the issue is within scope. |
| Budget | Collect hosting renewal and additional service costs. | Collect plan renewal and additional service costs. |
| Exit | Rehearse recovery and transfer with the selected host. | Rehearse content export and separately inventory the rest of the site. |
In either setup, assign ownership for account access, editorial changes and checking the site after changes. Ask who can restore service when the usual operator is unavailable.
Do not use the outdated “Business plan only” rule
As checked September 12, 2026, WordPress.com’s plugin documentation allows plugin installation on all paid plans: Personal, Premium, Business and Commerce. The free plan requires an upgrade. Some plugins are incompatible with the platform, so installation access alone does not establish compatibility.
List each required plugin by exact name and purpose. Check its dependencies, external accounts, recurring license, data handling and replacement option. Test the complete result: for example, a form should deliver its notification and preserve the expected record. A successful installation is only the first step.
For a custom theme or developer workflow, confirm the relevant plan’s current capabilities directly. If a required capability is unknown, mark the candidate “pending verification.” Avoid buying a higher tier merely because an old tutorial says to.
Build a two-year cost worksheet
Use written quotes for the same currency, taxes, site count and billing period. This worksheet contains no current vendor prices. Keep cash and staff time separate so an affordable subscription does not hide an operating burden.
| Record for both candidates | What to include |
|---|---|
| Year-one cash | Initial hosting or plan charge, domain, required licenses, migration and paid help. |
| Year-two cash | Actual renewal charges, expiring promotions and recurring add-ons. |
| Setup time | Configuration, content transfer, training and launch checks. |
| Operating time | Updates within your responsibility, verification, troubleshooting and access reviews. |
| Exit allowance | Export, rebuild work, redirects, overlap between services and verification. |
Modeled two-year total = two-year cash + (setup hours + operating hours + exit hours) × your hourly valuation. Count bundled items once. An included first-year domain does not establish its renewal price.
For illustration only, saving two operating hours per month over 24 months is 48 hours. At an assumed $25 per hour that represents $1,200 of time, not a provider discount or guaranteed cash saving. If a trial does not support the time saving, remove it from the model. Repeat the calculation for higher usage and a renewal without promotions.
Run a small acceptance trial
Use the same sample article, media, editor and required integrations. Choose criteria before trying either candidate, and record plan, date, configuration and limitations.
- Publish a draft, preview it on a phone and correct a mistake. Record where the editor needed assistance.
- Exercise the essential integration end to end using test data. Verify the intended output, not only a success banner.
- Confirm who can recover a broken change. Rehearse recovery in an isolated test environment with appropriate access.
- Export the sample and inspect or import it into a separate test destination. Check the article, media, internal links and required metadata.
- Record first-run setup time separately from repeat operation. Retain evidence with private information removed.
Accept a candidate when every essential requirement passes and the remaining burden has an owner. A failed required workflow outweighs a longer feature list. These are proposed tests for your setup; AffiliateBest has not claimed to run them on the two services.
A content export is not a full-site backup
WordPress.com’s export documentation explains that its XML export contains content such as posts, pages, comments, categories and tags, with links to media. It does not include the actual media files, theme, design customizations or plugins. Moving the domain and subscriber-related services requires separate attention.
Before moving, inventory content, media, URL structure, forms, integrations, design and subscriptions. Keep the original available for authorized media retrieval until verification finishes; protected files may need a separate secure transfer. Do not expose private content to simplify an import.
- Create a recoverable copy using the source provider’s supported method. Verify what that copy contains.
- Import into a restricted test destination. Compare representative pages and files, not just item counts.
- Rebuild omitted functionality and verify navigation, forms, mobile layouts and search metadata.
- Map changed URLs and prepare redirects. Treat domain routing and email configuration as separate checks.
- Schedule the final content sync, switch and rollback window. Retire the old service only after the required checks pass.
A WordPress-to-WordPress move still needs this review. Shared software does not guarantee that host-specific services or design settings transfer automatically.
Write a decision another person can use
Record the selected host or plan, the publishing job, essential tests, two-year budget and maintenance owner. Add unresolved limits, the exit method and a review trigger such as renewal, a new integration or repeated operational problems.
If both candidates pass, choose the trade-off your team can sustain. If neither passes, adjust the shortlist. If evidence is missing, defer the commitment and identify the next test.
Use the full Tools & Apps decision worksheet to retain your findings.
Sources and limits
Official documentation checked September 12, 2026. Product capabilities and plan terms can change; verify them before purchase. The fit scenarios, cost worksheet and acceptance process are editorial guidance, not performance measurements.
- WordPress.org: About WordPress — project and software background.
- WordPress.com: WordPress.com vs WordPress.org — hosting distinction; provider-authored source.
- WordPress.com: Install plugins — paid-plan access and compatibility caveats.
- WordPress.com: Export your website — content export scope and migration limits.
No commercial ranking, income outcome or universal winner follows from this documentation review. Check the service agreement and test the requirements that matter to your site.