WordPress hosting: what matters
WordPress runs on almost any shared hosting, so the choice seems easy. But the plan decides how fast the site opens, whether it gets security fixes and whether you can bring it back after a plugin update goes wrong. Below: what WordPress requires, what to check in a plan, what it costs and when shared hosting is no longer enough.
The short answer. You need a plan with recent PHP (8.3 or newer) and MySQL 8.4 or MariaDB 10.11, at least one database, free SSL and daily backups that you can restore yourself. A "for WordPress" label in the plan name guarantees nothing by itself: compare the specifications. Such hosting is enough for a blog or a company website, while a busy shop or a site with dozens of plugins will sooner or later need a VPS.
What WordPress requires
The official WordPress recommendations (the page was updated in May 2026):
| Component | Recommended | Still works, but outdated |
|---|---|---|
| PHP | 8.3 or newer | 7.4 or newer |
| Database | MySQL 8.4+ or MariaDB 10.11+ | MySQL 5.5.5 or newer |
| Web server | Apache or Nginx | any with PHP and MySQL |
| Connection | HTTPS | — |
The WordPress developers state plainly that old versions are not secure: their support has ended and they no longer receive fixes. Apache needs the mod_rewrite module, without which readable page addresses such as /blog/my-post do not work.
What to check in a plan
According to the accsly.io catalog as of 15 November 2026, 2,764 hosting plans at 698 hosts are suitable for WordPress: they include at least one database and no less than 5 GB of disk. But hosts leave out many of the parameters that matter for WordPress. What to check before you pay:
- PHP versions and switching between them. PHP versions are named for only 362 of the 9,497 hosting plans in the catalog; PHP 8.3 or newer for 154, while for 124 the newest version is 8.1 or older. Ask support which versions are available and whether you can switch the version yourself in the panel. Ask about the PHP memory limit (memory_limit) too: WooCommerce, for example, asks for at least 256 MB.
- Databases. One database is enough for one site. A second one is needed for a staging copy, where updates are tested before going live.
- Disk type. On NVMe the database and files are read faster than on SATA SSD. Of the plans suitable for WordPress, 912 are on NVMe and 1,846 on SSD. The difference shows on sites with a large database and in the admin area, which runs many queries. More in the article NVMe or SSD.
- Free SSL. It is listed for 1,008 suitable plans and explicitly absent from 27; for the rest the host does not mention it. How certificates work is covered in the article SSL certificates for a website.
- Backups. They are listed for 798 plans. Find out how often copies are made, how many days they are kept and whether you can restore a single database or a single folder without contacting support.
- Cron. The built-in WordPress scheduler (WP-Cron) runs when pages are visited: on a site with few visitors, scheduled posts and mailings run late, and on a busy one it adds needless load. It is better to switch it off with the DISABLE_WP_CRON constant and run wp-cron.php from a system cron job every few minutes, so the plan needs cron access.
- Hidden limits. The number of processes, the number of files (inodes) and the account's CPU time. How to find them in a host's terms is explained in the article How to read hosting plans.
"WordPress hosting" versus ordinary hosting
The catalog has 742 plans at 242 hosts with WordPress or WP in the name. Often this is ordinary hosting with WordPress preinstalled, a caching plugin and automatic core updates. Sometimes a one-click staging copy and protection against password brute-forcing are added. That is convenient, but the same features are usually available in the ISPmanager, cPanel or Plesk panel on any plan. So compare the specifications, not the name: a "WordPress" plan with one database and 3 GB of disk loses to an ordinary one with NVMe, several databases and daily backups. The same goes for "Bitrix" plans: what to check in them is covered in Hosting for 1C-Bitrix.
What it costs
Prices are as recorded in the catalog on 15 November 2026, per month with monthly billing and no prepayment for a year, in the host's own currency. Whether tax is included depends on the host and the country, so check it when ordering.
| Plans suitable for WordPress | Median per month | Number of plans |
|---|---|---|
| Priced in US dollars | $7.99 | 625 |
| Priced in euros | €8.95 | 506 |
| Priced in roubles (Russian hosts) | ₽820, a quarter cheaper than ₽400 | 129 |
Examples of plans that state the PHP version, free SSL and backups:
- FastFox, "Fox Start": ₽240 a month (₽2,280 when paid for a year): 2 sites, unlimited databases, 10 GB NVMe, PHP 7.4 to 8.5, backups kept for a month.
- LogicWeb, "Go": $5 a month: unlimited sites, 100 GB NVMe, PHP up to 8.4, daily backups for 7 days.
- acens, "Hosting Esencial": €6.9 a month: 25 databases, 100 GB NVMe, PHP up to 8.5, daily backups for up to 7 days.
About a quarter of the hosting plans in the catalog are sold only with payment several months in advance, so compare the price per month. All plans with a database and at least 5 GB of disk are in the selection hosting for WordPress.
WordPress security on shared hosting
WordPress sites are most often hacked through outdated plugins and themes, not through the host's server. Recommendations are in the WordPress hardening guide; in practice, what matters most is this:
- update the core, plugins and themes, and test major updates on a staging copy first;
- remove plugins and themes you do not use: even when deactivated, they stay on the disk;
- do not install plugins and themes from unofficial sources;
- turn on two-factor login for administrators and do not use the username admin;
- keep a copy of the site somewhere other than the host: export the database and files once a week to another location (more in Server backups).
When WordPress should move to a VPS
Shared hosting stops being enough when the site hits the account limits on ordinary days, not only at peaks. The signs: errors 503 and 508, a slow admin area whatever caching you use, a WooCommerce shop with thousands of products, or a need for Redis as an object cache or for your own web server configuration. Such a site usually does well on a VPS with 2 vCPU and 4 GB of memory: according to the catalog, the median price of such a plan is ₽1,080 a month at Russian hosts (164 plans), and €16.31 and $24.99 at hosts elsewhere. A selection: VPS for WordPress. When a move is justified is covered in the article When to move from shared hosting to a VPS, and the move itself in the article How to move a website from shared hosting to a VPS. If your WordPress site is a shop, read How to choose hosting for an online shop as well.