// the take
BlazorTable is a Blazor component for rendering a data table with client-side sorting, paging, and per-column filtering (strings, numbers, dates, enums, custom components). It targets anyone building Blazor Server or WASM apps who wants a grid without reaching for a commercial component library like Telerik or Syncfusion.
Filtering is genuinely granular — type-specific filter components (StringFilter, NumberFilter, DateFilter, EnumFilter) rather than one generic text box, plus a hook for custom filter UI. It works across both hosting models (separate Sample.Server and Sample.Wasm projects against a shared Sample.Shared), so you can verify your actual target before adopting it. Built-in localization ships with seven languages out of the box (da, de, es, fr, pt-BR, zh-CN plus English), which most hobby grid components skip entirely. There's an automated browser test suite (BrowserTests.cs) in addition to the usual unit tests, which is rare for a project this size.
Last commit was mid-2024 — over two years with no activity as of now, so bug fixes and compatibility with newer .NET/Blazor releases aren't guaranteed going forward. It hard-depends on Bootstrap 4 CSS for styling; Bootstrap 4 itself is end-of-life, so you're either stuck on an old CSS stack or doing override work to make it look right alongside Bootstrap 5 or a non-Bootstrap design system. Everything described is client-side paging/sorting/filtering — there's a ServerSideData sample and an IDataLoader interface, but the README doesn't explain the server-side contract at all, so expect to read source to figure out how to page a few hundred thousand rows without loading them all into the browser. No mention of virtualization for large row counts, which matters once you're past a few thousand rows in WASM.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →