PrestaShop 9: What’s New and Why It Matters in 2026

PrestaShop 9 is much more than a visual refresh. It is a major technical generation of the platform, built around a newer Symfony foundation, a modernized PHP stack, a new Admin API, native support for modern image formats, major front-office changes, and continued migration away from legacy architecture.

For merchants, agencies, and module developers, that makes PrestaShop 9 important for a simple reason: it changes the technical baseline on which future PrestaShop stores will be built.

The original PrestaShop 9.0 release arrived on June 10, 2025. During 2026, the platform evolved further with PrestaShop 9.1, which made Hummingbird 2 the default front-office theme and added support for PHP 8.5.

As of September 22, 2026, PrestaShop 9.1.5 is the latest stable release in the 9.1 line and was announced as the last planned 9.1.x release before PrestaShop 9.2. PrestaShop 9.2 has reached Release Candidate testing, so merchants should still treat it as pre-release software until the final stable version is published.

This guide explains the most important PrestaShop 9 changes, what they mean in practice, and what store owners and developers should consider before upgrading.

Quick Summary: What Changed in PrestaShop 9?

The biggest PrestaShop 9 changes include:

Symfony 6.4 LTS
PHP 8.1–8.4 support in PrestaShop 9.0
PHP 8.5 support in PrestaShop 9.1
a completely new Admin API
API Platform integration
OAuth2-based API authentication
native WebP image support
native AVIF image support
improved product and category URLs
continued Back Office migration to Symfony
Hummingbird as the modern front-office direction
Hummingbird 2 as the default theme in PrestaShop 9.1
performance improvements
developer architecture improvements
continued removal of legacy code
improved security maintenance

The significance of these changes depends on how you use PrestaShop.

A small merchant may mostly notice the new storefront architecture and improved compatibility with modern hosting. A module developer, however, will care much more about Symfony 6.4, dependency injection, the Admin API, PHP compatibility, and changed front-office data structures.

PrestaShop 9 Uses Symfony 6.4 LTS

One of the most important architectural changes in PrestaShop 9 is the move to Symfony 6.4 LTS.

PrestaShop 8 still relied on an older Symfony generation in important parts of the application. PrestaShop 9 makes a substantial jump forward.

This matters because Symfony is deeply integrated into modern PrestaShop development.

Developers use Symfony concepts for areas such as:

dependency injection
services
routing
controllers
forms
events
console commands
security
configuration
Back Office pages

Moving to Symfony 6.4 gives PrestaShop a newer and longer-supported framework foundation.

It also means that older modules may require changes.

A module that worked correctly on PrestaShop 8 should not automatically be considered compatible with PrestaShop 9 simply because the installation process does not throw an error.

Real compatibility testing should include:

module installation
configuration pages
Symfony routes
legacy controllers
hooks
front-office output
Back Office grids
cron jobs
CLI commands
multistore behavior
upgrade scripts
uninstall behavior

For module vendors, PrestaShop 9 is a good opportunity to remove technical debt instead of simply patching errors until old code runs again.

PHP Support Is Significantly More Modern

PrestaShop 9 requires a modern PHP environment.

According to the current official PrestaShop 9 system requirements:

PrestaShop 9.0

Supported PHP versions:

PHP 8.1
PHP 8.2
PHP 8.3
PHP 8.4

The recommended version for PrestaShop 9.0 is PHP 8.4.

PrestaShop 9.1

Supported PHP versions:

PHP 8.1
PHP 8.2
PHP 8.3
PHP 8.4
PHP 8.5

The recommended version for PrestaShop 9.1 is PHP 8.5.

That distinction is important.

A hosting company may advertise “PrestaShop 9 support,” but your real compatibility depends on the exact combination of:

PrestaShop version
PHP version
module versions
theme
Composer dependencies
custom code
external integrations

Before switching a production store from PHP 8.4 to PHP 8.5, test every critical workflow in staging.

Pay particular attention to:

checkout
payment modules
imports
product combination updates
scheduled jobs
email processing
image regeneration
PDF generation
ERP integrations
custom overrides

PHP compatibility problems often appear in less frequently used features rather than on the homepage.

PrestaShop 9 Introduces a New Admin API

The new Admin API is one of the most strategically important additions in PrestaShop 9.

It is designed as a modern alternative to the older PrestaShop Webservice approach.

The new API is built using API Platform and integrates with PrestaShop’s modern architecture.

This opens the door to cleaner integrations with:

ERP systems
PIM systems
CRM platforms
warehouse management systems
supplier systems
marketplaces
SaaS applications
reporting tools
automation platforms
custom mobile or administration applications

For developers building integrations, this is a major improvement.

Instead of treating PrestaShop as a database exposed through generic CRUD operations, integrations can increasingly work with application-level business operations.

OAuth2 Improves API Security

The new Admin API uses OAuth2.

This allows integrations to receive controlled access instead of relying on one universal credential with excessive permissions.

A good integration design should follow the principle of least privilege.

For example, a service that only synchronizes stock should not need permission to:

manage employees
alter unrelated store configuration
install modules
change payment settings

Separate API clients also make credential rotation easier.

If one external service is compromised, its credentials can be revoked without replacing every integration credential used by the shop.

API Platform Creates New Opportunities for Module Developers

PrestaShop 9’s Admin API is not only useful for core functionality.

Modules can participate in this architecture as well.

That means a commercial PrestaShop module can potentially expose structured API resources instead of creating custom PHP endpoints with inconsistent authentication.

Examples include modules for:

stock synchronization
supplier feeds
security auditing
order processing
external reporting
product enrichment
license management
warehouse automation

This is particularly valuable for developers building a PrestaShop module that also connects to a SaaS service.

Hummingbird Represents the New Front-Office Direction

PrestaShop 9 introduced Hummingbird as the modern front-office theme direction.

The change became even more important with PrestaShop 9.1, where Hummingbird 2.0 became the default theme for new installations.

Hummingbird is more than a redesign.

It represents a newer front-end approach with:

Bootstrap 5
modern browser assumptions
improved accessibility
updated components
better performance foundations
a more maintainable architecture

For new stores, this provides a stronger technical starting point.

For existing stores using a customized Classic-based theme, the decision is more complicated.

Replacing a theme can affect:

conversion rate
search visibility
templates
module compatibility
JavaScript behavior
structured data
checkout
navigation
image dimensions
CSS customizations

A theme migration should therefore be treated as a real project rather than a simple visual update.

Native WebP Support

PrestaShop 9 includes native WebP support.

WebP can reduce the size of product images while maintaining useful visual quality.

That can improve:

page weight
mobile performance
product-page loading
category-page loading
bandwidth usage
Core Web Vitals

However, enabling WebP does not automatically solve image-performance problems.

A store may still be slow if:

source images are unnecessarily huge
the theme requests oversized thumbnails
hundreds of unused image types exist
thumbnails are regenerated through long browser requests
the CDN is misconfigured
cache headers are poor

Modern formats work best as part of a complete image pipeline.

Native AVIF Support

PrestaShop 9 also added native AVIF support.

AVIF can provide excellent compression for product photography, although encoding can be more computationally expensive than traditional image formats.

Large stores should therefore think about image generation operationally.

If a catalog contains 100,000 products with several images per product, regenerating all image formats may involve hundreds of thousands or even millions of files.

For large catalogs, image processing is usually safer when handled through:

CLI
cron jobs
queues
resumable batches
controlled worker concurrency

instead of one Back Office browser request.

PrestaShop 9 Includes SEO and URL Improvements

PrestaShop 9 also introduced several SEO-related improvements.

Official release notes highlighted areas including:

cleaner product URLs
category removed from product URLs by default
improved handling of language prefixes
better redirect control for inactive categories

These are useful improvements, but merchants should be careful when upgrading an existing store.

Changing a URL structure across thousands of indexed pages can create significant SEO risk.

Before migration:

crawl the current store
export important URLs
identify pages receiving organic traffic
define redirect rules
test the new URL structure
verify canonical tags
check internal links
submit updated sitemaps
monitor search-engine coverage after launch

A technically cleaner URL is not automatically worth losing years of accumulated search signals.

The Back Office Continues Moving Away from Legacy Architecture

PrestaShop has been gradually modernizing the Back Office for years.

PrestaShop 9 continues this work.

The long-term direction is clear: more Symfony-based architecture and less reliance on legacy controllers and outdated patterns.

This improves the development experience because module developers can increasingly work with:

modern controllers
services
dependency injection
reusable application logic
cleaner routing
structured forms
modern security patterns

It also means old modules that depend heavily on legacy internals will become progressively more expensive to maintain.

PrestaShop 9 Is Better Positioned for Large Integrations

One of the most interesting consequences of the architecture changes is that PrestaShop is becoming easier to treat as part of a larger ecommerce ecosystem.

Modern stores rarely operate in isolation.

A serious shop may communicate with:

multiple suppliers
ERP
accounting software
CRM
PIM
shipping platforms
marketplaces
analytics systems
marketing services
warehouse software

The new API architecture, modern PHP baseline, Symfony services, and better CLI possibilities create a stronger foundation for these workflows.

The key is not to force every operation through a single request.

Large imports should still use proper job architecture.

For example:

Supplier XML/API
      ↓
Validation
      ↓
Import queue
      ↓
Create / Update workers
      ↓
PrestaShop
      ↓
Image queue
      ↓
Monitoring / retry

That is safer than downloading a huge supplier file and trying to update 100,000 products in a single HTTP request.

Module Compatibility Still Matters

A major PrestaShop version inevitably creates compatibility work.

Before upgrading, audit every installed module.

For each module, determine whether it is:

officially compatible
tested internally
replaceable
no longer required
blocking the upgrade

Pay special attention to modules that modify:

checkout
payment
stock
product pages
categories
URLs
images
orders
customer authentication
Back Office forms

Also inspect custom overrides.

An override created years ago may duplicate a core fix that is already included in PrestaShop 9.

Removing obsolete code can make the upgraded store both safer and easier to maintain.

Do Not Upgrade Production First

A major-version upgrade should always be rehearsed.

A good workflow looks like this:

1. Back up production

Create a complete copy of:

database
PrestaShop files
images
module data
configuration
cron definitions
server configuration

2. Create staging

Clone the production environment.

The staging copy should resemble the real store closely enough to expose problems.

3. Match the target PHP version

If the final environment will run PrestaShop 9.1 on PHP 8.5, test that exact combination.

4. Upgrade modules first where appropriate

Install PrestaShop 9-compatible module versions according to vendor guidance.

5. Perform the core upgrade

Use the officially supported upgrade process.

6. Test business workflows

Test more than the homepage.

Check:

product creation
product updates
combinations
search
cart
checkout
every payment method
order creation
refunds
invoices
emails
stock updates
cron jobs
imports
exports
image processing
multistore behavior

7. Measure performance

Compare response times before and after the migration.

8. Define rollback conditions

Before production migration begins, decide what failure threshold requires rollback.

This removes emotional decision-making during a stressful deployment.

PrestaShop 9.1.5 and Security Maintenance

PrestaShop 9 is not a release you install once and forget.

Security maintenance continues throughout the branch lifecycle.

PrestaShop 9.1.5, released on August 18, 2026, included five security fixes and around one hundred bug fixes.

The PrestaShop team also announced that 9.1.5 is the last planned 9.1.x release before PrestaShop 9.2.

That is a useful reminder for store owners.

Your maintenance process should include:

monitoring official PrestaShop releases
tracking security advisories
testing updates in staging
keeping modules updated
removing abandoned modules
maintaining backups
monitoring file integrity
reviewing logs

Security is a process, not a one-time module installation.

What About PrestaShop 9.2?

At the time this article was verified, PrestaShop 9.2 had reached Release Candidate testing.

That is important, but a Release Candidate is still not the same thing as a stable production release.

If you run a revenue-generating store, avoid planning production around pre-release features unless you explicitly accept the testing risk.

Wait for the final release, then check:

final release notes
module compatibility
theme compatibility
PHP requirements
known issues
upgrade guidance

This article will need to be updated once PrestaShop 9.2 becomes stable.

Is PrestaShop 9 Worth Using for a New Store?

For a new PrestaShop project in 2026, a maintained PrestaShop 9 release should normally be the starting point.

The main reasons are:

modern PHP support
Symfony 6.4
new Admin API
Hummingbird 2
modern image formats
ongoing architectural modernization
active security maintenance

The main exception would be a critical business dependency that does not yet support PrestaShop 9.

For example, if a specific ERP connector or payment solution is essential and only supports PrestaShop 8, compatibility may temporarily outweigh the benefits of the newer platform.

Should an Existing PrestaShop 8 Store Upgrade?

The answer depends on the store.

A heavily customized PrestaShop 8 installation should not be migrated just because version 9 exists.

First evaluate:

theme compatibility
module compatibility
PHP compatibility
custom overrides
custom SQL
ERP integrations
supplier integrations
payment providers
shipping integrations
cron jobs
custom APIs

Then estimate migration work.

For many stores, PrestaShop 9 is the correct long-term direction.

But a controlled migration is always better than a rushed one.

PrestaShop 9 Checklist for Merchants

Before adopting PrestaShop 9, confirm the following:

hosting supports the required PHP version
database version meets requirements
PHP memory is adequate
critical modules support PrestaShop 9
payment modules are tested
theme is compatible
overrides have been reviewed
cron jobs work with the target PHP binary
supplier imports are tested
backups have been restored successfully
staging migration has completed
checkout has been tested end to end
performance has been measured
rollback procedure is documented

PrestaShop 9 Checklist for Module Developers

Module developers should also review:

declared PrestaShop compatibility
PHP 8.x compatibility
Symfony 6.4 compatibility
service definitions
dependency injection
controller routes
removed or changed core behavior
front-office presenter changes
WebP/AVIF behavior
multistore context
CLI commands
upgrade scripts
package installation from a clean ZIP
static analysis
automated tests

Final Thoughts

PrestaShop 9 is important because it modernizes the foundation of the platform.

Symfony 6.4, modern PHP versions, the new Admin API, Hummingbird 2, native WebP and AVIF support, and continued architecture cleanup give developers and merchants a stronger base for future ecommerce projects.

The main mistake is to treat a major-version upgrade as a simple Back Office task.

For a real production store, the safest path is:

inventory → staging → compatibility testing → upgrade → regression testing → production migration → monitoring

Used this way, PrestaShop 9 is not merely a new version number. It is a more modern foundation for building, integrating, automating, and maintaining a PrestaShop store.

Frequently Asked Questions

What is the latest stable PrestaShop 9.1 version?

As of September 22, 2026, PrestaShop 9.1.5 is the latest stable release in the 9.1 branch.

Is PrestaShop 9.2 stable?

At the time this article was verified, PrestaShop 9.2 was in Release Candidate testing and had not yet reached its final stable release.

Which PHP version is recommended for PrestaShop 9?

The official compatibility table recommends PHP 8.4 for PrestaShop 9.0 and PHP 8.5 for PrestaShop 9.1.

Does PrestaShop 9 support PHP 8.5?

Yes. PrestaShop 9.1 supports PHP 8.5 and lists it as the recommended PHP version.

Which Symfony version does PrestaShop 9 use?

PrestaShop 9 is based on Symfony 6.4 LTS.

Does PrestaShop 9 support WebP?

Yes. Native WebP support was added in PrestaShop 9.

Does PrestaShop 9 support AVIF?

Yes. PrestaShop 9 also includes native support for AVIF images.

What is the PrestaShop 9 Admin API?

It is PrestaShop’s newer administration API architecture, built around API Platform and modern authentication and application patterns.

Is Hummingbird the default PrestaShop 9 theme?

Hummingbird was introduced with the PrestaShop 9 generation. Hummingbird 2.0 became the default theme for new PrestaShop 9.1 installations.

Should I upgrade directly from PrestaShop 8 to 9?

Use the officially supported upgrade process for your exact source version and test the migration on a staging copy first. Module, theme, PHP, and integration compatibility should be validated before production.

Official Sources

PrestaShop 9.0 release announcement
https://build.prestashop-project.org/news/2025/prestashop-9-0-available/
PrestaShop 9.1 release announcement
https://build.prestashop-project.org/news/2026/prestashop-9-1-0-available/
PrestaShop 9.1.5 security release
https://build.prestashop-project.org/news/2026/prestashop-9-1-5-security-release/
PrestaShop 9 system requirements
https://devdocs.prestashop-project.org/9/basics/installation/system-requirements/
PrestaShop project news / PrestaShop 9.2 release status
https://build.prestashop-project.org/news/

Related PrestaShop 9 guides and modules

Practical PrestaShop 9 troubleshooting and migration guides

Tags : Development, PrestaShop 9, Upgrade

Posted in: PrestaShop Updates & Upgrades