Decision guide
Choose the tool for the question.
Zustand already supports the Redux DevTools protocol through its official middleware. Dedicated panels add a different workflow. The best choice depends on whether you need a quick stream, per-store inspection, or a shareable reproduction.
| Option | Best fit | Setup | Trade-off |
|---|---|---|---|
Official devtools middleware + Redux DevTools |
Teams already using Redux DevTools that want action and state inspection | Wrap the store and optionally name actions/stores | Uses a general-purpose protocol and interface rather than a Zustand-specific trace workflow |
| Zustand DevTools free panel | Multiple registered stores, live state, searchable timeline and safe time travel | One bridge wrapper per store | A separate Chrome extension and bridge dependency |
| Zustand DevTools Pro Trace Sessions | Reproducing a difficult bug, comparing steps and sharing a redacted offline session | Same bridge; three previews included | €9.99 plus applicable tax, one-time for unlimited sessions; call-sites remain best-effort |
| Console logging or custom instrumentation | A tiny, isolated question or an environment where extensions are unavailable | Manual code | Easy to add, easy to leave behind, and harder to compare or share consistently |
Use the official middleware when
- Your team already has a reliable Redux DevTools workflow.
- Named actions and snapshots answer the question.
- You want the smallest addition and do not need a dedicated shareable session.
Use a dedicated panel when
- You repeatedly switch between several named stores.
- You need the first changed path rather than a full-state eyeball comparison.
- The bug needs to be replayed or handed to another developer without sharing live access.
They are not mutually exclusive. Zustand DevTools chains the React DevTools hook instead of replacing it, and the official middleware remains a valid choice. Evaluate with a real bug and keep the setup that makes the transition easiest to explain.
Questions to ask before adopting any debugging tool
- Can we identify every store and meaningful action?
- Does it expose sensitive state outside the machine?
- Can time travel break external side effects?
- Can a teammate inspect the reproduction without reconstructing it?
- What happens when framework or browser APIs change?
Try the dedicated workflow on one bug.
The free tier includes registered Stores, Timeline, safe time travel and three complete Trace Session previews.
Install from Chrome