Filament 5: wat je moet weten over de nieuwste major release van het Laravel‑adminpanel.
Filament continues to evolve at breakneck speed as one of the most popular admin panel and UI frameworks for Laravel. In late October 2025, the Filament team announced the first beta of Filament 5: a new major version that, despite not having many new features, still represents a significant step forward in the Laravel ecosystem.
A professional look at the latest phase of the Filament ecosystem.
Filament is an open source UI framework for Laravel that allows developers to quickly build admin panels and applications using Blade, Livewire and Alpine.js. It focuses on productivity, reusable components and an enjoyable developer experience. Filament is widely used in backend tooling and dashboards within Laravel projects and has an active community behind it. Recently, the beta of Filament 5 was launched. While at first glance this may seem like just an incremental step, this release marks an important moment for the framework and its compatibility with the latest Livewire versions. This article outlines what you need to know about Filament 5 Beta, what's new and what it means for your projects.
What's new in Filament 5 Beta.
Support for Livewire v4
The main thrust behind Filament 5 is the full support for Livewire v4. Livewire is a core component within Filament and the jump from Livewire v3 to v4 brings significant improvements. Filament 4 does not support this new Livewire version, requiring an upgrade to Filament 5 if you want to take advantage of the latest Livewire features.
While no major new Filament functionality has been added compared to v4 in this beta, the upgrade is still relevant because underlying dependencies and components have been updated to embrace the Livewire-v4 architecture. This means that most existing Filament functionality remains the same, but you can use the latest Livewire capabilities once you upgrade.
Step-by-step component updates
The Filament 5 betas also include smaller improvements, bug fixes and extension of component behaviours. Recent beta releases (such as beta6 and beta7) show work on things like:
Improved rich-editor functionality,
Extended configuration options for filters and tables,
Improved accessibility and international translation support.
These changes show that the team wants to refine both the internal quality and the user experience, even while the beta phase is still running.
Practical implications for developers and organisations.
Upgrade strategy and compatibility
For teams currently using Filament 4, it is important to plan for any upgrade. Since v5 is primarily a response to Livewire v4 requirements, this means:
Projects that stay with Livewire v3 and Filament v4 have no need to upgrade for now,
Projects that want to take advantage of new Livewire features do need to test with Filament 5 Beta,
The final stable release of v5 is likely to include breaking changes once the beta phase is over.
The final stable release of v5 is likely to include breaking changes once the beta phase is over.
It is wise to evaluate and gather feedback from the beta only in staging environments, rather than using it directly in production.
Impact op development workflows.
Through Livewire v4 compatibility, you can take advantage of improved responsiveness, performance optimisations and possible new API patterns within your Filament applications. This can contribute to, for example:
Better response times for complex forms,
More robust state-handling,
Efficient data binding in UI components.
For developers, this means investing time in exploring Livewire v4 and its Filament 5 integration, so that you prepare the switch well and get your team ready for future updates.
Code examples and upgrade tips
Because Filament 5 in its beta phase does not yet introduce any major API shifts compared to v4, many existing resource definitions and component configurations remain the same. For example, a typical resource also looks like this in v5:
namespace App\Filament\Resources;
use Filament\Resources\Resource;
use Filament\Resources\Table;
use Filament\Resources\Form;
class PostResource extends Resource
{
public static function form(Form $form): Form
{
return $form
->schema([
Forms\Components\TextInput::make('title'),
Forms\Components\Textarea::make('content'),
]);
}
public static function table(Table $table): Table
{
return $table
->columns([
Tables\Columns\TextColumn::make('title'),
Tables\Columns\TextColumn::make('created_at')->dateTime(),
]);
}
}
In most cases, your existing Filament 4 code will just stop working under v5 as long as the Livewire version is updated correctly.
Testing and feedback
As beta software can still change, it is useful to:
Extend unit and integration testing where Filament components are used,
Follow the community channels for breaking change notifications,
Gather and share feedback from your team in the official Filament Discord server.
Conclusie
Filament 5 Beta is not a revolutionary leap in terms of functionality, but mainly a necessary step to make the framework ready for the future. With Livewire v4 support and ongoing refinements in component behaviour, this release lays the foundation for stability and more modern development experiences within Laravel ecosystems.
For organisations and developers, this means they can look ahead to a streamlined upgrade path, where existing code continues to work but new features are unlocked. By experimenting with the beta now, you can plan for a smooth transition once the final v5 stable appears.
Klaar voor de volgende stap? We are too.
Want to know more about Filament? Let's connect.
Worth reading next...
GitLab 18.5 accelerates Agentic AI: from experimentation to wider deployment.
Laravel 13: wat je moet weten over de volgende grote stap van het PHP-framework.