For most small and growing WooCommerce stores, the practical starting point is Hetzner's managed web hosting, specifically Webhosting L or XL. Hetzner's own setup tutorial states that installing WooCommerce requires a web hosting plan L or higher, with plan XL recommended, alongside an active WordPress installation and a database. Those plans give you a supported PHP and database environment, Varnish and Redis caching, daily backups and SSL without you managing the underlying server.
A Cloud or dedicated server is the better fit only if you need root access and are prepared to handle updates, security patching and backups yourself. The sections below explain the requirements, compare the plans, and give you a sizing route through each option.
What Your WooCommerce Store Actually Requires
Start with the software floor, because a plan that misses it will cause problems regardless of how much traffic you expect.
WooCommerce 10.8 and later requires WordPress 6.9 or greater, PHP 8.3 or greater (tested up to PHP 8.4), MySQL 8.0 or greater or MariaDB 10.6 or greater, HTTPS support, and a WordPress memory limit of 256 MB or greater. WooCommerce still works on older stacks such as PHP 7.4 with MySQL 5.6 or MariaDB 10.4, but those versions have reached end of life and may expose your site to security vulnerabilities.
Beyond the core versions, WooCommerce recommends Apache or Nginx, though any server supporting PHP and MySQL will run it. Some setups also need cURL or fsockopen support for integrations, SOAP support for certain extensions, and Multibyte String support if you run a non-English store.
The Catch with Shared Hosting Memory Limits
Hetzner's web hosting plans publish PHP memory limits of 192 MB on Webhosting S, 256 MB on M, 384 MB on L and 512 MB on XL. Those are plan-level PHP limits, and they should not be read as a direct match for the 256 MB WordPress memory recommendation. The two limits are measured differently, so treat the plan figure as a ceiling on the whole PHP environment rather than a guarantee that WordPress gets 256 MB on its own.
This is the main reason not to pick the cheapest tier for a shop. Webhosting S and M sit at or below the WordPress recommendation and offer only 1 and 5 databases respectively, which leaves little room for a staging copy or additional applications.
What Hetzner Offers WooCommerce Stores
Hetzner's web hosting packages support shop systems such as Shopware and WooCommerce. The company markets Webhosting XL specifically as suitable for e-commerce webshops, for example with Shopware or WooCommerce. Independent reviews also list Hetzner among WooCommerce-capable hosts because of its WordPress installation option.
The decision is less about whether Hetzner can run WooCommerce and more about how much of the stack you want to operate. Hetzner's web hosting sits in a middle ground: it offers a one-click WordPress installer and automatic DNS entries, but it is still a shared hosting product rather than a fully managed WooCommerce service.
Managed Web Hosting vs. Self-Managed Cloud or Dedicated
| Aspect | Managed web hosting | Cloud or dedicated server |
|---|---|---|
| Who manages the operating system | Hetzner | You |
| Core updates and security patching | Hetzner handles the platform layer | You handle everything |
| Backups | Daily backups included | Your responsibility |
| Antivirus and malware scanning | Virus scans included | Your responsibility |
| SSL | SSL encryption included | You configure certificates |
| Root access | Not available | Full root access |
| Caching | Varnish and Redis on L and XL | You install and tune your own stack |
| Starting price | From €1.60/month excluding VAT on S | Not covered by supplied specifications |
The table shows the trade-off clearly. Web hosting takes routine maintenance off your plate and includes the operational basics that a shop needs to stay online and secure. A Cloud or dedicated server gives you control over the full environment, but every item in the right-hand column becomes your job.
Hetzner's supplied sources do not include Cloud or dedicated server specifications, pricing or management documentation, so those options can only be described in general terms here. If you are leaning toward a self-managed server, confirm the current vCPU, RAM, storage and price directly on Hetzner's product pages before committing.
Hetzner Web Hosting Plans Compared
The four plans differ mainly on storage, databases, PHP processes and memory. PHP processes matter for WooCommerce because they cap how many requests can be handled in parallel.
| Plan | Storage | Databases | PHP processes | PHP memory limit | Notable extras |
|---|---|---|---|---|---|
| S | 10 GB | 1 | 2 | 192 MB | Varnish |
| M | 50 GB | 5 | 5 | 256 MB | Varnish |
| L | 100 GB | 20 | 10 | 384 MB | Varnish, Redis, SSH, Node.js |
| XL | 300 GB | 50 | 20 | 512 MB | Varnish, Redis, SSH, Node.js |
Two patterns stand out. First, L and XL add Redis and SSH on top of Varnish, which matters for WooCommerce performance tuning. Second, the jump from 10 to 20 PHP processes between L and XL is the difference between a store that handles modest concurrent checkout traffic and one that can absorb a promotion spike.
On price, Webhosting S starts at €1.60 per month excluding VAT with a one-time setup fee of €8.32 excluding VAT. Webhosting XL starts at €16.72 per month excluding VAT with a one-time setup fee of €4.12 excluding VAT. Prices exclude VAT and domain registration, and Hetzner web hosting packages do not include a domain; you must order one separately.
Database and PHP Support
Hetzner web hosting databases include MariaDB, which is MySQL-compatible, plus Postgres, Redis and phpMyAdmin. The platform offers PHP 5, 7 and 8 with many extensions, including OPcache and APCu. The extension list also covers ImageMagick, XDebug and others that WooCommerce and its plugins may use.
Hetzner's product page lists PHP versions generally rather than confirming PHP 8.3 availability on each individual plan. If your store's plugin stack depends on PHP 8.3 specifically, confirm the available version in your hosting control panel after signup, or ask Hetzner support before ordering.
Sizing Your Store: A Practical Route
There is no single correct plan size because WooCommerce load depends on catalogue size, plugin count, traffic pattern and how much of that traffic is logged in. The figures below are rough starting points from third-party hosting guidance, not measured benchmarks for Hetzner.
Rough Heuristics for Self-Managed Servers
A third-party guide suggests small stores with roughly 5 to 15 concurrent users run well on 2 to 4 vCPU and 4 to 8 GB RAM, growing stores on 4 to 8 vCPU and 8 to 16 GB, and high-concurrency brands on 8 to 16 vCPU and 16 to 32 GB. The same guide recommends starting with 4 to 8 PHP workers and moving to 12 to 24 or more for busy campaigns.
Treat these as a conversation starter for sizing a Cloud server, not a promise. They assume a reasonably optimized stack, and results will vary with your theme, extensions and caching setup.
Mapping Those Heuristics Onto Web Hosting
For managed web hosting, the equivalent signals are simpler. If you are launching a small catalogue with light traffic, Webhosting L gives you 10 PHP processes and 384 MB. If you expect promotions, seasonal spikes or a larger plugin footprint, Webhosting XL doubles the PHP processes to 20 and raises memory to 512 MB.
The step down to M is worth considering only for a very small shop, and even then the 5 PHP processes and 256 MB limit leave little headroom. If you need a staging copy of the store, remember that each copy consumes a database, so S's single database is effectively full once the live site exists.
Caching Matters More Than Raw Specs
For WooCommerce, caching configuration does more for perceived speed than a modest bump in server resources. Hetzner's hosting supports Varnish for CMS caching and Redis object caching, both aimed at reducing page load times. L and XL include both; S and M list Varnish only.
The critical rule is that cart, checkout and account pages should not be full-page cached, because excluding them keeps carts accurate and avoids stale pricing. Misconfigured page caching on a shop can show a customer another shopper's cart contents or an outdated price at checkout, which is far worse than a slightly slower page.
For self-managed servers, you take on this configuration yourself. That means setting up a page cache, an object cache such as Redis, and explicit exclusions for WooCommerce's sensitive routes. It is achievable, but it is real work and a common source of launch-day problems.
Scaling as the Store Grows
Hetzner web hosting plans are described as easily scalable with no minimum contract period. In practice this means you can move from L to XL without a long commitment, which suits stores whose traffic is still taking shape.
For Cloud servers, scaling means resizing the instance or adding capacity, and that is a separate operational task you manage. The supplied sources do not cover migration procedures, expected downtime during upgrades, or load balancing on Hetzner Cloud. If you plan to run a high-traffic sale, test the resize path and the caching configuration on a copy of the store before the event, and confirm current procedures with Hetzner documentation.
Limitations to Weigh Before You Choose
Managed web hosting is simple to run but constrained. It does not give you root access, so any requirement for custom server software, unusual PHP extensions or a specific web server configuration pushes you toward Cloud or dedicated. The supplied sources also do not confirm whether Hetzner web hosting offers staging environments, WooCommerce-specific support, or managed WooCommerce updates, so treat those as questions to confirm rather than assumed features.
Self-managed servers invert the trade-off. You gain control and lose the safety net. Backups, patching, TLS certificate renewal and caching configuration all become your responsibility, and a missed security update on a store handling customer payment details is a serious risk.
A domain is a separate purchase either way, and Hetzner web hosting packages do not include one. Budget for domain registration and any paid plugins alongside the hosting cost.
Decision Checklist
Answer these questions before you order.
- How many people will work on the server itself? If the answer is nobody, choose managed web hosting.
- Does your plugin stack need root access or custom software? If yes, plan for a Cloud or dedicated server and the administration that comes with it.
- What are your peak concurrent shoppers? Use the heuristics above to estimate a Cloud server size, or step up to XL if you are staying on managed hosting.
- Do you need a staging site? Confirm whether the plan supports it, and count the extra database against the plan limit.
- Who handles backups and updates? On managed hosting, Hetzner includes daily backups and virus scans. On a self-managed server, this is your job.
- Is PHP 8.3 available on your chosen plan? Confirm before you migrate a live store.
For most stores getting started, Webhosting L is the minimum sensible choice and XL is the safer pick if you expect growth. Move to a self-managed server only when a specific technical requirement or a demonstrated traffic ceiling makes the extra control worth the extra work.


