Skip to content
Framework

Symfony Releases

Track every Symfony release from latest stable to end-of-life. Version timelines, LTS strategy, PHP compatibility, and upgrade guidance for PHP teams.

Total Versions

Supported

Latest

Version Timeline

All tracked releases with lifecycle status and EOL dates.

Loading version data…

Lifecycle Timeline

Visual overview of active support and maintenance windows.

5.4 LTS
6.0
6.1
6.2
6.3
6.4 LTS
7.0
7.1
7.2
7.3
7.4 LTS
2022 2023 2024 2025 2026 2027 2028 2029 2030
Active
Maint
Active
Maint
Active
Maint
Active
Maint
Active
Active
Maint
Active
Maint
Active
Maint
Active
Maint
Active
Active
Maint
Active / LTS
Maintenance
Today

Upgrade Paths

Migration guidance between major versions — breaking changes, effort estimates, and tips.

5.4 LTS 6.0 Medium Difficulty
Est. 4-8 hours

Breaking Changes

  • PHP 8.1+ required
  • All deprecated code from 5.x removed
  • Return type declarations added throughout
  • Removed legacy security system
  • Event dispatcher changes

Migration Notes

Follow the standard path: upgrade to 5.4 LTS first, fix ALL deprecation warnings (they become errors in 6.0), then upgrade to 6.0. Use Rector with symfony-60 config to automate type declaration changes.

6.4 LTS 7.0 Medium Difficulty
Est. 4-8 hours

Breaking Changes

  • PHP 8.2+ required
  • All deprecated code from 6.x removed
  • Native type declarations enforced everywhere
  • Removed compatibility layers
  • Messenger component changes

Migration Notes

Same pattern: fix all 6.4 deprecation warnings first. 6.4 and 7.0 have identical features — 7.0 just removes backward compat. If your code runs on 6.4 with zero deprecation warnings, it runs on 7.0.

6.4 LTS 7.4 LTS Medium Difficulty
Est. 4-8 hours

Breaking Changes

  • All changes from 7.0 through 7.3
  • PHP 8.2+ required
  • Multiple minor feature additions (non-breaking in .4)

Migration Notes

LTS-to-LTS jump. Fix all 6.4 deprecations, then go straight to 7.4 (skipping intermediate versions). 7.4 LTS will be supported until November 2029. Best target for teams wanting long-term stability.

Version Risk Assessment

Evaluate risk factors before choosing a version for production.

Version EOL Risk CVE Risk Ecosystem Cloud Support Overall Recommended Action
Symfony 5.4 LTS High Low LTS Full High Security support ends Nov 2025 — plan upgrade to 6.4 or 7.x
Symfony 6.0-6.3 Critical Medium Unsupported Legacy Critical Past EOL — upgrade to 6.4 LTS
Symfony 6.4 LTS Low Low Active Full Low LTS until Nov 2027 — recommended stable target
Symfony 7.0-7.1 High Low Maintenance Full High Update to 7.2+
Symfony 7.2 Low Low Active Full Low Current stable

Risk combines EOL status, PHP version requirements, security patch availability, and Composer ecosystem support. Assessed as of March 2026.

Version Feature Comparison

Side-by-side feature differences across major versions.

Feature 5.4 LTS 6.4 LTS 7.0 7.2
PHP minimum 7.2 8.1 8.2 8.2
PHP maximum tested 8.1 8.3 8.3 8.4
Native types Partial Full Enforced Enforced
AssetMapper (no Node) No Stable Stable Stable
Messenger component Stable Enhanced Enhanced Enhanced
Security authenticator Legacy New system New system New system
Scheduler component No No No Stable
Webhook component No Experimental Stable Stable
Remote Event component No No Experimental Stable
Attribute-based config No Expanded Expanded Expanded
LTS until Nov 2025 Nov 2027 N/A N/A

Embed Badges

Add live Symfony status badges to your README, docs, or dashboard.

Health Status

Overall support health

Symfony Health Status
![Symfony Health Status](https://img.releaserun.com/badge/health/symfony.svg)

EOL Countdown

Next end-of-life date

Symfony EOL Countdown
![Symfony EOL Countdown](https://img.releaserun.com/badge/eol/symfony.svg)

Latest Version

Current stable release

Symfony Latest Version
![Symfony Latest Version](https://img.releaserun.com/badge/v/symfony.svg)

CVE Status

Known vulnerabilities

Symfony CVE Status
![Symfony CVE Status](https://img.releaserun.com/badge/cve/symfony.svg)

Frequently Asked Questions

Common questions about Symfony releases and lifecycle.

How long are Symfony versions supported?
Standard releases get 8 months of bug fixes + 14 months of security fixes (22 months total). LTS releases (every 2 years, ending in .4) get 3 years of bug fixes + 4 years of security fixes. Symfony 6.4 LTS is supported until November 2027.
How often does Symfony release new versions?
Symfony ships a minor release every 6 months (May and November). Major versions ship annually in November alongside the LTS release of the previous major. Patch releases ship as needed for security fixes.
What is the Symfony LTS strategy?
Every .4 release (5.4, 6.4, 7.4) is an LTS. The LTS release contains the same features as the next major version minus backward compatibility breaks. This means 6.4 LTS and 7.0 have the same features — 7.0 just removes deprecated code.
Is upgrading Symfony difficult?
Symfony has excellent upgrade tooling. The deprecation system warns you in N.x, removes in (N+1).0. The rector/symfony-upgrade set automates many changes. Upgrade to the LTS first, fix all deprecations, then jump to the next major.
Symfony vs Laravel: which should I choose?
Symfony is component-based, enterprise-oriented, and has longer support cycles. Laravel is opinionated, developer-friendly, and ships faster for typical web apps. Laravel uses many Symfony components under the hood. Choose Symfony for large enterprise teams wanting stability and flexibility. Choose Laravel for rapid development and convention over configuration.
What PHP version does Symfony require?
Symfony 7.x requires PHP 8.2+. Symfony 6.4 LTS requires PHP 8.1+. Each release specifies PHP constraints. Keep PHP current to avoid being stuck on an old Symfony version.

Related Tools