Laravel 13: What’s New, and Is the PHP 8.3 Jump Worth It?

Still the biggest name in PHP, by a wide margin

Laravel remains the dominant framework in the PHP ecosystem in 2026, holding roughly 28% mindshare against Symfony’s 18% and Zend’s 17% – and PHP itself still quietly powers around three-quarters of websites running a known server-side language. None of that changed with Laravel 13, released in March 2026. What did change is worth walking through properly before you schedule the upgrade.

The headline change: PHP 8.3 is now the floor

Laravel 13 sets PHP 8.3 as its minimum supported version, dropping 8.1 and 8.2 support. If you’re still running an older PHP version in production, this is the forcing function – you can’t take the framework upgrade without the language upgrade first. Practically, that means:

• Audit your dependencies for PHP 8.3 compatibility before touching Laravel itself – third-party packages are the more likely blocker, not your own code.
• PHP 8.3’s typed class constants and the #[Override] attribute are worth adopting even outside Laravel-specific code, since they catch a real class of bugs (silently-non-overriding methods) at compile time instead of runtime.
• If you’re on shared or managed hosting, confirm PHP 8.3 availability before committing to a timeline – this is more often the actual bottleneck than the code changes.

Attributes over class properties

Laravel 13 leans further into PHP 8 attributes as the preferred way to configure components, rather than the array-based class properties that have been the convention for years. This isn’t just cosmetic – attribute-based configuration is more discoverable (IDEs and static analysis tools understand attributes natively) and keeps configuration next to the code it affects rather than in a separate property block. Existing array-property configuration still works, so this isn’t a breaking change – but new code and Laravel’s own documentation examples increasingly assume the attribute style, so it’s worth adopting for anything you write going forward.

Is it worth prioritising the upgrade?

A pragmatic framework for deciding:

• Upgrade soon if: you’re already on PHP 8.3+ (the framework change alone is low-risk), you want the attribute-based configuration for new modules, or you’re starting a genuinely new project (start on 13, don’t build fresh on an outgoing major version).
• Wait if: your PHP version is the real blocker and that upgrade touches infrastructure outside your immediate control (shared hosting, an ops team’s patch cycle), or you have a large legacy codebase with heavy use of patterns Laravel 13 has begun deprecating – budget a proper audit pass rather than a weekend upgrade.

What this fits into

Zooming out, Laravel’s 2026 trajectory is being described in “boring tech” terms deliberately – a framework doubling down on maturity and stability rather than chasing the churn seen elsewhere in web frameworks. Laravel 13’s changes fit that pattern: a language-version floor raise and a configuration style refinement, not a rewrite. If your team already trusts Laravel, this release gives you no real reason to reconsider that – just a PHP version to sort out first.