Check your Domain Availability...
Free Domain Manager
Live Demo - lock option, edit Whois, edit name servers, custom DNS records, URL redirection, etc.
PrestaShop Hosting
PrestaShop™ is a trademark of PrestaShop SA and shares no affiliation with HostiFul.
A Smooth PrestaShop Web Hosting Experience
- A single-click PrestaShop script installation
- A PrestaShop installation at signup
- HostiFul satisfies and exceeds all prerequisites for hosting PrestaShop-driven Internet shops.
- The most current stable releases of Apache, MySQL and PHP
- 24/7 technical support
- A twenty-minute average support ticket response time
PrestaShop Hosting Solutions
| Economy | Regular | Deluxe | Ultimate |
|
Perfect for customers who only want a simple personal website or a blog.
|
A good choice for any online store or a fairly complex website.
|
A reasonably priced shared web hosting package, good for resource-heavy personal websites.
|
The right solution for high-profile websites with lots of visitors.
|
| Unlimited storage | Unlimited storage | Unlimited storage | Unlimited storage |
| Unlimited bandwidth | Unlimited bandwidth | Unlimited bandwidth | Unlimited bandwidth |
| 1 website hosted | 5 websites hosted | Unlimited websites hosted | Unlimited websites hosted |
| 24/7/365 support | 24/7/365 support | 24/7/365 support | 24/7/365 support |
|
30 Days Money Back Guarantee |
30 Days Money Back Guarantee |
30 Days Money Back Guarantee |
30 Days Money Back Guarantee |
|
30-Day Free Trial |
30-Day Free Trial |
30-Day Free Trial |
30-Day Free Trial |
| $4.95 / month | $8.75 / month | $17.50 / month | $25.00 / month |
| Compare All Hosting Plans | Compare All Hosting Plans | Compare All Hosting Plans | Compare All Hosting Plans |
Questions about PrestaShop hosting? See our FAQ.
A narrative guide to PrestaShop hosting.
There is a moment in the life of an online store when the owner stops thinking about the website as a website.
At first, it feels like a website.
There is a home page, a logo, some products, a shopping cart, a few pictures, and a payment page. The owner checks orders in the morning and perhaps adds a new product in the afternoon.
Everything seems manageable.
Then sales begin to arrive.
Products need stock quantities. Customers create accounts. Orders have to be recorded. Payments need to be processed. Shipping information has to be stored. Product images multiply. Prices change. Promotions appear. Tax rules become relevant. Modules are installed. The catalog grows.
And eventually someone says the sentence every store owner would rather not hear:
“The site is slow.”
That is usually when hosting enters the conversation.
PrestaShop is built specifically for online commerce. It is not merely a publishing system with a shopping cart attached. The platform provides a catalog, customer accounts, orders, checkout, product management, back-office administration, modules, themes, payment integrations, and a database-driven storefront. The current PrestaShop documentation identifies version 9 as the current major branch and provides specific server requirements for it. ([devdocs.prestashop-project.org](https://devdocs.prestashop-project.org/9/))
That makes the choice of hosting rather more important than it may appear when a store is small.
An online shop has to do something a brochure website never has to do.
It has to conduct business.
The Beginning
Imagine a small company called Harbor Home Goods.
The owner has been selling kitchen equipment locally for years. Eventually, customers begin asking the same question:
“Can I order this online?”
So she builds an online store.
There are 80 products.
Most of them have three or four photographs. Customers can create accounts, add items to a cart, check out, and receive an order confirmation.
The store is powered by PrestaShop.
At this stage, the hosting decision seems almost embarrassingly easy.
The cheapest plan appears to have more than enough storage. It supports PHP. It includes a database. It has a control panel and email accounts.
The store goes live.
Nothing happens.
Then sales happen.
More products are added. More photographs appear. A few modules are installed. Customers begin returning regularly. Search traffic increases. The owner starts running promotions.
One month, the store has its best sales day ever.
It is also the first time anyone notices the checkout slowing down.
That is the beginning of the real hosting story.
What PrestaShop Actually Is
It is tempting to describe PrestaShop simply as ecommerce software.
That is true, but it does not really explain what the hosting environment has to support.
An online store is a collection of connected systems.
Products are stored in a database. Customers are stored there too. Orders are recorded. Prices and stock levels change. Categories are organized. Product combinations may have different prices or inventories. Images are associated with products. Modules extend the platform. Themes control the storefront. Payment services and shipping systems may communicate with the store from outside.
Every time a shopper opens a product page, adds something to the cart, logs in, changes an address, or places an order, the application is doing work.
It is not simply displaying a document.
The current PrestaShop 9 documentation reflects this more demanding environment. It specifies the web server, PHP version compatibility, SQL database requirements, memory allocation, PHP extensions, and certain PHP settings that the application needs. ([devdocs.prestashop-project.org](https://devdocs.prestashop-project.org/9/basics/installation/system-requirements/))
That distinction becomes important when a store owner starts comparing hosting packages.
A hosting plan is not being purchased for a pile of files.
It is being purchased for an application that has to conduct transactions.
When Hosting Becomes Part of the Store
Harbor Home Goods begins with a perfectly ordinary shared hosting account.
There is nothing inherently wrong with that.
A small store can often operate quite comfortably on good shared infrastructure. The problem comes when “shared hosting” is treated as a specification rather than as a particular environment.
Two providers may both sell shared hosting while giving customers very different amounts of CPU, memory, database capacity, PHP workers, storage performance, and process limits.
The store owner initially looks at storage.
“We get 100 GB. We only use 4 GB.”
That sounds reassuring.
But the missing 96 GB tells her almost nothing about whether the checkout will remain responsive during a busy afternoon.
PrestaShop's official requirements are a much better starting point. For PrestaShop 9, the documentation lists Apache 2.4 or later, MySQL 5.7 minimum or MariaDB 10.2 minimum, and recommends a PHP memory limit of at least 512M. It also states that Nginx can be used and that Unix-based environments are preferred. ([devdocs.prestashop-project.org](https://devdocs.prestashop-project.org/9/basics/installation/system-requirements/))
Those requirements do not tell the whole story, but they tell the store owner where to begin.
Compatibility comes first.
Capacity comes next.
Then reliability, security, backups, support, and the ability to grow.
The Server Beneath the Shop
There is something reassuring about a hosting control panel.
Everything looks tidy.
Domains are listed on one side. Databases on another. PHP settings are available from a menu. File management is a few clicks away.
It creates the impression that server administration has become simple.
For many routine tasks, it has.
But PrestaShop still depends on the environment underneath those controls.
For the current 9.x branch, the official documentation lists Apache 2.4 or later as the recommended web server environment, while noting that Nginx is supported. It recommends a current PHP version within the compatibility chart, with PHP 8.4 identified as the recommended version for PrestaShop 9.0 and PHP 8.5 recommended for 9.1. MySQL 5.7 or MariaDB 10.2 are listed as minimum database versions, with recent versions recommended. ([devdocs.prestashop-project.org](https://devdocs.prestashop-project.org/9/basics/installation/system-requirements/))
The documentation also lists a series of PHP extensions, including cURL, DOM, Fileinfo, GD, Iconv, Intl, JSON, Mbstring, OpenSSL, PDO, PDO MySQL, SimpleXML, and Zip. It specifically requires allow_url_fopen to be enabled. ([devdocs.prestashop-project.org](https://devdocs.prestashop-project.org/9/basics/installation/system-requirements/))
That last detail is particularly useful because it shows why “PHP is installed” is not a sufficient compatibility test.
An application needs a functioning environment around PHP.
Harbor Home Goods discovers this when a module refuses to operate correctly on one hosting account.
The provider had PHP.
What it did not have was every part of the environment the store expected.
That distinction can save a great deal of frustration when checked before purchasing hosting rather than after the store is already live.
The PHP Question
PHP versions create a peculiar problem for ecommerce stores.
Too old can be dangerous or incompatible.
Too new can also create trouble when older modules, themes, or custom code have not caught up.
That means a store owner should not simply choose the largest version number available in the control panel.
PrestaShop's official documentation provides a compatibility chart for each supported major release. For PrestaShop 9.0, PHP 8.1, 8.2, and 8.3 are supported, with 8.4 recommended; PHP 8.5 is not listed as supported for 9.0. For PrestaShop 9.1, PHP 8.1 through 8.5 are supported, with 8.5 recommended. ([devdocs.prestashop-project.org](https://devdocs.prestashop-project.org/9/basics/installation/system-requirements/))
That is the kind of detail that matters when choosing a host with automatic PHP upgrades.
An automatic upgrade sounds helpful until it changes the runtime to a version that a critical module has not been tested against.
Harbor Home Goods eventually learns to treat PHP as part of the shop's application stack rather than as a simple server switch.
Before an upgrade, the administrator checks the PrestaShop version, the modules, the theme, and the server environment.
The question changes from “What is the newest PHP version?” to “Which PHP version is appropriate for this store?”
That is a much safer question.
The Database Behind the Orders
Most shoppers never think about the database.
They should not have to.
They add a coffee machine to the cart and move on.
But somewhere underneath the page, the store knows which coffee machine they selected.
It knows the product identifier.
It knows the price.
It knows whether the item is available.
It knows the customer's cart.
And when the order is placed, it has to store the transaction information correctly.
That is why database reliability is fundamentally different for an online store than it is for a simple brochure website.
The PrestaShop installation process requires a database and corresponding access credentials. The current documentation specifically describes creating the database and ensuring that the necessary database access is available before installation. ([devdocs.prestashop-project.org](https://devdocs.prestashop-project.org/9/basics/installation/))
As the store grows, database activity grows with it.
There are more products.
More customers.
More orders.
More combinations.
More administrative activity.
More searches and filters.
A store can therefore have modest disk usage and still generate substantial database activity.
That is why a hosting company advertising huge disk space does not necessarily tell you much about how well the store will perform.
Harbor Home Goods eventually learns to ask a different question:
“How well does the hosting environment handle database-driven applications?”
That question gets much closer to the real issue.
A Growing Catalog Changes Things
At launch, Harbor Home Goods has 80 products.
Six months later, there are 700.
A year after that, there are several thousand.
Growth has arrived one product at a time, so nobody notices it happening.
The database becomes larger.
Search and category navigation become more important.
The administration area handles more information.
Product combinations multiply.
More images are stored.
The storefront has more pages to serve.
Nothing about any single product seems particularly demanding.
The workload comes from all of them together.
This is a common pattern with ecommerce.
A small store often feels fast because its workload is small. A large catalog can reveal weaknesses that were invisible when the store was new.
That does not necessarily mean the application is poorly designed.
It simply means the environment is now being asked to do more work.
Searches, filters, product pages, category pages, customer accounts, carts, orders, and back-office activity all compete for resources.
The hosting plan that was perfectly sensible at launch may no longer be sensible later.
That is normal.
The store has changed.
The Product Images Keep Coming
There is another form of growth that becomes obvious much faster.
Pictures.
Online stores need them.
Customers want to see the product before buying it. Many products require several views. Clothing may need front and back images. Furniture benefits from room photographs. Electronics need detail shots. Jewelry may require close-ups.
Before long, the store has thousands of image files.
Storage is relevant, but image delivery is just as important.
A product page with ten large photographs can require considerably more network transfer than a simple text page.
Large original images also consume browser bandwidth and can make pages feel slower for customers on mobile connections.
PrestaShop's server requirements include the GD extension, which the documentation notes is used to create thumbnails for uploaded images. ([devdocs.prestashop-project.org](https://devdocs.prestashop-project.org/9/basics/installation/system-requirements/))
That small technical requirement points to a larger truth.
Image handling is part of the storefront's infrastructure.
Good image compression, sensible dimensions, efficient formats, and appropriate thumbnail generation can make a meaningful difference.
Buying more server power cannot compensate for every oversized image uploaded by a product manager.
Harbor Home Goods eventually creates a simple rule:
Never upload a massive original photograph when the customer only needs a properly sized product image.
The hosting gets some of the credit for performance.
The content team gets some too.
When Customers Arrive All at Once
Saturday afternoon is normally quiet.
Then the store launches a major promotion.
The marketing email goes out.
People click.
Hundreds of shoppers arrive.
Some are browsing products.
Others are searching.
Some are adding items to their carts.
A percentage reach checkout.
At the same time, search engines and automated visitors continue accessing the site.
The number of registered customers has not changed.
The workload has.
This is why traffic is better understood as a pattern than as one monthly visitor figure.
A store serving 100,000 visitors evenly across a month may behave very differently from one receiving a large share of those visitors during a few promotional hours.
Hosting needs to cope with the busy periods, not just the monthly average.
CPU usage rises.
PHP workers become busy.
Database requests increase.
Memory usage changes.
More images are delivered.
More carts are active.
More checkout activity occurs.
If the environment is tightly constrained, the store can become slow precisely when customers are most ready to buy.
That is a particularly expensive kind of slowdown.
When a VPS Starts Looking Sensible
Eventually, Harbor Home Goods moves to a VPS.
The reason is not prestige.
The store does not need a server that sounds impressive in a sales brochure.
It needs an environment where resource allocation is more predictable and where the administrator has more control.
A VPS can provide that.
It can also introduce a new problem:
Someone has to manage it.
With more control come more responsibilities. Operating-system updates, server configuration, security hardening, monitoring, backups, PHP configuration, web-server configuration, and troubleshooting do not magically disappear because the server is virtual.
That creates an important choice.
Does the business want to administer the server?
Or does it want a provider to handle more of that work?
For a technical ecommerce team, an unmanaged VPS can be attractive.
For a business whose employees are primarily concerned with products and customers, managed hosting may be worth the additional cost.
Neither is universally better.
The right answer depends on who will be responsible when something goes wrong.
Modules and Themes Add Another Layer
PrestaShop stores rarely stay stock for long.
The owner wants a different layout.
A payment provider requires a module.
A shipping company supplies another.
Someone installs a product feed integration.
Then a marketing tool.
Then a search enhancement.
Then an analytics module.
Eventually the store looks nothing like the original installation.
That flexibility is one of the reasons platforms such as PrestaShop are attractive to businesses. The downside is that every additional component becomes another piece of software that has to remain compatible.
The PrestaShop 9 documentation separates the current platform from its older major branches and notes that version 9 introduces significant technical changes, including Symfony 6.4. That kind of platform evolution can affect modules and customizations built around earlier versions. ([devdocs.prestashop-project.org](https://devdocs.prestashop-project.org/9/core-reference/))
The lesson is not to avoid modules.
It is to know what is installed.
Harbor Home Goods begins maintaining a simple record of its critical modules, their versions, what they do, and whether they are essential to checkout, payment, shipping, product management, or administration.
That turns a mysterious upgrade into a manageable project.
Without such a record, one broken module can send the administrator hunting through the entire store trying to discover what changed.
The Store Has to Talk to Other Systems
An online store almost never operates by itself.
The payment gateway sits somewhere else.
The shipping carrier has its own system.
Tax or accounting tools may be external.
Marketing platforms may receive order information.
Product feeds may be sent to marketplaces.
The store has to communicate with these services.
This makes outbound connections important.
PrestaShop's current system requirements specifically describe cURL as being used to download remote resources such as modules and localization packages. The documentation also states that allow_url_fopen must be enabled because PrestaShop uses it to access remote files and because it is important to functions including payment processing. ([devdocs.prestashop-project.org](https://devdocs.prestashop-project.org/9/basics/installation/system-requirements/))
That is an excellent example of something a store owner can overlook.
The website may be perfectly capable of serving pages.
But ecommerce depends on communication beyond the server itself.
If outbound connections are restricted, blocked, unreliable, or improperly configured, the problem may show up somewhere completely different from the actual cause.
Harbor Home Goods eventually learns to include external integrations in its hosting checklist.
Not because every provider will cause a problem.
Because the store cannot afford to discover a restriction after the checkout system has stopped communicating.
A Store Needs Reliable Email
A store can survive a missing newsletter.
It cannot easily survive broken order communication.
Customers expect order confirmations.
They expect shipping notifications.
They may need password-reset messages.
They may receive payment-related information by email.
The store may also need to communicate with administrators.
When those messages stop arriving, customers tend to blame the store.
Sometimes the problem is the store.
Sometimes it is the mail configuration.
Sometimes it is DNS.
Sometimes the message is being rejected or filtered.
Sometimes the hosting environment has restrictions on outbound email.
The important point is that reliable ecommerce hosting needs reliable transactional communication.
Harbor Home Goods eventually tests its order messages deliberately.
New order.
Password reset.
Customer account.
Shipping update.
Administrator notification.
It is much easier to discover an email problem while testing than when an actual customer asks why an order confirmation never arrived.
Security Is Not a Decorative Feature
An online store holds information that people care about.
Customer accounts.
Addresses.
Order histories.
Administrative accounts.
Product information.
Configuration settings.
And, depending on how payments are integrated, connections to payment services.
Security therefore has to exist at several levels.
The hosting provider is responsible for important aspects of the server environment.
The store operator remains responsible for keeping PrestaShop, modules, themes, credentials, and custom code under control.
One cannot replace the other.
A fully patched server does not protect an outdated module.
A carefully updated application does not compensate for a poorly secured server.
Harbor Home Goods eventually adopts a simple habit: every change to the store starts with the question, “What happens if this goes wrong?”
That question leads naturally to backups, staging, access control, updates, monitoring, and recovery planning.
PrestaShop's own documentation includes guidance for staying up to date, migration, backups, updates, and post-update checks, showing that maintenance is treated as an ongoing part of operating the platform rather than a one-time installation task. ([devdocs.prestashop-project.org](https://devdocs.prestashop-project.org/9/))
A secure store is not a store where nothing ever changes.
It is a store where changes are made deliberately.
The Day the Backup Becomes Important
There is an old rule among website administrators:
You do not really believe in backups until you have needed one.
Harbor Home Goods eventually gets its test.
An administrator changes something in the store configuration.
It seemed harmless.
It was not.
A module begins behaving badly, and a series of changes follows.
Eventually the storefront is in a state nobody recognizes.
The good news is that the store had a recent backup.
The better news is that the backup can actually be restored.
That second part deserves emphasis.
A backup file sitting somewhere is not the same thing as a functioning recovery process.
For an ecommerce platform, the relevant data is spread across both application files and the database.
Product information, customer information, orders, configuration, and other structured data reside in the database. Files contain the application itself, themes, modules, images, and other resources.
A complete recovery therefore has to account for the whole installation.
PrestaShop's current documentation includes dedicated guidance for store backups and restoration as part of its operational documentation. ([devdocs.prestashop-project.org](https://devdocs.prestashop-project.org/9/basics/))
Harbor Home Goods eventually keeps multiple backup generations and tests restoration.
The store owner sleeps better after that.
Updates and Compatibility
Updating an ecommerce store is different from updating a phone.
When the phone installs an update, the manufacturer controls much of the environment.
With PrestaShop, the store owner may have a custom theme, a collection of modules, payment integrations, shipping integrations, and custom code that all interact with the platform.
That makes compatibility part of the upgrade process.
PrestaShop 9 introduced major technical changes compared with version 8, including its move to Symfony 6.4. The project also provides specific documentation for updating the platform and checking the environment afterward. ([devdocs.prestashop-project.org](https://devdocs.prestashop-project.org/9/core-reference/))
A store administrator therefore needs to distinguish between three things.
The application may be supported.
The server may be supported.
A particular module may still be incompatible.
Those are not the same question.
Harbor Home Goods begins testing significant updates on a staging copy before touching the live store.
The payment module gets tested.
The cart gets tested.
Checkout gets tested.
Product pages get tested.
Customer registration gets tested.
Administrative functions get tested.
Only after the important pieces work does the update move to production.
It adds another step to the process.
It can also prevent a far more expensive problem.
Moving an Established Store
Eventually Harbor Home Goods decides to move to another provider.
The old host has become too restrictive.
The store needs more resources.
The new provider offers a better environment.
On paper, migration looks simple.
Copy the files.
Copy the database.
Change DNS.
Done.
Real ecommerce is rarely so cooperative.
The store may have orders arriving while the migration is being prepared.
Customers may have active carts.
Product information may change.
Inventory may be updated.
Modules need to behave exactly as expected.
Images must be present.
Database credentials have to be correct.
The domain must resolve to the new server.
SSL must work.
Email needs to continue functioning.
The back office has to remain accessible.
Payments must still work.
Shipping integrations need to be checked.
PrestaShop maintains dedicated documentation for migration as part of its current documentation set. ([devdocs.prestashop-project.org](https://devdocs.prestashop-project.org/9/))
Harbor Home Goods finally schedules its migration during a quieter business period.
The database is copied.
The files are transferred.
The new environment is tested.
DNS is switched.
Orders are monitored carefully.
The old host remains available until the new environment has been confirmed.
The customers never know anything happened.
That is the ideal outcome.
What Actually Makes an Online Store Fast
There is a temptation to believe that faster hardware automatically means a faster store.
Hardware matters.
It just does not work in isolation.
A store's performance can be affected by CPU capacity, memory, storage speed, PHP workers, database performance, network latency, caching, images, modules, theme code, external services, and the number of simultaneous requests.
One inefficient module can create a bottleneck that extra storage will never solve.
An enormous product image can delay a page even when the server itself responds quickly.
A poorly performing external payment or inventory service can introduce a delay outside the web server altogether.
That is why “fast hosting” is a weak description without context.
The better question is:
“Fast under what workload?”
A store receiving a handful of shoppers per hour does not place the same demands on the server as a catalog receiving hundreds of simultaneous visitors during a promotion.
PrestaShop's current system requirements recommend at least 512M of PHP memory per script for version 9. That recommendation alone illustrates why memory allocation can matter in addition to CPU speed. ([devdocs.prestashop-project.org](https://devdocs.prestashop-project.org/9/basics/installation/system-requirements/))
Harbor Home Goods eventually starts looking at performance as a chain.
The page is only as fast as the slowest important part of the operation.
Sometimes that part is the server.
Sometimes it is the application.
Often, it is a mixture of both.
When the Store Outgrows Its First Home
Five years after opening its online store, Harbor Home Goods has little in common with the shop that launched with 80 products.
There are thousands of products now.
Customers place orders every day.
Promotions bring sudden traffic spikes.
The product catalog is tightly connected to internal business processes.
The website is no longer an experiment.
It is a sales channel.
That distinction changes the economics of hosting.
A few dollars saved each month are no longer particularly impressive if the store becomes unavailable during a major promotion.
At the same time, spending a large amount on infrastructure simply because the business has grown is not automatically sensible either.
The store needs enough capacity, not maximum theoretical capacity.
A well-configured shared plan may continue to work for some businesses.
A larger shared environment may be appropriate for others.
A managed VPS can make sense when more predictable resources and control are needed.
Dedicated infrastructure can eventually become appropriate for businesses with substantial traffic or demanding workloads.
Cloud-based architectures can also enter the discussion when elasticity, redundancy, or broader infrastructure requirements become important.
The key is to let actual requirements drive the decision.
Not the marketing label.
How to Choose PrestaShop Hosting
Imagine the store owner is back at the beginning.
She has five hosting providers in front of her.
One is the cheapest.
One advertises unlimited storage.
One specializes in ecommerce.
One offers a VPS.
One has excellent technical support but does not have the flashiest marketing page.
Which one should she choose?
The first step is not price.
It is compatibility.
Can the environment run the intended PrestaShop version?
Does it provide the required PHP version and extensions?
Is the database supported?
Is enough PHP memory available?
Are the necessary settings permitted?
The current PrestaShop 9 documentation is specific enough that these questions can be checked rather than guessed. ([devdocs.prestashop-project.org](https://devdocs.prestashop-project.org/9/basics/installation/system-requirements/))
Then comes capacity.
How much CPU can the account use?
How much memory?
How many PHP workers?
What happens during traffic spikes?
Are database resources heavily shared?
What happens if the store reaches a resource limit?
Then operations.
Are backups included?
Can the provider restore them?
Is migration assistance available?
Can the PHP version be changed?
Can the plan be upgraded?
Is the server managed?
What support is available when a technical problem appears?
And finally, the most practical question:
Will this environment still make sense if the store doubles in size?
The cheapest provider can be a bargain.
The right provider can be far more valuable.
Common Hosting Mistakes
The first mistake is choosing by storage.
A huge storage allowance does not compensate for poor database performance or tight CPU and memory limits.
The second mistake is checking only the PHP version.
PrestaShop requires specific extensions and configuration, so PHP compatibility is broader than a single number. ([devdocs.prestashop-project.org](https://devdocs.prestashop-project.org/9/basics/installation/system-requirements/))
The third mistake is installing modules without a compatibility strategy.
Every added component becomes part of the store's software environment.
The fourth mistake is treating images as an afterthought.
Poorly optimized product images can make a store feel slow even when the server is performing well.
The fifth mistake is forgetting about outbound connections.
Payment systems, module downloads, localization resources, APIs, and other integrations can depend on the store being able to communicate with external services. PrestaShop's documentation specifically identifies cURL and allow_url_fopen as important parts of the environment. ([devdocs.prestashop-project.org](https://devdocs.prestashop-project.org/9/basics/installation/system-requirements/))
The sixth mistake is relying on backups that have never been tested.
A backup is only part of a recovery plan.
The seventh mistake is updating the live store without considering module and theme compatibility.
The eighth mistake is waiting for serious performance problems before upgrading the hosting environment.
And the ninth is buying an unmanaged VPS without understanding what server administration actually involves.
None of these mistakes is especially complicated.
That is precisely why they are so common.
A Practical Hosting Setup
There is no single hosting specification that should be applied to every PrestaShop store.
There is, however, a sensible starting point.
Choose the PrestaShop version first.
Then check its official system requirements.
For the current PrestaShop 9 branch, that means checking the supported PHP version, required extensions, supported SQL database, web-server environment, and recommended PHP memory allocation. The current documentation recommends at least 512M for memory_limit and identifies PHP 8.4 as recommended for PrestaShop 9.0 and PHP 8.5 for 9.1. ([devdocs.prestashop-project.org](https://devdocs.prestashop-project.org/9/basics/installation/system-requirements/))
Then consider the store's workload.
How many products?
How many customers?
How many orders?
How much traffic?
How large are the images?
How many modules are installed?
How often do traffic spikes occur?
Does the store depend heavily on external APIs?
Who will manage the server?
A modest store can often begin comfortably with quality shared hosting.
A growing operation may benefit from a managed VPS.
A larger store with demanding workloads may need dedicated or more sophisticated infrastructure.
The label on the package matters less than whether the environment can comfortably handle what the store actually does.
The Long-Term View
Harbor Home Goods eventually stops talking about hosting very much.
That may sound strange after everything it has been through.
But it is actually a good sign.
The server is doing what it should.
The database is functioning.
The store is available.
Customers are buying.
Orders are being processed.
Backups are running.
Updates are being tested.
Traffic is being watched.
The hosting environment has changed as the business has changed, but nobody is surprised by that anymore.
That is the mature way to think about infrastructure.
Hosting is not a one-time purchase that remains perfect forever.
The right environment can change as the business changes.
A startup store may prioritize simplicity and low cost.
A growing company may prioritize predictable performance.
A large ecommerce operation may prioritize redundancy, scalability, monitoring, and stronger infrastructure controls.
There is no contradiction between those choices.
They are simply different stages of the same story.
The Store Has Become a Business
One evening, the original developer visits the Harbor Home Goods store.
He remembers what it looked like on launch day.
There were 80 products.
The order table was tiny.
The database barely had anything in it.
Today, the store looks completely different.
Thousands of products are available.
Customers order from different locations.
Promotions bring sudden bursts of traffic.
Payment and shipping systems communicate with the platform.
The administration team works in the back office every day.
The website has become part of the company's operation.
That is the moment when hosting takes on a different meaning.
The business is no longer paying for somewhere to put a website.
It is paying for infrastructure that supports sales.
PrestaShop provides the application layer, but the application still needs a suitable environment beneath it. The project's current documentation makes that relationship explicit through its detailed server, PHP, database, memory, extension, and configuration requirements. ([devdocs.prestashop-project.org](https://devdocs.prestashop-project.org/9/basics/installation/system-requirements/))
That leads to a simple conclusion.
The best hosting for a PrestaShop store is not automatically the cheapest.
It is not automatically the biggest.
It is not automatically a VPS.
And it is not automatically the hosting company with the longest list of ecommerce features.
The right environment is the one that fits the application, the workload, the people managing it, and the stage of the business.
A small shop should not have to pay for infrastructure it does not need.
A busy store should not be forced into an environment that regularly runs out of resources.
A highly customized store should not treat compatibility as an afterthought.
And a business that depends on online sales should never discover its recovery strategy during a crisis.
PrestaShop hosting is therefore really a story about matching infrastructure to commerce.
Once the store becomes important to the business, the server beneath it becomes important too.
Practical Takeaway
Before choosing hosting for PrestaShop, start with the exact version of the software you plan to run and compare the host's environment with the official requirements. For PrestaShop 9, that includes the supported PHP version, required PHP extensions, supported MySQL or MariaDB versions, web-server compatibility, and sufficient PHP memory. The official documentation also identifies cURL and allow_url_fopen as important for the platform's operation. ([devdocs.prestashop-project.org](https://devdocs.prestashop-project.org/9/basics/installation/system-requirements/))
Then look beyond compatibility.
Consider the store's catalog size, database activity, image workload, traffic patterns, modules, integrations, email requirements, backup strategy, security responsibilities, and likely growth.
A small store may be perfectly comfortable on quality shared hosting.
A growing store may need more predictable resources.
A busy ecommerce operation may eventually require a VPS or dedicated infrastructure.
The important thing is not to buy the largest server available.
It is to give the store a stable environment in which it can keep doing its job.
Because the real measure of successful PrestaShop hosting is not how impressive the server looks on paper.
It is what happens when a customer arrives, finds the product she wants, adds it to the cart, pays for it, and receives the confirmation without ever having to think about the technology underneath.
When that happens consistently, the hosting has done its job.
And the store can get on with the much more important business of selling.
FAQ
This FAQ explains what a web host needs to provide for a PrestaShop store to operate reliably, from the PHP and database stack through storage, security, email, backups, migrations, performance, scaling and day-to-day server administration.
FAQ menu
- 1. Choosing a Hosting Environment
- 2. Server and Software Requirements
- 3. Installing a Store
- 4. PHP and Extensions
- 5. Databases and Database Performance
- 6. Storage, Images and File Limits
- 7. Domains, SSL and Web Server Configuration
- 8. Speed, Caching and Server Resources
- 9. Email and Scheduled Tasks
- 10. Backups, Updates and Recovery
- 11. Security and Access
- 12. Migration and Hosting Changes
- 13. VPS, Dedicated Servers and Scaling
- 14. Multistore, Development and Advanced Hosting
- 15. Troubleshooting and Choosing the Right Plan
1. Choosing a Hosting Environment
1. What is included when a host says it supports PrestaShop?
At the most basic level, you are renting an environment in which the application can run: web space, PHP, a database, file storage, and network access. A useful package also gives the store enough CPU, memory and other limits to handle the work it actually has to do.
2. Can a small shop start on shared hosting?
Yes. A modest catalog and a relatively light flow of visitors can fit quite comfortably on a good shared account. The catch is that you are sharing the underlying machine, so the provider's CPU, memory, PHP-process and database limits matter more than the word shared itself.
3. What usually tells me that shared hosting has become restrictive?
Look for patterns rather than one bad moment. Frequent throttling, exhausted PHP workers, memory errors, slow database responses or pages that crawl during normal busy periods are stronger evidence than a single slow request.
4. Why is Linux the usual choice for this software?
PrestaShop works best in Unix-based environments, and Linux hosting has the mature PHP, database and web-server tooling that most stores need. That makes it the practical default for a production installation.
5. Would Windows hosting be a sensible production choice?
It can run in some circumstances, but the current project documentation says Windows is not actively supported. For a store you depend on, the supported Unix-based route is generally the less troublesome one.
6. Do I need cPanel or Plesk to run a store?
No. Those panels make tasks such as creating databases, changing PHP versions and managing files easier, but they are interfaces rather than requirements. The application only cares about the services and configuration underneath them.
7. What does managed hosting change for the owner?
A managed service can take server administration off your plate, such as handling system updates, server configuration, monitoring or certain backup and security tasks. The phrase is not standardized, so check the provider's exact list of responsibilities before paying extra for it.
8. Is a hosting package built for PrestaShop automatically better?
Not necessarily. A specialist environment can save setup time and may be tuned for the platform, but you still need to examine the underlying limits, software versions, support and actual server capacity. A generic but well-configured host can be perfectly suitable.
9. How important is a one-click installer?
It is mainly a convenience. A manual installation can work just as well when the server meets the requirements; an automatic installer simply takes care of tasks such as uploading files and creating the initial database connection.
10. Which hosting details deserve attention before I order?
Check the version support first, then look at memory limits, CPU and process policies, database limits, storage and file-count restrictions, backups, SSL, server location and the provider's upgrade path. Those details have much more practical value than a long list of vague feature badges.
Back to FAQ menu2. Server and Software Requirements
11. Which server setup does current PrestaShop 9 documentation call for?
For PrestaShop 9, the current documentation specifies Apache 2.4 or later, while Nginx 1.0 or later can also be used. It lists MySQL 5.7 or MariaDB 10.2 as minimum database versions and recommends at least a 512M PHP memory limit; PHP compatibility depends on the specific 9.x release.
12. Is PHP 8.5 the right choice for all PrestaShop 9 stores?
No. The 9.x compatibility table is release-specific. For example, 9.0 lists PHP 8.4 as the recommended version, while 9.1 lists PHP 8.5 as recommended, so the minor version installed on your store should be checked before changing the runtime.
13. Do PrestaShop 8 and 9 use the same PHP rules?
No. Each major version has its own compatibility range. The current documentation for version 8 recommends PHP 8.1, while version 9 has a different support matrix, which is why a hosting decision should always be tied to the exact release you are running.
14. What database versions are acceptable?
For version 9, the project's current requirements state MySQL 5.7 minimum or MariaDB 10.2 minimum, with a recent release preferred. Older versions of the application have their own requirements, so the age of the store matters here.
15. Why can't I simply check the requirements once and forget them?
Because a store's requirements can change when the application is upgraded. A server that was comfortable for one major release can become unsuitable after a PHP or database support change, even though the website itself has not changed in appearance.
16. Does the 512M figure mean I need 512 GB of server RAM?
No. That figure is the recommended PHP memory_limit for each PHP process in the current PrestaShop 9 documentation. It should not be confused with the total physical RAM available to the entire server.
17. Can the application run on macOS as well as Linux?
The documentation says it works best on Unix-based systems such as Linux and macOS. For public web hosting, however, Linux is by far the normal server choice, while macOS is more relevant to local development.
18. Is Nginx officially usable?
Yes. PrestaShop 9 documentation says it can run with Nginx 1.0 or later, provided the server is configured for the application's routing and PHP handling. Nginx therefore is not an automatic reason to reject a hosting plan.
19. Why is a large RAM number on a hosting sales page not enough information?
Because the store can hit a different ceiling first. CPU allocation, PHP workers, database speed, storage I/O and per-account restrictions can all become bottlenecks long before the headline memory figure is exhausted.
20. How can I verify an existing environment instead of guessing?
PrestaShop supplies a requirements checker. Its current instructions involve placing the provided phppsinfo.php file in the store directory and viewing it in a browser so the environment can be compared with the application's prerequisites and recommendations.
Back to FAQ menu3. Installing a Store
21. Can the host handle the initial installation for me?
Many hosts can, either through an installer or by offering migration and setup assistance. What you receive varies considerably, so distinguish between a button that copies the files and a service that actually checks the database, PHP configuration and finished site.
22. What should already exist before I start the installer?
Have the domain pointed to the right server, make sure the required PHP and database versions are available, and have access to the directory where the files will live. You will also need database credentials that the installation can use.
23. Can the storefront live below the main domain in a folder?
Yes. You can install it in a path such as a subdirectory rather than the domain root. The important thing is that the web server, the domain mapping and PrestaShop all agree about that location.
24. Can I put a second shop on a subdomain?
Yes. A subdomain can point to another directory and host a separate installation. This is often handy for a development copy, a regional shop or a completely independent storefront on the same account, provided the hosting plan allows it.
25. Is an FTP client enough for manual installation?
It is enough to transfer the files, and PrestaShop's manual installation instructions describe doing exactly that. SFTP is preferable when offered because the file-transfer session is protected rather than sent as plain FTP traffic.
26. What are the database credentials actually used for?
They give the application permission to connect to the database that contains the store's records. A typo in the host, database name, username or password can leave you with a perfectly uploaded set of files that still cannot function.
27. Why does a completely uploaded copy sometimes refuse to install?
Uploading the files is only one piece of the puzzle. The server may have an unsupported PHP release, a missing extension, restrictive settings, incorrect permissions or a database connection problem that prevents the installer from finishing.
28. Does the document root have to be the same as public_html?
No. public_html, www and similar names are common conventions, not application requirements. What matters is that the domain or subdomain points to the directory containing the installation and that the server is configured to serve it there.
29. Should an established shop be updated directly on the live server?
For significant changes, a separate test environment is safer. That gives you somewhere to try a new PHP release, module or application upgrade without discovering a compatibility problem in front of customers.
30. What is worth testing before calling the installation finished?
Do more than open the homepage. Try product and category pages, add an item to the cart, exercise the checkout as far as possible, sign into the back office, test image handling and confirm that important outgoing email functions work.
Back to FAQ menu4. PHP and Extensions
31. What can go wrong when the PHP version is wrong?
PHP is the runtime that executes the application, so an unsupported release can produce anything from warnings and broken modules to pages that will not load at all. The core version and every important extension around it need to be compatible.
32. Is newest PHP always the safest PHP?
No. Newer is only better after compatibility has been established. A store may be ready for a newer PHP branch while one of its modules or its theme is not, so upgrading the runtime without checking the rest can create the problem you were trying to avoid.
33. Can a PrestaShop 9 store still use PHP 7?
No. PrestaShop 9 no longer supports PHP 7.x and requires at least PHP 8.1. An older store may still depend on an older PHP branch, which is another reason not to treat all installations as though they have identical server requirements.
34. Which extensions should I expect to find enabled?
For PrestaShop 9, the official list includes cURL, DOM, Fileinfo, GD, Iconv, Intl, JSON, Mbstring, OpenSSL, PDO, PDO MySQL, SimpleXML and Zip. They support tasks ranging from database access and image processing to XML handling, localization and package extraction.
35. Why would missing GD show up as an image problem?
GD is used to create thumbnails. The upload itself can succeed, yet the resized versions needed elsewhere in the store may fail because the server cannot perform the required image processing.
36. What does allow_url_fopen have to do with hosting?
It is a PHP setting controlling certain forms of remote file access. The current PrestaShop 9 documentation requires it to be enabled because the application relies on remote access for some functions, including parts of payment processing.
37. Can a low PHP memory limit cause only certain pages to fail?
Yes. A light page may fit comfortably while an import, image operation or complicated back-office request uses much more memory. That is why a store can appear healthy until one particular operation crosses the limit.
38. Why do long imports sometimes stop partway through?
A PHP or server execution limit can terminate a request before the work is complete. Splitting a large job into smaller batches may be more reliable than simply increasing the timeout, especially on hosting with strict process limits.
39. Can I ask a shared host to enable a missing extension?
You can ask, but the answer depends on how much control the provider gives customers. Managed and dedicated environments are usually more flexible; tightly controlled shared plans may not let you alter the PHP build at all.
40. What should happen before I switch PHP on a live store?
Check the application's compatibility chart, verify the modules and theme against the target PHP release, take a current backup and test the change separately when possible. PrestaShop specifically recommends compatibility checks and backups before updating PHP.
Back to FAQ menu5. Databases and Database Performance
41. What kind of store information lives in the database?
The database holds the structured records that make the shop work, such as product data, customers, orders and configuration. Images and other files live on the filesystem, so the database is important but it is not a complete copy of the store.
42. Could a store work without MySQL or MariaDB?
No. A PrestaShop installation needs a supported database service for its operational data. The service may be hosted separately or shared at the infrastructure level, but the application still depends on a compatible SQL database.
43. Why do separate stores usually benefit from separate databases?
It keeps the two shops cleaner to manage and restore. You can move or repair one without having to untangle unrelated records from another installation.
44. Is MariaDB a supported choice rather than merely a workaround?
Yes. PrestaShop's current requirements explicitly support MariaDB, including version 10.2 as the stated minimum for version 9. As always, match the database version to the exact application release rather than relying on a generic hosting label.
45. How can the database become the slow part of a store?
Every product page, filter, search, customer request and back-office action may require database queries. As the catalog and traffic grow, inefficient queries or limited database resources can leave PHP waiting for results.
46. Why might a shared database feel slower than the rest of the account?
The database server may be serving many accounts at once. Your store can therefore encounter contention or provider-side limits even when its own files are sitting on a fast storage system.
47. What happens to the shop when the database connection disappears?
Anything that depends on stored data can stop working, including product pages and administrative functions. PrestaShop's own guidance lists bad credentials, missing privileges, an unavailable database server, version incompatibility and overload among possible causes.
48. Does database space always come from the normal disk quota?
There is no universal rule. Some hosts count database files inside the account's storage allowance, while others publish separate database limits. Read the provider's resource policy rather than assuming the numbers are interchangeable.
49. Can phpMyAdmin be used with a hosted shop?
Often it can, when the provider supplies it. It is useful for exports and inspection, but direct database editing should be treated as a powerful administrative tool: one incorrect change on a live store can have immediate consequences.
50. Why is a dedicated database account preferable to root access?
The application does not need the power of the database server's root account. A dedicated user limits the scope of damage if its credentials are exposed, and PrestaShop specifically advises against using the root user for the store.
Back to FAQ menu6. Storage, Images and File Limits
51. How much disk space should I allow for a shop?
There is no sensible universal quota. One store may be mostly text and product data, while another keeps large originals, generated thumbnails, modules, logs and local backups. Measure the current footprint and give yourself room for growth and temporary working space.
52. Are product photos usually a major part of disk usage?
They can be, especially when original images are large and several display sizes are generated. Ten thousand product records do not necessarily consume much space, but a few thousand records with multiple large images can change the calculation dramatically.
53. Can I run out of files before I run out of disk space?
Yes. Some hosting providers impose an inode or file-count ceiling as well as a storage quota. A media-heavy store or one with many cached and generated files can reach that limit while still showing plenty of free gigabytes.
54. What can stop an upload when there is still lots of room on the drive?
The file can be rejected earlier by PHP's upload limit, a request-size rule, an application setting, a memory ceiling or file permissions. Free disk space only answers one of those questions.
55. Does image size affect server load as well as storage?
It does. A very large source image takes more memory and processing time to resize, especially when many files are handled together. Sensibly sized originals can make image-related tasks considerably lighter.
56. Why are there several files for what looks like one product picture?
The application can create different image sizes for different parts of the storefront. That avoids downloading the original everywhere, but it also means one source image can result in multiple stored derivatives.
57. Could a CDN take the pressure off image delivery?
Yes. Static images can be served from edge locations instead of being delivered repeatedly from the origin server. That can reduce bandwidth and improve delivery for distant shoppers, although it does not eliminate PHP or database work.
58. Can product images be kept in external storage?
They can in architectures that support the required storage integration. This can be attractive for a large media library, but the integration must preserve reliable paths or URLs and should be proven with both storefront and administrative image functions before moving everything.
59. Is keeping every backup beside the live site a good idea?
It is better than having no backup, but it does not cover every failure scenario. If the account, disk or server is lost, a same-server backup may disappear with it, so an independent copy is much more useful for disaster recovery.
60. How often should storage usage be reviewed?
Make it part of routine maintenance rather than waiting for an error. A quick weekly or monthly check can reveal a rapidly growing image library, log directory, cache or backup set before the account reaches a hard limit.
Back to FAQ menu7. Domains, SSL and Web Server Configuration
61. Can I keep my domain with one company and host the store somewhere else?
Absolutely. The registrar and the web host do not have to be the same company. You simply use DNS to direct the domain to the server where the installation is running.
62. What does DNS have to do with a hosting migration?
DNS decides where browsers are sent when they request the domain. If it still points to the old server after a migration, visitors will continue reaching the old copy even though the new installation is ready.
63. Should a production storefront always use HTTPS?
Yes. An ecommerce site handles account credentials and other sensitive traffic, so encrypted HTTPS is the sensible baseline. It also avoids exposing customers to an avoidable browser security warning.
64. Does the host have to sell me the SSL certificate?
No. The certificate can come from the host or another certificate authority. The important part is that the certificate is valid for the domain and that the web server and application consistently use the HTTPS version of the site.
65. Why can HTTPS produce warnings about insecure content?
The main page may be secure while an image, script or stylesheet is still being requested over HTTP. Browsers flag that mixture, so the remaining insecure references need to be corrected.
66. What are rewrite rules doing for PrestaShop?
They help the web server route friendly URLs to the right application requests. When those rules are wrong or missing, you can see 404s, redirect loops or URLs that behave differently from direct technical paths.
67. Can Apache configuration affect a perfectly good installation?
Yes. PrestaShop can depend on web-server features such as URL rewriting, and a small configuration difference between servers can change how requests are handled. That is why migrations sometimes uncover server-level problems that were invisible before the move.
68. Is Nginx usually used by itself?
It can be, and PrestaShop supports it, but Nginx can also sit in front of another web server in more elaborate setups. The added layer is not automatically an improvement; it simply gives you another place where configuration has to be correct.
69. Should I redirect every HTTP request to HTTPS?
A consistent secure URL is usually the right goal, but the redirects should be designed carefully. Proxy layers, CDN rules and application settings can accidentally create loops if more than one layer tries to enforce HTTPS in a conflicting way.
70. Why can one line in a server configuration take the whole store offline?
Web-server configuration sits directly in the request path. A syntax mistake or an incorrect routing rule can therefore prevent requests from reaching PHP at all, so keep a known-good configuration and test changes before applying them to a busy store.
Back to FAQ menu8. Speed, Caching and Server Resources
71. How much of a store's speed comes from the server?
A lot of the work happens there: PHP code has to execute, database queries have to finish and files have to be read and delivered. It is not the whole story, because modules, themes, external services and the shopper's connection also matter.
72. If I add CPU, will every slow page improve?
Not necessarily. CPU helps when the processor is the bottleneck, but a slow database query or external request can leave plenty of CPU unused while the page still waits. Measure first, upgrade second.
73. What does server-side caching actually save?
It avoids repeating work that does not need to be repeated. Depending on the environment, that can mean reusing compiled PHP code, cached application results or previously generated responses instead of rebuilding everything from scratch on every request.
74. Can I cache the cart and checkout like a product page?
Not safely in the same way. Public catalog pages can often be shared between visitors, while carts, accounts and checkout contain customer-specific information. Caching rules need to know the difference or they can serve the wrong content.
75. What is OPcache doing on a PHP server?
OPcache keeps compiled PHP bytecode in memory so the server can execute code without recompiling the same scripts every time. It is a server-side efficiency improvement rather than an application feature you configure from a product page.
76. Can the speed of the storage system matter to PrestaShop?
Yes. The application, database, cache and logs all read and write data. Faster storage can reduce waiting, particularly under load, although it will not repair an inefficient module or a slow external API call.
77. Can a sudden burst of shoppers overwhelm shared hosting?
It can. The issue is not simply monthly visitor volume; many simultaneous requests can use up PHP workers, CPU, memory or database connections in a short period and leave later requests waiting or failing.
78. Why does a store sometimes slow down only during certain hours?
A time-specific problem often points to a workload that appears on a schedule: traffic spikes, imports, backups, indexing or cron jobs. Comparing the slow period with server metrics and scheduled tasks can reveal far more than a speed test run at a quiet time.
79. Can a CDN hide the need for better server resources?
It can reduce the origin server's work for static assets, but it cannot move PHP or database processing to the edge in the same way. A CDN is a useful layer, not a replacement for adequate application hosting.
80. What should I investigate before buying a bigger server?
Find the bottleneck first. Check PHP response times, database behavior, CPU, memory, storage activity, external calls and recent software changes. That lets you spend money on the resource that is actually limiting the store.
Back to FAQ menu9. Email and Scheduled Tasks
81. How should a hosted store send customer email?
It needs a dependable mail path for things such as order notices, password resets and customer messages. That may use the server's mail service, authenticated SMTP or a separate transactional provider, depending on the environment.
82. Is the server's basic PHP mail function enough?
It can work, but it is not automatically the most dependable arrangement for an important store. Authenticated SMTP or a transactional service can give you stronger control over authentication, delivery and the sender identity.
83. What should I test after changing hosts if the site looks fine?
Test email separately. DNS, SMTP credentials and sender authentication can change during a migration, and a storefront that loads normally can still be failing to deliver order and account messages.
84. Why would a store need a cron job?
A cron job lets the server perform scheduled work without waiting for someone to open a page. Depending on the modules installed, that can be useful for imports, maintenance tasks, feeds, notifications or other background processing.
85. Do all installations require scheduled server tasks?
No. The requirement comes from the particular application features and modules you use. If nothing calls for a scheduled job, there is no reason to create one merely because the control panel offers cron settings.
86. Can shared hosting run scheduled tasks?
Many shared providers expose cron functionality, but the exact interval and commands allowed can be restricted. On a VPS or dedicated server, you generally have much more control over the scheduler and the PHP environment used to run it.
87. Why can the same PHP script work in a browser but fail from cron?
The two execution paths may use different PHP binaries, environment variables, permissions or working directories. A scheduled command therefore needs to be tested in the environment in which it will actually run.
88. Is it safe to run store automation as root?
Usually not. Scheduled work should run with only the permissions it needs. Root access turns a simple mistake or compromised script into a much broader server-level problem.
89. Can a long-running import exceed hosting limits even when cron is enabled?
Yes. Scheduling a task does not remove CPU, memory or execution-time restrictions. The host can still terminate the process, especially if one job tries to process a very large amount of data in one pass.
90. How do I confirm that a scheduled task really ran?
Use the hosting panel's cron history or server logs when available, and check the application's own records if the module keeps them. Do not confuse a saved cron schedule with proof that the command completed successfully.
Back to FAQ menu10. Backups, Updates and Recovery
91. What belongs in a proper backup of a store?
At minimum, think in two parts: the database and the files. The database contains orders and other records, while the filesystem holds the application, configuration, modules, themes and uploaded material. A recovery copy needs both sides to line up.
92. Can I rely entirely on the backups supplied by my host?
They can be valuable, but you should know their retention period, location, restore process and coverage before treating them as your only safeguard. Keeping an independent copy gives you protection if the hosting account itself becomes unavailable.
93. Why is an off-site backup more valuable than another copy on the same server?
A same-server copy disappears in some of the same disasters as the live site. An independent backup remains available when the host, account or storage system is the thing that has failed.
94. How much backup frequency is sensible for an active shop?
Base it on the amount of order or customer data you are prepared to lose. A store taking orders throughout the day benefits from much more frequent database protection than a site whose catalog changes once every few weeks.
95. Should a PrestaShop upgrade always start with a backup?
Yes. PrestaShop's current guidance recommends backing up before updates, along with checking module and theme compatibility. That gives you a known recovery point if the new code or one of its extensions causes trouble.
96. Why take a backup before changing PHP if the database is untouched?
Because the runtime can expose incompatible code in modules, themes or customizations. A backup preserves the working combination of files and data before you introduce a new variable.
97. Would a fresh database dump be enough to restore the site?
Not by itself. You also need the matching application files and uploaded content. Restoring only the database can leave you with records that refer to files or code that no longer exist.
98. Can rolling back only the website files also create inconsistencies?
Yes. If the files return to an earlier state while the database remains newer, versions can disagree about configuration or data structures. Recovery works best when the database and files are restored from a compatible point in time.
99. How can I find out whether my backups are actually usable?
Perform a test restore on a separate environment. That exercise exposes missing files, unusable database dumps, permission problems and undocumented configuration steps while there is still no customer waiting for the result.
100. What should a practical disaster-recovery plan contain?
Know where the latest database and file backups live, how the DNS is controlled, what PHP and database versions the store uses, how to rebuild the environment, and how you will test the restored copy. The valuable part of a backup is being able to turn it into a working store.
Back to FAQ menu11. Security and Access
101. How much responsibility for security sits with the hosting provider?
The provider controls important parts of the foundation, such as operating-system maintenance, network controls and some server configuration, depending on the service. You still remain responsible for the application, modules, passwords and many store-level decisions, so security is shared rather than outsourced completely.
102. Why should an old PHP branch worry me even if the store still works?
A runtime can continue executing perfectly well after its normal maintenance period has ended. The problem is that newly discovered security issues may no longer receive fixes, leaving the application dependent on an unsupported component.
103. Why is SFTP preferable to plain FTP?
SFTP protects the file-transfer session and credentials instead of sending ordinary FTP traffic in an unencrypted form. It is a small administrative improvement that makes sense whenever the host provides it.
104. Can file permissions make a store less secure?
They can. Permissions that are excessively open give attackers or other processes more freedom to alter files, while permissions that are too tight can stop legitimate application operations. Good permissions provide the minimum access needed for the job.
105. Is it safer to put a busy store in its own hosting account?
It can be. Separation reduces the blast radius of certain problems and makes resource usage easier to understand. On some shared arrangements that isolation is not available, but commercially important stores benefit from clear boundaries where practical.
106. Which credentials should I protect most carefully?
Think beyond the back-office password. Hosting-panel logins, SSH and SFTP credentials, database accounts, API keys and DNS access can all provide ways to alter or take control of the store and its infrastructure.
107. Would a web application firewall help protect an installation?
It can add another filtering layer for incoming requests. It is not a substitute for updates and secure credentials, and a badly tuned WAF can interfere with legitimate checkout or API traffic, so it should be configured and tested rather than simply switched on.
108. Do I actually need SSH on the hosting account?
Not for every shop. SSH becomes useful when you need command-line administration, diagnostics, scheduled scripts or development tools. A managed shared environment may intentionally omit it because the provider handles those tasks for you.
109. Should MySQL or MariaDB be reachable from the public internet?
Normally it should not be exposed unnecessarily. Restricting database access to the application and approved administration paths reduces the number of network routes through which someone could attack the database service.
110. What is the right first response if I think the hosting account was hacked?
Treat the incident as potentially broader than one altered page. Contact the provider, secure or replace affected credentials, review access and file activity, preserve useful evidence, and use a known-clean recovery point where appropriate while you work out how the compromise happened.
Back to FAQ menu12. Migration and Hosting Changes
111. Is migrating an existing store to another host realistic?
Yes. The usual job is to transfer the files, move the database, reproduce the required environment, adjust configuration, test the new copy and then change where the domain points. The process is familiar, but a live store needs more care than a static website because orders keep arriving.
112. What gets left behind if I move only the database?
The database is only the record-keeping side of the installation. Without the matching application files, modules, themes, configuration and images, you do not have a complete working storefront.
113. Should the new server duplicate every detail of the old server?
It should reproduce what the application actually needs, not necessarily every old setting. A move is a good time to modernize unsupported PHP or database versions, but compatibility with the current store has to be preserved during the transition.
114. Can careful DNS planning reduce migration disruption?
Yes. Build and test the destination before the final switch, keep the old copy available during the cutover, and review DNS timing in advance. The amount of unavoidable disruption depends partly on how the live database is handled during the final change.
115. What is the hard part of moving a store that is still receiving orders?
The source database keeps changing while you copy it. A simple one-time dump can miss orders or customer changes made afterward, so the final cutover needs either a controlled maintenance window or a method for handling the last changes safely.
116. Is it a bad idea to change both domain and host in the same move?
It is possible, but two simultaneous changes make diagnosis harder. Moving the hosting first while keeping the domain stable gives you a simpler test; a domain change can then be handled separately with its own SSL, redirects and URL considerations.
117. What causes a database connection error right after migration?
The new server may use different database credentials or a different hostname, port or access policy. The application can still be carrying the old connection details even though the database itself was imported correctly.
118. Why can a migrated store show broken or missing pictures?
The image files may not have been copied, may be in the wrong directory, or may be blocked by permissions or URL settings. A successful database import does not prove that the media library made the journey too.
119. How much migration assistance do hosting companies normally provide?
There is a wide range. One host may simply give you an SFTP account, while another will move the database, copy the files, change DNS and help investigate post-migration problems. Ask exactly what the migration service includes.
120. When is it safe to close the old hosting account?
Only after the new store has survived real testing and you have confirmed the storefront, back office, database, email, SSL, scheduled jobs and DNS. Keep a separate backup before cancelling the old service so you do not destroy your last fallback by accident.
Back to FAQ menu13. VPS, Dedicated Servers and Scaling
121. Would a VPS suit a larger PrestaShop installation?
It can be a strong step up when a shared account starts imposing limits. A VPS gives you more control over the PHP runtime, database and web server and normally provides more predictable resources, although you still have to manage or pay someone else to manage the machine.
122. Does moving to a VPS guarantee a faster store?
No. The benefit is control and resource allocation, not a magic speed increase. A badly configured VPS can be slower than a well-run shared environment, particularly if the database and PHP stack have not been tuned properly.
123. What would make a dedicated server reasonable?
Usually a combination of sustained workload, business importance and the need for predictable resources. If a store's traffic and processing demands justify an entire machine, dedicated hosting can make sense; otherwise it may simply add cost and administration without solving a real problem.
124. Is managed VPS hosting easier to live with?
For most non-specialists, yes. A managed plan can shift tasks such as system updates, monitoring and server maintenance back to the provider. An unmanaged VPS leaves those responsibilities largely with you, which can be perfectly fine when you have the knowledge and time to handle them.
125. What does it mean to scale a server upward?
You keep the same basic architecture but give it more resources, such as additional CPU, RAM or storage. That is often the simplest response to a growing store when one machine is still fundamentally suitable.
126. What would scaling out look like for a much busier store?
Instead of one larger machine, you introduce more components, such as additional web nodes, dedicated database infrastructure, load balancing or separate caching and storage services. It can handle more demand, but it also creates more moving parts to operate.
127. Can the database live on a separate machine?
Yes. A dedicated database server can give the SQL workload its own CPU, memory and storage resources. This becomes useful when database activity is the limiting factor, not merely because the store has reached some arbitrary product count.
128. What is the point of placing a load balancer in front of several web servers?
It spreads incoming requests between the available web nodes. That can increase concurrent capacity and resilience, but the application must also cope with shared or synchronized data, sessions, caches and configuration across those nodes.
129. Are dedicated resources particularly useful for high-traffic shops?
Often they are, because predictable capacity makes it easier to absorb busy periods without competing with unrelated customers on the same machine. Even then, resource allocation should be based on observed workload rather than a generic traffic threshold.
130. Which measurements tell me whether I actually need more server capacity?
Look at CPU pressure, available memory, PHP worker saturation, database latency, storage I/O, bandwidth and error rates. The pattern usually makes the next step clearer than a provider's generic recommendation to upgrade.
Back to FAQ menu14. Multistore, Development and Advanced Hosting
131. Can several stores share one server?
Yes, provided the machine has enough capacity and the installations are configured carefully. The practical limit is determined by combined workload, storage, isolation and administration rather than by a fixed number built into PrestaShop hosting.
132. Is putting multiple stores in one hosting account always economical?
It can be, but the convenience comes with shared consequences. They may compete for the same CPU, memory, storage and database resources, and a problem that exhausts the account can affect several storefronts at once.
133. How is multistore different from running several independent installations?
Multistore keeps multiple shops inside one PrestaShop environment, while independent installations have separate application and database structures. Multistore is attractive when the shops need shared management or data relationships; separate installations provide stronger independence.
134. Why keep staging separate from production?
A staging copy is supposed to be a safe place to experiment. It should not accidentally send real customer emails, process live payments or modify the production database merely because both copies happen to be on the same server.
135. What is the practical benefit of a staging server?
It gives you somewhere to test changes before exposing them to shoppers. PHP upgrades, module updates, theme work and server configuration changes become much less risky when you can break and fix the test copy first.
136. Can staging use a smaller hosting plan than production?
Yes for many tasks. A reduced environment may be perfectly adequate for testing code or configuration, but it will not give you a meaningful picture of production performance unless the important server characteristics are reasonably similar.
137. Will a normal production shop need Composer installed?
Not necessarily. PrestaShop uses Composer in its package management, but ordinary store operation does not mean the store owner has to run Composer commands on the server. The need depends on your installation and development workflow.
138. Why does current PrestaShop development documentation mention Node.js 20.x?
It is part of the development workflow used for frontend dependencies and asset compilation. That does not mean every production hosting customer needs Node.js simply to keep an ordinary storefront online.
139. Can PrestaShop be deployed with Docker?
Yes. Docker can package the application and its supporting services into a controlled environment, which is particularly useful for development and repeatable deployments. It also adds container administration, so it is an option rather than a requirement.
140. Can I use the built-in webservice API from a regular hosting account?
Yes, where the hosting environment permits the required application and network behavior. The API is an application capability; the hosting service supplies the PHP and network environment in which those API requests operate.
Back to FAQ menu15. Troubleshooting and Choosing the Right Plan
141. What does a 500 server error tell me about a broken store?
Only that the server failed to complete the request. It does not tell you why. PHP errors, incompatible extensions or modules, bad rewrite rules, permissions and exhausted resources can all produce a 500 response, so logs are the next useful source of information.
142. Why can customers get errors while the back office still opens normally?
The front and back ends exercise different paths through the code. A theme problem, frontend module or routing rule can therefore damage public pages without preventing administrator pages from loading.
143. Can the opposite happen, with the storefront working while the back office is broken?
Yes. Administration requests can use different controllers, templates, memory and permissions, so a healthy-looking storefront does not prove that the entire installation is functioning correctly.
144. What should I examine when a previously fast shop suddenly slows down?
Start with what changed and what the server is doing at the same time. Check resource consumption, database latency, PHP workers, scheduled jobs, backups, traffic and recently installed or updated modules before changing the hosting plan.
145. Why would the database suddenly become unreachable after a server move?
The imported database can be fine while the application points to the wrong host, user or password. The new provider may also use different access rules or network settings, so the connection details need to be checked in the destination environment.
146. What does it mean when a shared host reports that my account hit a process or CPU limit?
The store used more of the provider's allowed computing resources than the account could have at that moment. That can result in throttling, slow requests or failures, and it tells you that the limit itself is now part of the hosting problem.
147. Should the word unlimited influence my choice of hosting?
Not by itself. An unlimited bandwidth promise can coexist with strict CPU, memory, database, PHP-worker or file-count limits. Read the actual resource policy because those hidden ceilings are often more relevant to application hosting.
148. Is a 99.9% uptime promise enough to identify good hosting?
No. Availability is only one part of the picture. A server can technically remain online while the database is sluggish, pages are slow or support takes hours to respond, none of which is captured by a simple uptime figure.
149. What is a sensible starting environment for a new store?
Choose a service that clearly meets the requirements of the version you intend to install, has some resource headroom, includes dependable backups and SSL, and lets you scale later without rebuilding everything. A small store does not need the same infrastructure as a national retailer on day one.
150. When should I stop adding resources and inspect the application instead?
When the server has plenty of unused capacity but the problem continues, especially if only particular pages or functions are affected. At that point a module, theme, database query, external service or custom code is more likely to be the culprit than the size of the server.
Back to FAQ menu