redux vs @tanstack/react-query
@tanstack/react-query is downloaded 1.7× more often than redux (225,327,948 vs 133,171,760 per month), so it has the larger community and more answered questions online. redux ships 90% less gzipped JavaScript (1.4 kB vs 13.3 kB), which matters if bundle size is a priority. Both projects are actively maintained.
| Metric | redux | @tanstack/react-query |
|---|---|---|
| Weekly downloads | 31,133,484 | 51,850,189✓ |
| Monthly downloads | 133,171,760 | 225,327,948✓ |
| GitHub stars | 61,439✓ | 49,542 |
| Minified size | 3.3 kB✓ | 45.1 kB |
| Minified + gzipped | 1.4 kB✓ | 13.3 kB |
| Dependencies | 0✓ | 1 |
| Open issues | 43✓ | 172 |
| Last commit | 2026-05-15 | 2026-06-02✓ |
| Latest version | 5.0.1 | 5.100.14 |
| License | MIT | MIT |
When to choose which
redux
The original predictable state container.
Choose it when: Rarely on its own anymore — reach for Redux Toolkit instead. Use raw redux only for legacy code or custom store setups.
- + Battle-tested
- + Framework-agnostic core
- - Lots of boilerplate without RTK
- - Async needs middleware
@tanstack/react-query
Async server-state: caching, refetching and mutations.
Choose it when: Managing data from an API — caching, background refetch, pagination, mutations. It complements (not replaces) a client store.
- + Best-in-class server cache
- + Great devtools
- + Handles refetch/stale data
- - Not for client/UI state
- - More config than SWR
Feature comparison
| Feature | redux | @tanstack/react-query |
|---|---|---|
| Paradigm | Flux / reducers | Async server cache |
| First-class TypeScript | Verbose | ✓ Yes |
| Works outside React | ✓ Yes | Partial |
| Dedicated devtools | ✓ Yes | ✓ Yes |
| Built-in async / server state | ✗ No | ✓ Yes |
| Boilerplate | High | Low |
Related comparisons
Embed this comparison
A live badge for your README — it updates as the numbers change.
[](https://devcompare.dev/compare/redux-vs-tanstack-react-query)Data from npm, Bundlephobia and GitHub. Last updated 2026-06-02.