The difference that determines your choice
WordPress.org and WordPress.com refer to two different things. WordPress.org is the website of the WordPress project, open-source software you can use with a compatible hosting provider. WordPress.com is a commercial service operated by Automattic: it hosts sites using WordPress and supplies a set of features according to the plan you choose. Buying WordPress hosting elsewhere therefore does not mean subscribing to WordPress.org.
The software lets you publish and organise your content. Hosting makes it accessible on the internet. The domain name is its address. These three elements may be bundled in an offer, but they remain separate. A single invoice does not mean that every necessary service is included either: professional email or a specialised plugin may cost extra.
To decide, start with your actual project. By the end of this process, you should know which solution covers your essential features, how much it will cost after the initial period, and who will intervene if something goes wrong. An already functioning site should not be moved simply because its owner has discovered the difference between the two names.
Identify your situation if your site already exists
Start by finding your hosting invoice and the account used to manage the service. Note the domain concerned, the provider’s name and the contract holder. If an agency created the site, ask for this information and the access procedure. Having the password for a WordPress author account is not enough to administer hosting.
A custom domain does not settle the question: a site hosted on WordPress.com can use your own address. Conversely, having a WordPress.com account does not prove that all your sites are hosted there. The account may be used for other services. The WordPress logo in the administration interface and the site’s public appearance are not sufficient evidence either.
Carry out this check without changing settings. Changing the site address, nameservers or credentials to see what happens may interrupt a working service. If the difficulty only concerns logging in, address that problem separately before considering a migration.
- Record the hosting provider, domain registrar and email provider: they may be different companies.
- Check that the account you are viewing contains the domain and service you need, not just an old order.
- Keep this information in a private document without copying passwords into it.
Write down your needs before comparing plans
Describe three tasks your visitors will actually need to perform. For a professional practice, these might be reading about services, finding the address and sending an enquiry. For an association, they might be viewing the calendar, downloading a document and registering for an event. A store needs to specify its products, payment methods and order management. These examples define different needs, even if every site uses WordPress.
Classify each feature as essential at launch, useful later or optional. For every essential need, identify the proposed tool: an included feature, an editor block, a plugin or an external service. An expensive plan does not become necessary simply because it advertises more options. Conversely, an inexpensive plan is a poor choice if it forces you to abandon the one tool your business depends on.
Add your working constraints: number of people publishing, support language, time available for maintenance and approximate media volume. Specify who will receive enquiries from the site. A visible form with nobody responsible for reading its messages does not meet the need.
- Write a verifiable sentence for each feature, for example: a visitor must be able to send an enquiry and receive confirmation.
- Associate each feature with a specific tool and its documentation, then check its edition and requirements.
- Temporarily set aside options with no identified use rather than counting them as advantages.
Choose an approach suited to your level of independence
First approach: choose WordPress.com when you want a bundled service and its features cover your project. You are then evaluating a specific plan, its limitations and permitted tools. A free plan can help you explore the editor, but it does not establish that every feature of a paid plan is available or has been tried.
Second approach: choose managed WordPress hosting from another provider. You use the software distributed by WordPress.org while entrusting some operations to the provider. Ask which ones: backing up a server, restoring a site and resolving a plugin conflict are three different services. The word “managed” has practical value only when its scope is written down.
Third approach: administer a more independent installation, either yourself or with a professional. This route may suit a custom development project or an organisation that already has technical expertise. It means planning for updates, monitoring and interventions. For a first site, fully administering your own server is not a mandatory step to benefit from WordPress.
Check the plugins and access you need
The claim that WordPress.com always prohibits plugins is outdated. As of 3 November 2026, its documentation states that plugins can be installed on paid Personal, Premium, Business and Commerce plans. The free plan does not provide this right. This information concerns installation; it does not make commercial plugin licences or connected services free.
Some plugins remain incompatible with the platform or prohibited because they conflict with its services. Check the exact product, not just the general category of “allowed plugins”. For an essential theme or tool, look for its name in the compatibility documentation and resolve any ambiguity before committing. Do not try to force an installation that is explicitly refused.
With another host, your freedom also depends on the contract and the access granted. For advanced needs, ask separately whether you will have access to files, the database, a test environment and scheduled tasks. These tools are not essential for every beginner, but their absence may block maintenance later entrusted to a service provider.
Calculate both the launch and renewal budgets
Compare the amount actually payable for the same duration. A price advertised per month may require several years to be paid upfront. Record the currency, commitment period, whether taxes are included, and the stated renewal rate. If information is missing, write “to be confirmed” in your comparison instead of assuming it is included.
Distinguish hosting, domain registration, email, licences and usage-based services. A domain included free for the first year may renew separately. A free plugin may depend on a paid service. An annual licence may cover updates and support without having the same expiry terms as your hosting subscription.
To make the comparison useful, prepare two totals: the mandatory startup cost and the cost of a normal year after the promotion ends. Include your time or a provider’s time when you know a plan requires more maintenance. Do not assign a numerical saving to a service without the conditions needed to calculate it.
- Open the summary of the offer you are considering, without paying, and record the total, period and currency.
- Find the renewal charges for the domain and required options; keep a dated copy of the terms.
- Check how to disable automatic renewal and what happens to the site at expiry before making a commitment.
Assign maintenance to a person or service
Prepare a simple list: WordPress, theme and plugin updates; backups; restoration; user accounts; and intervention during an outage. For each item, name a responsible person and a way to contact them. Avoid a blanket answer such as “the host takes care of it” until the scope is specified.
A usable backup must correspond to what you want to recover. In a standard installation, files and the database serve different purposes: keeping only one generally does not provide a complete copy. Ask about backup frequency, retention period, any restoration charge and the ability to download an independent copy.
Not all WordPress.com plans provide the same recovery tools. Its documentation distinguishes, in particular, the backups and staging environments offered with Business and Commerce. With another provider, also check the specific plan. Security advertised by a platform does not remove the need to protect your accounts and limit collaborators’ permissions.
- Ask where to find the date of the latest backup and who can start its restoration.
- Plan a recovery test on an isolated copy where possible, never by improvised overwriting of the live site.
- For a store or registrations, specify how to preserve data received since the backup before any restoration.
Keep control of the domain and email
The domain must remain identifiable in an account accessible to the person responsible for the project. Record its expiry date, contact address and registered holder. When a provider creates the site, agree from the outset on handing over access and on the transfer procedure. WordPress administrator access does not replace access to the domain manager.
Connecting a domain and transferring its registration are two different operations. You can host a site in one place and manage its domain elsewhere. Choosing WordPress.com or another host should therefore not automatically trigger a transfer of all your services.
Before a future launch, also inventory the domain’s email accounts and their provider. A DNS change may affect several services. Have the necessary changes prepared with a list of existing records and a rollback plan. Choosing a platform here requires no immediate domain change: keep the current site and email working throughout the evaluation.
Evaluate the editor with a small representative project
If a trial environment is offered, build a reduced version of your project. Create a homepage, a content page, a post and the journey that matters most to you. Use demonstration text and images you have the rights to use. Do not import a customer file just to explore an interface.
This check answers concrete questions: can you edit a menu, change an image, correct text using the intended account, and find a publication again? Is a necessary plugin actually available in the environment you are testing? A sales demonstration may show a different plan from the one you are considering: note any feature you cannot verify.
Then try the journey as a visitor, on desktop and phone. For a form, use your own address. For payments, use only a documented test mode if you are authorised to configure it; do not make a real transaction simply to compare two offers. These actions support your decision; they are not a speed or uptime benchmark.
- Draw up a short list of expected results before starting, then mark each result as achieved, absent or unverified.
- Record reproducible obstacles with the screen name and action involved; distinguish a missing feature from a setting you have not yet found.
- Keep your test content locally and check the environment’s deletion terms before closing it.
Plan your exit: exporting content does not back up everything
On WordPress.com, the content export tool produces an XML file, sometimes packaged in an archive. It transfers posts, pages and other elements supported by the importer. This file does not contain a complete copy of the theme, plugins and their settings. Media are referenced in it; their presence in the document does not mean the original files have been downloaded with it.
For an initial check, open Tools, then Export, select all content, and download the offered file. Store it privately and verify that it is present. This export prepares for an exit; it does not prove that the future site will be identical. A trial import to a separate destination then lets you check what is actually recovered.
Also retrieve media using the method appropriate to your plan and plugin activation status. WordPress.com’s documentation distinguishes several routes: do not necessarily expect the same button on every account. Keep the old site available for authorised file transfers. If it is private, do not make it public to simplify migration: arrange suitable access or a file transfer with the technical lead.
- Compare a few posts, their images, internal links and important pages after the trial import.
- List separately the elements that need recreating or transferring: layout, forms, settings, users or commercial data, depending on the project.
- Do not delete the source site or cancel its service before validating the destination and retaining a recoverable copy.
Make a decision and plan when to review it
You can now state a precise decision: this offer supports my three essential uses, its renewal cost is known, and an identified person manages maintenance. If a required tool remains incompatible or data recovery is still unexplained, the choice is not ready. Resolve that point rather than hoping to fix it after payment.
Keep the decision sheet, dated terms and answers received. Review them when your needs change: opening a store, adding several writers, introducing new services or handling larger media files. A price increase does not always require migration; a specific restriction may justify one even when the subscription remains affordable.
If you eventually change platforms, prepare a separate migration project with a tested destination, a backup and checks on recent content. Until validation, avoid combining a domain transfer, deletion of the old hosting and a site redesign. The goal is a site you can run and develop with clear responsibilities.


