Same features, different deal with time
Late in 2025 Symfony released 7.4 and 8.0 at the same time. Both lines share the same features. 7.4 keeps the deprecation layer and gets LTS. 8.0 removes the old paths and lives a shorter support window, while keeping you closer to the next minors.
In 2026 the question is not which release looks newer. It is whether you want a calm three year fix window or a steady stream of features.
What Symfony 7.4 LTS actually buys you
7.4 needs PHP 8.2+. Bug fixes run through November 2028, security through November 2029. For teams with long release cycles and audits, that is often enough.
Along the way LTS also landed changes you feel in daily work:
- XML configuration is deprecated. YAML and PHP stay.
- Better JSON schemas for YAML (services, routing, validation, serialization), so the IDE catches typos earlier.
- UUID v7 as the default in the UUID component. Better index behavior when you insert a lot of rows.
- HTTP Client caching aligned with RFC 9111 when you call external APIs.
If you are still on 6.4 LTS, 7.4 is the natural migration target before 6.4 support ends.
When Symfony 8.x is the better bet
8.0 requires PHP 8.4+. It has none of the 7.4 deprecations, so a jump from a dirty 7.3 can hurt if you ignored notices earlier. You gain a shorter path to 8.1, 8.2, and beyond, without waiting for the next LTS in November 2027.
Choose 8.x when:
- the team ships upgrades every few months,
- you are already aiming at PHP 8.4 or 8.5,
- you want features from minors, not only security patches,
- you have green tests and budget to clean deprecations now, not “later”.
Deprecations worth fixing before the jump
XML is the loudest change. Bundles and older apps love services.xml and XML routing. Symfony has conversion helpers, but review file by file instead of merging a 400 file PR overnight.
The other classic is $request->get(). Explicit bags (query, request, attributes) are clearer and less magical. In a large codebase that means hundreds of small edits, so collect them on 7.3/7.4 instead of the night before an 8.0 cutover.
What to pick in Q3 2026
Greenfield app on PHP 8.4+: take 8.x if the team likes staying current. Enterprise product with rare releases: 7.4 LTS and a quiet path through 2028/2029. App stuck on 6.4: move to 7.4 with deprecations cleared first, then decide whether to jump to 8.x or stay on LTS.
Pick the version based on how often you deploy and what one big yearly upgrade costs your team.