WooCommerce Hosting Requirements: Your 2026 Server Guide

Running a WooCommerce store on the wrong hosting plan is one of the fastest ways to lose sales you never knew you had. Before you pick a plan or migrate a store, here is the short version of what you need:

Minimum specs to run WooCommerce at all:

• WordPress 6.6 or greater, with 6.9 or greater recommended per WooCommerce's official server documentation
• PHP version at least 8.1, with 8.3 or greater strongly preferred
• MySQL 8.0+ or MariaDB 10.6+
• Valid HTTPS/SSL certificate
• PHP memory limit set to at least 256 MB

Recommended baseline for any production store:

• PHP 8.3+ (tested to 8.4), with OPcache and PHP-FPM enabled
• MySQL 8.0+ or MariaDB 10.6+, InnoDB storage engine
• 512 MB+ PHP memory
• NVMe SSD storage
• Object caching (Redis or Memcached) and a CDN for static assets

Three checks to run right now:

1. Open your terminal and run php -v to confirm your PHP version.
2. In WordPress, go to Tools > Site Health or run wp --info via WP-CLI to see your environment summary.
3. Load your storefront over HTTPS and confirm the padlock is valid with no mixed-content warnings.

Pro Tip: Saving $5/month on a cheap shared plan often costs far more in lost conversions during slow page loads and checkout errors. A host built for WooCommerce pays for itself quickly.

Key Takeaways

Meeting WooCommerce hosting requirements means matching PHP 8.3+, MySQL 8.0+/MariaDB 10.6+, 512 MB PHP memory, NVMe storage, and object caching to your store's actual traffic tier before launch.

Table of Contents

• What are the exact WooCommerce hosting requirements?
• Which PHP extensions and settings does WooCommerce need?
• What optional components make a real difference for WooCommerce?
• What security does WooCommerce hosting require?
• How much RAM, CPU, and storage does your store actually need?
• How do you verify and change your server settings?
• Which hosting type is right for your WooCommerce store?
• How does inSave Hosting map to WooCommerce store tiers?
• Why your hosting choice is really a revenue decision
• inSave Hosting delivers what WooCommerce stores actually need
• Sources
• FAQ

What are the exact WooCommerce hosting requirements?

WooCommerce's server requirements draw a clear line between what will technically run the software and what will actually serve customers well. The gap between those two things is where most store owners get burned.

Software version minimums vs. recommended

PHP version matters more than most people realize. WooCommerce's PHP and WordPress update documentation maps each WooCommerce release to its minimum PHP and WordPress versions, and the pattern is consistent: each new WooCommerce major version drops support for older PHP releases. Running PHP 8.3+ is not just a performance choice. It is a security boundary. PHP 8 releases offer improved requests-per-second and memory efficiency compared to PHP 7.x, which reached end-of-life in late 2022.

For databases, InnoDB is the required storage engine for both MySQL and MariaDB. MyISAM lacks row-level locking, which causes table-level locks under concurrent WooCommerce writes. That translates directly to checkout failures during traffic spikes. WordPress's own requirements page confirms MySQL 8.0 or MariaDB 10.6 as the current recommended baseline.

HTTPS is not optional. A store without a valid SSL certificate will trigger browser security warnings, fail modern payment gateway requirements, and lose the HTTP/2 multiplexing that speeds up asset delivery. HTTP/2 requires TLS, so your SSL certificate is also a performance dependency, not just a trust signal.

Quick verification commands:

1. php -v — confirms PHP version and build date
2. mysql --version — confirms MySQL or MariaDB version
3. wp core version — confirms WordPress version via WP-CLI
4. wp option get woocommerce_db_version — confirms WooCommerce database schema version

Which PHP extensions and settings does WooCommerce need?

WooCommerce itself requires a specific set of PHP extensions, and many popular payment gateways and shipping plugins add their own dependencies on top. Missing one extension typically surfaces as a cryptic plugin error rather than a clear message.

Required PHP extensions:

• cURL — payment gateway API calls and webhook delivery
• mbstring — multibyte string handling for international characters and email
• OpenSSL — encrypted connections to payment processors and external APIs
• ZIP — plugin and theme installation/updates
• json — data interchange with every modern API
• dom and xml — HTML/XML parsing used by shipping calculators and feed generators
• SimpleXML — required by several shipping and tax extensions

Optional but frequently required:

• SOAP — some legacy shipping carriers and ERP integrations depend on it
• intl — localized number formatting and currency display for international stores

Performance extensions to enable:

• OPcache — caches compiled PHP bytecode in memory, cutting PHP CPU cost on every request. WooCommerce's server recommendations list OPcache explicitly as a recommended component. Enable it and set opcache.memory_consumption to at least 128 MB.
• PHP-FPM — process manager that gives WooCommerce isolated PHP workers instead of sharing a process pool with other sites on the server.

Key php.ini settings and practical targets:

max_input_vars deserves special attention. WooCommerce product pages with many attributes and variable products POST large arrays. The default value of 1000 causes silent data truncation on complex product saves. Set it to at least 3000 for any store with variable products.

To check which extensions are loaded, run php -m. To see all runtime settings, run php -i | grep memory_limit or load a phpinfo() page in a temporary file.

Pro Tip: When contacting your host's support team, ask specifically: "Can you enable OPcache with at least 128 MB memory_consumption, and confirm PHP-FPM is running isolated workers for my account?" Vague requests get vague responses.

What optional components make a real difference for WooCommerce?

Some of these are labeled "optional" in official documentation, but for any store taking real orders, they function more like requirements.

Server-level caching vs. plugin caching

LiteSpeed with LSCache and Nginx with microcaching both operate below the PHP layer, serving cached responses without spawning a PHP process at all. Plugin-based caches like W3 Total Cache or WP Rocket still invoke PHP before serving the cached file. The server-level approach is faster and uses fewer resources. The critical caveat: WooCommerce cart, checkout, and My Account pages must be excluded from full-page caching. A caching misconfiguration that caches Cart or Checkout pages is one of the most common causes of customers seeing each other's cart contents or getting checkout errors. WooCommerce-aware caching platforms handle these exclusions automatically. For a deeper look at plugin options, this overview of caching plugins for WooCommerce covers the leading approaches.

Object caching with Redis

Redis moves frequent database query results into RAM. For a store with hundreds of SKUs, every product page load triggers inventory checks, pricing rules, and session lookups. Without object caching, those queries hit MySQL on every request. Object caching with Redis substantially reduces database load and becomes near-mandatory once a store crosses a few hundred daily orders.

CDN for static assets

A CDN offloads product images, CSS, and JavaScript to edge nodes closer to the customer. That frees PHP workers to handle dynamic requests like cart updates and checkout submissions instead of serving static files. For stores with international customers, a CDN can cut time-to-first-byte by several hundred milliseconds on image-heavy product pages.

Backups and staging

Daily automated backups are the floor. For active stores, real-time or hourly transaction-level backups are worth the extra cost. A staging environment lets you test plugin updates and theme changes before they touch live orders. Losing a day of order data because a plugin update broke the database is a recoverable disaster only if you have a backup from before the update. For a comparison of backup approaches, this guide to backup plugins for WooCommerce covers the main options.

Pro Tip: If your budget is tight, prioritize in this order: Redis object cache, daily backups, then CDN. Server-level caching usually comes with the hosting plan itself.

What security does WooCommerce hosting require?

WooCommerce stores handle payment data, personal information, and order records. The hosting environment is the first line of defense.

HTTPS and PCI considerations

A valid SSL certificate is mandatory. WordPress has pushed for site-wide HTTPS since 2016, and modern browsers actively warn users on non-HTTPS pages. For payment compliance, the PCI Security Standards Council sets the framework for how card data must be handled. Most WooCommerce stores use redirect-based payment flows (Stripe, PayPal) that keep card data off your server entirely, which significantly reduces your PCI scope. Your host still needs to provide a segregated, patched environment. This is general guidance; consult a qualified security assessor for your specific compliance obligations.

File and folder permissions

WordPress core files should be set to 644 for files and 755 for directories. The wp-config.php file warrants 600 or 640. The wp-content/uploads directory needs write access (755 or 775 depending on your server user setup), but executable permissions on uploaded files should be blocked at the server level. Never set directories to 777. That opens every file in the directory to modification by any process running on the server.

Host-level security features to require:

• Web application firewall (WAF) that filters malicious requests before they reach PHP
• Automated malware scanning with alerts
• Automated core and plugin update options or at least notifications
• Daily backups with off-server storage
• DDoS mitigation at the network edge

For a practical hardening checklist, the WordPress security guide for SMBs covers file permissions, login hardening, and plugin hygiene in detail. You can also find a broader overview of security measures for budget WordPress hosting that applies directly to WooCommerce environments.

Pro Tip: When opening a support ticket about security, be specific: "Please confirm the WAF is active on my account, that PHP execution is blocked in wp-content/uploads, and that daily backups are stored off-server." Generic requests get generic answers.

How much RAM, CPU, and storage does your store actually need?

WooCommerce's workload is fundamentally different from a blog or brochure site. A blog serves mostly cached HTML. WooCommerce generates uncached PHP responses for cart updates, checkout submissions, session management, and inventory writes. Every active shopper at checkout is consuming a PHP worker for the duration of that request.

These figures align with traffic-aware resource targets from Prestige Technologies and the workload analysis from OpsForge Labs.

PHP workers and checkout concurrency

Each PHP worker handles one request at a time. If your store has 10 workers and 12 shoppers hit checkout simultaneously, two of them wait. That wait shows up as a slow or stalled checkout. Estimate your peak concurrent shoppers and add 30–50% headroom. A flash sale or holiday promotion can spike concurrent users 3–5x above your daily average.

Why NVMe storage matters

NVMe drives deliver dramatically higher IOPS than standard SATA SSDs. WooCommerce's checkout process writes to the database repeatedly: order creation, inventory decrement, session update, payment confirmation. Each write is a disk operation. On a high-IOPS NVMe drive, those writes complete in microseconds. On a slow shared disk, they queue. That queue is what turns a 2-second checkout into an 8-second one.

Pro Tip: Buy 25–50% more resources than your current traffic requires. Hosting upgrades during a flash sale are stressful and sometimes impossible. Headroom is cheap insurance.

How do you verify and change your server settings?

Knowing what you need is half the job. Confirming what you actually have is the other half.

Command-line verification:

1. php -v — PHP version and build
2. php -m — all loaded PHP extensions
3. php -i | grep memory_limit — current memory_limit value
4. php -i | grep max_input_vars — current max_input_vars
5. mysql --version — MySQL or MariaDB version
6. redis-cli info server — Redis version and uptime (if Redis is installed)
7. wp core version — WordPress version
8. wp plugin list — installed plugins and their versions

WordPress-native checks:

Go to Tools > Site Health in your WordPress dashboard. The "Info" tab shows PHP version, database version, active extensions, and memory limits. WooCommerce adds its own WooCommerce > Status page that lists every relevant server setting alongside a pass/fail indicator. This is the fastest way to spot a misconfiguration without touching the command line.

Control panel steps:

Most cPanel and Plesk environments let you switch PHP versions under Software > PHP Selector or PHP Version Manager. php.ini overrides go in a .user.ini file in your document root or through the panel's PHP Settings interface. To enable an extension, look for PHP Extensions in the panel or add extension=intl to your .user.ini.

Sample support ticket text:

Pre-launch verification checklist:

1. SSL certificate valid and no mixed-content warnings
2. PHP 8.1+ confirmed (8.3+ preferred)
3. memory_limit at 256 MB minimum
4. max_input_vars at 3000+
5. OPcache enabled
6. Permalinks set (Settings > Permalinks, click Save)
7. WP-Cron running or replaced with a server cron job
8. Automated daily backups confirmed and tested with a restore

Pro Tip: Run a test restore from your backup before launch, not after a crisis. A backup you have never restored is a backup you cannot trust.

The WooCommerce hosting features checklist for SMB WordPress sites covers additional environment checks worth running before you go live.

Which hosting type is right for your WooCommerce store?

The hosting type you choose determines your resource ceiling, your isolation from other sites, and how much server management falls on you.

Shared hosting puts your site on a server with dozens or hundreds of other accounts. PHP workers, RAM, and CPU are shared. For a brand-new store with under 200 daily visitors and no flash sales, shared hosting can work if the provider runs LiteSpeed, offers NVMe storage, and enforces per-account resource limits. The common failure mode: a neighboring account spikes CPU, your checkout slows, and you have no visibility into why.

Managed WordPress/WooCommerce hosting gives you isolated PHP workers, WooCommerce-aware caching with correct cart/checkout exclusions, and support staff who understand WooCommerce-specific issues. WooCommerce's own hosting guidance recommends choosing a host optimized for stores, citing automated backups, performance tuning, and WooCommerce-aware support as the key differentiators.

VPS hosting gives you dedicated RAM and CPU on a virtual machine. You control the software stack, which means you can install Redis, tune PHP-FPM, and configure Nginx exactly as needed. The tradeoff is that server management is your responsibility unless you choose a managed VPS.

Cloud and dedicated servers make sense when you have consistent high traffic, need load balancing across multiple nodes, or run a multi-store WooCommerce network. The cost is higher, but so is the ceiling.

Decision checklist:

1. Under 1,000 daily visitors and limited technical skill? Start with managed WordPress hosting.
2. 1,000–10,000 daily visitors or complex plugin stack? Managed WordPress or managed VPS.
3. Over 10,000 daily visitors or running promotions that spike traffic? VPS, cloud, or dedicated with load balancing.
4. Need full stack control? Unmanaged VPS or dedicated, with in-house ops or a DevOps contractor.
5. Budget under $30/month? Shared hosting with LiteSpeed and NVMe, with a clear upgrade path.

Pro Tip: Ask any host before buying: "How many PHP workers does my plan include, and can I add more without upgrading the entire plan?" The answer tells you more about WooCommerce readiness than any marketing page.

How does inSave Hosting map to WooCommerce store tiers?

inSave Hosting's plans are built around the technologies WooCommerce actually needs: LiteSpeed with LSCache, MariaDB, modern PHP versions including PHP 8.x, free SSL certificates, daily backups, and staging environments. The inSave Hosting shared and WordPress plans cover the full range from new stores to growth-stage operations.

Store-tier mapping:

inSave Hosting's LiteSpeed integration handles WooCommerce caching exclusions for cart and checkout pages automatically through LSCache. MariaDB 10.6+ is available across plans, meeting WooCommerce's recommended database version. Free SSL is included, satisfying the HTTPS requirement from day one.

Signals that you need to upgrade your plan:

• PHP memory errors appearing in WooCommerce > Status
• Checkout page load times above 3 seconds under normal traffic
• Database connection errors during peak hours
• Site Health showing memory_limit below 256 MB

What to ask inSave support when migrating a WooCommerce store:

Pro Tip: inSave Hosting includes free migration assistance. Use it. A professional migration avoids the database charset mismatches and file permission errors that trip up manual moves.

Why your hosting choice is really a revenue decision

Most store owners treat hosting as a cost to minimize. That framing is backward.

A checkout page that takes 4 seconds to load does not just annoy customers. It loses them. The relationship between page speed and conversion is well-documented across e-commerce, and WooCommerce's dynamic workload makes it more sensitive to hosting quality than a static site by an order of magnitude. A misconfigured PHP worker pool that queues checkout requests during a sale is not a technical inconvenience. It is direct revenue loss, measurable in abandoned carts.

The failure modes I see most often are predictable: a store on shared hosting with no Redis runs fine at 50 daily visitors, then falls over during a product launch because 200 people hit checkout simultaneously and exhaust the PHP worker pool. Or a store with no staging environment applies a plugin update that breaks the checkout flow, and the owner does not notice for six hours because they have no uptime monitoring. Or a store with no off-server backups loses three days of order data after a database corruption event.

None of these are exotic edge cases. They are the standard failure modes of under-provisioned WooCommerce hosting, and they all have the same fix: match your hosting environment to your actual workload, verify the specs before launch, and treat backups and staging as non-negotiable.

inSave Hosting delivers what WooCommerce stores actually need

The gap between a WooCommerce store that converts and one that frustrates customers usually comes down to three things: fast storage, enough PHP workers, and caching that understands WooCommerce's dynamic pages. inSave Hosting's WordPress-optimized plans are built around exactly that stack: LiteSpeed with LSCache for WooCommerce-aware caching, NVMe storage for fast database writes, MariaDB 10.6+, PHP 8.x with OPcache, free SSL on every plan, daily backups, and staging environments for safe updates.

For a new store, the shared WordPress plan covers all minimum requirements and most recommended ones. For a growing store crossing 1,000 daily visitors, the VPS and cloud options add dedicated resources and Redis. Free migration is included, so moving an existing store does not require a technical project.

Check available plans and confirm your specs at inSave Hosting, or contact support directly to ask about PHP worker counts and Redis availability before you commit.

Sources

The specifications in this guide come from official documentation and are worth bookmarking for future updates:

• WooCommerce Server Recommendations Documentation
• WooCommerce Hosting Requirements: 2026 Server Guide | Prestige Technologies
• WooCommerce Hosting Requirements: What Your Store Actually Needs to Run Well | OpsForge Labs
• WordPress requirements
• PCI Security Standards Council

FAQ

What are the server requirements for running WooCommerce?

WooCommerce requires WordPress 6.6+, PHP 8.1+ (8.3+ recommended), MySQL 8.0+ or MariaDB 10.6+, a valid SSL certificate, and a PHP memory limit of at least 256 MB. OPcache, PHP-FPM, and NVMe storage are strongly recommended for production stores.

Does WooCommerce provide its own hosting?

WooCommerce does not sell hosting directly, but its hosting solutions page lists recommended hosts that meet its performance and compatibility standards, including managed WordPress hosts with WooCommerce-aware caching and support.

What is the minimum PHP memory limit for WooCommerce?

The official minimum is 128 MB, but WooCommerce recommends 256 MB and most production stores with active plugins and variable products need 512 MB to avoid memory exhaustion errors during checkout.

What are the main disadvantages of WooCommerce on shared hosting?

Shared hosting limits PHP workers, RAM, and CPU across many accounts. Under concurrent checkout load, WooCommerce stores on shared hosting frequently experience queued requests, slow checkouts, and database connection errors. Moving to managed WordPress hosting or a VPS resolves most of these issues.

What is the minimum requirement to run WordPress locally?

WordPress requires PHP 8.1 or greater, MySQL 5.7 or greater or MariaDB 10.4 or greater, and a web server such as Apache or Nginx. For local WooCommerce development, tools like LocalWP or DevKinsta pre-configure these dependencies automatically.

Recommended

• Best Website Hosting for Ecommerce: 2026 Buying Guide
• Hosting features list for SMB WordPress sites in 2026
• Types of web hosting: choose the best for WordPress in 2026
• Boost website speed and reliability: hosting optimization guide