Filament upgrade path to Laravel 13: v2, v3, v4, v5

Read from Packagist on 2026-10-30. The Laravel constraint sits on filament/support, which the main package requires. A constraint means Composer will install the pair, not that every feature has been tested on it. The wider picture is in our package compatibility matrix.

If you’re on Filament 3

1. Upgrade Laravel to 13, keeping Filament 3. Our 12 to 13 guide covers the framework.
2. Release and let it settle.
3. Upgrade to Filament 4 as its own project, then to 5 if you need it.

Don’t feel you must rush past Filament 3. Its latest release is recent, and the framework move is the part with a deadline. Laravel 12’s security fixes end soon, whereas this is your own schedule. Check on Filament’s site how long version 3 will keep receiving fixes before you settle on a date.

If you’re on Filament 2

1. Upgrade Laravel to at least 10.45, which Filament 3 needs, keeping Filament 2. Our guide to old Laravel versions covers the steps.
2. Upgrade Filament to 3, which also moves you from Livewire 2 to Livewire 3.
3. Then carry on as above.

Each major has its own guide and script, which is the place to start. Run them on a clean branch and review the diff.

# Example: Filament 3 to 4
composer require filament/upgrade:"^4.0" -W --dev
vendor/bin/filament-v4
# Follow the remaining steps in Filament's guide, then:
composer remove filament/upgrade --dev

On 2 to 3, Filament’s guide has an instruction worth repeating: upgrade Filament before you upgrade to Livewire 3.

The Filament 4 guide lists behaviour changes that can pass without an error. These are the ones we’d test by hand:

• File uploads. Uploads on non-local disks, such as S3, now default to private visibility. Images that used to load from a public URL may stop displaying.
• Table filters. Filters are deferred by default, so users click a button to apply them. It isn’t a bug, but they’ll notice. Decide whether to keep it, and tell them if so.
• Unique validation. unique() now ignores the current record by default. Check any form where you’d set this up yourself.
• Layout. Grid, Section and Fieldset now span one column by default rather than the full width, so forms can look different. Click through them.
• Tailwind. If you use Tailwind CSS 3 with Filament, Filament 4 needs 4.1 or later. Theme files use @source directives instead of tailwind.config.js, and Tailwind classes in your own Blade views won’t work without a custom theme. This is often where the visible work is.

The Filament 5 guide lists PHP 8.2, Laravel 11.28, Livewire 4 and Tailwind CSS 4. Livewire 4 is the point of the upgrade, so anything else in your application that uses Livewire directly moves too. Read Livewire’s own upgrade notes for your custom components. If you have nothing that needs Filament 5 yet, Filament 4 on Laravel 13 is also a valid place to be, according to the constraints above.

Filament’s core packages may be ready before your plugins are. Before you commit to a date, list them and ask Composer:

composer show | grep -i filament
composer why-not filament/filament ^4.0
composer why-not laravel/framework ^13.0

If a plugin you depend on has no release for your target, your options are to wait, replace it, or fork it and maintain that yourself. Paid plugins may need a licence check as well. This is often the difference between a short project and a long one, so do it first.

Teams with a small admin panel and decent tests can usually follow Filament’s guides themselves. If the panel is large, has custom components, or runs your operations, our Laravel upgrade service covers the framework and Filament together, with a fixed price after a free assessment. You can see published prices and our upgrade checklist.