TanStack Solid Table is the Solid adapter of TanStack Table—headless primitives for state, sorting, filtering, and column models. You wire the UI yourself: every <td>, every interaction, every virtualization integration.
Simple Table for Solid is batteries-included: virtualization, column pinning, row grouping with aggregations, and inline editing all ship in one MIT package, built on Solid's fine-grained reactivity.
This article compares the two so you can pick the one that fits your team's appetite for building UI from primitives.
Quick comparison
| Feature | TanStack Solid Table | Simple Table for Solid |
|---|---|---|
| License | MIT | MIT |
| Approach | Headless (BYO UI) | Batteries-included |
| Solid signals integration | Yes | First-class |
| Solid-Start support | Yes | Yes |
| Bundle size (gzipped) | ~14 kB core (UI not included) | ~70 kB (full grid) |
| Built-in row virtualization | No (BYO virtualizer) | Yes |
| Built-in column pinning | State only (BYO UI) | Yes |
| Row grouping + aggregations | State only (BYO UI) | Built-in |
| Inline cell editing | BYO | Built-in |
| Setup time to first table | Hours / days | Minutes |
Stay headless when…
- You want pixel-level control over every <tr> and <td>.
- You're already shipping a custom virtualization layer (TanStack Virtual).
- Your design system has unique table layouts.
- You're standardized on TanStack across your stack and want consistency.
Switch to Simple Table for Solid when…
- You want virtualization, pinning, grouping with aggregations, and editing in one package.
- Your team is small and time-to-feature beats absolute UI control.
- You also build React / Vue / Angular / Svelte / Vanilla surfaces and want one engine.
- You want signal-based reactivity without writing the UI primitives.
Real-world scenarios
Custom design system with unique row layouts
Need full control over markup, styling, animations.
Stay on TanStack Solid Table—you'll get exactly the markup you want.
Reporting tool, 100k rows, grouping required
Sum/avg footers, virtualization, time-to-feature matters.
Switch to Simple Table for Solid—heavy lifting is built in.
Greenfield Solid-Start app
Want signals-first data grid; team is small.
Pick Simple Table for Solid—batteries-included on Solid signals.
Multi-stack platform (React + Solid)
Want one engine and one mental model across both.
Choose Simple Table—same engine via @simple-table/react and @simple-table/solid.
Frequently asked questions
- Is TanStack Solid Table dead?
- No—it's actively maintained as part of the TanStack family. The trade-off vs Simple Table is headless vs batteries-included, not maintenance.
- Can I migrate gradually?
- Yes. Replace one table at a time. Map your column defs to HeaderObject entries; replace your TanStack Virtual integration with Simple Table's built-in virtualization; convert custom cell renderers to Simple Table cellRenderer Solid components.
- Does Simple Table for Solid use signals?
- Yes. Inputs accept signals or static values; updates flow through Solid's fine-grained reactivity.
The verdict
Both are MIT, both are Solid-native, and both are maintained. The choice is philosophy.
If you want primitives and full UI control, stay on TanStack Solid Table. If you want virtualization, pinning, grouping with aggregations, and editing without building them, switch to Simple Table for Solid.