How to tell which Magento version a store runs
Why the version matters
Every Magento release line gets security patches for about three years. After that date the store keeps working, but new holes are never fixed, and card skimmers and admin takeovers aim at exactly those stores.
The version also tells you what an upgrade will involve: the PHP version, the search engine and which extensions need new releases.
| Release line | Released | Security patches until |
|---|---|---|
| 2.4.9 | May 2026 | May 2029 |
| 2.4.8 | April 2025 | May 2028 |
| 2.4.7 | April 2024 | May 2027 |
| 2.4.6 | March 2023 | August 2026 (ended) |
| 2.4.5 | August 2022 | August 2025 (ended) |
| 2.4.4 | April 2022 | April 2025 (ended) |
| 2.3 | 2018 to 2021 | September 2022 (ended) |
| Magento 1 | 2008 | June 2020 (ended) |
Dates from Adobe's lifecycle policy, which Magento Open Source and Mage-OS follow. Adobe Commerce licence holders can buy extended support for some older lines.
Ways to check the version yourself
- Open /magento_version on the store. When it is not blocked it answers with the release line and edition, for example Magento/2.4 (Community).
- In the Magento admin, the exact version is printed at the bottom right of every page.
- On the server, run bin/magento --version in the store folder, or look for the Magento product package in composer.lock.
- From the outside, static file paths and init scripts give away Magento 2, and a missing RequireJS usually means a Hyvä theme. This is what the checker reads.
Hyvä or Luma?
Luma is the theme Magento ships with. It loads RequireJS, Knockout and a lot of JavaScript, which is why many Magento stores score low on mobile.
Hyvä replaces that front-end with Alpine.js and Tailwind CSS. Stores that move to Hyvä load far less JavaScript and pass Core Web Vitals more easily. The checker tells you which of the two a store uses and the theme folder name.
What to do with an old version
On 2.4.6 or older, plan an upgrade to 2.4.8 or 2.4.9. It brings a newer PHP and search engine, so test it on a staging copy first. On Magento 1 or 2.3 the store is years behind and every month adds risk: a migration to a current Magento 2 is the safe road.
Our Magento upgrade service does the work on a staging copy, tests checkout and extensions, and switches only when everything works.