WordPress.com or self-hosted WordPress: balancing maintenance, costs and control

WordPress.com is a service offering website hosting and other features. WordPress.org is where you obtain WordPress software and community resources. Their differences cannot be reduced to ‘free versus paid’: self-hosted software is available free of charge, but hosting, a domain, maintenance and extensions may still cost money.

If you are deciding where to put your first blog, first write down whether you need particular plugins, who will handle updates, how much maintenance you can take on and whether data migration is required. Rather than comparing promotional prices, the following sections separate service responsibilities that are easily confused, so you know exactly what to check before buying.

Choosing hosting also means assigning the work

With WordPress.com, the platform provides hosting and your plan determines the available features. If you self-host the software from WordPress.org, you must choose a host and manage the website, or hire someone to manage it. Self-hosting does not mean putting your site on WordPress.org, and the software community will not handle your bills, site failures or insufficient hosting resources for you.

Separate the work into website infrastructure, content and third-party services. Infrastructure includes servers, certificates and software updates; content includes posts, images and account roles. Third-party services may include email, bookings or payments. A platform handling one layer does not mean all the others are included. Ask specific questions, such as how far support will investigate when a form submission fails to arrive by email.

Check current official requirements for plugins

On the date checked, WordPress.com’s official plugin documentation stated that all paid plans could install plugins, while free sites needed an upgrade. Older tutorials that restrict plugin installation to higher-tier plans cannot be assumed to describe the current rules. Permission to install also does not mean every plugin is compatible: check the platform’s incompatible-plugin list, the plugin’s own requirements and the functions you actually need.

Self-hosted WordPress gives you more flexibility in choosing plugins, but hosting environments, plugin licences and technical compatibility still matter. A plugin activating successfully does not guarantee that email, payments or scheduled tasks work. Compare a real task, such as a visitor completing a booking and receiving confirmation, rather than stopping at a box labelled ‘supports booking plugins’.

Separate plan fees from the total cost

List the advertised subscription fee separately from the website’s total costs. Domain renewals, professional email, paid themes, plugin subscriptions, outside help and migration work may all add expenses. Check the currency, billing cycle, promotional period and renewal terms. A monthly equivalent for a different billing cycle is not necessarily a price you can pay and cancel month by month.

For a personal site with regular posts, start by comparing publishing, media storage and administration needs. A long list of business features is not itself a reason to upgrade. For a shop, assess products, payments, orders, tax display and email workflows together. Features you do not actually need will not automatically bring revenue or better rankings just because they are included in a package.

Backups, content exports and full-site restores are different

WordPress.com’s export documentation explains that the export file contains content such as posts, pages and comments, but not the complete theme design, custom settings or plugins. Media in this type of export is usually represented by source links, which the new site retrieves during import. Downloading a file therefore does not mean you have a complete backup of the site’s appearance and every image.

Self-hosted sites also require separate handling of files, databases and data held by external services. When comparing the options, ask which dates you can restore, who performs the restore, whether services need configuring again afterwards and how missing data will be detected. Do not delete the old site merely to test a move. Keep recoverable original data until content and media have both been checked.

Use a small trial to discover practical limits

Use the same subject and materials to create a post and a static page in each candidate environment. Then edit content with different account roles and check previews, publishing, images and navigation. This reveals the actual editing workload and helps distinguish theme-design issues from platform features or usage problems, instead of attributing everything to hosted or self-hosted operation.

If you need an external integration, read both providers’ official documentation first. Confirm the accounts, permissions and plans required before testing. Do not use real customer lists or live transaction keys during a trial. Keep a record of your actions, missing features and acceptable alternatives so the final choice rests on evidence, rather than a single smooth or frustrating experience.

1. List essential features for now separately from features you might add later, rather than mixing them into one purchasing requirement.
2. Read the official documentation for current plans and required plugins, and record the date and limitations.
3. Use the same content to test editing, publishing, visitor access and required integrations, and keep the results.
4. Check content export, hosting backups and account handover, then estimate the full annual cost before choosing.

Choose an arrangement you can keep maintaining

If you want to spend most of your time writing and can work within a platform’s boundaries, an integrated hosting service is worth considering. If you already have maintenance support, specialised data workflows or a required hosting environment, self-hosting may fit better. These are starting points for a decision. Neither model is inherently more professional; reliability still depends on configuration, content and maintenance.

Keep the requirements list used for your decision, especially the limitations you accepted. When the site’s size, payment needs or division of work changes, compare upgrading the existing service, changing workflows and migrating. Whichever option you choose, make ownership of the domain, administration email and important data clear so the site can keep operating when collaborators change.

Read the full description

Compare WordPress.com and self-hosting through feature requirements, maintenance responsibilities, total costs and data migration.

Choosing a CMS or website platform: let your update workflow guide the choice

Planning a website budget: separate first-year, renewal and maintenance costs

• Tutorials
• Apps & software
• Websites & e-commerce
• WordPress