Start with WordPress’s current recommended environment: PHP 8.3 or later, MariaDB 10.11 or later or MySQL 8.0 or later, and HTTPS. Then check your plugins, recovery process and support responsibilities. Meeting the software baseline does not prove a plan has enough capacity for your particular site.
Research scope. Software recommendations checked against WordPress and WooCommerce documentation on 15 September 2026. This is a hosting-purchase checklist, not a benchmark or a guarantee that one RAM size supports a fixed visitor count.
Disclosure. HostingHunt may earn a commission from qualifying purchases. Commercial relationships do not determine our recommendations. How affiliate links work.
The official software baseline
Use the current recommendations when choosing a new plan, rather than an old minimum version copied into a hosting article. WordPress notes that it can run on some older software versions, but warns that those versions have reached end of life and can expose the site to vulnerabilities.
| Requirement | What to verify with the host |
|---|---|
| PHP | Version 8.3 or later, compatible with your plugins |
| Database | MariaDB 10.11+ or MySQL 8.0+ |
| Secure connection | HTTPS support and a certificate renewal process |
| Web server | WordPress recommends Apache or Nginx |
| Updates | A supported upgrade path for the software you actually use |
Check the whole site, not just WordPress core
Make a short list of your essential theme, shop, membership, booking and page-building tools. Check their supported environments before changing PHP versions or buying a new plan. A host’s ability to install WordPress does not establish compatibility with every extension you use.
Test changes on a staging copy with representative content. Exercise the parts that matter to the business: account creation, forms, payments, search, uploads and scheduled work. A successful homepage preview cannot reveal all plugin or integration failures.
Ask whether the plan lets you choose a supported PHP version and safely test an upgrade. Also ask how long a rollback is available. Do not keep an unsupported runtime indefinitely simply because an old plugin depends on it; plan to update or replace that dependency.
WooCommerce adds requirements and a different workload
WooCommerce’s current server guidance for version 10.8 and later recommends a WordPress memory limit of at least 256 MB, alongside its version and HTTPS requirements. The WordPress memory limit concerns memory available to PHP execution; it is not the same thing as the total RAM size of a server.
For a store, check both WordPress’s current recommendations and WooCommerce’s requirements for the version you intend to run. WooCommerce’s system status report can help identify the actual environment and settings. Do not assume a value shown in a documentation example is a universal requirement.
In practical testing, include an uncached cart and checkout, logged-in customers, product search and any scheduled imports. Ordinary page caching does not make every store operation free of server work. A shop with complex integrations may need more headroom than a content site with similar traffic.
There is no universal RAM-to-visitors conversion
Monthly visitor totals hide how people use a website. A cached article read and an uncached product-filter request do not require the same work. Traffic arriving all at once can also behave very differently from the same total spread over a month.
Ask the host about the limits that matter for your plan: CPU access, concurrent PHP work, database resources, disk space, file counts and transfer. When a limit is exceeded, find out whether the result is an extra charge, slower responses, errors or a required upgrade.
If you already have a site, bring recent resource observations and error logs without exposing personal data. If the site is new, test a realistic version and choose an upgrade path. Avoid pretending that a single memory number proves production readiness.
- Include media, databases, logs and staging copies in storage estimates.
- Test the busiest important journey, not just the front page.
- Measure errors and response time while the site handles concurrent activity.
- Leave room for backups, imports and updates that temporarily increase resource use.
Require a recovery plan, not just a backup badge
Ask what is backed up, how often, how long copies are retained and whether you can download one independently. Confirm whether staging and backups consume your main plan’s storage. Understand whether a restore overwrites the whole site or can recover a specific component.
For a store, decide how much recent order data you can tolerate losing. A backup taken before the last working day may be technically restorable while still being a poor business recovery point. Design the backup approach around that risk rather than selecting the cheapest schedule automatically.
Rehearse a restore before the launch or migration. Confirm that the restored database, media and configuration agree, and that test environments do not send real messages or process real payments. Record the steps and the people authorized to perform them.
Send this brief to a shortlisted host
You do not need to become a server specialist to buy carefully. Describe the website in ordinary language and ask the provider to map it to an exact plan. Keep the response with your purchase notes so everyone knows what was agreed.
- We are building a blog, business website, store or membership site; these are the essential plugins.
- Please confirm supported PHP and database versions and how upgrades are tested.
- Please identify the relevant resource limits and what happens when we exceed them.
- Tell us who handles system updates, website updates, security incidents and recovery.
- Explain the backup schedule, retention, restore process and any additional charges.
- Confirm the complete recurring cost, renewal price and migration or cancellation process.
Common questions
Does WordPress need a VPS?
No. Choose an environment that meets the software, capacity and operational requirements. A suitable managed or shared service can be a better fit when you do not want server administration.
Is 256 MB enough RAM for a WooCommerce server?
The 256 MB recommendation refers to WordPress’s memory limit, not total server RAM. The server also has other processes and concurrent work to support. Size the deployment from the workload.
Can I use an old PHP version if the site still loads?
A page loading is not evidence of a supported or safe environment. Check current support requirements and plan a tested upgrade or dependency replacement.
Does managed WordPress hosting update everything?
Do not assume so. Ask which system, core, plugin and theme updates are included, who checks compatibility, and what happens if an update breaks the site.
Find hosting for what you’re building.
Tell us about your project, budget and how much help you need. Build a shortlist, then verify the final plan and price with the provider.
Help me choose hosting