Hosting WordPress: A Practical Guide to Choosing a Host

Hosting WordPress is less complicated than the marketing pages make it look. Underneath the plan names, every host is selling the same basic thing: a server that runs PHP, a database, and enough resources to answer your visitors quickly. This guide covers what WordPress actually needs from a server, the main hosting types and their trade-offs, how to match a plan to your site’s size, and how to move a site and point your domain at it without downtime.

What WordPress needs from a server

WordPress has modest requirements. The official requirements page recommends three things:

• A current version of PHP. WordPress runs on older versions too, but newer PHP releases are faster and still receive security fixes. The recommended version rises over time, so check the page above.
• MySQL or MariaDB at a currently supported version.
• HTTPS support. Free certificates from Let’s Encrypt are standard on most hosts now; there is no good reason to run a site without TLS.

Apache or Nginx are the recommended web servers, and LiteSpeed is also widely used by WordPress hosts. Beyond the minimums, a few practical features make hosting WordPress noticeably easier:

• The ability to choose your PHP version per site, so you can upgrade on your own schedule.
• Automatic daily backups with one-click restore, stored away from the server itself.
• A staging environment for testing updates before they hit the live site.
• SSH and WP-CLI access, which turns many chores (updates, search-replace, exports) into one-line commands.
• Server-level caching or an object cache such as Redis or Memcached.
• A data center region close to most of your visitors.

The four main types of WordPress hosting

Shared hosting

Your site lives on a server alongside many other customers’ sites, sharing CPU, memory and disk. It is the cheapest option and usually comes with a control panel (cPanel or a host’s own equivalent) and a one-click WordPress installer. The trade-off is that resources are capped and can be affected by neighbors. Shared plans are often sold at an introductory rate that renews higher, so read the renewal price before you commit to a long term.

VPS (virtual private server)

A VPS gives you a slice of a physical server with guaranteed resources and root access. You can tune the stack exactly as you like, but unless you buy a managed VPS, you are responsible for the operating system, security patches, firewall and backups. Panels such as those offered by server-management services can take some of that load off. A VPS suits developers and agencies comfortable with Linux administration.

Managed WordPress hosting

Managed hosts run infrastructure built only for WordPress and take on the operational work: core updates, caching, backups, staging, malware scanning and WordPress-aware support. You pay more than for shared hosting, and some managed hosts restrict certain plugins (typically caching or backup plugins that duplicate their own systems) or meter usage by visits or storage. For a business site where downtime costs money, it is often worth it. Our managed WordPress hosting guide covers what to ask before buying.

Cloud hosting

Cloud platforms such as AWS, Google Cloud, DigitalOcean and others let you rent compute, storage and databases by the hour and scale them independently. This is the most flexible option and the most demanding: you design the architecture yourself, or use a managed layer on top of a cloud provider. Many managed WordPress hosts actually run on these clouds behind the scenes.

Type	Relative cost	Technical effort	Typical fit
Shared	Lowest	Low	New blogs, small brochure sites
Managed WordPress	Medium to high	Lowest	Business sites, stores, busy blogs
VPS	Low to medium	High (unless managed)	Developers, multi-site agencies
Cloud	Variable, usage-based	Highest	High traffic, custom architectures

Choosing a plan by site size

Raw traffic is only part of the picture. What matters is how much work the server does per visit. A static-feeling blog with good page caching can serve a lot of readers from a small plan; a WooCommerce store or membership site, where logged-in users bypass the cache, needs far more PHP capacity for the same traffic.

• Personal blog or portfolio: a reputable shared plan or an entry-level managed plan is enough. Prioritize backups and HTTPS.
• Small business site: managed WordPress or a higher-tier shared plan with staging. Support quality matters more than raw specs.
• Online store or membership site: managed hosting or a well-resourced VPS with object caching. Check PHP worker limits and whether the host supports uncached cart and checkout pages properly.
• News, magazine or high-traffic site: plan for traffic spikes. Look for a CDN, full-page caching, and the ability to scale up quickly. A network of many sites may also benefit from WordPress Multisite.

Hosting is only one lever for speed. A lean theme, sensible image sizes and caching often matter as much; see our speed optimization techniques. If you are comparing specific providers, our guide to the best WordPress hosting lays out the criteria to judge them by. The WordPress project also maintains a short list of hosts on its hosting page.

Questions to ask before hosting WordPress anywhere

1. What is the renewal price, not just the first-term price?
2. How often are backups taken, how long are they kept, and can I restore them myself?
3. Is there a staging site, and can I push changes from staging to live?
4. Which PHP versions are available, and can I switch?
5. Are any plugins disallowed?
6. What are the limits on storage, inodes, bandwidth, visits or PHP workers, and what happens when I exceed them?
7. Is email hosting included, or will I need a separate provider?
8. Can I export my full site at any time without fees?

Migrating an existing site to a new host

A WordPress site is two things: the files (above all wp-content, which holds themes, plugins and uploads) and the database. Moving a site means copying both and updating the configuration.

The easy route

Many hosts offer free migration, either done by their staff or via their own plugin. Migration plugins such as Duplicator, All-in-One WP Migration or Migrate Guru also package the site and unpack it on the new server. Check the free tier’s size limits before relying on one.

The manual route

1. Take a full backup of the old site. See our WordPress backup guide.
2. Export the database (phpMyAdmin, mysqldump or wp db export) and download the files via SFTP or SSH.
3. Create a new database and user on the new host, then import the SQL file.
4. Upload the files and edit wp-config.php with the new database name, user, password and host.
5. If the domain or protocol changes, run a serialization-safe search and replace, for example wp search-replace 'http://old.example' 'https://new.example' --dry-run, then repeat without --dry-run.
6. Test the site on the new server before switching DNS, using a temporary URL or your computer’s hosts file.

The WordPress developer documentation has a detailed reference on moving WordPress. Avoid doing a plain text find-and-replace on the SQL file: WordPress stores some data as PHP-serialized strings with length prefixes, and editing them blindly corrupts the data.

DNS basics: pointing your domain at the host

Your domain registrar and your web host can be different companies. DNS is what connects them. There are two common approaches:

• Change the nameservers at your registrar to the ones your host provides. The host then manages all DNS records. Simple, but remember to recreate any existing email (MX) and verification (TXT) records on the host first.
• Keep DNS where it is and edit individual records: an A record for the root domain pointing to the server’s IPv4 address (plus an AAAA record if the host offers IPv6), and a CNAME for www pointing to the root domain or a hostname the host gives you.

DNS changes take time to spread because resolvers cache records for the duration of their TTL (time to live). A day or two before a migration, lower the TTL on the records you will change so the switch takes effect quickly. Leave the old host running until traffic has fully moved. A DNS and CDN service such as Cloudflare can sit in front of any host; our Cloudflare for WordPress guide covers the setup and the common redirect-loop pitfall.

Once the domain resolves to the new server, issue the TLS certificate, confirm that Settings → General shows the right https addresses, and force HTTPS with a redirect.

Frequently asked questions

Can I host WordPress on my own computer?

For development and testing, yes: tools like WordPress Studio and LocalWP run a site locally. For a public site, a home connection is rarely reliable or secure enough, and residential IP addresses change.

Does my host affect security?

Significantly. Account isolation, firewalls, malware scanning and current PHP versions all happen at the host level. The rest is up to you; our security hardening guide covers the site side.

When should I upgrade my plan?

When you see consistently slow uncached responses, resource-limit warnings, or errors during traffic peaks, and you have already optimized caching and plugins.

Key takeaways

• Hosting WordPress requires a current PHP version, MySQL or MariaDB, and HTTPS; check the official requirements page for exact versions.
• Shared hosting is cheapest, managed hosting is least work, VPS and cloud offer the most control at the cost of more administration.
• Match the plan to how much uncached work your site does, not only to visitor numbers.
• Always ask about renewal pricing, backups, staging and plugin restrictions before buying.
• Migrate files and database together, use a serialization-safe search-replace, and lower DNS TTLs before switching.