Laravel 13: What's New and Whether to Upgrade from Laravel 12

The short answer

Laravel 13 was released on March 17, 2026 and requires PHP 8.3 or newer. If you are on Laravel 12, the upgrade is usually small and worth doing this quarter, mostly because of the support calendar. If you are still on Laravel 11, you are already out of security support and the upgrade is no longer optional.

Support timeline

The dates below come from the official Laravel support policy: bug fixes for 18 months, security fixes for two years.

Two things follow from this. Laravel 11 is end of life. Laravel 12 stopped getting bug fixes in August and is now security only, which is fine for a while but means a non-security bug you hit will not be patched upstream.

What is new in Laravel 13

A first-party AI SDK

The headline change is the Laravel AI SDK (laravel/ai): one API for text generation, agents, embeddings, images, audio, transcription and vector stores, with providers including OpenAI, Anthropic and Gemini behind it. If you have been wiring AI features with hand-rolled HTTP clients or a third-party wrapper, this is the part that changes your architecture. I cover it with working code in Laravel AI SDK: build an agent with tools and semantic search.

Vector search in the query builder

Eloquent can now query vector columns directly with whereVectorSimilarTo(), backed by PostgreSQL and the pgvector extension. That makes semantic search a normal query instead of a separate service. If you are choosing a database for a new product, this tips the balance toward PostgreSQL for AI-heavy features; the trade-offs are in MySQL vs PostgreSQL for Laravel SaaS.

Smaller changes worth knowing

• PHP attributes are available as an optional alternative to class properties in many places in the framework. Nothing forces you to migrate existing code.
• JSON:API resources for APIs that follow the JSON:API specification.
• Queue routing to send jobs to the right connection and queue centrally.
• Cache::touch() to extend a cached item's lifetime without rewriting it.
• Stricter request forgery protection (CSRF), which is the change most likely to need a look in apps with unusual form or API setups.

Check the official release notes and upgrade guide for the exact list before you start; point releases keep adding to it.

Upgrade checklist

1. Check your PHP version. Laravel 13 needs 8.3 or newer. Moving PHP is often the bigger job, so do it first and ship it on its own.
2. Read the upgrade guide top to bottom and note anything that touches code you actually use.
3. Check your packages. Every first-party and third-party package needs a release that allows Laravel 13. Billing, admin panels and permissions packages are the usual blockers.
4. Bump the constraint to ^13.0, run composer update, and fix what breaks.
5. Run the test suite, then exercise the paths tests rarely cover: queues, scheduled commands, webhooks, mail, file uploads and anything that posts a form from another origin.
6. Deploy to staging, run it for a few days, then production, with the previous release one command away.

Most Laravel 12 applications upgrade with limited code changes. The time goes into PHP, packages and verification, not framework code.

Should you upgrade now?

• Yes, now: you are on Laravel 11, or you want to build AI features and would rather use the first-party SDK than maintain your own client.
• Soon: you are on Laravel 12 with a healthy test suite. Plan it into the next quiet sprint, and do it before the February 2027 security cut-off puts it under time pressure.
• Not yet: a key package has no Laravel 13 release, or the app has no tests and no staging. Fix that first; the upgrade will be easier afterwards.

Need a hand?

Upgrading a production Laravel app, or adding AI features to one? See Laravel development and AI integration, or email devusamaworks@gmail.com or WhatsApp +92 303 8004684 for a free 30-minute call.