Symfony 4.4 or older, 5.0 to 5.3
No bug or security fixes
Move one major version at a time, clearing deprecations at each LTS step. It can be planned as a single project, and each step is a working release you could stop at.
4.45.46.47.4
Guide · dates checked 30 October 2026
Symfony 6.4 is winding down. Plan the move to 7.4.
Symfony 6.4 LTS stops getting bug fixes in November 2026 and security fixes in November 2027. The PHP versions many 6.4 apps run on are ending sooner: PHP 8.1 is already unsupported, and PHP 8.2 ends on 31 December 2026. Here are the dates, the requirements and the upgrade route for each version.
symfony_6.4: bug fixes end Nov 2026, security fixes end Nov 2027 symfony_7.4: LTS, bug fixes to Nov 2028, security to Nov 2029 symfony_5.4: security fixes only, extended to Feb 2029 symfony_8.x: a new minor every six months, each supported briefly php_8.2: security support ends 31 Dec 2026
November 2027Symfony 6.4 gets its last security fixes
Timeline
The dates that matter.
From Symfony's release pages and PHP's supported versions list. Symfony gives end dates by month. Long-term support (LTS) dates are fixed when a version is released, so they rarely move.
Symfony 5.4 bug fixes ended
Security fixes continue until February 2029, thanks to extended support funded by Ibexa.
PHP 8.1 end of life
The oldest PHP version Symfony 6.4 runs on no longer gets security fixes.
Symfony 8.0 end of support
8.0 users should already be on 8.1.
Symfony 6.4 bug fixes end. Symfony 8.2 due
From here 6.4 gets security fixes only. Symfony 8.2 is planned for the same month.
PHP 8.2 end of life
Security fixes for PHP 8.2 stop. Symfony 6.4 apps on PHP 8.2 need a newer PHP version even before they upgrade Symfony.
Symfony 8.1 end of support
8.1 users need to be on 8.2 by then.
Symfony 6.4 end of security fixes
The last Symfony 6 version stops getting security fixes. No extended support has been announced.
PHP 8.3 end of life
PHP 8.3 stops getting security fixes.
Symfony 7.4 bug fixes, then security fixes, end
The current LTS version is supported for three more years.
Where are you now?
Your upgrade path, by version.
Not sure which version you're on? Run php bin/console about, or look for symfony/framework-bundle in your composer.lock. Symfony upgrades one major version at a time, so older apps step through each LTS version on the way.
Symfony 5.4
Security fixes until February 2029, no bug fixes since November 2024
Security fixes continue thanks to Symfony's extended support, but bugs aren't fixed any more and third-party bundles keep dropping 5.4. Use the time to plan a two-step move to 7.4.
5.46.47.4
Symfony 6.0 to 6.3
No bug or security fixes
Update to 6.4 first. Within the same major version that's usually a small job. Then plan the move to 7.4.
6.x6.47.4
Symfony 6.4
Bug fixes end Nov 2026, security fixes end Nov 2027
You have time, but check PHP first: if you're on PHP 8.1 or 8.2, PHP runs out of support before Symfony does. Clear the deprecations 6.4 reports, then upgrade to 7.4, ideally well before November 2027.
6.47.4
Symfony 7.0 to 7.3
No bug or security fixes
Update to 7.4 LTS. It's a minor version upgrade, so usually quick, and it gives you support until 2029.
7.x7.4
Symfony 7.4
Bug fixes to Nov 2028, security to Nov 2029
You're on the current LTS version. Keep up with patch releases and clear deprecations as they appear, so the move to Symfony 8 is small when you're ready for it.
7.48.x later
Symfony 8.0 or 8.1
8.0 unsupported since July 2026, 8.1 ends January 2027
Symfony 8 versions aren't LTS, so you keep up with each new minor version. Move to 8.1 now if you're on 8.0, and to 8.2 when it's released in November 2026.
8.08.18.2
Requirements
Check your PHP version too.
Each Symfony version needs a minimum PHP version, and PHP versions have their own end-of-life dates. An app can be on a supported Symfony version and still run on unsupported PHP.
| Symfony 6.4 LTS | Symfony 7.4 LTS | Symfony 8.x | |
|---|---|---|---|
| Minimum PHP | 8.1 | 8.2 | 8.4 |
| Released | November 2023 | November 2025 | 8.0 November 2025, 8.1 May 2026, 8.2 planned November 2026 |
| Bug fixes until | November 2026 | November 2028 | About eight months per version |
| Security fixes until | November 2027 | November 2029 | 8.1 to January 2027, 8.2 to July 2027 |
| PHP version | Security fixes until |
|---|---|
| PHP 8.1 | Ended 31 December 2025 |
| PHP 8.2 | 31 December 2026 |
| PHP 8.3 | 31 December 2027 |
| PHP 8.4 | 31 December 2028 |
| PHP 8.5 | 31 December 2029 |
How I'd do it
Symfony 6.4 to 7.4, step by step.
Symfony removes nothing in a major version that wasn't flagged as deprecated in the version before. Most of the work happens on 6.4, while the app is still running in production.
Upgrade assessment
Composer dependencies, third-party bundles, the deprecation report, test coverage and PHP version reviewed. You get a written list of everything that has to change.
Get PHP onto a supported version
Move to PHP 8.3 or 8.4 on staging first. That's often the most urgent step, given PHP 8.1 and 8.2's end dates.
Clear the 6.4 deprecations
Every deprecation fixed, with Rector's Symfony rules doing the repetitive rewrites, until the test suite runs clean on 6.4.
Update third-party bundles
Bundles moved to versions that support Symfony 7, and abandoned ones replaced.
Upgrade to 7.4
Symfony packages moved to 7.4, Flex recipes updated, then a full test run, including the routes and integrations tests don't cover.
Release with a way back
Deployed through staging with a rollback plan, then monitored closely for the first days.
Questions
Frequently asked.
Do we have to upgrade Symfony 6.4 before November 2026?
No. Symfony 6.4 keeps getting security fixes until November 2027. After November 2026, though, bugs won't be fixed, and your PHP version may run out first: PHP 8.2's security support ends on 31 December 2026. Use 2027 to upgrade calmly rather than at the last minute.
Should we go to Symfony 7.4 or Symfony 8?
For most business applications, 7.4. It's the long-term support version, with security fixes until November 2029 and a minimum of PHP 8.2. Symfony 8 has the newest features, but each version is supported for a short time, so you'd upgrade roughly every six months, and it needs PHP 8.4. Code that runs cleanly on 7.4 with no deprecations is most of the way to Symfony 8.
Can we jump straight from Symfony 5.4 to 7.4?
Not in one step. Symfony upgrades one major version at a time: clear 5.4's deprecations, move to 6.4, clear 6.4's, then move to 7.4. It can still be one planned project, with a working release at each step.
Is there extended support for Symfony 6.4, like there is for Drupal 7?
None has been announced. Symfony 5.4's security support was extended to February 2029 with funding from Ibexa, and the fixes are public for everyone. If something similar is announced for 6.4, I'll update this page. Until then, plan to be on 7.4 before November 2027.
How long does an upgrade take?
It depends on the size of the codebase, how many third-party bundles it uses, how many deprecations it reports and how good the tests are. The upgrade assessment answers that for your app, with a fixed price for the work.
Symfony and PHP upgrades
Get a plan before support runs out.
Tell me which Symfony and PHP versions you're on. I'll come back with what has to change, the route to a supported version and a fixed price. The first conversation is free and comes with no obligation.
Sources
Symfony dates were checked on symfony.com and PHP dates on php.net on 30 October 2026.
- Symfony 6.4 release ↗ · 7.4 ↗ · 8.0 ↗ · 8.1 ↗ · 8.2 ↗
- Symfony 5.4 LTS will receive security fixes until February 2029 ↗
- PHP supported versions ↗
This page is general information, not a guarantee of Symfony's or PHP's schedule. Always check the dates on symfony.com and php.net before you plan around them.