Weave Code
Filament Jetstream Theme Laravel Package
webbingbrasil/filament-jetstream-theme
Filament Jetstream Theme brings Laravel Jetstream's clean, modern design to Filament admin panels, helping you create a consistent UI across your Laravel application with minimal setup. Ideal for teams already using Jetstream.
A jetstream theme for filament
Frequently asked questions about Filament Jetstream Theme
- What is webbingbrasil/filament-jetstream-theme used for?
- It is a presentation-layer theme that brings Laravel Jetstream's visual language, including palette, typography, radii and selector overrides, to Filament admin panels. It ships no models, migrations, middleware or domain logic, just Tailwind presets and theme CSS. The goal is a consistent UI between a Jetstream-scaffolded app and its Filament admin.
- How do I install the Filament Jetstream theme with Composer?
- Run composer require webbingbrasil/filament-jetstream-theme, then register the theme in your panel provider using Filament::registerTheme() on Filament 2. Because the package is archived and pins Filament ^2.x, installation will likely conflict on current panels. Most teams clone the repository and extract the CSS rather than adding the dependency.
- Is webbingbrasil/filament-jetstream-theme compatible with Filament 3 or Filament 4?
- No, it was built for the Filament 2.x DOM and last released in April 2023, so expect broken styling on Filament 3 and 4 rather than minor imperfections. Filament 3 reworked its Blade views, Tailwind conventions and CSS-variable approach, so the theme's selectors no longer match. Any working state on newer versions should be treated as coincidental.
- Does this theme work with Laravel 11 or Laravel 12?
- Unverified. The package targets the Laravel 9/10 era and Filament 2.x, and there is no maintainer to confirm newer support. PHP 8.1 and 8.2 are likely fine, while PHP 8.3 and 8.4 are untested. Test on a throwaway branch before committing to anything.
- Is the package still maintained?
- No. The repository is archived, so there is no PR queue, no compatibility release path and no maintainer. Adopting it puts an unmaintained artifact in the critical path of your admin UI, which means your team owns it by default. If you use any of it, pin by commit SHA and vendor the CSS.
- How do I remove the package and keep the theme styles?
- Run composer remove webbingbrasil/filament-jetstream-theme, relocate the theme CSS and Tailwind preset into app-owned files such as resources/css/filament/admin/theme.css, and re-register the theme in your panel provider. Then visually diff login, dashboard, resource list, resource form, modals, notifications and dark mode. This extraction is the recommended path even if you never installed it.
- Does it work with Jetstream's Inertia stack?
- Only at token level. Jetstream's Inertia flavor has no shared Blade layer with your Filament panel, so visual parity is limited to design tokens such as colors and typography. If you are on Inertia, the case for a theme package weakens, and copying the preset values is usually enough.
- How do I register the theme in a Filament panel provider?
- On Filament 2, call Filament::registerTheme() inside your panel provider. On Filament 3 and later, use the ->viteTheme() method on your Panel configuration, often combined with ->theme() for the Tailwind setup. The package itself was built for the v2 registration path, so on newer versions you will be registering your own extracted CSS anyway.
- Are there alternatives to this Filament Jetstream theme?
- The main alternative is building your own Filament theme. A competent Laravel frontend developer can reproduce the design tokens and selector overrides in one to two days and own the result outright. You can also start from Filament's official theme scaffolding and port the Jetstream palette yourself, or look for an actively maintained theme package instead of an archived repo.
- Is it safe to use webbingbrasil/filament-jetstream-theme in production?
- Security risk is low because there are no network calls, no user input handling and barely any PHP beyond a service provider. The real risk is lifecycle: an archived artifact sitting in your admin UI and a Composer constraint that could block a Filament security upgrade. Vendor the CSS into your own resources and drop the dependency if you want it in production.
Weaver
How can I help you explore Laravel packages today?