File: devtools.md | Updated: 11/15/2025
devtools middleware lets you use Redux DevTools Extension
without Redux. Read more about the benefits of using Redux DevTools for debugging.
[!IMPORTANT] In order to use
devtoolsfromzustand/middlewareyou need to install@redux-devtools/extensionlibrary.
const nextStateCreatorFn = devtools(stateCreatorFn, devtoolsOptions)
devtools<T>(stateCreatorFn: StateCreator<T, [], []>, devtoolsOptions?: DevtoolsOptions): StateCreator<T, [['zustand/devtools', never]], []>
['zustand/devtools', never]
<!-- prettier-ignore-end -->
devtools(stateCreatorFn, devtoolsOptions)stateCreatorFn: A function that takes set function, get function and store as arguments.
Usually, you will return an object with the methods you want to expose.devtoolsOptions: An object to define Redux Devtools options.
name: A custom identifier for the connection in the Redux DevTools.enabled: Defaults to true when is on development mode, and defaults to false
when is on production mode. Enables or disables the Redux DevTools integration
for this store.anonymousActionType: Defaults to the inferred action type or anonymous if
unavailable. A string to use as the action type for anonymous mutations in the Redux DevTools.store: A custom identifier for the store in the Redux DevTools.actionsDenylist: A string or array of strings (regex patterns) that specify which
actions should be filtered out from Redux DevTools. This option is passed directly to Redux DevTools
for filtering. For example, ['secret.*'] will filter out all actions starting with "secret".devtools returns a state creator function.
This example shows you how you can use Redux Devtools to debug a store
import { create, StateCreator } from 'zustand'
import { devtools } from 'zustand/middleware'
type JungleStore = {
bears: number
addBear: () => void
fishes: number
addFish: () => void
}
const useJungleStore = create<JungleStore>()(
devtools((set) => ({
bears: 0,
addBear: () =>
set((state) => ({ bears: state.bears + 1 }), undefined, 'jungle/addBear'),
fishes: 0,
addFish: () =>
set(
(state) => ({ fishes: state.fishes + 1 }),
undefined,
'jungle/addFish',
),
})),
)
This example shows you how you can use Redux Devtools to debug a Slices pattern based store
import { create, StateCreator } from 'zustand'
import { devtools } from 'zustand/middleware'
type BearSlice = {
bears: number
addBear: () => void
}
type FishSlice = {
fishes: number
addFish: () => void
}
type JungleStore = BearSlice & FishSlice
const createBearSlice: StateCreator<
JungleStore,
[['zustand/devtools', never]],
[],
BearSlice
> = (set) => ({
bears: 0,
addBear: () =>
set(
(state) => ({ bears: state.bears + 1 }),
undefined,
'jungle:bear/addBear',
),
})
const createFishSlice: StateCreator<
JungleStore,
[['zustand/devtools', never]],
[],
FishSlice
> = (set) => ({
fishes: 0,
addFish: () =>
set(
(state) => ({ fishes: state.fishes + 1 }),
undefined,
'jungle:fish/addFish',
),
})
const useJungleStore = create<JungleStore>()(
devtools((...args) => ({
...createBearSlice(...args),
...createFishSlice(...args),
})),
)
You can filter out specific actions from Redux DevTools using the actionsDenylist option. This is useful for hiding internal or sensitive actions from the DevTools timeline.
import { create } from 'zustand'
import { devtools } from 'zustand/middleware'
type Store = {
user: string | null
token: string | null
login: (user: string, token: string) => void
logout: () => void
updateData: () => void
}
const useStore = create<Store>()(
devtools(
(set) => ({
user: null,
token: null,
login: (user, token) => set({ user, token }, undefined, 'auth/login'),
logout: () => set({ user: null, token: null }, undefined, 'auth/logout'),
updateData: () =>
set({ user: 'updated' }, undefined, 'internal/updateData'),
}),
{
name: 'AuthStore',
// Filter out actions matching these regex patterns
actionsDenylist: ['internal/.*'], // Hides all 'internal/*' actions
},
),
)
You can also use a single regex string:
const useStore = create<Store>()(
devtools(
(set) => ({
// ... state and actions
}),
{
name: 'MyStore',
actionsDenylist: 'secret.*', // Hides all actions starting with 'secret'
},
),
)
[!NOTE] The
actionsDenylistoption uses regex pattern matching and is handled directly by Redux DevTools Extension. All actions are still sent to DevTools, but matching actions are filtered from the display.
When a store is no longer needed, you can clean up the Redux DevTools connection by calling the cleanup method on the store:
import { create } from 'zustand'
import { devtools } from 'zustand/middleware'
const useStore = create(
devtools((set) => ({
count: 0,
increment: () => set((state) => ({ count: state.count + 1 })),
})),
)
// When you're done with the store, clean it up
useStore.devtools.cleanup()
This is particularly useful in applications that wrap store in context or create multiple stores dynamically.
By default, Redux Devtools only show one store at a time, so in order to see other stores you
need to use store selector and choose a different store.
If an action type name is not provided, it is defaulted to "anonymous". You can customize this
default value by providing a anonymousActionType parameter:
For instance the next example doesn't have action type name:
import { create, StateCreator } from 'zustand'
import { devtools } from 'zustand/middleware'
type BearSlice = {
bears: number
addBear: () => void
}
type FishSlice = {
fishes: number
addFish: () => void
}
type JungleStore = BearSlice & FishSlice
const createBearSlice: StateCreator<
JungleStore,
[['zustand/devtools', never]],
[],
BearSlice
> = (set) => ({
bears: 0,
addBear: () => set((state) => ({ bears: state.bears + 1 })),
eatFish: () => set((state) => ({ fishes: state.fishes - 1 })),
})
const createFishSlice: StateCreator<
JungleStore,
[['zustand/devtools', never]],
[],
FishSlice
> = (set) => ({
fishes: 0,
addFish: () => set((state) => ({ fishes: state.fishes + 1 })),
})
const useJungleStore = create<JungleStore>()(
devtools((...args) => ({
...createBearSlice(...args),
...createFishSlice(...args),
})),
)
In order to fix the previous example, we need to provide an action type name as the third parameter.
Additionally, to preserve the default behavior of the replacement logic, the second parameter
should be set to undefined.
Here's the fixed previous example
import { create, StateCreator } from 'zustand'
type BearSlice = {
bears: number
addBear: () => void
}
type FishSlice = {
fishes: number
addFish: () => void
}
type JungleStore = BearSlice & FishSlice
const createBearSlice: StateCreator<
JungleStore,
[['zustand/devtools', never]],
[],
BearSlice
> = (set) => ({
bears: 0,
addBear: () =>
set((state) => ({ bears: state.bears + 1 }), undefined, 'bear/addBear'),
})
const createFishSlice: StateCreator<
JungleStore,
[['zustand/devtools', never]],
[],
FishSlice
> = (set) => ({
fishes: 0,
addFish: () =>
set((state) => ({ fishes: state.fishes + 1 }), undefined, 'fish/addFish'),
})
const useJungleStore = create<JungleStore>()(
devtools((...args) => ({
...createBearSlice(...args),
...createFishSlice(...args),
})),
)
[!IMPORTANT] Do not set the second parameter to
trueorfalseunless you want to override the default replacement logic