With the release of Shopware 6.7.7 in February 2026, full PHP 8.5 compatibility has been officially confirmed. PHP 8.5 introduces property hooks, the pipe operator, asymmetric visibility, and a fundamentally redesigned JIT compiler - features that enable modern code while delivering measurable performance benefits for your Shopware shop. In this guide, you will learn how to carry out the migration safely, what benchmarks to expect, and what to watch out for with plugins. Also facing a version or platform switch? See our Shopware migration page.
PHP 8.5: Key New Features at a Glance
PHP 8.5 was released in November 2025 and marks a significant leap in language development. PHP runs on 70.2% of all websites whose server-side programming language is known (W3Techs). The PHP Foundation has delivered several long-awaited features with this release that improve both the developer experience and runtime performance. For e-commerce applications like Shopware, the JIT improvements and more efficient memory management are particularly relevant.
Property Hooks
Define getters and setters directly in the property declaration - less boilerplate code with the same functionality
Asymmetric Visibility
Properties can have different visibility for reading and writing - cleaner API designs
Pipe Operator |>
Chain function calls as readable pipelines instead of nested function calls
JIT Compiler 3.0
Fundamentally redesigned just-in-time compiler with significantly improved type inference
Optimized Memory Management
Improved garbage collector and more efficient array implementation reduce memory footprint
New Standard Library Functions
array_any(), array_all() and more helper functions for more expressive code
Performance Benchmarks: PHP 8.5 vs. 8.3 vs. 8.1
The performance differences between PHP versions are noticeable for Shopware shops, but how large they turn out depends on the individual shop: the number of products and variants, the state of the plugins, the hardware and the caching setup. External benchmarks therefore indicate a direction, not a promise for your shop. Only a measurement on your own machine is dependable - recorded before the migration and repeated afterwards under identical conditions. The table below names the measurement points that have proven useful.
| Metric | Measured with | Before the migration | After the migration |
|---|---|---|---|
| Requests/s (product listing) | Load test with a fixed scenario | record a baseline per page type | same scenario, same load |
| TTFB homepage | Server response time in the field | baseline across a full week | compare the same time span |
| Memory per worker | PHP-FPM status page | note the peak under load | peak under load again |
| Checkout throughput | Load test up to order confirmation | baseline with real carts | same cart, same payment method |
| Import of large catalogues | Runtime of the import command | runtime of the same data set | same data set, same machine |
| Opcache warmup | Opcache statistics after a restart | time to a full hit rate | same measurement after the switch |
The most significant improvements appear in compute-intensive operations such as product imports, price calculations, and OpenSearch indexing. Shops with many product variants — especially multistore setups — benefit disproportionately from the improved JIT compiler.
Higher throughput on product listings means in practice: your hosting server serves more concurrent visitors on the same hardware. That pushes back the point at which a more expensive server package becomes necessary, while simultaneously improving Core Web Vitals, which Google uses as a ranking factor. The combination of faster page delivery and lower memory consumption makes PHP 8.5 the recommended runtime for Shopware 6 in 2026.
Shopware 6.7.7 and PHP 8.5 Compatibility
Shopware introduced official PHP 8.5 support with version 6.7.7 (February 2026). The core team has verified all internal classes for compatibility, replaced deprecated functions, and extended the test suite for PHP 8.5. For shop operators, this means: the core of the shop system is ready - the challenge lies in plugins and custom code.
- Shopware core: Full PHP 8.5 compatibility from version 6.7.7
- Symfony 7.2 support: Updated framework foundation
- Doctrine DBAL 4.x: Database abstraction optimized for PHP 8.5
- Twig 4.0: Template engine with improved performance
- PHPUnit 11: Test framework for modern PHP features
Important to note: Shopware 6.6.x and older versions do not support PHP 8.5. If your shop still runs on an older Shopware version, a Shopware update is required first before the PHP migration can proceed.
Migration Path: Step by Step to PHP 8.5
A successful PHP migration requires systematic planning. The following migration path has proven effective in practice and minimizes the risk of downtime. In our experience, a well-prepared migration for a typical Shopware shop takes 2-4 weeks - from analysis to production deployment.
- Inventory: Document current PHP version, Shopware version, and all installed plugins
- Update Shopware: Ensure at least Shopware 6.7.7 is installed
- Compatibility analysis: Run PHPStan and Rector against the codebase to identify incompatibilities
- Plugin check: Verify all plugins for PHP 8.5 compatibility (details in the next section)
- Staging environment: Install PHP 8.5 on a test server and deploy the shop there
- Automated tests: Run the entire test suite on the staging environment
- Manual tests: Manually test checkout, payment processes, and critical business workflows
- Performance baseline: Measure and compare benchmarks on old and new versions
- Production migration: Activate PHP 8.5 on the live server, ideally outside peak hours
- Monitoring: Closely monitor error logs and performance metrics for the first 48 hours
If your shop still runs on PHP 8.1, we recommend the intermediate step via PHP 8.3. This allows deprecated functions to be replaced incrementally rather than handling all changes at once.
Common Pitfalls with Deprecated PHP Functions
PHP 8.5 has permanently removed or marked as deprecated several functions and behaviors commonly found in older Shopware code and plugins. The following overview highlights the most relevant changes for Shopware developers:
// REMOVED: utf8_encode() / utf8_decode()
// Old:
$encoded = utf8_encode($string);
// New:
$encoded = mb_convert_encoding($string, 'UTF-8', 'ISO-8859-1');
// DEPRECATED: implicit nullable parameters
// Old:
function setName(string $name = null) { }
// New:
function setName(?string $name = null) { }
// REMOVED: ${} string interpolation
// Old:
$text = "Product ${name} costs ${price}";
// New:
$text = "Product {$name} costs {$price}"; The change to implicitly nullable parameters is particularly impactful, as this pattern was widely used across many Shopware plugins. Tools like Rector can automate most of these adjustments. For custom plugin development, we recommend a professional code review to identify subtle compatibility issues early on.
Checking and Ensuring Plugin Compatibility
Plugins are typically the most critical aspect of a PHP migration. While the Shopware core is officially tested, PHP 8.5 readiness among third-party plugins varies considerably. A systematic check is essential to prevent production issues.
- Composer check:
composer why-not php 8.5shows all packages with incompatible PHP constraints - PHPStan Level 8: Static analysis with
--php-version=80500reveals type errors and deprecated calls - Rector audit:
rector process --dry-runshows required code changes without executing them - Plugin Store check: PHP compatibility has been available as a filter in the Shopware Store since January 2026
- Contact vendors: For business-critical plugins, ask vendors directly about their PHP 8.5 timeline
Whether an extension runs under PHP 8.5 is decided plugin by plugin and cannot be quantified across the board. Actively maintained extensions tend to follow soon after a PHP release; older and unmaintained ones often never do. For a plugin that does not follow, there are three options: wait for an update, adapt the code yourself, or replace the plugin with a compatible alternative. For custom-developed plugins, we handle the PHP 8.5 adaptation as part of the migration.
Server Configuration for Maximum PHP 8.5 Performance
PHP 8.5 alone brings performance benefits, but the right server configuration makes the decisive difference. The following settings are optimized for Shopware 6 on PHP 8.5 and should be adjusted in the php.ini or pool configuration.
; OPcache configuration for PHP 8.5
opcache.enable=1
opcache.memory_consumption=256
opcache.max_accelerated_files=20000
opcache.validate_timestamps=0
opcache.jit=tracing
opcache.jit_buffer_size=256M
; Memory and limits
memory_limit=512M
max_execution_time=60
upload_max_filesize=32M
post_max_size=32M
; Realpath cache (important for Symfony)
realpath_cache_size=4096K
realpath_cache_ttl=600 For Shopware 6, we recommend the tracing JIT compiler mode. It analyzes the actual execution path and optimizes hot paths - ideal for complex e-commerce business logic. The function mode is better suited for CLI scripts like imports and cron jobs.
Beyond PHP configuration, web server setup also plays a role. Nginx with PHP-FPM and a dedicated worker pool for Shopware, combined with a CDN and HTTP/3, delivers the best results. Our hosting solutions are already optimized for PHP 8.5 and Shopware 6.
Property Hooks and Pipe Operator in Practice
Beyond performance improvements, PHP 8.5 introduces language features that make daily development work significantly more productive. Property hooks replace repetitive getter/setter methods, and the pipe operator makes nested function calls readable.
// PHP 8.5: Property hooks replace getters/setters
class Product {
public string $name {
set(string $value) => $this->name = trim($value);
}
public int $price {
get => $this->price;
set(int $value) {
if ($value < 0) throw new \InvalidArgumentException();
$this->price = $value;
}
}
}
// PHP 8.5: Pipe operator for readable pipelines
$result = $input
|> htmlspecialchars(...)
|> strtolower(...)
|> trim(...); For Shopware plugins, these features mean: less code with the same functionality, better maintainability, and fewer error sources. Asymmetric visibility (public private(set)) also enables cleaner API designs where properties can be read externally but only set internally - ideal for entity classes in Shopware.
Impact on SEO and Core Web Vitals
PHP performance directly impacts search engine optimization. Since 2021, Google has evaluated Core Web Vitals as a ranking factor, where Largest Contentful Paint (LCP) and Time to First Byte (TTFB) are heavily influenced by server-side processing speed. A shorter TTFB moves the starting point for everything that loads afterwards - LCP only benefits from it if images and fonts do not slow things down in turn.
The effect on conversion has been measured: a mere 0.1 second faster mobile load time lifted retail conversions by 8.4% and average order value by 9.2% (Google/Deloitte). How much of that reaches your shop is something only your own measurement before and after the migration will show. The PHP 8.5 migration is therefore not just a technical upgrade but an investment in your e-commerce success.
Record a baseline before the migration: Lighthouse performance, TTFB and memory usage under load, per page type. Without that baseline you cannot tell afterwards what the switch delivered and what came from a caching setting changed along the way.
Migration Checklist for Shop Operators
The following checklist summarizes all steps to be carried out before, during, and after the PHP 8.5 migration. Use this list as the basis for your planning - or contact us to have us handle the migration professionally.
- Database, files, and configuration backup created
- Shopware updated to version 6.7.7 or higher
- All plugins checked for PHP 8.5 compatibility (composer why-not, PHPStan)
- Staging environment with PHP 8.5 set up and tested
- Deprecated functions in custom code replaced
- OPcache and JIT configuration optimized for PHP 8.5
- Checkout and payment processes manually tested on staging
- Performance benchmark measured before and after migration
- Rollback plan documented (PHP version can be switched back quickly)
- Error monitoring set up for the first 48 hours after go-live
This is what your electronics shop could look like:
Elektronik-Fachhandel
For official PHP 8.5 support, you need at least Shopware 6.7.7, released in February 2026. Older Shopware versions such as 6.6.x or 6.5.x do not support PHP 8.5 and must be updated first. Contact us for an assessment of your update effort.
That cannot be quantified in general. How large the difference turns out depends on your shop configuration, product count, installed plugins and hardware. Only your own comparison is dependable: the same load, the same machine, once before and once after the switch.
Not automatically. Whether a plugin runs is decided plugin by plugin: actively maintained extensions usually follow soon after a PHP release, older ones often never do. We recommend performing a systematic compatibility check using Composer, PHPStan, and Rector before the migration and contacting vendors for critical plugins.
A well-prepared migration typically takes 2-4 weeks - from analysis through staging to production deployment. Shops with many custom plugins or proprietary code tend to need more time for compatibility adjustments. The actual server switch itself can be completed within minutes.
A rollback to the previous PHP version is typically possible within minutes and requires no code changes. We recommend preparing a documented rollback plan and performing the migration outside peak business hours. For our hosting clients, we monitor the migration and can intervene immediately if needed.
The PHP 8.5 migration is worthwhile for shops of any size. Smaller shops benefit primarily from lower memory consumption, which enables more affordable hosting plans, and from faster load times that improve SEO rankings. Additionally, PHP 8.1 will only receive security updates until November 2026 - a migration will become necessary regardless.
This article draws on php.net (PHP 8.5 release date), W3Techs (PHP usage share) and Google/Deloitte (effect of mobile load time on conversion and order value). The measurement points named in the text are instructions for your own measurement, not a promise: what a migration delivers for you depends on server configuration and shop setup and only shows in a before-and-after comparison on your own machine.