This is the mix-up I hear most from clients: “I already have WordPress.com, so we have WordPress.” Then they send a Figma file, ask for Elementor Pro, Rank Math, a custom plugin, or a move to Hostinger — and we discover the site is not the kind of WordPress an agency usually builds on.
The names look like twins. They are not. WordPress.org is the free software. WordPress.com is a paid (or free) hosted service run by Automattic, using that software, with their rules, their hosting, and their plans. Your public website can still end in .com on either setup. That last part is what confuses everyone.
If you read the Framer vs WordPress post, think of WordPress.com as closer to Framer (one company hosts everything). Think of WordPress.org as the house you own on a plot you rent from a host.
First: .com the domain is not WordPress.com
Three different things get mashed into one sentence:
- The software — WordPress (the CMS: pages, posts, users, plugins).
- The host — the company whose computers keep the site online 24/7 (WordPress.com, Hostinger, SiteGround, WP Engine, your own server…).
- The domain — the address people type:
yourbrand.com. You buy this from a registrar. It is not the same as an account at wordpress.com.
You can run self-hosted WordPress on Hostinger and still use yourbrand.com. You can run a site on WordPress.com and still connect yourbrand.com on a paid plan. The ending .com only means you bought a commercial domain. It does not mean the site lives at WordPress.com.
When a client says “we are on .com,” I always ask: do you log in at wordpress.com, or at yourbrand.com/wp-admin on a separate host? That one question usually settles it.
What WordPress.org actually is
WordPress.org is the home of the open-source project. You download WordPress for $0. Nobody at wordpress.org hosts your live site for you. You (or your developer) install that software on hosting you control.
That setup is called self-hosted WordPress (sometimes “WordPress.org” in sales calls). “Self” does not mean you must be a programmer. It means:
- You pick the host and pay that host.
- You (or an agency) install WordPress there, or the host offers “one-click WordPress.”
- You choose the theme, plugins, and who has admin access.
- You can move the whole site to another host later and keep the same domain.
Analogy: WordPress.org is the recipe and the ingredients. Self-hosting is cooking in a kitchen you rent (the host). You can change kitchens. You still own the food (your pages, images, and database).
What WordPress.com actually is
WordPress.com is a product: sign up, pick a plan, and they host WordPress for you. Updates, backups, and a lot of security are their job. You get a dashboard, themes, and support (“Happiness Engineers”). On the free plan the address looks like yoursite.wordpress.com and may show their branding or ads depending on the plan era — paid plans let you use your own domain.
Analogy: a furnished apartment building. The landlord (WordPress.com) sets house rules. Some furniture (plugins and developer tools) is allowed only on higher floors (higher plans). You can decorate a lot. You cannot knock down every wall.
At a glance
| Question | WordPress.com | Self-hosted (WordPress.org) |
|---|---|---|
| What you buy | A plan from Automattic (hosting bundled) | Hosting + domain + optional plugins; software is free |
| Who is the landlord | WordPress.com | Hostinger, SiteGround, Cloudways, WP Engine, etc. |
| Login you remember | wordpress.com (and your domain) | yourbrand.com/wp-admin |
| Plugins and custom code | Paid plans allow many plugins; some are blocked; full developer tools on higher plans | You may install almost anything you accept the risk for |
| Elementor / custom PHP / unusual plugins | Often limited or awkward | Normal daily work for agencies |
| Updates and security | Mostly done for you | You or your maintainer must update core, theme, plugins |
| Leaving later | Export is possible; rebuild is common | You already own files + database; change host |
| Best for | Simple sites, less IT, one vendor | Business sites that must grow, shops, custom design |
What “self-hosted” means in practice
When an agency says “we need self-hosted WordPress,” they are asking for this stack:
- A hosting account in your name (or the company’s), not only a WordPress.com user.
- WordPress installed in that account (“WordPress.org” software).
- Access: wp-admin, plus usually FTP/SFTP or a file manager, and a database backup tool.
- Freedom to install Elementor Pro, Rank Math, Wordfence, contact forms, a child theme, or a small custom plugin.
You still do not have to touch code. “Self-hosted” is about who owns the keys, not about you becoming a sysadmin. Many clients never log into the host. Their developer does. The client still owns the hosting invoice, which is what you want if you change agencies.
“Managed WordPress hosting” (Kinsta, WP Engine, some Hostinger plans) is still self-hosted in this sense: WordPress.org software on a host that helps with speed and backups. It is not WordPress.com.
Benefits of WordPress.com
- One bill, one login culture. Hosting, updates, and a lot of security are included. Good if nobody in the company wants to hear the word “plugin update.”
- Fast start. A brochure or personal blog can be live the same day.
- Official support from WordPress.com, not only forum volunteers.
- Less surface area. You are less likely to install a shady plugin that bricks the site, because the platform is picky.
- Fine for non-technical owners who will only edit text and photos, and who do not need a pixel-perfect Figma build.
Plans (always check wordpress.com/pricing; numbers move): a Free tier for trying; Personal / Premium for a custom domain and more design; Business (often around $25/month billed yearly) when you need developer-style access (SFTP, WP-CLI, Git); Commerce when the site is really a store. Older blog posts said “no plugins until Business.” WordPress.com has opened plugins on more paid plans, but they still block risky or incompatible plugins, and serious agency work still usually wants Business-level tools or a move off the platform.
Limits of WordPress.com (why agencies push back)
- House rules. A plugin or theme your designer relies on (Elementor, a specific form tool, a custom module) may be blocked or unsupported.
- Custom design from Figma is harder. You can get close with their editor and allowed themes. A full Elementor Pro or custom-theme build is the self-hosted default.
- Monetization and ads on cheaper plans can have platform rules. Shops are cleaner on Commerce or on self-hosted WooCommerce with any gateway your country needs.
- You rent the platform. Pricing, features, and blocked plugins can change. Export exists; a pixel-perfect move still takes paid hours.
- Who is admin? Agencies need a real Administrator role, SFTP, and staging. That is awkward or extra on lower WordPress.com plans.
Benefits of self-hosted WordPress.org
- The software is free. You pay hosting (often a few dollars to a few tens per month), the domain (~$10–20/year), and any premium plugins you choose.
- Full plugin and theme directory — plus paid tools: Elementor Pro, WooCommerce extensions, booking, LMS, multilingual, CRM. If a business process exists, there is usually a plugin. Quality still varies; you need someone to choose them.
- You own the files and database. Change host, change developer, keep
yourbrand.com. - Roles. Let a client edit posts without giving them plugin access. Agencies live on this.
- Performance and SEO you can tune with Rank Math (or Yoast), caching, a CDN, and a host that fits your traffic.
- Huge talent pool. If your freelancer disappears, another WordPress person can pick up a self-hosted site. WordPress.com-only tricks are a smaller skill set.
Costs of self-hosted (the honest side)
- Someone must update WordPress, the theme, and plugins, and keep backups. That can be you, a host add-on, or a small monthly care plan.
- A cheap host plus 40 plugins will be slow and fragile. Budget for decent hosting.
- Security is manageable (HTTPS, strong passwords, limited admins, firewall, backups) but it is not automatic like WordPress.com.
- The build itself (Figma to Elementor, custom theme) is a project fee. That is separate from hosting either way.
Pricing picture (do not compare $0 to $25)
WordPress.org software = $0. A live self-hosted site is not $0.
- WordPress.com: one subscription. Easy to forecast until you need a higher plan, extra storage, or a store add-on.
- Self-hosted: hosting + domain + optional Elementor/SEO/security licenses + (optional) maintenance. Over a few years this is often cheaper for a growing business site, especially if you already pay a developer.
There is no universal winner. A tiny brochure that never changes can be cheaper and calmer on WordPress.com. A company site that will add a blog, careers, landing pages, and later a shop almost always belongs on self-hosted WordPress.
Security and updates
WordPress.com: they patch the platform. You still use a strong password and are careful who you invite. If they have an outage, you wait.
Self-hosted: the host protects the server; you protect WordPress. Outdated plugins are the usual disaster, not “WordPress cannot be secure.” A monthly update + backup habit (or an agency retainer) makes this boring, which is the goal.
Can you move from WordPress.com to self-hosted?
Yes. WordPress.com offers export. A developer imports content into a self-hosted install, reconnects the domain, and rebuilds design where the theme does not copy 1:1. Budget time for that rebuild if you used WordPress.com-only blocks or a locked theme. Moving the other way (self-hosted → WordPress.com) can fail if plugins are not allowed.
If you already know you want Elementor, a custom theme, or unusual plugins, start self-hosted. Do not build for six months on WordPress.com and then pay to migrate.
How to tell what you have today
- You created the site by signing up at wordpress.com and you manage billing there → WordPress.com.
- You have a Hostinger / SiteGround / cPanel / “WordPress toolkit” login, and wp-admin is on your domain → self-hosted (WordPress.org software).
- Your designer asks for FTP, a database, or “install this plugin zip” and WordPress.com says no → you are on WordPress.com limits.
Who should choose which?
Stay on or start with WordPress.com if you want one vendor, a simple site, little customization, and you will not hire an agency to implement a full Figma file.
Choose self-hosted WordPress.org if you are a business that will grow, need Elementor or custom development, want any plugin your country or CRM requires, want to own the asset, or want any WordPress developer to be able to take over.
If a client emails “we have WordPress.com, please install Elementor Pro and connect our Figma,” the kind answer is: that is a different product. We can keep a simple site on WordPress.com, or we move to self-hosted and then build it properly. Mixing the two in your head is how projects stall in week one.
A five-question check for non-technical clients
- Do we log in at wordpress.com, or only at our own domain’s wp-admin on another host?
- Will we need Elementor, a custom theme, or a special plugin in the next year?
- Who will update the site and keep backups?
- Do we want to be able to change host or developer without rebuilding from zero?
- Is this a small brochure, or the company’s main digital office?
If the answers point to growth, custom design, and ownership, you want self-hosted WordPress (the software from WordPress.org) on a host you control — and a real .com domain pointing at that host. WordPress.com is a valid product. It is just not the same thing. Photo: Rodrigo Rodrigues / Unsplash.
