WordPress.com and WordPress.org use related software but represent different operating models. One is a hosted service with plan-based rules; the other is open-source software installed on hosting chosen by the site owner. The right choice depends less on design templates than on control, maintenance and the cost of future change.
The practical difference
| Criterion | WordPress.com | WordPress.org / self-hosted |
|---|---|---|
| Hosting | Included and managed by the service | Chosen and paid for separately |
| Updates and server operation | Largely handled by the platform | Shared between host, site owner and suppliers |
| Themes and plugins | Availability depends on the current plan and platform rules | Broad choice, subject to compatibility and security checks |
| Technical control | Restricted to what the service exposes | High control over files, database, code and infrastructure |
| Support | Provided according to the selected service plan | Split among hosting, theme, plugin and developer suppliers |
| Migration | Possible, but features and presentation may not transfer directly | Full files and database can normally be moved between compatible hosts |
| Maintenance burden | Lower for ordinary use | Higher and must be planned |
| Cost model | Subscription plus optional services | Hosting, licences, development and maintenance |
Choose WordPress.com when
- The site is relatively simple and the available plan clearly covers its required features
- The business values managed operation more than server-level control
- A single hosted service is preferable to coordinating several suppliers
- The exit path has been tested and accepted
Choose self-hosted WordPress when
- The business needs broad plugin, integration or development flexibility
- Hosting choice, data access and deployment control matter
- The site is expected to grow beyond a simple brochure
- The business can fund and assign maintenance responsibility
Costs that are easy to compare incorrectly
Do not compare only the cheapest subscription with the cheapest hosting headline. Include the plan or hosting tier actually needed, premium extensions, backups, security, developer time, payment fees, support and the cost of migration. A managed option can be economical when it removes real operational work; self-hosting can be economical when the business uses its flexibility deliberately.
Questions to test before deciding
- Can the required plugins, integrations and payment methods be used on the intended plan?
- Who owns the domain and can it be pointed elsewhere?
- What content and data can be exported?
- What happens to premium features if the subscription changes?
- Who is responsible for backups, security incidents and restores?
- Can a replacement supplier take over without rebuilding everything?
Avoid the naming trap in proposals
A proposal that says only “WordPress website” is incomplete. It should identify the hosting model, exact plan or server, ownership, included licences, ongoing responsibilities and exit process.
Practical next step
Ask every supplier to describe the operating model in one paragraph: where the site runs, who maintains it, what the business owns and how it can leave. Compare those answers rather than comparing the shared name.
Examples of different priorities
A sole trader who needs a small information site and rarely changes it may value the managed hosted model. A content-led business, membership project or shop with specialist integrations may benefit from self-hosting. Neither conclusion follows from company size alone: the decisive issue is the required control and the organisation’s ability to maintain it.
Test the exit before committing
Create sample pages, posts, media, forms and any commerce data during a trial. Then examine what can be exported and how much design or functionality would need rebuilding elsewhere. A theoretical export button does not mean the entire operating website is portable.
Also separate domain portability from website portability. A business-owned domain can normally be pointed to another service, but content, layouts, memberships, bookings or product configuration may still need a planned migration.
Sources and date checked
This guide was checked on 21 July 2026. WordPress, hosting environments and extensions change, so recheck the relevant official documentation before making a major change.
Keep the decision under your control
Retain the relevant accounts, source material, supplier terms and recovery information. Recheck changing prices, interfaces and rules before acting.