What is the difference between web hosting and WordPress hosting?
Web hosting runs any app. WordPress hosting is tuned, often managed, for WordPress. What changes in caching, access, plugins and pricing.
Web hosting is the general category: a server or account that can run whatever software it supports. "WordPress hosting" is hosting that has been configured, pre-installed and usually looked after with WordPress in mind. How much that label means depends entirely on the plan. On a cheap shared plan it can be a one-click installer and a sticker. On a managed WordPress platform it is a different product, with server-level caching, staging, backups, updates and support staff who know the software, and you pay for it with fewer freedoms, a list of banned plugins and pricing metered by visits or bandwidth.
Last verified: 2026-11-12.
A note on method. I work on VeloCMS, and this post sits on its developer blog, so VeloCMS shows up near the end as one option among several, with its weaknesses stated. Every number below was read from the linked vendor page today. Where a page was silent, vague or contradicted itself, I say so or leave the claim out. Prices are in the currency each page served me, they shift by region and promotion, and several are first-term deals, so read them as a map and not a quote.
What is the actual difference between web hosting and WordPress hosting?
Start with how little WordPress asks for. The WordPress requirements page recommends PHP 8.3 or greater, MariaDB 10.11 or newer or MySQL 8.0 or newer, and HTTPS support. It recommends Apache or Nginx as the most robust and featureful servers while saying any server that supports PHP and MySQL will do, and it says each host on WordPress.org's own hosting page supports the requirements. So by the strict definition, any decent PHP-and-database host is already WordPress hosting.
That's why the label is really about the layer around the software. I find it easiest to split that layer into four jobs:
- Configuration: server software, PHP settings and caches set up for WordPress's request pattern.
- Tooling: staging, backups, SSH, WP-CLI and Git hooks wired into the panel.
- Operations: who applies updates, watches the box and restores it when something breaks.
- Policy: which plugins are allowed, what counts against your quota and how many sites a plan covers.
A generic plan gives you a runtime and leaves the four jobs to you. A "WordPress" plan takes some of them. A managed platform takes most. The next section walks that spectrum.
Where do the different kinds of plan sit?
Generic shared hosting
You get an account on a machine shared with other customers, with PHP, a database and a control panel. WordPress is one installer in a list of applications. The host looks after the operating system and the web server, and everything inside your account, including the application, is yours. This is the cheapest shape and the least opinionated one. It runs a WordPress blog, a static site and a hand-written PHP script equally well, and equally unattended.
Shared plans sold as WordPress hosting
Most of the household names sell shared infrastructure under a WordPress label, and the label usually buys you caching defaults, staging and a command line.
SiteGround's WordPress page (the UK version, which is what I was served) lists "WP-CLI and SSH" on all three plans, managed auto-updates on all three, staging from the GrowBig plan up and staging plus Git on GoGeek. StartUp hosts one website, the other two host unlimited websites, and all three say "unlimited traffic" with storage of 10, 50 and 100 GB. Its footnotes show renewal at £13.99 a month on StartUp, prepaid for 12 months, excluding VAT.
Bluehost lists staging, SSH and WP-CLI, static content caching and object caching on its Starter, Business and eCommerce Essentials plans, with 10, 50 and 100 websites. It's a good example of why you read the fine print: the plan table says "Weekly Website Backups" while the FAQ on the same page promises daily off-site backups with multiple restore points, and the page never reconciles the two.
Hostinger describes LiteSpeed servers and a toolkit with WP-CLI, SSH, Git and PHP version control, but the text I read doesn't tie each tool to a plan. Its Premium plan lists weekly backups and three websites, while Unlimited lists daily backups. It says unlimited features are "subject to our Fair Usage Policy", and the Premium card reads "Today you pay $95.52 for 48 months. Renews at $10.99/mo for the same term."
Read those three together and the pattern is clear. The hardware is shared, the quotas are soft, and the intro price is not the price you'll pay for long.
A VPS or cloud instance
Here the "WordPress" part is whatever you install. DigitalOcean's Basic Droplets start at $4 a month for 512 MiB of RAM, 1 vCPU, 500 GiB of transfer and 10 GiB of SSD, then $6 for 1 GiB, 1,000 GiB and 25 GiB. The page says inbound bandwidth is always free, and doesn't state an outbound overage rate. Hetzner Cloud sells comparable shared-CPU instances, though its landing page didn't give me sizes or traffic terms, so I won't quote any.
You get root, you pick the stack, and you do all four jobs. I'm not going to guess what size runs a given WordPress site, because I found no official figure and it depends on your plugins and traffic.
Managed WordPress platforms
This is where "WordPress hosting" stops being a label and becomes a product.
WP Engine puts its Essential tier at an estimated 25,000 to 400,000 visits a month (it says the numbers are estimates), 10 to 50 GB of storage and 75 GB of bandwidth, with daily backups, one-click staging, a Cloudflare-powered CDN and SSH. Git-based CI/CD isn't on Essential. Its terms keep backups for no fewer than 30 and no more than 60 days.
Kinsta's plans let you choose between billing by bandwidth or by visits. The entry plan the page showed, Business Single 20GB, includes one WordPress install, 10 GB of storage, 20 GB of server bandwidth, 125 GB of CDN bandwidth and 14 days of backup retention, at $35 a month (the page was running a Black Friday promotion on the first months). Extra sites are $30 a month each.
Pressable, which is owned by Automattic, prices Signature 1 at $250 a year for one install, 30,000 visits and 20 GB. It includes one staging site and one sandbox site, and the page lists "Page Cache & Query Cache" without mentioning an object cache.
WordPress.com Business is the hybrid. It's $25 a month billed annually with 50 GB of storage, and it lists SFTP/SSH, WP-CLI, Git and GitHub Deployments, staging and real-time backups. Hosting is part of the service itself, and its comparison page says "Managed hosting is built-in."
What does a WordPress-specific stack actually add?
Most of the following exists to avoid running PHP and querying MySQL for every anonymous visitor.
Server-level page caching. The classic pattern stores rendered HTML at the web server so PHP is skipped. Nginx's fastcgi_cache directives do this, defining a shared memory zone and storing cache data in files. WP Engine documents its cache layers in detail: a Varnish page cache with a default expiry of 10 minutes, default exclusions for the admin area, wp-login.php, cart and checkout pages and pages where a cookie containing wordpress_ has a value set, plus an edge page cache that only some of its products enable. The LiteSpeed Cache plugin calls its cache a server-level cache and says the page-caching features need a LiteSpeed-based server or the QUIC.cloud CDN. If a host runs this layer, a caching plugin adds a second, conflicting one, which is the reason you'll see caching plugins on banned lists.
A persistent object cache. WordPress's own performance docs say a persistent object cache saves trips to the database, and that your host has to provide a cache server for it before you install a plugin that talks to it. The Redis Object Cache plugin is a common choice. The Hosting Handbook lists APCu, Memcached and Redis as alternatives and says only one is needed. Availability varies a lot. Kinsta lists Redis as an add-on next to server caching, a CDN and edge caching, and WP Engine calls its object cache optional. Bluehost's page lists object caching on its plans, and the SiteGround and Hostinger pages I read didn't mention it. That's a hole in what I could verify, not proof that they lack it.
Current PHP and a sane PHP configuration. The Hosting Handbook recommends PHP 8.4 or later for production, lists json, hash and mysqli as required extensions, a longer highly recommended set that includes curl, dom, imagick, intl, mbstring, openssl, xml and zip, opcache as a recommended caching extension, and suggests a memory_limit of 128M as a minimum and 256M as a default, going to 512M or more for heavy sites. PHP's own support table is why this matters: as of today 8.2 is security-only until 31 December 2026, 8.3 is security-only until 31 December 2027, 8.4 is in active support until 31 December 2026 and 8.5 is in active support until 31 December 2027. A good WordPress host keeps you off the branches that are about to expire and lets you choose a version per site.
Shell and deploy tooling. WP-CLI is the command line interface for WordPress administration, and its value is automation: updates, search-replace, user management and imports in a script. Hosts that give you SSH and WP-CLI let you treat a site like a deployable thing. Hosts that don't leave you clicking through a dashboard.
Staging, updates and backups. One-click staging, auto-updates and scheduled backups are on nearly every plan above, with differences that matter. Retention ranges from 14 days on Kinsta's entry plan to 30 to 60 days at WP Engine, and some plans, as with Bluehost, publish two different answers on one page.
Scheduled-task handling. WordPress's pseudo-cron, WP-Cron, runs on page loads, which means a heavily cached or low-traffic site can run scheduled jobs late. The documented fix is to set DISABLE_WP_CRON to true in wp-config.php and have a system scheduler call wp-cron.php at the intervals you need. On a VPS that's a crontab line. On managed hosting, it depends on whether the platform exposes a real cron, and the pages I read didn't say.
Security extras. Most managed vendors talk about firewalls and malware scanning. I couldn't find a vendor page that specified what the scanner covers or how fast cleanup happens, so I won't repeat the marketing. If this matters to you, ask for the specifics in writing.
What do you give up on managed WordPress?
Four things, and each is a trade you should make deliberately.
Plugin freedom. WP Engine's disallowed plugins page says the listed plugins "have proven that they will negatively impact performance or security on our platform." The categories include caching plugins (conflicts with built-in caching), backup plugins (the company runs its own nightly backups), plugins that hammer the server or database, related-posts plugins and plugins that duplicate platform behaviour. Kinsta's banned plugins page says it doesn't allow caching, backup or related-posts plugins, lists examples like Cache Enabler, All-in-One WP Migration and BackupBuddy, and notes that Wordfence needs extra firewall configuration and that its Traffic Logging feature is disabled for causing high IOPS. It also admits the list moves: WP Rocket used to be banned and is now a partner. WordPress.com takes the same stance in softer words, saying it "proactively blocks potentially risky plugins". Check your plugin list against the vendor's page before you migrate, not after.
Server control. None of the managed pages I read promised root access. SSH and WP-CLI are there, which covers most day-to-day work, but if you need a system package or a custom daemon, ask support first.
Predictable pricing. Managed vendors meter on things you don't fully control.
- WP Engine defines a visit as one unique IP address per day (UTC). Known and suspected bots aren't counted, and overage is $2 per 1,000 extra monthly visitors.
- Kinsta's overages page lists $0.50 per 1,000 visits, $0.50 per GB of server bandwidth, $2 per GB of disk per month and $0.05 per GB of CDN bandwidth. It keeps your sites running for visits and CDN overage, but says an overage as large as your plan cost or $500, whichever is less, can lead to a payment demand and temporary limits on your site.
- Pressable's overage line is $1.20 per 1,000 visits and $1.00 per GB of storage, and its visit counting defaults to a privacy-preserving analytics method that excludes many bots, with an opt-in server-side page-view count that the page says frequently records higher numbers.
Three vendors, three definitions of "a visit". You can't compare plans on the headline number.
Plan shape. The pricing pages above are per install. Kinsta's entry plan is one site and Pressable's is one install, while shared hosts like Bluehost sell 10 websites on the cheapest plan. None of the managed pages I read advertised running non-WordPress software on the same plan, so treat a managed WordPress plan as a WordPress plan and nothing else.
Then there's renewal. WP Engine's plans page marks first-year pricing as available to new customers on Essential and says renewal pricing is subject to change. Bluehost says plans renew automatically at the then-current regular rate. The Hostinger and SiteGround numbers above show the same gap in raw numbers. Budget on the renewal price.
How should a developer evaluate a plan?
I'd take this checklist to any sales page, and I'd treat "not stated" as a question for support.
- PHP versions: which branches can you select, can you pin per site, and what's the plan when your version leaves security support (8.2 does on 31 December 2026)?
- Object cache: is Redis or Memcached included, an add-on or unavailable, and is the persistent drop-in allowed on your plan?
- Page cache behaviour: what's the default TTL, what does it skip (logged-in users, cart, checkout) and how do you purge it from CLI or API?
- Shell access: SSH, WP-CLI, SFTP and Git, and which plan tier unlocks each (WP Engine's Git CI/CD isn't on its Essential tier, for instance).
- Staging: can you push and pull between staging and production including the database, or only clone one way?
- Backups: how often, how long they're kept, whether restores are self-serve and whether the number on the pricing block matches the FAQ.
- Visit definition and overage: what counts as a visit, how bots are treated, the rate per 1,000 visits and what happens at an extreme overage.
- Bandwidth and egress: does the quota include CDN traffic, is there a separate allowance and what's the per-GB rate after it?
- Sites and storage: installs per plan, storage per plan, cost of an extra install and whether staging sites count.
- Cron: can you disable WP-Cron and run a real scheduler?
- Email: WP Engine's disallowed plugins page says email plugins aren't banned but recommends a third-party email service. Ask every host what outbound mail it supports, and plan on a dedicated sending provider for anything transactional.
- Renewal price and term: the renewal rate, the minimum term and whether the intro price is for the first term only.
- Plugin policy: download the disallowed list and diff it against
wp plugin list.
When is generic hosting the better choice?
Reach for generic hosting or a VPS when WordPress is one of several things you run. If your stack includes a Node service, a Python worker, a static site and a WordPress blog, a managed WordPress plan forces you to split them across vendors, while a VPS or a plain shared account keeps them together. It also wins when you want root, need a package the platform doesn't ship, or like reproducible infrastructure where a Docker Compose file and a deploy script define the whole environment. And it wins on cost for hobby projects, where a $4 or $6 droplet is hard to beat if you're happy to do the upkeep.
The price is that every job in the four-part list is yours. That includes the dull, important ones: patching, backup tests and watching disk space.
When is managed WordPress worth the money?
It's worth it when WordPress is the product, the site makes money, and an hour of downtime costs more than a month of hosting. You're buying a team that has seen this failure before, caching that someone else tuned, restore points and a support channel that understands plugin conflicts. For an agency maintaining a dozen client sites, the staging flow and the per-install pricing tend to line up with how the work is billed. For a single-person blog on a modest budget, it might be more than you need, and a good shared WordPress plan could cover it.
When might you not want WordPress hosting at all?
If the thing you want is a website and not a WordPress installation, a hosted platform that bundles hosting is another route. These are five, each described at about the same length so they're comparable.
WordPress.com
It's WordPress with the server work removed. The pricing page lists a Free plan at $0 with 1 GB of storage, then paid plans from $4 a month (Personal, 6 GB) through $8 (Premium), $25 (Business, 50 GB) and $45 (Commerce), billed annually. Plugin installs need a paid plan, and the Business tier brings SSH, WP-CLI, Git and staging. The strength is the familiar editor and ecosystem with no server upkeep. The trade-off is that the vendor's plugin and policy rules apply to you.
Ghost(Pro)
Ghost's pricing page lists Starter at $18 a month, Publisher at $29 and Business at $199, all labelled as billed yearly, with a monthly toggle and member-based limits. Starter doesn't allow custom themes or marketplace themes, while Publisher and Business do, and Publisher adds integrations such as Zapier and webhooks. Its strength is a focused publishing and membership product with no plugin chain to patch. The weakness is that it's a publishing tool more than a general website builder, and that its own pricing page is inconsistent about the Business member limit, so confirm it before you buy.
Squarespace
Squarespace says all of its plans include fully managed cloud hosting. It sells Basic, Core, Plus and Advanced tiers, offers extensions it describes as the equivalent of plugins, add-ons or apps, and gates code injection and the advanced code block above the Basic tier. The page localised its prices to my region, so I won't quote any. The strength is a polished all-in-one design tool. The limit is that you work inside its templates and extension model, not a codebase you control.
Wix
Wix includes hosting in every plan and has a Free plan at $0 with no credit card required, then paid yearly plans from Light through Business Elite. Its page didn't explain code access or its app market in the text I could read. The strength is a gentle start and an app market. The weakness is that, like Squarespace, you build inside its system and leave the PHP world behind.
VeloCMS
VeloCMS is a hosted blog and website CMS with a newsletter, memberships and a store built in. Pro is $9 a month ($86.40 a year), Business $29 ($278.40) and Agency $69 ($662.40). There's no free plan, just a 14-day trial that needs a card unless you hold a cardless trial code, with the first charge on day 15. It takes a 0% platform fee on Stripe sales, though Stripe's own fees still apply. The strength is having blog, newsletter, membership and store behind one login with nothing to host. The weakness is that it's newer with a much smaller ecosystem, and, per its own comparison page, it's a proprietary managed service with no self-hosting, and WordPress's plugin ecosystem is "genuinely unmatched".
Which option fits which person?
- Generic shared hosting: best for cheap, simple PHP sites and mixed workloads where you don't need WordPress-specific tooling.
- Shared plan with a WordPress label: best for a small WordPress site that wants staging, WP-CLI and caching defaults at a low price, provided you budget for the renewal rate.
- VPS or cloud: best if you want root, version-pinned infrastructure and several apps on one box, and you accept the upkeep.
- Managed WordPress (WP Engine, Kinsta, Pressable): best for revenue-generating or client sites where you'd rather pay for tuned caching, restores and support than run them yourself.
- WordPress.com: best for WordPress's editor and plugins with no server work, if a vendor's plugin rules are acceptable.
- Ghost(Pro): best when newsletter and memberships are the business and you don't need plugins.
- Squarespace and Wix: best for non-technical owners who want one subscription covering design, hosting and a store.
- VeloCMS: best if you want blog, newsletter, membership and store in one login and don't need WordPress's plugin depth.
When is VeloCMS the wrong pick?
Quite often. If your reason for being here is a specific WordPress plugin or theme, you can't bring it: per its comparison page, plugin functionality is replaced by built-in features and VeloCMS's own plugin marketplace, and self-hosting isn't offered. If you want a free plan, it isn't one. If your business depends on an existing WordPress site, its own comparison page says to plan a migration project rather than a casual switch, and it concedes that WordPress is more mature for deep multilingual support and highly customized editorial-review workflows for very large teams. And if you want to learn server operations, a VPS and a Compose file will teach you more than any subscription.
FAQ
Is WordPress hosting just regular hosting with WordPress installed?
On many shared plans, close to it. The infrastructure is shared, and the difference is an installer, caching defaults and a few tools. On managed platforms there's more: server-level caching, staging, backups and update handling are part of the product, and you accept plugin rules and metered pricing in return.
Can I run WordPress on regular web hosting?
Yes, if it meets the requirements. The WordPress requirements page recommends PHP 8.3 or greater, MariaDB 10.11 or newer or MySQL 8.0 or newer, and HTTPS support, and says each host on its hosting page supports them. You'll handle caching, backups and updates yourself.
Why do managed hosts ban caching and backup plugins?
Their platforms already provide those layers. WP Engine says caching plugins can conflict with its built-in caching and that it runs nightly backups, and Kinsta says it doesn't allow caching, backup or related-posts plugins (WP Engine, Kinsta).
Which PHP version should WordPress hosting run?
The Hosting Handbook recommends PHP 8.4 or later for production (handbook). PHP.net lists 8.4 with security support until 31 December 2028 and 8.5 until 31 December 2029 (php.net).
Do I need WordPress hosting for WooCommerce or a membership site?
The sources I read don't say you need a specific hosting type. What changes is that dynamic pages like cart and checkout skip the page cache, as WP Engine's cache documentation describes, so a store leans harder on PHP capacity and, where the host offers one, an object cache. Ask each host how it treats those pages.
Does VeloCMS have a free plan?
No. It has a 14-day trial, a card is required unless you have a cardless trial code, and the first charge is on day 15 (velocms.org/pricing).
About the author
- Building VeloCMS.org , A fast multilingual CMS for blogs and online stores. I write about headless CMS, Next.js, SEO and moving off WordPress and Shopify.
Comments
Join the discussionGood breakdown. The checklist at the end is really useful. Quick disclosure: I work at Cloudways, so take this with that in mind. One thing I noticed is the gap between a VPS and managed WordPress. Managed cloud hosting sits in between, where you pick a server size and get things like staging and backups handled without per-visit metering and plugin lists. It also helps when WordPress is one of a few apps you run. Worth adding for readers who want server-level management without visit-based pricing or rigid plugin restrictions.