Zustand DevTools Chrome extension v1.2
State changes.Explained.
Inspect registered Zustand stores. Follow captured updates, revisit earlier state, and trace the moment a bug began.
Free Stores + Timeline · local state · no account required
One action. See the path that changed.
Change the sample cart. This illustrated panel follows each update.
€39
€129
Make a change here
Stores
Timeline: click an entry to time-travel (free)
Interactive product illustration. Add the keyboard again to reveal items[1].quantity. The real sample app uses the extension and bridge.
One bridge wrapper per store · 3 Pro Trace Sessions to try · zero telemetry
Listed on Zustand's third-party libraries page · community listing, not an official recommendation
Your store. Every captured update.
Register a store once for accurate live state, searchable history and safe ID-based time travel. The zero-setup Component Hooks view stays experimental.
- ONE WRAPPER
- Register a store. Keep your bearings.
withDevtoolsBridge(creator, { name: 'cart' })gives you live state. Expanded branches stay open during updates, and you can copy displayed JSON. - FILTER THE NOISE
- Find the update that matters. Search stores by name, state key or displayed value. Filter Timeline by store or replay availability, then preview a snapshot before changing your app.
- STAYS LOCAL
- State never leaves your machine. Data flows from the inspected page to your own panel and nowhere else: no server, no analytics, no telemetry.
Time travel restores captured store state in this tab. It does not undo network requests or other side effects; entries from before a reload remain inspectable but cannot be replayed.
From install to your first action.
Install the extension and bridge. Add Zustand DevTools to Chrome, then run this in your app:
npm install zustand-devtools-bridge
Wrap a store and give it a name. This complete Vite example keeps the bridge enabled only in development:
import { create } from 'zustand';
import { withDevtoolsBridge } from 'zustand-devtools-bridge';
export const useCounter = create(withDevtoolsBridge(
(set) => ({
count: 0,
increment: () => set((state) => ({ count: state.count + 1 }), false, 'counter/increment'),
}),
{ name: 'counter', enabled: import.meta.env.DEV },
));
Trigger increment in your app: Timeline shows counter/increment and count: 0 → 1. Using another build tool? Replace import.meta.env.DEV with its development flag.
Open DevTools → Zustand. Reload your app, open Stores and interact with the app. Each captured action appears in Timeline.
Try the working sample first · Read the bridge documentation
Installed, but no stores appear?
Check that the bridge wraps the store used by your app and that it is enabled in your current build. Reload the page after installing the extension, then reopen the Zustand panel. Stores created later appear when your app creates them.
Component Hooks is experimental and can show other React hook values. Use Stores for accurate inspection of your registered Zustand stores.
Rewind the bug.
Record while reproducing a bug. Then inspect path-level diffs, likely call-sites, compare any entries, and export a redacted session for offline review.
Interactive product illustration. This session contains a real bug: drag the playhead to step 4 and find the moment the total went wrong. Every step is a one-click jump in the real panel.
TRACE SESSIONS / PRO
one-time · no subscription
Try 3 complete sessions free before buying.
From the first bad update to its cause.
- Unlimited Trace Sessions (3 full previews free)
- Deep path-level diffs and best-effort call-sites
- Compare any two entries, filters, bookmarks and notes
- Redacted session export, validated view-only import
Start with the free Stores and Timeline tools from the Chrome Web Store. Pro supports up to 5 Chrome profile activations and a 30-day no-questions refund. Gumroad delivers the licence key; activation sends only that key and this product's public ID after consent.
Debug the state change, not the symptom.
Three source-linked guides for teams deciding how to label, inspect and reproduce Zustand state bugs.
Name Zustand stores and actions
Turn anonymous updates into a readable timeline with stable store identities and domain-first action labels.
set up readable traces →How to debug Zustand state changes
A repeatable workflow for multiple stores, named actions, path-level diffs and safe reproduction.
read the workflow →Zustand debugging tools compared
When the official middleware, Redux DevTools and a dedicated Chrome panel each fit.
compare the options →Questions people ask
Can I use it today?
Yes. Install the public release from the Chrome Web Store. Stores and Timeline are free; Pro Trace Sessions are an optional €9.99 plus applicable tax, one-time purchase.
What do I need for it to work?
For Stores, Timeline and Trace Sessions, use Chrome (or a Chromium browser that supports DevTools extensions), Zustand 4 or 5, and the
zustand-devtools-bridge wrapper on each store you want to inspect. React is not required for registered stores: the working sample uses vanilla Zustand. The experimental
Component Hooks view requires React and is not guaranteed to show Zustand state.
Install bridge 0.2.1 from
npm.
The repository README
includes the setup example.
Does it conflict with the React DevTools extension?
No. It chains onto the same renderer hook React DevTools uses instead of replacing it, so both extensions work side by side regardless of which loads first.
What data does it collect?
No analytics and no telemetry. Application state stays on your machine: it flows from the inspected page to your own DevTools panel, and what the extension keeps (recent Trace Sessions, the free-preview counter, a license record) lives in your browser's local extension storage. The bridge keeps a bounded per-tab history in the inspected page's own sessionStorage. The only network requests are ones you trigger yourself: activating a licence sends the key and this product's public ID to Gumroad. Full details in the privacy policy.
How does the license work?
A one-time Gumroad purchase (base price €9.99 plus applicable tax) generates and delivers a licence key. Paste it into the extension and approve the one-time optional Gumroad permission to activate. One licence supports up to 5 Chrome profile activations, with no subscription or expiry.
What if it doesn't work for me?
Email within 30 days of purchase for a full refund, no questions asked. Bug reports are welcome on GitHub issues either way. See terms and refunds.
Is the €199 diagnosis part of the Pro licence?
No. Pro is the self-serve extension licence. The Async Trace Diagnosis is a separate, fixed-scope professional service for one reproducible bug, agreed by email before payment.
Need a second pair of eyes?
An optional async diagnosis for one difficult Zustand bug. This is a separate service, not part of the Pro licence.
Async Zustand Trace Diagnosis
Send a minimal reproduction or redacted trace with the behavior you expected.
One reproducible bug, an annotated change path, likely causes and next checks within three working days. Scope and payment are confirmed in writing before the engagement starts.
Check paid diagnosis fitSeptember clinic · intake closed The free feedback cohort closed on 18 September 2026. No new cohort has been announced. Ask about a future clinic.