Appearance
Supported Magento versions
When you create a store you choose which Magento version it runs. This page lists every version we support, which one you should pick, and what comes bundled with each.
Which version should I pick?
For a brand-new store, take the default — 2.4.9. It's the latest recommended release: newest features, longest runway before you need to upgrade. Most new stores never need to change this.
Pick an older version only if you're importing an existing store. An import needs a matching Magento version — a store on a newer version will reject data from an older one. So if the store you're moving in runs, say, 2.4.7-p3, create your new store on 2.4.7-p3 first, then import. See Migrating a store in from another host.
Supported versions and what comes with each
Every Magento version ships as a complete, managed bundle — the matching PHP, database (MariaDB), search engine (OpenSearch), cache (Valkey on versions that support it, otherwise Redis), full-page cache (Varnish), web server (nginx) and Composer are all set up and kept in step with your version for you. You don't install or manage any of it.
The optional column lists message brokers that are available on that version but off by default — they're started only if your store's configuration asks for one (see Advanced options when you create a store). The main reason to care about the rest of the table is extension compatibility — some extensions require a particular PHP version.
| Magento version | PHP | MariaDB | OpenSearch | Cache | Varnish | nginx | Composer | Optional (off by default) |
|---|---|---|---|---|---|---|---|---|
| 2.4.9 (recommended) | 8.4 | 11.4 | 3 | Valkey 8.1 | 8.0 | 1.30 | 2.10.3 | RabbitMQ 4.3, ActiveMQ Artemis 2 |
| 2.4.8-p5 | 8.4 | 11.4 | 3 | Valkey 8.1 | 8.0 | 1.30 | 2.10.3 | RabbitMQ 4.3, ActiveMQ Artemis 2 |
| 2.4.8-p4 | 8.4 | 11.4 | 3 | Valkey 8.1 | 8.0 | 1.30 | 2.10.3 | RabbitMQ 4.3, ActiveMQ Artemis 2 |
| 2.4.8-p3 | 8.4 | 11.4 | 3 | Valkey 8.1 | 8.0 | 1.30 | 2.10.3 | RabbitMQ 4.3, ActiveMQ Artemis 2 |
| 2.4.8-p2 | 8.4 | 11.4 | 3 | Valkey 8.1 | 8.0 | 1.30 | 2.10.3 | RabbitMQ 4.3 |
| 2.4.8-p1 | 8.4 | 11.4 | 2.19 | Valkey 8.1 | 7.7 | 1.26 | 2.9.3 | — |
| 2.4.8 | 8.4 | 11.4 | 2.19 | Valkey 8.1 | 7.7 | 1.26 | 2.9.3 | — |
| 2.4.7-p10 | 8.3 | 10.11 | 2.19 | Valkey 8.1 | 8.0 | 1.30 | 2.10.3 | RabbitMQ 4.3, ActiveMQ Artemis 2 |
| 2.4.7-p9 | 8.3 | 10.11 | 2.19 | Valkey 8.1 | 8.0 | 1.30 | 2.10.3 | RabbitMQ 4.3, ActiveMQ Artemis 2 |
| 2.4.7-p8 | 8.3 | 10.11 | 2.19 | Valkey 8.1 | 8.0 | 1.30 | 2.10.3 | RabbitMQ 4.3, ActiveMQ Artemis 2 |
| 2.4.7-p7 | 8.3 | 10.11 | 2.19 | Valkey 8.1 | 8.0 | 1.30 | 2.10.3 | RabbitMQ 4.3 |
| 2.4.7-p6 | 8.3 | 10.11 | 2.19 | Valkey 8.1 | 8.0 | 1.30 | 2.10.3 | RabbitMQ 4.3 |
| 2.4.7-p5 | 8.3 | 10.6 | 2.19 | Redis 7.2 | 7.7 | 1.28 | 2.9.3 | RabbitMQ 4.1 |
| 2.4.7-p4 | 8.3 | 10.6 | 2.12 | Redis 7.2 | 7.5 | 1.26 | 2.9.3 | — |
| 2.4.7-p3 | 8.3 | 10.6 | 2.12 | Redis 7.2 | 7.5 | 1.26 | 2.9.3 | — |
| 2.4.7-p2 | 8.3 | 10.6 | 2.12 | Redis 7.2 | 7.5 | 1.26 | 2.9.3 | — |
| 2.4.7-p1 | 8.3 | 10.6 | 2.12 | Redis 7.2 | 7.5 | 1.26 | 2.9.3 | — |
| 2.4.7 | 8.3 | 10.6 | 2.12 | Redis 7.2 | 7.5 | 1.26 | 2.9.3 | — |
| 2.4.6-p15 | 8.2 | 10.11 | 2.19 | Valkey 8.1 | 8.0 | 1.30 | 2.10.3 | RabbitMQ 4.3, ActiveMQ Artemis 2 |
| 2.4.6-p14 | 8.2 | 10.11 | 2.19 | Valkey 8.1 | 8.0 | 1.30 | 2.10.3 | RabbitMQ 4.3, ActiveMQ Artemis 2 |
| 2.4.6-p13 | 8.2 | 10.11 | 2.19 | Valkey 8.1 | 8.0 | 1.30 | 2.10.3 | RabbitMQ 4.3, ActiveMQ Artemis 2 |
| 2.4.6-p12 | 8.2 | 10.11 | 2.19 | Valkey 8.1 | 8.0 | 1.30 | 2.10.3 | RabbitMQ 4.3 |
| 2.4.6-p11 | 8.2 | 10.11 | 2.19 | Valkey 8.1 | 8.0 | 1.30 | 2.10.3 | RabbitMQ 4.3 |
| 2.4.6-p10 | 8.2 | 10.6 | 2.19 | Redis 7.2 | 7.7 | 1.28 | 2.9.3 | RabbitMQ 4.1 |
| 2.4.6-p9 | 8.2 | 10.6 | 2.12 | Redis 7.2 | 7.5 | 1.26 | 2.9.3 | — |
| 2.4.6-p8 | 8.2 | 10.6 | 2.12 | Redis 7.2 | 7.5 | 1.26 | 2.9.3 | — |
| 2.4.6-p7 | 8.2 | 10.6 | 2.12 | Redis 7.2 | 7.5 | 1.26 | 2.9.3 | — |
| 2.4.6-p6 | 8.2 | 10.6 | 2.12 | Redis 7.2 | 7.5 | 1.26 | 2.9.3 | — |
| 2.4.6-p5 | 8.2 | 10.6 | 2.12 | Redis 7.2 | 7.5 | 1.26 | 2.9.3 | — |
| 2.4.6-p4 | 8.2 | 10.6 | 2.5 | Redis 7.0 | 7.3 | 1.26 | 2.9.3 | — |
| 2.4.6-p3 | 8.2 | 10.6 | 2.5 | Redis 7.0 | 7.3 | 1.26 | 2.9.3 | — |
| 2.4.6-p2 | 8.2 | 10.6 | 2.5 | Redis 7.0 | 7.3 | 1.26 | 2.9.3 | — |
| 2.4.6-p1 | 8.2 | 10.6 | 2.5 | Redis 7.0 | 7.3 | 1.26 | 2.9.3 | — |
| 2.4.6 | 8.2 | 10.6 | 2.5 | Redis 7.0 | 7.3 | 1.26 | 2.9.3 | — |
| 2.4.5-p14 | 8.1 | 10.6 | 2.19 | Valkey 8.1 | 7.7 | 1.28 | 2.9.3 | RabbitMQ 4.1 |
| 2.4.5-p13 | 8.1 | 10.6 | 2.19 | Valkey 8.1 | 7.7 | 1.28 | 2.9.3 | RabbitMQ 4.1 |
| 2.4.5-p12 | 8.1 | 10.6 | 2.19 | Redis 7.2 | 7.7 | 1.28 | 2.9.3 | RabbitMQ 4.1 |
| 2.4.4-p13 | 8.1 | 10.6 | 2.19 | Redis 7.2 | 7.7 | 1.28 | 2.9.3 | — |
This table is generated from the same version data that drives the version picker when you create a store, so it always matches what you'll see there. The picker also lists the recent security patch levels within each line (for example 2.4.8, 2.4.8-p1, … 2.4.8-p4) so you can match the exact patch level of a store you're importing.
Older lines (2.4.4–2.4.6) are offered mainly to make imports possible — if you're starting fresh, there's no reason to choose them over the default.
Your version and your plan are independent
Your plan sets your store's size — CPU, memory, and disk. Your Magento version is a separate choice. Any plan can run any supported Magento version, and changing your plan later never changes your Magento version (or the reverse). Pick the version that fits your store and the plan that fits your traffic; the two don't constrain each other.
Moving to a newer version later
Choosing a version at creation doesn't lock you in for good. From your store's Maintenance tab, Update Magento moves your store to the next available version — a full backup is taken first so you can roll back, and it runs in your maintenance window. See Upgrading your Magento store.