Remix & React Router Framework Build Cache (.cache/remix)

Bottom Line: It is 100% safe to delete .cache/remix and build/ folders. Remix automatically rebuilds server and client bundle manifests on your next remix dev or remix build.

Why Does Remix Build Cache Exist?

Remix (and React Router v7) compiles full-stack web applications into client JavaScript bundles and server-side route handlers. Vite and Esbuild cache transformed modules inside .cache/remix and build/.

• Primary Purpose: Incremental route bundling, SSR (Server-Side Rendering) module resolution, and asset fingerprinting.
• Storage Impact: Project builds accumulate intermediate bundles consuming 500 MB to 5 GB.
• Cache Issues: Stale route manifest caches can cause Route manifest mismatch or loader data hydration errors.

What Happens If You Delete Remix Cache?

• System Safety: ✅ 100% Safe to Delete. Source code inside app/ is untouched.
• Automatic Regeneration: Running npx remix build re-compiles fresh server and client bundles.
• Reclaimed Storage: Reclaims 500 MB to 5 GB of disk space.

How to Delete Remix Build Cache

# Delete Remix build cache and distribution bundles
rm -rf .cache/remix build public/build

Frequently Asked Questions (FAQ)

Will deleting Remix cache clear user session cookies?

No. .cache/remix is a local developer build directory. User session cookies and database records are stored in external data stores.