Choosing hosting for a WooCommerce store is not the same as choosing hosting for a small brochure website. A store has logged-in sessions, carts, checkout requests, background jobs, database-heavy admin screens, payment callbacks, stock updates and often external integrations running at the same time.
The result is simple: a hosting plan can look fast on a cached homepage while still struggling badly where WooCommerce actually does work.
This guide explains the WooCommerce hosting requirements that matter in 2026, what the official minimums do and do not tell you, and how to evaluate a hosting environment before performance problems become operational problems.
Official WooCommerce server requirements in 2026
WooCommerce currently recommends a modern WordPress environment with PHP 8.3 or newer, MySQL 8.0 or newer (or MariaDB 10.6+), HTTPS, and a WordPress memory limit of at least 256 MB. The official server recommendations are a useful compatibility baseline, but they are not a sizing guide for every store.
That distinction matters. Meeting the minimum software requirements means WooCommerce can run. It does not mean a particular server has enough CPU, RAM, database capacity or concurrency for your catalog, traffic and integrations.
There is also a timely reason to review older hosting environments. On September 8, 2026, the WooCommerce development team proposed raising the minimum PHP requirement to PHP 8.1 for WooCommerce 11.5, currently targeted for January 2027. Stores still running PHP 7.4 or 8.0 should therefore treat a runtime upgrade as a real planning item, not indefinite technical debt.
Official references: WooCommerce server recommendations and the WooCommerce PHP requirement proposal.
1. PHP version: compatibility and execution speed both matter
PHP executes much of the application logic behind WooCommerce. Running a current supported PHP release gives you security fixes and generally better runtime performance than legacy branches.
For a production store, do not choose a host merely because it technically offers PHP. Check whether you can select current PHP versions yourself, whether upgrades can be tested on staging, and whether the host keeps supported versions available promptly.
This becomes especially important on stores with custom plugins or integrations. A PHP upgrade can expose compatibility problems in old themes, abandoned extensions or custom snippets. Test the full purchasing workflow on staging: product pages, cart, checkout, payment methods, transactional email, scheduled tasks and any external API or ERP flow.
2. Memory limit: 256 MB is a baseline, not a performance strategy
WooCommerce recommends a WordPress memory limit of at least 256 MB. If a process exceeds available memory, you can see fatal errors, failed imports, incomplete background jobs or slow admin operations.
But simply increasing the limit does not solve every problem. A plugin consuming excessive memory remains inefficient at 512 MB; it merely has more room before failing.
Check both the PHP memory limit and WordPress memory limit under WooCommerce → Status → System Status. If the store repeatedly approaches the limit during imports, reports or large batch operations, investigate the workload rather than blindly raising the ceiling.
3. CPU and concurrency are often more important than disk space
Hosting marketing tends to emphasize storage and bandwidth because they are easy numbers to compare. For WooCommerce, CPU availability and the number of PHP requests the environment can process concurrently are often much more important.
A visitor opening a cached page may consume very little PHP. A customer adding a product to the cart, calculating shipping, logging in or checking out triggers dynamic work that cannot simply be served as the same cached HTML to everyone.
Concurrency becomes visible during campaigns and traffic spikes. Ten customers checking out simultaneously are not equivalent to ten people reading a cached blog article.
WooCommerce’s scaling guidance uses a simple baseline for self-hosted environments: around 1 vCPU, 2 GB RAM, PHP OPcache, a CDN for static assets and persistent caching such as Memcached. Larger or more complex stores need sizing based on their actual workload rather than this starting point.
4. Database performance matters more as the catalog grows
WooCommerce is database-intensive. Products, variations, orders, customer data, metadata, sessions and extension-specific records all create queries.
A store with 100 simple products behaves very differently from a catalog with 50,000 products and hundreds of thousands of variations. Large catalogs also amplify inefficient queries from plugins, filters and custom functionality.
When evaluating hosting, look beyond the database version. Ask whether the database shares heavily constrained resources, whether slow-query diagnosis is possible, and whether persistent object caching is available.
If catalog operations themselves are becoming repetitive, hosting is only one part of the problem. Our guide to WooCommerce dynamic product collections explains how rule-based catalog automation can reduce manual category maintenance as product data changes.
5. Caching helps, but checkout must remain dynamic
Page caching is excellent for public catalog and content pages, but WooCommerce contains user-specific areas that must be handled carefully. Cart, checkout, account data and session-dependent responses cannot be treated like a static landing page.
A good WooCommerce hosting stack normally combines several layers:
- page caching where responses are safe to reuse;
- PHP OPcache for compiled PHP bytecode;
- persistent object caching for reusable database-derived objects;
- a CDN for images, CSS, JavaScript and other static assets;
- correct cache exclusions for cart, checkout and account workflows.
A cache plugin cannot compensate for a slow database query, a blocking external API call or an overloaded PHP worker pool. Treat caching as one layer of the architecture, not as a universal fix.
6. Background jobs can make or break store reliability
Modern WooCommerce stores do significant work outside the page request itself. Imports, email, subscription operations, webhooks, synchronization tasks and extension jobs often run through WP-Cron or Action Scheduler.
This is where weak hosting can create confusing failures. The storefront may appear normal while queues accumulate in the background.
For stores with important scheduled operations, check:
- whether cron execution is reliable;
- whether long-running PHP processes are aggressively terminated;
- whether Action Scheduler queues can be inspected;
- whether server logs are accessible;
- whether command-line WP-CLI is available for maintenance and diagnostics.
Large media operations also benefit from controlled queues instead of trying to process everything in one request. Our guide to importing WooCommerce product images from URLs covers the operational side of remote media workflows.
7. ERP and API integrations change the hosting requirements
A standalone store is one thing. A WooCommerce installation connected to an ERP, CRM, supplier feed, courier service, payment gateway and custom APIs is a distributed system.
External calls introduce latency and failure modes that hosting benchmarks do not capture. An ERP may be unavailable. An API may respond slowly. A supplier feed may suddenly contain tens of thousands of updates.
Do not run heavy synchronization blindly inside customer-facing requests. Reliable integrations usually need explicit queues, batching, retries, idempotency and logging. Read our WooCommerce ERP integration architecture guide for a deeper treatment of those decisions.
8. Shared hosting, managed WooCommerce hosting or VPS?
Shared hosting
Shared hosting can be perfectly adequate for a small store with modest traffic and a lightweight extension stack. The risk is not the label “shared”; it is resource opacity. Two plans with similar storage can have very different CPU limits, process limits and database performance.
Managed WooCommerce hosting
Managed hosting can reduce operational work by providing caching, backups, staging, security controls and WooCommerce-aware configuration. It is useful when the store owner does not want to manage the server stack directly.
VPS or cloud server
A VPS provides more control and clearer resource allocation, but also transfers more responsibility to whoever manages it. Updates, backups, firewall rules, monitoring, database tuning and incident response do not disappear just because the server is more powerful.
Choose a VPS when the workload or architecture justifies the control, not simply because “VPS” sounds faster.
How to evaluate a WooCommerce host before migrating
Use a workload-based checklist rather than comparing only headline specifications.
- Runtime: current PHP, MySQL/MariaDB and WordPress compatibility.
- Memory: at least the recommended WooCommerce baseline, with room for real workloads.
- CPU: enough capacity for uncached PHP requests and background processing.
- Database: responsive storage and the ability to diagnose slow queries.
- Caching: OPcache, persistent object cache and correct WooCommerce page-cache rules.
- Staging: a safe place to test PHP, WooCommerce and plugin upgrades.
- Backups: automated backups with a tested restore path.
- Observability: PHP/server logs and access to WooCommerce/Action Scheduler diagnostics.
- Cron: reliable scheduled execution.
- Integrations: sufficient execution capacity for feeds, ERP/API sync and webhooks.
Common mistake: upgrading hosting before finding the bottleneck
A faster server can hide inefficient software, but it does not fix the architecture.
Before migrating, identify what is actually slow. Is time spent in PHP execution, database queries, an external API, image processing, background queues or frontend assets? Does the problem affect every page or only checkout/admin/import operations?
This distinction can save money. A store blocked by a slow third-party API will not suddenly become reliable because the server has twice as much RAM. Likewise, a badly indexed query may continue to degrade as the database grows.
FAQ
How much RAM does a WooCommerce store need?
There is no universal number. WooCommerce’s scaling guidance uses 2 GB RAM as a baseline for a simple self-hosted setup, but catalog size, traffic, plugins, imports and integrations can raise the requirement substantially. Size the environment from observed workload.
Is 256 MB PHP memory enough for WooCommerce?
256 MB is the current recommended WordPress memory baseline from WooCommerce. It may be enough for many stores, but large imports, complex extensions or batch operations can require more. Repeated memory exhaustion should trigger investigation, not only a larger limit.
Does WooCommerce need a VPS?
No. A small WooCommerce store can run well on good shared or managed hosting. A VPS becomes useful when you need more predictable resources, control or architecture-specific services and have the capability to manage them properly.
Which PHP version should WooCommerce use in 2026?
WooCommerce currently recommends PHP 8.3 or newer. The WooCommerce team has also proposed PHP 8.1 as the minimum for WooCommerce 11.5, targeted for January 2027. Stores on PHP 7.4 or 8.0 should plan and test an upgrade.
Final recommendation
Good WooCommerce hosting is not the plan with the largest storage number. It is the environment that can execute dynamic commerce requests reliably, keep the database responsive, process background jobs, support current software versions and give you enough visibility to diagnose failures.
If a store has complex catalog logic, ERP/API synchronization or custom operational workflows, hosting and application architecture need to be evaluated together. WebCraft Masters builds custom WooCommerce systems and integrations around those real workloads rather than treating infrastructure as an isolated checkbox.