How to clear the .next and .turbo cache

.next is Next.js build output plus its build cache; .turbo holds Turborepo’s local task cache (Turborepo 2.0+ keeps it in .turbo/cache). Both are rebuilt automatically, and deleting them is also the classic fix for strange dev-server errors.

One project

Stop next dev first.

rm -rf .next .turbo node_modules/.cache

Remove-Item -Recurse -Force .next, .turbo, node_modules\.cache -ErrorAction SilentlyContinue

To keep the build output but drop only Next’s build cache, delete .next/cache instead.

A whole monorepo or code folder

List first, skipping anything inside node_modules:

find . -name node_modules -prune -o -type d \( -name .next -o -name .turbo \) -prune -print

Read the list. When it only shows folders you mean, replace -print with -exec rm -rf {} + and run it again.

Older Turborepo

Before 2.0, Turborepo cached in node_modules/.cache/turbo. The one-project command above covers both locations.

Measure with devdisk

devdisk is a free, read-only scanner. It finds every .next (next to a package.json) and every .turbo folder and lists them under Safe to regenerate. It never deletes anything; it only shows sizes and writes a cleanup script you read and run yourself.

curl -fsSLO https://disk.sadana.app/devdisk.py && python3 devdisk.py

iwr https://disk.sadana.app/devdisk.py -OutFile devdisk.py; py devdisk.py

Run free scannerSample report

FAQ

More cleanup guides

• Clear Xcode DerivedData
• Delete node_modules
• Clear Gradle cache
• Delete Ollama models
• Free Docker disk space
• Clear Homebrew cache
• Prune pnpm store
• Clear Yarn cache
• Clean Rust target/
• Clear pip & uv cache
• Clear Hugging Face cache
• Delete Android emulators