Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Hosting · Explainer

What Hosting Resources Does WooCommerce Need?

Short answer

A WooCommerce store needs PHP 8.3 or newer, MySQL 8.0 or newer or MariaDB 10.6 or newer, WordPress 6.9 or newer, a WordPress memory limit of 256 MB or more, and HTTPS support, as of November 2026. It also needs enough CPU and PHP workers for cart and checkout requests, which cannot be served from a page cache, plus fast storage and a persistent object cache.

Key takeaways

  • WooCommerce 10.8 and later asks for WordPress 6.9 or newer, PHP 8.3 or newer, and a WordPress memory limit of 256 MB or more.
  • Cart, Checkout and My Account pages must stay out of the page cache because they show data for one customer.
  • PHP 8.2 stops receiving security fixes on 31 December 2026, so a store should already run PHP 8.3 or newer.
  • High-Performance Order Storage is on by default for new stores since WooCommerce 8.2 and stores orders in dedicated tables.
  • The default WordPress object cache lasts for one request only, so a busy store needs a persistent cache such as Redis or Memcached.
  • Action Scheduler runs 25 actions per batch with one concurrent batch, so a backlog can delay order emails and renewals.

What does WooCommerce need from a host?

A WooCommerce store needs current PHP and database versions, at least 256 MB of WordPress memory, HTTPS, enough CPU and PHP workers for uncached checkout traffic, fast storage, page caching for the catalogue, and a persistent object cache.

WooCommerce is a WordPress plugin, so it runs on the same stack as WordPress, with extra load from carts and checkout. WooCommerce's server recommendations list the versions and limits a host should meet for WooCommerce 10.8 and later.

ItemWhat to ask for, as of November 2026Why it matters
WordPress6.9 or newerThe base WooCommerce runs on
PHP8.3 or newer, tested up to 8.4Runs every uncached page, cart and checkout
DatabaseMySQL 8.0 or newer, or MariaDB 10.6 or newerStores products, customers and orders
MemoryWordPress memory limit of 256 MB or moreRoom for WooCommerce, a theme and extensions
HTTPSSupported on every pageEncrypts logins, carts and checkout
Web serverApache or NginxServes PHP pages and static files

Start with a host that meets every row in that table. A plan that meets the WordPress minimums but not the WooCommerce ones will still install, then struggle under real orders. Read our guide on how to choose hosting for an online store before you compare plans.

What PHP and database versions should a WooCommerce host run?

Choose a host that offers PHP 8.3 or newer, tested up to PHP 8.4, with MySQL 8.0 or newer or MariaDB 10.6 or newer, as of November 2026.

WooCommerce's server recommendations set those versions for WooCommerce 10.8 and later, along with WordPress 6.9 or newer. WordPress.org goes further on the database: its Requirements page recommends PHP 8.3 or greater and MariaDB 10.11 or greater or MySQL 8.4 or greater. Meet the stricter database version when you can, since it covers both lists.

Version dates matter as much as version numbers. php.net lists security support ending on 31 December 2026 for PHP 8.2, 31 December 2027 for PHP 8.3 and 31 December 2028 for PHP 8.4. PHP 8.1 already reached end of life on 31 December 2025, so no new security fixes arrive for it.

Older versions still install in many cases, but that does not make them safe. WooCommerce notes that PHP 7.4 and MySQL 5.6 or MariaDB 10.4 still work in legacy environments, while warning that those versions have reached end of life and may expose a site to security vulnerabilities.

Pick a host that lets you change the PHP version yourself.

How much memory does WooCommerce need?

Set the WordPress memory limit to 256 MB or more, and make sure the host's PHP memory limit is at least that high.

WooCommerce lists a WordPress memory limit of 256 MB or greater in its server recommendations for WooCommerce 10.8 and later.

The WordPress limit is set by WP_MEMORY_LIMIT in wp-config.php, and it cannot exceed the PHP memory_limit the host allows. A host default below 256 MB will cap the store no matter what you set in WordPress.

Memory pressure grows with every extension you add. A payment gateway, a shipping calculator, a product filter and an email plugin all load on store pages.

Checkout, reports and product imports are the hungriest jobs. If checkout fails with memory errors, raise the limit toward 256 MB first, then remove extensions you do not use. Learn how to read the numbers on a plan in our guide on how to read a hosting plan's CPU and RAM limits.

How much CPU and how many PHP workers does a store need?

A store needs enough CPU and PHP workers to run cart, checkout and account requests at the same time, because those pages cannot be served from a page cache.

A PHP worker is a PHP process that handles one uncached request at a time. When every worker is busy, the next shopper waits, and checkout slows down or times out.

Catalogue pages rarely hit this limit because a page cache serves them without PHP, but every add to cart, checkout step and account page needs a free worker.

There is no single vCPU or worker number that fits every store. Traffic, extensions, the theme and the cache setup all change the answer, so hosts publish worker limits per plan. Ask the host how many PHP workers the plan includes and what happens when the limit is reached.

How much storage and what kind of disk does WooCommerce need?

Use fast SSD storage with room to grow for product images, the database, orders and backups.

Product images usually take the most disk space on a store, and the database grows with every product, customer and order.

A store with thousands of products and years of orders needs far more room than a new store with 20 products, so check the plan's disk limit against the catalogue you plan to have in a year, not the one you have today.

Ask the host whether the plan uses SSD or NVMe storage, since faster disks speed up catalogue pages and admin searches.

Backups need space too, and they belong somewhere other than the live server alone.

Keep a recent backup copy off the server so a disk failure or a bad update does not take the store and its only backup at the same time. Our guide on how to back up WordPress shows the routine to follow.

What caching does WooCommerce need, and what can never be cached?

Cache product and category pages, but keep Cart, Checkout and My Account out of the page cache, and add a persistent object cache for repeated database work.

WooCommerce's caching guide names Cart, Checkout and My Account as pages that must stay dynamic, because they show information specific to the current customer and cart. A cached checkout could show one shopper another shopper's cart, so every serious cache setup excludes those three pages by default or by setting.

The object cache is a separate layer. By default, the WordPress object cache is non-persistent: data lives in memory only for the duration of one request, as the WP_Object_Cache reference explains. A persistent object cache keeps those results between requests in Redis or Memcached, through a drop-in file at wp-content/object-cache.php.

That layer helps a store more than a blog because so much store traffic is logged in or has items in a cart.

WordPress Site Health recommends a persistent object cache on many sites, so ask the host whether Redis or Memcached is available on the plan. See our guide on how to speed up WordPress for the full caching order.

Judge speed against a fixed target, not a single lab test. Google's web.dev guidance rates a good page at LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less, judged at the 75th percentile of real visits.

How does High-Performance Order Storage change database needs?

High-Performance Order Storage stores orders in dedicated database tables, and it is on by default for new stores since WooCommerce 8.2.

Before version 8.2, WooCommerce stored orders in the WordPress _posts and _postmeta tables. High-Performance Order Storage, known as HPOS, uses four custom tables built for order queries: _wc_orders, _wc_order_addresses, _wc_order_operational_data and _wc_orders_meta, according to the HPOS documentation.

Dedicated tables keep order lookups simpler as the order count grows.

Existing stores are not moved to HPOS on their own. You switch under WooCommerce, then Settings, then Advanced, then Features, after checking that every extension declares HPOS support.

Turn on compatibility mode first so orders sync to both storage types, and the sync copies 25 orders at a time in the background. Read our guide on what HPOS is in WooCommerce before you switch a live store.

What scheduled jobs and cron setup does a store need?

Give the store a real server cron job for WP-Cron and watch the Action Scheduler queue, because orders, emails and renewals depend on background jobs.

WordPress runs scheduled jobs through WP-Cron, which only fires when a page loads. Pages served from a full page cache do not load WordPress, so they do not trigger it. The fix is to set DISABLE_WP_CRON to true in wp-config.php and have the server call wp-cron.php on a fixed schedule instead.

WooCommerce hands background work to Action Scheduler, its built-in job queue, which runs order emails, stock updates, webhooks and subscription renewals.

The Action Scheduler documentation states that it runs 25 actions per batch, with one concurrent batch and a maximum of 30 seconds per request, and that an action running for more than 5 minutes is marked as failed.

Check the queue under WooCommerce, then Status, then Scheduled Actions. A few failed actions are normal, but a growing list of pending actions older than a day points to a cron or worker problem, not to a single broken email. Fix the schedule first, then re-run the failed actions.

How do you check your hosting setup in WooCommerce?

Open WooCommerce, then Status, in your admin to see WordPress, PHP and database versions, the memory limit and missing extensions in one report.

The System Status report checks your server against the current WooCommerce release and flags anything that falls short.

Compare each line with the server recommendations for WooCommerce 10.8 and later: WordPress 6.9 or newer, PHP 8.3 or newer, MySQL 8.0 or newer or MariaDB 10.6 or newer, HTTPS, and a WordPress memory limit of 256 MB or more.

Then open Tools, then Site Health, then Info in WordPress. Its Server and Database sections show the web server, PHP settings and database versions the host provides.

  1. Open WooCommerce, then Status, and read the System Status report.
  2. Note every line flagged in red or below the recommended version.
  3. Open Tools, then Site Health, then Info, and compare the server details.
  4. Ask the host to fix shortfalls you cannot change yourself.

When should you move from shared hosting to a VPS or managed plan?

Move from shared hosting when checkout slows at peak times, PHP workers run out, or the plan cannot raise memory, PHP or worker limits.

Shared hosting suits a small store with light traffic because the catalogue cache carries most visits. The move becomes necessary when uncached traffic grows: more checkouts at once, more logged-in shoppers, or a sale that fills every PHP worker. A VPS or managed plan gives the store its own CPU, memory and worker pool.

Do not judge the move by visitor count alone. A store with 500 visitors a day and a busy checkout can need more workers than a blog with 5,000 readers, because blog readers get cached pages and shoppers do not.

Before you move, list what the new plan must include: the PHP and database versions above, a 256 MB memory limit, enough PHP workers, a persistent object cache, daily backups and a staging site. If a plan cannot name those limits in writing, it is not an upgrade.

What mistakes should you avoid?

Avoid these seven mistakes and most hosting problems never reach your shoppers.

  • Picking a host on price alone when its PHP version or memory limit falls below the WooCommerce minimums.
  • Caching the Cart, Checkout or My Account pages, which can mix up one shopper's data with another's.
  • Running PHP 8.1 or older after its security support has ended.
  • Ignoring the Action Scheduler queue until order emails or renewals stop.
  • Keeping the only backup on the same server as the live store.
  • Adding extension after extension without checking memory, workers and HPOS support first.
  • Judging a plan by visitor count while ignoring how much of the traffic reaches checkout.

Frequently asked questions

Can WooCommerce run on shared hosting?

Yes, a small store with light traffic can run on shared hosting if the plan meets the WooCommerce minimums: PHP 8.3 or newer, MySQL 8.0 or MariaDB 10.6 or newer, a 256 MB memory limit and HTTPS. The limit appears when many shoppers check out at once, because checkout pages need free PHP workers and cannot be cached. Move to a larger plan when checkout slows at peak times.

How much RAM does a WooCommerce store need on the server?

WooCommerce asks for a WordPress memory limit of 256 MB or more, which is the memory one PHP request may use. Total server RAM is a separate number set by the host, and it must also cover the operating system, the database, the web server and every PHP worker at once. Ask the host for both numbers, and raise the memory limit before adding more extensions.

Does WooCommerce need a VPS?

No, WooCommerce does not need a VPS by itself. A small store can run on shared or managed hosting that meets the version and memory requirements. A VPS becomes useful when the store outgrows shared limits on CPU, PHP workers or memory, or when it needs a persistent object cache and server cron jobs the shared plan does not offer.

Why is my WooCommerce checkout slow even with a caching plugin?

Checkout cannot be cached, so a caching plugin does not help it. Every checkout request runs PHP, reads the cart and writes an order, which needs free PHP workers, enough CPU and a fast database. Slow checkout usually means workers are busy, the database is slow, or an extension adds heavy work to the request. Check the PHP worker limit and the Action Scheduler queue first.

Do I need Redis for WooCommerce?

Redis is not required, but a persistent object cache such as Redis or Memcached helps a busy store. The default WordPress object cache only lasts for one request, so repeated database lookups run again on every page. A persistent cache keeps those results between requests, which matters most for logged-in shoppers and cart pages that a page cache cannot serve.

What is the minimum PHP version for WooCommerce in November 2026?

For WooCommerce 10.8 and later, the recommended PHP version is 8.3 or newer, tested up to PHP 8.4. WooCommerce still works with PHP 7.4 in legacy environments, but that version has reached end of life and may expose the store to security vulnerabilities. PHP 8.2 stops receiving security fixes on 31 December 2026, so plan the move to PHP 8.3 or 8.4 now.

Sources

  1. Server Recommendations WooCommerce
  2. Requirements WordPress.org
  3. High-Performance Order Storage WooCommerce
  4. Configuring Caching Plugins WooCommerce
  5. Supported Versions PHP.net
  6. WP_Object_Cache WordPress Developer Resources
  7. Web Vitals web.dev

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test