Weave Code
Breeze Laravel Package
laravel/breeze
Laravel Breeze is a minimal starter kit that scaffolds authentication and a clean UI with Blade, Vue, or React, including login, registration, password reset, email verification, and profile pages to speed up new Laravel apps. Supports Laravel 11.x and prior.
Laravel Breeze is a minimal, opinionated starter kit that scaffolds authentication for Laravel 11.x and prior. It provides ready-to-use login, registration, password reset, email verification, and profile management, with simple Blade/Tailwind views or frontend stacks via Inertia.
- Blade + Tailwind CSS views for quick customization
- React or Vue frontends powered by Inertia
- API authentication using Laravel Sanctum
- Built-in profile management and password updates
- Lightweight structure ideal for learning or small apps
For the latest starter kits, see laravel.com/starter-kits.
Frequently asked questions about Breeze
- How do I install Laravel Breeze?
- Install it as a dev dependency with composer require laravel/breeze --dev, then run php artisan breeze:install and choose a stack such as blade, livewire, react, vue, or api. The installer copies routes, controllers, views or Inertia pages, Tailwind and Vite config, and tests into your application. Finish with npm install, npm run dev, and php artisan migrate.
- Which frontend stacks can I choose with Laravel Breeze?
- Breeze offers Blade with Tailwind, Livewire with Blade, React via Inertia, Vue via Inertia, and an API stack backed by Sanctum. Installer flags cover variants such as --typescript, --ssr, --pest, --dark, --eslint, and --prettier. Pick the stack your team can actually maintain, because the generated frontend becomes your application code.
- Does Laravel Breeze support Laravel 12 and Laravel 13?
- The README states Breeze is for Laravel 11.x and prior and points to laravel.com/starter-kits for the latest kits. The changelog still shows compatibility work for Laravel 12 and 13, so it is maintained but no longer the flagship onboarding path. For a new 2025+ build, compare Breeze against the current laravel starter kits before committing.
- What is the difference between Laravel Breeze, Jetstream, and Fortify?
- Breeze is a minimal, first-party authentication scaffold you install once and then own. Jetstream is a larger starter kit with teams, two-factor authentication, and profile management built on Fortify. Fortify is a headless authentication backend you can add when you need features like 2FA or password policies without Breeze's view scaffolding.
- Does Laravel Breeze include two-factor authentication, teams, or roles?
- No. Breeze covers login, registration, password reset, email verification, and password confirmation only. There is no two-factor authentication, no teams or organizations, no roles or permissions, no audit trail, and no admin surface. If any of those are table stakes, decide between building them or using Fortify or Jetstream before you scaffold.
- Is Laravel Breeze suitable for production applications?
- Breeze is a dev-time scaffolding tool, not a runtime dependency, so the generated authentication code becomes application code you own. That means password reset, email verification, session regeneration, and login throttling are files you must review, test, and patch yourself. It is production-ready as a starting point, but only if you treat the output as your responsibility and add the policies your app needs.
- Can I use Laravel Breeze for a headless API or SPA?
- The api stack scaffolds Sanctum token authentication for first-party clients, which works for simple headless or SPA use cases. It does not give you an OAuth2 authorization server, SSO, or an identity provider. If authentication is centralized in an identity provider, Breeze is the wrong starting point.
- How do I customize Laravel Breeze views and Tailwind styling?
- Breeze copies Blade views into resources/views or Inertia pages into resources/js/Pages, plus Tailwind and Vite config, and those files are yours to edit directly. Re-running the installer can overwrite customizations, so commit before re-scaffolding. Use the --dark, --typescript, and --ssr flags at install time to reduce manual rework.
- How do I run the authentication tests included with Breeze?
- The installer publishes feature tests for the authentication flows under tests/Feature/Auth, using Pest by default if you pass --pest or your app's existing test setup. Run them with php artisan test. Treat these as a baseline and extend them when you change controllers, form requests, or throttling.
- How do I get security updates or upgrade Laravel Breeze later?
- There is no composer update path for the generated authentication code, because Breeze copies files into your application rather than shipping runtime classes. Upstream security fixes reach you by manually re-diffing the stubs or re-scaffolding and merging changes. Keep the generated authentication code under review and track Breeze releases so you know when stubs change.
Weaver
How can I help you explore Laravel packages today?