This page is also available as Markdown: request this page's URL with an
Accept: text/markdown header. For an index of Next.js documentation, see /docs/llms.txt.Turbopack Memory Eviction
Last updated July 7, 2026
Usage
turbopackMemoryEviction controls whether Turbopack reclaims memory while the persistent (FileSystem) cache is enabled. After Turbopack writes a snapshot of its cache to disk, it can 'evict' the in-memory copies of that data and reload them from disk on demand.
Currently there are three options
false: never evict. Cached data stays in memory for the lifetime of the process.'auto'(default): evict after a snapshot only once enough memory has been allocated since the last eviction to make it worthwhile. Leverages thresholds and memory pressure feedback from the operating system.'full': evict all possible data from memory every time we save to disk.
Good to know: This option only has an effect in
next devsessions when the FileSystem Cache is enabled, since eviction relies on data already being persisted to disk. It is experimental and under active development.
next.config.ts
import type { NextConfig } from 'next'
const nextConfig: NextConfig = {
experimental: {
turbopackMemoryEviction: 'auto',
},
}
export default nextConfigVersion Changes
| Version | Changes |
|---|---|
v16.3.0 | turbopackMemoryEviction released as experimental. |
Was this helpful?