Newsletter
Join the Community
Subscribe to our newsletter for the latest news and updates
Blazor component library with 30+ Tailwind CSS UI components built on the Flowbite design system.
Flowbite Blazor is an open-source Blazor component library that ports the Flowbite design system to ASP.NET Blazor 8/9 on top of Tailwind CSS v4, providing 30+ reusable UI components for .NET developers. It is maintained by the Themesberg team behind Flowbite and is currently in beta (v0.2.x-beta).
Flowbite Blazor takes Blazor component markup as input and produces accessible, keyboard-navigable UI styled with Flowbite's design tokens. It runs on .NET 8.0 or .NET 9.0 with Tailwind CSS v4 and Node.js 18+ as prerequisites. The library ships as the Flowbite NuGet package, with a companion Flowbite.ExtendedIcons package and a Flowbite.Templates.Wasm project template for Blazor WebAssembly.
Flowbite Blazor is for Blazor Server and Blazor WebAssembly developers who want production-style components without writing Tailwind utilities by hand. Teams that already use Flowbite for marketing sites can extend the same design language into .NET applications. Developers who need keyboard navigation, ARIA labels, and motion-reduce support for accessibility compliance will also find the built-in behavior useful.
After installing the Flowbite NuGet package, you call builder.Services.AddFlowbite() in Program.cs, add the flowbite.min.css and flowbite.js references to your layout, and configure Tailwind CSS v4 with the flowbite plugin and @source paths for your .razor files. Then you can use any of the 30+ components directly in Razor markup.
Yes, Flowbite Blazor is released under the MIT License, so it is free to use, modify, and include in commercial projects.
The library targets .NET 8.0 and .NET 9.0 SDKs. You also need Node.js 18+ and Tailwind CSS v4.x to build the styles.
The project is in beta (v0.2.x-beta). The v0.2.0 release renamed Button.Style to Button.Variant and Tooltip.Style to Tooltip.Theme, so breaking API changes may still occur before a stable 1.0.
Yes, dark mode is configured via a minimal tailwind.config.js that sets darkMode to class. The library ships with the Tailwind CSS class-based dark mode setup.
You can pass a Class parameter to any component and TailwindMerge resolves conflicts, or you can use the Slots parameter on complex components to style specific parts like the modal header or dropdown menu.
