Bladewell vs BladewindUI
BladewindUI and Bladewell are close: both are free Blade components with vanilla JavaScript and Tailwind CSS, no Livewire or Alpine needed. They differ in how the components reach your app, and in what each needs from your Content Security Policy.
Side by side
BladewindUI's column is taken from its own docs, repository and Packagist page as they read on 7 October 2026, each linked as its source. Something out of date? Tell us.
| Topic | Bladewell | BladewindUI |
|---|---|---|
| Price and licence | Free, MIT licensed. Every component, no paid tier. | Free, MIT licensed. Source: Price and licence, BladewindUI |
| How you install it | php artisan bladewell:add copies each component's Blade, JavaScript and CSS into your app. You edit them like your own code; bladewell:add --installed updates the files you haven't changed and lists the ones you have. The package can stay a dev dependency. | A Composer package your app runs: the whole library, a group or single components. You can publish the views to edit them, and publishing again overwrites your edits. Source: How you install it, BladewindUI |
| Without Livewire | Yes: plain Blade. The same components work inside Livewire 3 and 4 components too. | Yes: vanilla JavaScript, with Livewire supported. Source: Without Livewire, BladewindUI |
| JavaScript it brings | One small vanilla JS module per component, bundled by your own Vite build. No Alpine, no Livewire, nothing from a CDN. | Its own vanilla JS. The file picker wraps FilePond and Cropper.js. Source: JavaScript it brings, BladewindUI |
| CSS | Tailwind CSS 4.1 or later, with a theme file of colour tokens. | Tailwind CSS 4, or its precompiled stylesheet. Source: CSS, BladewindUI |
| Laravel and PHP | Laravel 12 or 13, PHP 8.3 or later. | Laravel 10 to 13, PHP 8.1 or later. Source: Laravel and PHP, BladewindUI |
| Date range picker | Yes, free. | Yes: the date picker with range="true". Source: Date range picker, BladewindUI |
| Data table | Yes: sorting, filters with option counts, row selection and pagination, run by your controller or Livewire component, with the URL kept in step. | Yes: sorting, search, pagination and selection in the browser, plus a separate data grid. Source: Data table, BladewindUI |
| File upload | Yes, including direct upload with progress and retry. | Yes, built on FilePond. Source: File upload, BladewindUI |
| Under a strict CSP | No inline scripts, onclick or style attributes, and no eval: nothing needs 'unsafe-inline' or 'unsafe-eval', and there's no nonce to set up. | Works without 'unsafe-inline' once you set a nonce in its config, as components print inline scripts. Props that take JavaScript strings still need 'unsafe-inline'. Source: Under a strict CSP, BladewindUI |
| Accessibility | Keyboard support and ARIA in every component. Every example is checked with axe, light and dark, closed and open, on every change. | Every component reachable with Tab and usable without a mouse, with its own ARIA roles. Source: Accessibility, BladewindUI |
| Latest release | 1.0.0, 9 October 2026. 42 components so far. | v5.1.0, 13 September 2026. Source: Latest release, BladewindUI |
Which to pick
BladewindUI, if
- You want more components than Bladewell has today.
- You'd like a precompiled stylesheet, without a Tailwind build of your own.
- You're on Laravel 10 or 11.
Bladewell, if
- You want to edit components and still get updates: Bladewell skips the files you've changed instead of overwriting them.
- You want no inline scripts at all, so no nonce to configure.
- You want a table that filters and sorts on the server, by your controller or Livewire component, with the URL kept in step.
Also compared: Flux, Mary UI, WireUI and Blade UI Kit.