PrestaShop is open source, which means the software is free and the running costs are not. The single biggest line item for most stores is hosting, and it is also the decision where vendors push hardest, because a managed plan is where the recurring margin lives. This guide strips out the sales angle and looks at what PrestaShop actually needs from a server, what changes as your catalog and traffic grow, and where store owners overspend or underspend.
The goal is practical. By the end you should be able to read a hosting spec sheet, match it to your store, and know which numbers matter and which are filler. We will use US dollars and US retail examples, though the technical requirements are identical wherever you operate.
In short
- PrestaShop is PHP plus MySQL or MariaDB, so any host that runs those well can run PrestaShop. The version of PHP matters more than the brand of host.
- Shared hosting works up to roughly a few hundred orders a month, then a VPS or managed cloud plan becomes the cheaper option once you count lost sales from slow pages.
- Memory and PHP configuration cause more failures than raw CPU. A low
memory_limitor shortmax_execution_timebreaks imports and the back office long before traffic does. - Caching is the multiplier. OPcache, a full-page cache, and a content delivery network turn a modest server into a fast store, often for less money than a bigger box.
- Buy for your real load, not the vendor pitch. Most small and midsize stores are oversold managed plans they do not need, while fast-growing stores cling to shared hosting far too long.
Why this topic matters in 2026
Hosting is no longer a background utility. Page speed is a confirmed ranking and conversion factor, and the gap between a store that loads in under two seconds and one that takes six is measured directly in revenue. For a PrestaShop store, that speed is mostly decided by the server, the PHP version, and the caching layer, not by the theme.
The platform itself keeps moving. PrestaShop 8 raised the minimum PHP version, and the project has signaled a path toward a Symfony-based core that expects modern infrastructure. Hosts that were fine for a PrestaShop 1.6 store in 2018 will quietly hold you back today. If you are weighing whether the platform still fits at all, our companion piece on PrestaShop in 2026: still a real option in Europe covers the broader case, and the wider question of fit sits inside how to choose the right e-commerce platform for your store.
There is also a cost angle. Hosting prices have crept up as data center energy costs rose through 2024 and 2025, and managed PrestaShop plans now span a wide range for what is, underneath, similar hardware. Understanding the requirements lets you tell the difference between a plan that earns its premium and one that simply marks up a basic VPS.
Key terms and definitions
Hosting marketing leans on jargon, so it helps to fix a few terms before comparing plans. None of these are complicated, but vendors often blur them to make a cheap plan sound bigger than it is.
Shared, VPS, dedicated, and cloud
Shared hosting puts many sites on one physical server, splitting its resources. It is cheap and hands-off, but a noisy neighbor can slow your store. A virtual private server (VPS) carves a physical machine into isolated slices with guaranteed CPU and memory. Dedicated hosting gives you the whole machine. Cloud hosting spreads your store across pooled infrastructure and can scale on demand, which is why most managed PrestaShop offers today are cloud underneath.
Managed versus unmanaged
An unmanaged server hands you a bare operating system and the keys. You install the web server, PHP, and the database, and you own every update and security patch. A managed plan does that work for you and usually adds backups, monitoring, and support. The premium pays for time and risk reduction, not for faster hardware.
The LAMP and LEMP stack
PrestaShop runs on a classic web stack. LAMP means Linux, Apache, MySQL, and PHP. LEMP swaps Apache for Nginx (the E is for its pronunciation). Both work well. Nginx tends to handle high concurrency with less memory, while Apache is more forgiving of .htaccess rules that some modules rely on.
The actual PrestaShop hosting requirements
Here is the part vendors rarely lead with, because it is unglamorous and it makes clear how little exotic hardware you need. PrestaShop publishes its system requirements openly, and they are modest. The art is in configuration, not in buying the biggest plan.
For a current PrestaShop 8 store, the baseline looks like this. PHP 8.1 or newer is required, with 8.1 being the practical floor and 8.2 a safer choice for module compatibility. The database should be MySQL 5.6 or later, or MariaDB 10.3 or later, with newer versions preferred for performance. The web server can be Apache 2.4 or Nginx. You also need a handful of PHP extensions enabled, including cURL, GD or Imagick, intl, OpenSSL, DOM, PDO MySQL, and Zip.
Memory is where most trouble starts. PrestaShop technically runs with a 256 MB PHP memory_limit, but real stores with modules should set 512 MB, and large catalogs benefit from more. A short max_execution_time will break long operations like product imports or database upgrades, so 300 seconds is a sensible floor for admin tasks even if front-end requests stay fast.
Storage is the quiet requirement. Product images, generated thumbnails, and cached files grow faster than owners expect, and a catalog with many variants can balloon to tens of gigabytes once every size is rendered. Check whether your plan counts that storage against a hard cap and what an overage costs, because running out of disk mid-day will take a store offline as surely as a traffic spike. The type of storage matters too: NVMe solid state drives cut both page render time and import duration noticeably over older SATA drives.
Minimum versus recommended specifications
The table below separates the bare minimum that will install and run from the configuration a serious store should actually use. The minimum column will technically work. The recommended column is what keeps the back office usable and imports from timing out.
| Setting | Bare minimum (will run) | Recommended for a real store |
|---|---|---|
| PHP version | 8.1 | 8.2 or 8.3 |
| PHP memory_limit | 256 MB | 512 MB or more |
| max_execution_time | 30 seconds | 300 seconds for admin tasks |
| Database | MySQL 5.6 or MariaDB 10.3 | MySQL 8.0 or MariaDB 10.6 and up |
| OPcache | Optional | Enabled, 256 MB |
| Storage type | Standard SSD | NVMe SSD |
| Web server | Apache 2.4 | Nginx or Apache with PHP-FPM |
Notice what is missing from that table: any mention of a specific CPU model or a large number of cores. For most stores, PHP version and memory configuration decide performance long before core count does. A well-configured two-core VPS routinely beats a badly configured eight-core box.
Hosting types compared: what each really costs
The honest way to compare hosting is by the store it suits, not by the headline price. A $4 shared plan and a $40 cloud plan are not competing for the same store, and pretending they are is how owners end up on the wrong tier. The table below maps each type to the store size where it earns its keep.
| Hosting type | Typical monthly cost | Best for | Main risk |
|---|---|---|---|
| Shared hosting | $5 to $25 | New stores, under a few hundred orders a month | Noisy neighbors, capped resources, slow under load |
| Unmanaged VPS | $20 to $80 | Technical owners who want control and value | You own all updates, patches, and downtime |
| Managed VPS or cloud | $50 to $200 | Growing stores without a sysadmin on staff | Premium pricing, occasional vendor lock-in |
| Dedicated server | $120 to $400 and up | High-traffic stores with steady, heavy load | Overkill and wasted spend below real scale |
| Specialist managed PrestaShop | $30 to $250 | Owners who want PrestaShop-tuned support | Paying for branding over genuine tuning |
Two patterns repeat across stores we have seen. First, brand-new stores often buy a managed plan they do not yet need, paying for support tickets they never file. Second, stores that have clearly outgrown shared hosting hang on because migration feels risky, and they pay for it in lost conversions every busy day. Both mistakes come from buying on price or fear rather than on load.
How PrestaShop hosting works in practice
To size a server sensibly, it helps to picture what happens when a shopper hits your store. Every page that is not cached triggers a chain of work, and each link in that chain has a hardware cost. Understanding the chain tells you where to spend.
The request lifecycle
A visitor requests a product page. The web server hands the request to PHP, which boots the PrestaShop framework, queries the database for the product, its stock, prices, and related items, runs through active modules, renders the template, and returns HTML. On an uncached request that can mean dozens of database queries and meaningful PHP work. Multiply that by concurrent visitors and you see why memory and database speed matter more than they first appear.
Where caching changes everything
Caching short-circuits that chain. OPcache stores compiled PHP so the framework does not recompile on every request. A full-page cache serves a saved copy of a page to anonymous visitors, skipping the database entirely. A content delivery network serves images and static files from locations near the shopper. With all three in place, a modest server handles traffic that would otherwise need a far larger box. This is why the cheapest real performance upgrade is usually configuration, not hardware.
Sizing to catalog and traffic
Two numbers drive server sizing: catalog size and concurrent traffic. A catalog of 50,000 products with many combinations puts steady pressure on the database and benefits from more memory and faster storage. Traffic spikes, by contrast, stress CPU and the web server’s ability to handle concurrent connections. A flash sale store and a deep-catalog store can need very different machines at the same revenue.
Common mistakes and how to avoid them
Most PrestaShop hosting pain is self-inflicted and cheap to avoid once you know the failure modes. These are the recurring ones, roughly in order of how often they bite.
Running an outdated PHP version. Stores left on PHP 7.4 lose a large chunk of free performance and drift out of module compatibility. Upgrading PHP is often the single biggest speed win available, and it costs nothing on most hosts. Always test on staging first, because old modules can break on new PHP.
Setting memory_limit too low. A 128 MB or 256 MB limit looks fine until an import, a module install, or a database upgrade hits the ceiling and fails with a white screen. Setting 512 MB removes a whole category of mysterious errors.
Skipping OPcache. Some budget hosts ship with OPcache off or undersized. Turning it on and giving it 256 MB is one line of configuration for a large, free speed gain. It is the first thing to check on any slow PrestaShop store.
Buying CPU to fix a caching problem. When a store is slow, the reflex is to upgrade to a bigger plan. Often the real fix is enabling the full-page cache and a content delivery network, which costs far less than doubling the server. Diagnose before you upgrade.
Ignoring backups until you need one. Open source means you own recovery. A host that does not take automated daily backups, or charges extra to restore one, is a false economy. This is one place where a managed plan genuinely earns its premium.
Security, backups, and uptime: the unglamorous requirements
Performance gets the attention, but the requirements that actually keep a store in business are security, backups, and uptime. These are easy to ignore until the day they decide whether you have a store at all, and they belong in any honest hosting checklist.
Keeping the stack patched
PrestaShop, PHP, the database, and the operating system all ship security updates, and an unpatched stack is the most common way stores get compromised. On a managed plan the host handles operating system and PHP patches, while you stay responsible for PrestaShop core and module updates. On an unmanaged server every layer is yours. Decide which of those jobs you are realistically going to do before you choose a plan, because an unpatched server is a liability no amount of caching fixes.
Backups you have actually tested
A backup you have never restored is a hope, not a plan. Good hosting takes automated daily backups, keeps several days of history off the main server, and lets you restore without a support fee or a long wait. Test a restore to a staging URL at least once so you know the process works and how long it takes. For a store, the recovery time after a failure is a business number, not a technical footnote.
Uptime and the SSL basics
Uptime guarantees in service level agreements sound impressive but matter less than the host’s track record and how fast support responds during an incident. A valid TLS certificate is non-negotiable for a store that takes payments, and HTTPS is effectively required for trust and search visibility. Most quality hosts now include free automated certificates, so treat a host that charges extra for basic SSL as a warning sign. The broader security expectations for handling customer data are summarized well in the public material on the Payment Card Industry Data Security Standard, which most hosted checkouts inherit through their payment provider.
Examples from US retail and e-commerce
Concrete cases make the tradeoffs clearer than spec sheets. The following are composite examples drawn from common store profiles, with the numbers rounded for clarity.
The new boutique. A US apparel startup launches with 200 products and a few dozen orders a month. A quality shared plan at roughly $15 a month, with PHP 8.2 and OPcache enabled, is entirely sufficient. Spending $90 a month on managed cloud here would buy nothing the store can use. The right move is to start small and watch the metrics.
The growing home goods store. A furniture retailer hits 800 orders a month with a 5,000-product catalog and starts seeing slow back office pages during imports. The fix is a managed VPS around $70 a month with 512 MB PHP memory and NVMe storage. The slowness was never the front end; it was admin operations starving on a shared box.
The seasonal spike. An outdoor gear store does steady business but sees traffic multiply during a holiday sale. Rather than pay year-round for peak capacity, it uses a cloud plan that can scale up for the event and back down afterward. Pairing that with an aggressive full-page cache means the database barely notices the surge.
The high-traffic flash retailer. A footwear brand built around limited drops sees normal traffic explode for ten minutes when a release goes live. Here the bottleneck is concurrency, not catalog depth, so the answer is a load-balanced cloud setup with the checkout path carefully exempted from the full-page cache. Throwing a single bigger server at a concurrency problem rarely helps; the work has to spread across more workers and a fast queue.
The thread across all three is matching the plan to real load. For stores comparing PrestaShop against other systems before committing, the tradeoffs in PrestaShop versus WooCommerce for European SMB stores are worth reading alongside this, and the broader fit question still returns to choosing the right e-commerce platform for where you are headed.
Tools, partners, and vendors worth knowing
You do not need a named PrestaShop host to run PrestaShop well, but some categories of provider and tooling save real time. The point is to recognize what each one actually does, so you are not paying for a label.
General hosts versus PrestaShop specialists
Large general hosts and cloud providers run PrestaShop fine, and they often cost less than specialists. PrestaShop-specific managed hosts justify their price when they pre-tune PHP and caching for the platform, offer one-click staging, and support staff who know the back office. The premium is worth it only if you would otherwise pay someone to do that tuning.
Performance tooling
Whatever host you pick, a few tools repay their cost quickly. A content delivery network offloads images and static files. A server-level cache like Varnish or a PrestaShop full-page cache module cuts database load. Object caching with Redis or Memcached speeds repeated queries on larger stores. For choosing the modules that touch performance, our roundup of the best PrestaShop modules for a serious store is a useful companion.
When to bring in help
If your store crosses into six figures of annual revenue, the cost of a slow or fragile server starts to dwarf the cost of expert setup. A one-time engagement with a PrestaShop agency or freelance sysadmin to configure caching, tune the database, and set up monitoring often pays for itself in a single avoided outage. Hosting is one of the few areas where buying expertise once beats buying bigger hardware forever.
Frequently asked questions
What are the minimum PrestaShop hosting requirements?
For PrestaShop 8 you need PHP 8.1 or newer, MySQL 5.6 and up or MariaDB 10.3 and up, and Apache 2.4 or Nginx, plus standard PHP extensions like cURL, GD, intl, and Zip. A PHP memory_limit of at least 256 MB is required, though 512 MB is the practical recommendation for any store with modules.
Can I run PrestaShop on cheap shared hosting?
Yes, for a new or small store. Shared hosting works well up to roughly a few hundred orders a month, provided the host offers a current PHP version and lets you enable OPcache. Beyond that point, resource caps and noisy neighbors start to cost you sales, and a VPS or managed cloud plan becomes the cheaper choice overall.
How much memory does PrestaShop need?
Set the PHP memory_limit to 512 MB for a typical store with modules, even though 256 MB will technically run. Low memory limits are the most common cause of failed imports, module installs, and white screens, so the extra headroom removes a whole class of errors for no real cost.
Which PHP version is best for PrestaShop in 2026?
PHP 8.2 or 8.3 is the sweet spot. PHP 8.1 is the minimum for PrestaShop 8, but newer releases bring meaningful speed gains and longer security support. Always test a PHP upgrade on a staging copy first, since older modules occasionally break on newer versions.
Is managed PrestaShop hosting worth the extra cost?
It depends on your skills and time. Managed plans handle updates, security patches, backups, and monitoring, which is genuinely valuable if you have no sysadmin and your store is mission critical. If you are comfortable on the command line, an unmanaged VPS gives the same performance for less, with you carrying the maintenance load.
Does hosting affect my store’s SEO?
Yes, mainly through page speed and uptime. Faster servers and good caching improve the speed signals that influence rankings and conversion, and frequent downtime damages both crawling and trust. Hosting will not rank a store on its own, but a slow or unreliable host can quietly cap how well everything else performs.
What causes PrestaShop to run slowly?
The usual culprits are an outdated PHP version, OPcache turned off, no full-page cache, and an unindexed or overloaded database. Hardware is rarely the first problem. Before upgrading your plan, check the PHP version, enable caching, and review heavy modules, since those fixes are free and often solve the issue.
How do I move my PrestaShop store to a new host?
Copy the full file tree and export the database, import both on the new server, update the database credentials in the configuration, and point your domain once everything is verified on a temporary URL. Test checkout, payments, and the back office before switching DNS, and keep the old host live until the new one is confirmed working.
Do I need a content delivery network for PrestaShop?
For most growing stores, yes. A content delivery network serves images and static files from locations near the shopper, which cuts load time and offloads work from your origin server. It is often a cheaper and more effective speed upgrade than moving to a larger hosting plan.
The takeaway
PrestaShop hosting is simpler than the marketing suggests. The platform needs a current PHP version, a healthy memory limit, a modern database, and good caching. Almost everything else is a question of matching the plan to your real catalog and traffic, then upgrading on evidence rather than on a vendor’s recommendation.
Start smaller than the upsell suggests, watch your speed and error metrics, and spend on configuration before hardware. Do that and you will run a fast PrestaShop store for a fraction of what most owners pay, with the budget you save going toward the parts of the business that actually grow it.