Download the PHP package abdulrahman-dev22/filament-icon-picker without Composer

Filament Icon Picker

A drop-in icon picker form field for Filament v3, v4 and v5.

IconPicker::make('icon') renders a searchable grid of icons organised into tabs: one tab for the bundled Heroicons, plus a tab for every custom SVG folder or custom icon set you register. The selected icon is stored as a single string (heroicons:o-academic-cap, brand:logo) that you can render anywhere in your app.

• Zero configuration: Heroicons work out of the box.
• Custom icons: point at a folder of .svg files. Drop a file in, it shows up.
• Extensible: implement one small interface to add any icon source as its own tab.
• Let admins upload new SVG icons from the picker itself; uploads are sanitised and stored on any Laravel disk.
• Choose how the value is stored: compact reference, Blade Icons name, array/JSON with inline SVG and URL, or raw SVG.
• API ready: FilamentIconPicker::toArray() and an optional {set}/{name}.svg route for mobile and SPA clients.
• Client-side search per tab, configurable grid columns, keyboard focus styles, dark mode, RTL.
• Inherits every standard field behaviour: required(), disabled(), default(), live(), validation, etc.
• Same code path on Filament 3, 4 and 5. No version-specific hacks in your project.

Requirements

Heroicons are pulled in through blade-ui-kit/blade-heroicons, which every supported Filament version already depends on.

Installation

Publish the field's stylesheet with Filament's asset command. Panel projects that have @php artisan filament:upgrade in their composer.json post-autoload-dump scripts (the default from filament:install) do this automatically:

Optionally publish the config file:

Notes per Filament version

• Filament 3 – nothing else to do. The stylesheet is plain CSS registered through FilamentAsset, so you do not need a custom Tailwind theme or to add the package's views to tailwind.config.js.
• Filament 4 / 5 – nothing else to do. The field extends Filament\Forms\Components\Field and works inside resources, schemas, actions, relation managers and custom pages.
• Standalone forms (no panel) – make sure your layout includes @filamentStyles and @filamentScripts as described in the Filament docs; the field's stylesheet is injected by @filamentStyles.

Usage

Bundled Heroicons only

Stores e.g. heroicons:o-academic-cap.

By default only the outline style is listed (324 icons). Enable more styles in the config:

Custom icons from a folder

Every .svg in that folder becomes an icon. The file name (without extension) is the icon name and the default label (shopping-bag.svg → Shopping Bag). Nested folders are joined with a dot (social/twitter.svg → social.twitter). Stored value: brand:shopping-bag.

To make a folder available to every IconPicker in the project, configure it globally instead:

Globally registered folders are also registered with Blade Icons under the set key as prefix, so the stored value doubles as a plain icon name everywhere Filament accepts one: ->icon('brand-shopping-bag'), <x-filament::icon icon="brand-shopping-bag" />, @svg('brand-shopping-bag'). (Blade Icons prefixes cannot contain dashes; for such keys the picker falls back to rendering the SVG inline and you should use the Blade component below.)

Both, and several custom tabs

Renders three tabs: Heroicons, Brand, Flags.

Excluding sets, or ignoring the global registry

Registering a fully custom icon set

Implement AbdulrahmanDev22\FilamentIconPicker\IconSets\IconSet:

Register it globally through the config (classes are resolved from the container):

…or at runtime in a service provider:

…or for a single field (a set with the same key as a global one replaces it for that field only):

The bundled sets are ordinary implementations of the same interface, so you can also pass new HeroiconsIconSet(styles: ['s'], label: 'Solid') or new CustomIconSet($path, $key, $label).

Field API

Plus everything from Filament's Field: label(), required(), disabled(), default(), live(), afterStateUpdated(), rules(), hidden(), columnSpan(), etc.

The field validates automatically that a submitted value belongs to one of the field's icon sets.

Storage formats

Internally the picker always works with a reference: "<set-key>:<icon-name>", e.g. heroicons:o-academic-cap or brand:star. No file paths are ever stored. What gets written to the model is up to you, per field or globally (storage_format in the config):

storeAsArray() needs a JSON column and an array cast on the model, otherwise Eloquent cannot save the array:

On Laravel 10 use the $casts property instead: protected $casts = ['icon' => 'array'];. storeAsJson() does the same job without a cast if you prefer a plain text column.

Whatever the format, loading a record converts the stored value back to a reference so the picker shows the current selection. Existing data keeps working if you switch format later, because the converter accepts every format on the way in (it even matches raw SVG markup back to its icon).

Rendering the value elsewhere

All helpers accept any storage format (reference, Blade Icons name, array, JSON string or SVG). The set only needs to be registered globally, not on the field, to resolve outside the form.

API responses

url is null until you enable the icon route. It serves every globally registered icon as an SVG file with long-lived cache headers, so mobile apps and CDNs can load icons by URL:

GET /filament-icon-picker/{set}/{name}.svg → image/svg+xml, 404 for unknown icons. FilamentIconPicker::url('brand:star') returns the same link.

AbdulrahmanDev22\FilamentIconPicker\Support\IconReference::from($value) splits a reference into ->set and ->name when you need the parts.

Letting users upload icons

Icons normally come from the filesystem you deploy. To let admins add icons at runtime, give the picker a set that lives on a Laravel disk and turn on the upload action:

An "Upload icon" link appears next to the selected value. It opens a modal with an SVG file input and an optional name; on submit the file is sanitised (scripts, event handlers, <foreignObject>, external and javascript: references and unsafe <style> rules are removed), stored as {directory}/{name}.svg, the set's cache is refreshed and the new icon is selected.

• DiskIconSet reads from Storage::disk(), so uploads survive deployments and are shared across servers when the disk is S3/GCS. It also registers with Blade Icons, so uploads:star works as the plain icon name uploads-star.
• Folder based sets (customIconsPath(), custom_icon_sets) can receive uploads too, but only when named explicitly with ->uploadable(set: 'key'), so the SVGs you ship with the app are never written to by accident.
• Names are slugged and made unique (star, star-2, …). Customise the modal with ->uploadAction(fn (Action $action) => $action->label('…')->modalWidth('lg')).
• To use your own sanitiser (for example enshrined/svg-sanitize), call SvgSanitizer::using(fn (string $svg): string => …) in a service provider.
• Programmatic uploads: app(IconUploader::class)->upload($set, $svgMarkup, name: 'star') returns the IconReference of the stored icon. Any set implementing IconSets\Contracts\AcceptsUploads works.

Caching

Icon folders are scanned once per request. To avoid touching the filesystem on every request in production, the resolved list of each set can be cached:

After adding or removing SVG files with caching enabled, clear the cached lists:

php artisan cache:clear works too. Sets you implement yourself decide their own caching; use the AbdulrahmanDev22\FilamentIconPicker\IconSets\Concerns\CachesIconList trait to opt into the same mechanism.

How multi-version support works

The field extends Filament\Forms\Components\Field and only touches Filament through extension points that are stable across 3, 4 and 5: the field wrapper view is resolved with $getFieldWrapperView(), state is bound with $applyStateBindingModifiers() / $entangle, shared Blade components (x-filament::input.wrapper) are used for the search box, and the stylesheet is registered through FilamentAsset. Colours use a CSS var() fallback chain so the same file works with Filament 3's RGB channel variables and Filament 4/5's oklch variables. Nothing in the package branches on the Filament version.

Testing

The suite covers icon set enumeration, the registry, the field's set resolution, value parsing and rendering, plus Livewire render / round-trip / validation tests for the field.

Publishing under another vendor name

The package is published as abdulrahman-dev22/filament-icon-picker with the AbdulrahmanDev22\FilamentIconPicker namespace. To fork it under your own name:

1. Replace the namespace AbdulrahmanDev22\FilamentIconPicker with Acme\FilamentIconPicker in src/, tests/, resources/views/ and composer.json (autoload, autoload-dev, extra.laravel).
2. Change name, homepage and authors in composer.json, and FilamentIconPickerServiceProvider::$composerPackage (used as the asset package id).
3. Optionally rename the config key / view namespace filament-icon-picker (FilamentIconPickerServiceProvider::$name, config/, the $view property of IconPicker, translation keys and <x-filament-icon-picker::icon>).
4. Update LICENSE.md and this README.
5. Run composer validate --strict and composer test.
6. Push to GitHub, tag a release (git tag v1.0.0 && git push --tags) and submit the repository on packagist.org. Enable the GitHub service hook so new tags are picked up automatically.

Follow Semantic Versioning: patch for fixes, minor for backwards compatible features (new field methods, new sets), major for changes to the IconSet contract or the stored value format.

Changelog

See CHANGELOG.md.

License

MIT. See LICENSE.md.