Laravel 13 arrived in March 2026, and by November many teams are deciding whether to move. The release is described as a small upgrade in effort, yet it raises the minimum PHP version, and that one detail can decide your plan.
This Laravel 13 upgrade guide explains the support dates, the main new features and the checks that make an upgrade calm instead of risky. Everything below follows the official Laravel 13 release notes. It is written for business owners who depend on a Laravel application, as well as for the developers who maintain it.
| Laravel | Status in November 2026 |
|---|---|
| Laravel 11 | Security fixes ended on 12 March 2026 |
| Laravel 12 | Security fixes only, until 24 February 2027 |
| Laravel 13 | Current version, PHP 8.3 minimum, security fixes until 17 March 2028 |
Laravel 13 at a glance
Laravel 13 was released on 17 March 2026. The official support table lists PHP 8.3 to 8.5 as supported, and the release notes state that Laravel 13 requires PHP 8.3 as a minimum. The notes also say Laravel 13 has minimal breaking changes and is a relatively minor upgrade in effort.
Laravel’s policy is bug fixes for 18 months and security fixes for two years for every release. Here is the table from the official page for the three newest versions.
| Version | PHP | Released | Bug fixes until | Security fixes until |
|---|---|---|---|---|
| 11 | 8.2 to 8.4 | 12 March 2024 | 3 September 2025 | 12 March 2026 |
| 12 | 8.2 to 8.5 | 24 February 2025 | 13 August 2026 | 24 February 2027 |
| 13 | 8.3 to 8.5 | 17 March 2026 | Q3 2027 | 17 March 2028 |
Today is mid-November 2026. That means Laravel 11 no longer receives security fixes, Laravel 12 receives security fixes only and Laravel 13 is the current version with full support.
Why the version matters to a business
An unsupported framework version stops receiving security fixes. If your application runs Laravel 11, it should be on a plan to move. If it runs Laravel 12, you have time until February 2027 for security fixes, but you lose bug fixes already, so plan the move in the next few months rather than the next few years.
PHP matters just as much. Laravel 13 needs PHP 8.3 or later, and the October 2026 PHP security fixes only reach supported branches, which we explain in our PHP vulnerability guide. Our PHP 8.5 guide lists the support dates for each branch.
What is new in Laravel 13
The official notes list these headline features:
- Laravel AI SDK. A first-party, unified API for text generation, tool-calling agents, embeddings, audio, images and vector stores.
- JSON:API resources. First-party support for serialising responses in the JSON:API format, including relationships and sparse fields.
- Request forgery protection. The CSRF layer is formalised as
PreventRequestForgery, with origin-aware verification that still works with token-based protection. - Queue routing. You can route queued jobs by class with
Queue::route(...). - More PHP attributes. Attributes such as
#[Middleware],#[Authorize],#[Tries],#[Backoff]and#[Timeout]are supported across more of the framework. - Cache touch.
Cache::touch(...)extends a cache entry’s lifetime without storing the value again. - Vector search. A
whereVectorSimilarToquery for PostgreSQL with pgvector, plus helpers to create embeddings.
None of these forces you to change your application. They are choices you can adopt later.
What a Laravel 13 upgrade involves
Upgrades follow the same pattern whether the change is large or small.
1. Check the PHP version first
Find out which PHP version your server runs, both on the web and on the command line. If it is lower than 8.3, plan the server change before the framework change. Upgrading PHP is often the larger job, because it touches hosting, extensions and every package.
2. Read the official upgrade guide
The Laravel documentation includes an upgrade guide for each major version with a list of changes that might affect you. Read it with your developer and mark each item as relevant or not.
3. Audit packages
List every Composer package, check that its latest version supports Laravel 13 and replace anything that has been abandoned. A single old package is the most common reason an upgrade stalls.
4. Upgrade on a copy
Create a branch or a staging copy, update the framework and packages, run the tests and fix what breaks. If you have no automated tests, write a short checklist of the key journeys, such as sign-in, checkout, forms, emails and admin screens, and test them by hand.
5. Deploy with a way back
Take a backup and prepare a rollback before you deploy. Deploy at a quiet hour and watch the logs closely for the first day. Our backup strategy guide shows how to think about restore tests.
How long should it take
The official notes call this a minor upgrade in effort, but time depends on your application. A small, well-tested application may take a day or two. A larger one with many packages, custom code and no tests can take weeks. The honest answer comes from a short audit, not from a rule of thumb.
Should you adopt the AI SDK
Treat it like any new dependency. Decide the use case first, such as summarising support tickets or searching documents. Decide what data may leave your systems and who is allowed to see results. Read your vendor’s data terms, and keep a human in the loop for anything customer-facing. Our AI coding tools guide lists the checks we use for AI features in client projects.
Security habits to keep alongside the upgrade
Upgrading the framework does not fix an insecure application by itself. Keep dependencies updated, review who has server access and test your forms and logins. The OWASP Top 10 guide is a useful checklist for those reviews.
Questions to ask your Laravel developer
- Which Laravel and PHP versions do we run today, and when do they lose security fixes?
- Which packages block an upgrade, and what is the plan for each?
- Do we have automated tests, and what do they cover?
- What is the rollback plan if the release goes wrong?
- Which parts of Laravel 13 do you recommend we adopt, and which can wait?
Need help with a Laravel upgrade
Our Laravel development team can audit your version, packages and tests, and give you a clear plan with effort and risk. We tell you what we find, including when the right answer is to wait.
A sample upgrade timeline for a small application
A short plan helps you explain the work to colleagues and budget for it. In week one, audit the PHP version, the Laravel version, the packages and the tests. In week two, upgrade PHP on a staging server if needed, then update Laravel and the packages on a branch. In week three, fix what breaks, run the tests and check key journeys by hand.
In week four, deploy at a quiet hour with a backup and watch the logs. A very small application may need only a few days, while a large one may need longer, and the audit tells you which you have.
What to watch in your packages
Most upgrade delays come from packages, not from the framework. Look at each package’s repository and note when it was last updated, whether it lists Laravel 13 support and whether it has open security issues. If a package is abandoned, decide whether to replace it, fork it or remove the feature. Prefer packages with active maintainers and clear release notes. Run the dependency audit that comes with Composer, and read the output with your developer, because it lists known security advisories.
Hosting and deployment checks
Laravel 13 needs PHP 8.3 or later on the web server and on any command-line workers, such as queue workers and scheduled tasks. It is easy to upgrade the web side and forget the workers, which then fail quietly. Check the versions in every environment: local, staging, production and continuous integration. Confirm that the extensions your application needs are installed for the new PHP version, and that your host supports it. If you use a managed platform, read its notes on PHP version changes.
Planning for Laravel 14 and beyond
The official policy gives each release 18 months of bug fixes and two years of security fixes, so you can plan years ahead. At the time of writing, the Laravel team has not announced a date for Laravel 14 that we could confirm, so do not plan around a rumour.
A simple habit works well: review your framework and PHP versions every quarter, note the end-of-support dates in a shared calendar and budget a small upgrade every year instead of a large one every four years. Small, regular upgrades are cheaper and safer than rare, big ones.
What the AI SDK means for client projects
A first-party AI package lowers the effort of adding features like summaries, search and assistants, and it also lowers the effort of adding risk. Before anyone writes code, decide which data may be sent to an external provider, how long the provider keeps it and who reviews the outputs. Add rate limits and logging, and keep a manual fallback when the provider is unavailable. Treat the AI SDK as an optional extra, and upgrade the framework first, because the two decisions are independent.
Need a Laravel upgrade plan?
Our team audits your Laravel and PHP versions, packages and tests, and gives you a plan with effort and risk before any work starts.
Frequently Asked Questions
Is Laravel 13 a big upgrade?
The official release notes describe it as a relatively minor upgrade in effort, with minimal breaking changes. The larger job is usually the PHP 8.3 minimum.
Is Laravel 12 still supported?
According to the official table, Laravel 12 receives security fixes until 24 February 2027, and bug fixes ended on 13 August 2026.
Can I run Laravel 13 on PHP 8.2?
No. The release notes state a minimum of PHP 8.3, and the support table lists PHP 8.3 to 8.5.
Do I have to use the AI SDK?
No. It is a new first-party package you can adopt when you have a clear use case and a data policy.

