Skip to main content
You are currently viewing the documentation for Filament 4.x, which is a previous version of Filament.Looking for the current stable version? Visit the 5.x documentation.

​
Introduction

Filters allow you to define certain constraints on your data, and allow users to scope it to find the information they need. You put them in the $table->filters() method. Filters may be created using the static make() method, passing its unique name. You should then pass a callback to query() which applies your filter’s scope: 
use Filament\Tables\Filters\Filter;
use Filament\Tables\Table;
use Illuminate\Database\Eloquent\Builder;

public function table(Table $table): Table
{
    return $table
        ->filters([
            Filter::make('is_featured')
                ->query(fn (Builder $query): Builder => $query->where('is_featured', true))
            // ...
        ]);
}

​
Available filters

By default, using the Filter::make() method will render a checkbox form component. When the checkbox is on, the query() will be activated.
  • You can also replace the checkbox with a toggle.
  • You may use a select filter to allow users to select from a list of options, and filter using the selection.
  • You can use a ternary filter to replace the checkbox with a select field to allow users to pick between 3 states - usually “true”, “false” and “blank”. This is useful for filtering boolean columns.
  • The trashed filter is a pre-built ternary filter that allows you to filter soft-deletable records.
  • Using a query builder, users can create complex sets of filters, with an advanced user interface for combining constraints.
  • You may build custom filters with other form fields, to do whatever you want.

​
Setting a label

By default, the label of the filter is generated from the name of the filter. You may customize this using the label() method: 
use Filament\Tables\Filters\Filter;

Filter::make('is_featured')
    ->label('Featured')
As well as allowing a static value, the label() method also accepts a function to dynamically calculate it. You can inject various utilities into the function as parameters.
Learn more about utility injection.
Filter
$filter
Filament\Tables\Filters\BaseFilter
The current filter instance.
Livewire
$livewire
Livewire\Component
The Livewire component instance.
Table
$table
Filament\Tables\Table
The current table instance.
Customizing the label in this way is useful if you wish to use a translation string for localization: 
use Filament\Tables\Filters\Filter;

Filter::make('is_featured')
    ->label(__('filters.is_featured'))

​
Customizing the filter schema

By default, creating a filter with the Filter class will render a checkbox form component. When the checkbox is checked, the query() function will be applied to the table’s query, scoping the records in the table. When the checkbox is unchecked, the query() function will be removed from the table’s query. Filters are built entirely on Filament’s form fields. They can render any combination of form fields, which users can then interact with to filter the table.

​
Using a toggle button instead of a checkbox

The simplest example of managing the form field that is used for a filter is to replace the checkbox with a toggle button, using the toggle() method: 
use Filament\Tables\Filters\Filter;

Filter::make('is_featured')
    ->toggle()

​
Customizing the built-in filter form field

Whether you are using a checkbox, a toggle or a select, you can customize the built-in form field used for the filter, using the modifyFormFieldUsing() method. The method accepts a function with a $field parameter that gives you access to the form field object to customize: 
use Filament\Forms\Components\Checkbox;
use Filament\Tables\Filters\Filter;

Filter::make('is_featured')
    ->modifyFormFieldUsing(fn (Checkbox $field) => $field->inline(false))
The function passed to modifyFormFieldUsing() can inject various utilities as parameters.
Learn more about utility injection.
Field
$field
Filament\Forms\Components\Field
The field object to modify.
Filter
$filter
Filament\Tables\Filters\BaseFilter
The current filter instance.
Livewire
$livewire
Livewire\Component
The Livewire component instance.
Table
$table
Filament\Tables\Table
The current table instance.

​
Applying the filter by default

You may set a filter to be enabled by default, using the default() method: 
use Filament\Tables\Filters\Filter;

Filter::make('is_featured')
    ->default()
If you’re using a select filter, visit the “applying select filters by default” section.

​
Persisting filters in the user’s session

To persist the table filters in the user’s session, use the persistFiltersInSession() method: 
use Filament\Tables\Table;

public function table(Table $table): Table
{
    return $table
        ->filters([
            // ...
        ])
        ->persistFiltersInSession();
}

​
Live filters

By default, filter changes are deferred and do not affect the table, until the user clicks an “Apply” button. To disable this and make the filters “live” instead, use the deferFilters(false) method: 
use Filament\Tables\Table;

public function table(Table $table): Table
{
    return $table
        ->filters([
            // ...
        ])
        ->deferFilters(false);
}

​
Customizing the apply filters action

When deferring filters, you can customize the “Apply” button, using the filtersApplyAction() method, passing a closure that returns an action. All methods that are available to customize action trigger buttons can be used: 
use Filament\Actions\Action;
use Filament\Tables\Table;

public function table(Table $table): Table
{
    return $table
        ->filters([
            // ...
        ])
        ->filtersApplyAction(
            fn (Action $action) => $action
                ->link()
                ->label('Save filters to table'),
        );
}

​
Deselecting records when filters change

By default, all records will be deselected when the filters change. Using the deselectAllRecordsWhenFiltered(false) method, you can disable this behavior: 
use Filament\Tables\Table;

public function table(Table $table): Table
{
    return $table
        ->filters([
            // ...
        ])
        ->deselectAllRecordsWhenFiltered(false);
}

​
Modifying the base query

By default, modifications to the Eloquent query performed in the query() method will be applied inside a scoped where() clause. This is to ensure that the query does not clash with any other filters that may be applied, especially those that use orWhere(). However, the downside of this is that the query() method cannot be used to modify the query in other ways, such as removing global scopes, since the base query needs to be modified directly, not the scoped query. To modify the base query directly, you may use the baseQuery() method, passing a closure that receives the base query: 
use Illuminate\Database\Eloquent\Builder;
use Illuminate\Database\Eloquent\SoftDeletingScope;
use Filament\Tables\Filters\TernaryFilter;

TernaryFilter::make('trashed')
    // ...
    ->baseQuery(fn (Builder $query) => $query->withoutGlobalScopes([
        SoftDeletingScope::class,
    ]))

​
Excluding filters when resolving records

When a user interacts with a table record (e.g., clicking an action button), Filament resolves that record from the database. By default, all active filter conditions are applied, ensuring users cannot access records outside their filter scope. However, some filters like TrashedFilter modify global scopes rather than restricting access. When a record’s state changes after the user saw it in the table, you may still want the user to interact with it. You may mark a filter to be excluded when resolving records using the excludeWhenResolvingRecord() method: 
use Filament\Tables\Filters\Filter;
use Illuminate\Database\Eloquent\Builder;
use Illuminate\Database\Eloquent\SoftDeletingScope;

Filter::make('trashed')
    ->query(fn (Builder $query) => $query->onlyTrashed())
    ->baseQuery(fn (Builder $query) => $query->withoutGlobalScopes([
        SoftDeletingScope::class,
    ]))
    ->excludeWhenResolvingRecord()
When excludeWhenResolvingRecord() is used:
  • The filter’s query() callback is not applied when resolving records
  • The filter’s baseQuery() callback is still applied when resolving records
Do not use excludeWhenResolvingRecord() on filters that enforce authorization rules. For example, if you have a filter that restricts records by tenant or user ownership, those filters should remain enforced to prevent unauthorized access.

​
Customizing the filters trigger action

To customize the filters trigger buttons, you may use the filtersTriggerAction() method, passing a closure that returns an action. All methods that are available to customize action trigger buttons can be used: 
use Filament\Actions\Action;
use Filament\Tables\Table;

public function table(Table $table): Table
{
    return $table
        ->filters([
            // ...
        ])
        ->filtersTriggerAction(
            fn (Action $action) => $action
                ->button()
                ->label('Filter'),
        );
}

​
Filter utility injection

The vast majority of methods used to configure filters accept functions as parameters instead of hardcoded values: 
use App\Models\Author;
use Filament\Tables\Filters\SelectFilter;

SelectFilter::make('author')
    ->options(fn (): array => Author::query()->pluck('name', 'id')->all())
This alone unlocks many customization possibilities. The package is also able to inject many utilities to use inside these functions, as parameters. All customization methods that accept functions as arguments can inject utilities. These injected utilities require specific parameter names to be used. Otherwise, Filament doesn’t know what to inject.

​
Injecting the current filter instance

If you wish to access the current filter instance, define a $filter parameter: 
use Filament\Tables\Filters\BaseFilter;

function (BaseFilter $filter) {
    // ...
}

​
Injecting the current Livewire component instance

If you wish to access the current Livewire component instance that the table belongs to, define a $livewire parameter: 
use Filament\Tables\Contracts\HasTable;

function (HasTable $livewire) {
    // ...
}

​
Injecting the current table instance

If you wish to access the current table configuration instance that the filter belongs to, define a $table parameter: 
use Filament\Tables\Table;

function (Table $table) {
    // ...
}

​
Injecting multiple utilities

The parameters are injected dynamically using reflection, so you are able to combine multiple parameters in any order: 
use Filament\Tables\Contracts\HasTable;
use Filament\Tables\Table;

function (HasTable $livewire, Table $table) {
    // ...
}

​
Injecting dependencies from Laravel’s container

You may inject anything from Laravel’s container like normal, alongside utilities: 
use Filament\Tables\Table;
use Illuminate\Http\Request;

function (Request $request, Table $table) {
    // ...
}
Edit this page on GitHub

Sponsored by

KirschbaumSerpApiAgiledropCMS MaxBaiz.aiMailtrap