Laravel version support
Which Laravel and PHP versions still get fixes, how to check your app, and what to upgrade first. Reviewed regularly.
Laravel support dates
Last reviewed 21 Oct 2026
Laravel ships a major release each year, around the first quarter. Each release gets 18 months of bug fixes and 2 years of security fixes. Once security support ends, nothing arrives at all.
| Laravel | PHP | Released | Bug fixes until | Security fixes until | Status |
|---|---|---|---|---|---|
| 10 | 8.1–8.3 | 14 Feb 2023 | 6 Aug 2024 | 4 Feb 2025 | End of life |
| 11 | 8.2–8.4 | 12 Mar 2024 | 3 Sep 2025 | 12 Mar 2026 | End of life |
| 12 | 8.2–8.5 | 24 Feb 2025 | 13 Aug 2026 | 24 Feb 2027 | Security fixes only |
| 13 | 8.3–8.5 | 17 Mar 2026 | Q3 2027 | 17 Mar 2028 | Supported |
Laravel 10
End of lifeLaravel 10 gets no fixes at all. Treat the upgrade as current work, not next-year work.
Laravel 11
End of lifeLaravel 11 gets no fixes at all. Treat the upgrade as current work, not next-year work.
Laravel 12
Security fixes onlyLaravel 12 gets security fixes only until 24 Feb 2027. Plan the upgrade to a supported release now.
Laravel 13
SupportedLaravel 13 gets bug and security fixes. Safe to run; schedule the next yearly upgrade before support narrows.
Laravel 13 needs PHP 8.3 or newer, so an app on older PHP has to move the language version first. Laravel 13 focused on minimal breaking changes, so most apps upgrade without changing much code.
PHP support dates
The framework is only half the story. PHP itself stops receiving security patches on fixed dates, and an unsupported PHP version leaves holes that no Laravel upgrade can close.
Check both numbers together. A supported framework on an unsupported language is still an unsupported app.
| PHP | Security fixes until | Status |
|---|---|---|
| 8.2 | 31 Dec 2026 | Security fixes only |
| 8.3 | 31 Dec 2027 | Security fixes only |
| 8.4 | 31 Dec 2028 | Supported |
| 8.5 | 31 Dec 2029 | Supported |
How to check your version
Ask your developer, or check these yourself if you have server access. Run this in the project directory for the framework version:
php artisan --version
Run this for the PHP version that serves the app:
php -v
Then open composer.json and read the php and laravel/framework requirements. The commands show what runs; these lines show what the app allows. Compare the results with the tables above.
Upgrade order
A safe upgrade follows the same order every time. Work through these steps and test after each one:
- Back up the app and the database, and confirm the backup restores.
- Bring the test suite to green on the current versions.
- Upgrade PHP first, to a version the target Laravel supports. For Laravel 13 that means PHP 8.3 or newer.
- Upgrade the framework next, one major version at a time, following each upgrade guide.
- Update packages after the framework lands, starting with Laravel first-party packages. Replace packages that no longer support your target versions.
- Deploy to staging and run the suite again with a manual pass over checkout, signup, and queued jobs. Ship to production only when staging holds.
What end of life means
- Disclosed bugs go unpatched. When a new advisory names your version, the fix ships only for supported releases.
- Packages drift away. Maintainers test against supported releases, and one day a package you depend on refuses to install on your stack.
- Hosting options narrow. Platforms ship current PHP and retire old builds, which can leave teams stuck on costly legacy images.
- Every later upgrade gets harder. A yearly upgrade takes days. A jump across three versions can take weeks.
On Laravel 11? Here is what to do now.
On a version past end of life? Upgrade it.
Our upgrade service moves your app to the current Laravel release, PHP included. Start with a free assessment: we read the codebase, list the blockers, and send a fixed written quote before work starts.