Key takeaways
- Laravel 13 was released in March 2026 and needs PHP 8.3 or newer.
- Laravel 12 security fixes end on 24 February 2027. Laravel 11 and older are already out of support.
- Upgrades from Laravel 12 are usually small. The cost grows with every version you skip.
- Packages and PHP versions cause more work than the framework itself.
Laravel 13 was released in March 2026. If your application runs on Laravel, you are probably wondering whether you need to upgrade, how risky it is and what it will cost. This guide answers those questions without assuming you are a developer.
Do you need to upgrade?
Laravel supports each major version for a fixed period: bug fixes for 18 months and security fixes for two years. After that, if a security flaw is found in the framework, your version will not be patched.
As of October 2026:
| Version | Status | Security fixes until |
|---|---|---|
| Laravel 13 | Fully supported | 17 March 2028 |
| Laravel 12 | Security fixes only | 24 February 2027 |
| Laravel 11 | End of life | Ended 12 March 2026 |
| Laravel 10 and older | End of life | Ended |
So:
- On Laravel 12? You have until February 2027. Plan the upgrade for the next few months, while it is still a small job.
- On Laravel 11 or older? Your framework no longer gets security fixes. Upgrading should be a priority.
- On Laravel 5, 6 or 7? You are several years out of support, and probably on an unsupported PHP version too. This is a bigger project, but a very common one.
Our Laravel version support tracker has the full list of dates.
What Laravel 13 requires
The most important requirement is PHP 8.3 or newer. If your servers run PHP 8.2 or older, they will need upgrading as part of the project. Laravel 13 supports PHP 8.3, 8.4 and 8.5.
Laravel 13 itself has relatively few breaking changes. Most applications on Laravel 12 can move across with modest effort, as long as their packages support the new version.
What usually causes the work
In our experience, the framework is rarely the hard part. The work comes from everything around it.
Packages. Every third-party package in your application must support Laravel 13. Popular, well-maintained packages usually update quickly. Abandoned packages do not, and need replacing or rewriting.
PHP versions. Jumping several PHP versions at once can surface deprecated functions and changed behaviour in your own code.
Missing tests. Without automated tests, the only way to know whether the upgrade broke something is to check every feature by hand. We usually add basic tests for the most important paths before upgrading.
Skipped versions. Laravel has to be upgraded one major version at a time, because each step has its own changes. Going from Laravel 8 to 13 means five upgrades in a row, each one tested.
How long does it take?
As a rough guide, for a typical business application:
- Laravel 12 to 13, well tested, few packages: often a day or two.
- Laravel 10 or 11 to 13: usually a few days.
- Laravel 5.x to 8 to 13: typically one to two weeks, mostly because of packages and PHP.
Large applications, unusual packages and very thin test coverage all add time.
What does it cost?
Our core framework upgrades start at £195 per codebase, excluding VAT. A short assessment of your code, packages and tests gives you a fixed quote before work starts. Work on bespoke or abandoned packages is quoted separately, so there are no surprises. See our Laravel upgrade service for details.
How a safe upgrade works
- Assess. Review the current version, PHP version, packages and test coverage, and list the risks.
- Prepare. Add tests for critical paths and make sure staging matches production.
- Upgrade step by step. One major version at a time, following the official upgrade guides, with tests run at every step. Automated tools such as Rector, and AI coding agents, handle much of the repetitive editing, with an engineer reviewing every change.
- Upgrade PHP on staging, then production.
- Check on staging. You test the key features yourself.
- Release at a quiet time, with a rollback plan ready.
Is it worth it if everything works?
Usually, yes. Beyond security fixes, staying current means packages keep working, developers are easier to find and future upgrades stay small. Our Laravel upgrade planner shows every step from your current version, with notes on what changes along the way.
Once you are on Laravel 13, a support and maintenance plan keeps you current, so you never face a big catch-up again.