What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Laravel 13 requires PHP 8.3 or later. Released on March 17, 2026, it adds a first-party AI SDK, JSON:API resources, semantic and vector-search capabilities, and expanded PHP attributes. If you are moving from Laravel 12, plan for a code-and-configuration review: the framework team estimates 10 minutes for the upgrade, but the actual effort depends on your application and dependencies.
What Laravel 13 changes
Laravel describes this release as focused on AI-native workflows, stronger defaults, and more expressive developer APIs. The headline features are framework capabilities—not bundled model access, vector databases, or free AI usage.
As an Amazon Associate I earn from qualifying purchases.
AI SDK
The first-party AI SDK provides a unified API surface for text generation, tool-calling agents, embeddings, audio, images, and integrations with vector stores. You still need to select and configure providers or services for the capabilities you use; the release notes do not say that provider access or usage is included.
Free tools Windows power users keep installed
One-click scans. No signup required.
API resources and search
Laravel 13 adds JSON:API resources and semantic/vector-search capabilities. These provide framework-level ways to build API representations and search workflows; they do not remove the need to choose, configure, and operate any external services your application requires.
#1 Best Overall
Expanded PHP attributes
PHP attributes are available in more framework areas, including controller middleware and authorization, as well as queue controls. This gives developers another way to express framework configuration in code. Check the Laravel 13 documentation for the specific attribute and supported options before changing an application.
PHP requirement and support dates
Laravel 13 requires PHP 8.3 or later. Laravel’s release notes list March 17, 2026 as the release date, bug fixes through Q3 2027, and security fixes through March 17, 2028. These dates are Laravel’s published support schedule for the release.
Rank #2
For deployment, the official guide also lists required PHP extensions alongside the PHP version requirement. Verify that both the PHP runtime and extensions are available in your local, CI, and production environments before upgrading. Laravel’s deployment documentation identifies Laravel Cloud and Forge as managed deployment options.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteLaravel 12 vs. Laravel 13: what to weigh
| Area | Laravel 12 | Laravel 13 |
|---|---|---|
| Minimum PHP version | Not stated in the cited Laravel 13 release and upgrade guides. | PHP 8.3 or later. |
| Highlighted capabilities | The cited Laravel 13 release notes do not specify Laravel 12 feature equivalents. | First-party AI SDK, JSON:API resources, semantic/vector search, and expanded PHP attributes. |
| Upgrade starting point | The documented upgrade guide covers moving from Laravel 12.x. | Review the Laravel 13 upgrade guide and application-specific breaking changes. |
| Laravel 13 support schedule | The cited Laravel 13 release notes do not state Laravel 12’s support dates. | Bug fixes through Q3 2027; security fixes through March 17, 2028. |
The decision is not just about new features. Check whether your hosting runtime can meet PHP 8.3, whether your dependencies support the target framework, and whether the new security and serialization defaults fit your application.
Upgrade from Laravel 12
Laravel’s documented path is from Laravel 12.x. Its upgrade guide marks the dependency update as high impact and gives 10 minutes as an estimate. Treat that as the framework team’s estimate for the documented update, not a promise about testing, debugging, or deployment time for your project.
- Check runtime and dependencies. Confirm PHP 8.3 or later is available in every environment. Update the framework and, as applicable, Boost, Tinker, PHPUnit, and Pest according to the Laravel 13 upgrade guide.
- Review breaking changes by impact. Use the upgrade guide’s impact classifications to identify changes that apply to your code, tests, database, and deployment setup. Do not assume that a low-impact item is irrelevant if your application uses the affected behavior.
- Update CSRF middleware references. Replace direct references to
VerifyCsrfTokenorValidateCsrfTokenwithPreventRequestForgery, including references in route or test middleware exclusions. The older names remain deprecated aliases, but direct references should be updated. - Inspect cache and session serialization. Check whether your application caches PHP objects or relies on existing session data, then apply the checks in the next section.
- Run application and deployment checks. Test the routes, middleware, queues, database operations, authentication, and deployment process your application uses. Confirm production PHP and required extensions meet the deployment guide’s requirements.
Security-sensitive changes to check
Request-forgery protection and request origin
Laravel 13 renames the CSRF middleware to PreventRequestForgery and adds request-origin verification using the Sec-Fetch-Site header. Update direct middleware references and test the request flows your application relies on, especially where browsers, clients, or proxies may affect request headers.
Rank #4
Cache allow-list
The new Laravel 13 application skeleton sets serializable_classes to false. If your application intentionally stores PHP objects in the cache, explicitly allow the classes it needs or change the cached payloads to non-object data. Review what is actually serialized rather than broadly allowing classes without a reason.
Session serialization
The new skeleton uses JSON session serialization to reduce deserialization risks. Switching an existing application from PHP serialization can invalidate active sessions, so users may need to authenticate again. Account for that effect when planning the configuration change and deployment.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Other compatibility checks
Several upgrade-guide changes matter only when your application uses the affected behavior. Search for these patterns and test the relevant code paths:
- MySQL and MariaDB upserts: ensure
uniqueByis non-empty. - MySQL joined deletes: review queries that combine joins with ordering or limits because their behavior changed.
- Model booting: check code that depends on model instantiation during the booting process.
- Custom pivot models: verify inferred polymorphic pivot names where custom pivots are involved.
- Collection serialization: test serialization of collections with eager-loaded relations, whose restoration behavior changed.
- Laravel installer: account for the installer compatibility update in the tools or setup workflow your team uses.
What has changed within the 13.x line
Laravel’s changelog shows that 13.x continued to evolve after launch. Its September 2026 entries describe semantic and hybrid Typesense search in Scout, plus improvements to MariaDB vector queries and an Eloquent vector cast. These are dated 13.x updates, not features to attribute to the initial March 2026 release.
Deployment and installation
Before deploying, check the Laravel deployment guide for the current PHP extension list and deployment requirements. For a new project or a local setup, follow the official Laravel installation guide. Keep the PHP version consistent across development, continuous integration, and production so version-specific failures do not appear only after release.
Recommended Free Tools
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
