How does Laravel 13 impact PHP version requirements and what version should I migrate to?

Laravel 13 raises the PHP requirement to 8.3 (dropping 8.2), and nudges developers toward newer Symfony 8 components, so you’ll want to upgrade your PHP runtime and dependencies before migrating. As nunomaduro explains, this shift is a core compatibility decision for Laravel 13, and it aligns with tightening security and performance expectations in the framework’s ecosystem. Laravel Daily confirms the 8.3 minimum and highlights that the upgrade flow has been designed to be smooth, with Boost upgrades triggered after npm install to detect newly installed packages. He also notes that Laravel AI SDK becomes officially stable with Laravel 13, signaling new AI-enabled workflows you can adopt as part of the upgrade. On the performance side, nunomaduro dives into Blaze, Laravel’s high-performance Blade compiler, showing real-world benchmarks where first- and second-run render times cluster around 100 ms and illustrate dramatic speedups over standard Blade rendering; memoization and compile-time folding can push gains even higher, especially for data-driven or dynamic content. Finally, Laravel Daily points out practical upgrade steps and the reduced surface area for breaking changes, meaning you can enable new features like semantic vector search (whereVector) without a wholesale rewrite in many starter-kit contexts, while keeping security and maintenance in focus.}

• act: nunomaduro points out that Laravel 13 drops PHP 8.2 support and requires at least PHP 8.3, with PHP 8.4 entering maintenance later, so upgrading the runtime is essential before migrating.
• act: Laravel Daily notes the upgrade flow changes, including Boost upgrades triggering after npm install and the AI SDK becoming stable with Laravel 13, signaling new tooling to plan for during the move.
• act: nunomaduro highlights Blaze as a high-performance Blade compiler with dramatic render-time improvements; memoization and folding can make Blaze three times faster in certain dynamic content scenarios, and you can toggle Blaze per component or apply it project-wide.
• act: Laravel Daily adds practical context about a smooth upgrade path with minimal breaking changes, plus the availability of semantic vector search (whereVector) for AI-enabled features, which helps justify the move to 13 for teams leveraging new capabilities.