Can I Delete .parcel-cache? Yes, and Here's the Safe Way

Yes, it's safe to deleteDiskmack safety tier: Safe to clean

**/.parcel-cache

Yes, you can delete .parcel-cache. It's Parcel's incremental build cache, and the bundler rebuilds it from scratch the next time you run a dev server or a build. You lose nothing except one slower first build. If the folder sits in a project you no longer touch, it's pure dead weight.

What it is

Parcel is a JavaScript bundler, the tool that turns a web project's source files into something a browser can run. The .parcel-cache folder is where Parcel 2 keeps its incremental build cache: transformed copies of your source files, a graph of how every module in the project connects, and the intermediate output of its plugins. It lives at the top level of each project that uses Parcel, next to package.json, and it's hidden in Finder because the name starts with a dot.

The cache exists to make rebuilds fast. On the first build, Parcel processes every file from scratch and saves the results. After that it only reprocesses what changed, which is why the second run starts so much faster than the first. The cost is disk space: the cache holds processed copies of much of your project and its dependencies, so on a mid-size app it often reaches several hundred megabytes, and heavy projects can push past a gigabyte. Every Parcel project on your Mac has its own copy. (Parcel 1 used a folder named .cache instead; same idea, older name.)

Is it safe to delete?

Deleting .parcel-cache is safe. It contains no source code, no configuration, and nothing you wrote. Everything inside is derived from your project files, and Parcel rebuilds it automatically on the next build or dev server start. The only cost is time: that first rebuild processes everything from scratch, so it takes about as long as the very first build of the project did.

The one thing worth doing first is stopping any running Parcel dev server, since deleting the cache out from under it can produce confusing errors until you restart. For projects you've abandoned there is no cost at all; the folder is dead weight. Diskmack identifies every .parcel-cache across your projects automatically and cleans them the safe way. Clearing this cache is also the standard first move when Parcel misbehaves, because a stale cache is behind a lot of odd build errors.

How to check its size

In Finder: In Finder, choose Go > Go to Folder (or press Cmd+Shift+G) and enter your project's path, for example ~/Projects/my-app. Press Cmd+Shift+. (period) to show hidden files, click the .parcel-cache folder once, then press Cmd+I to see its size.

In Terminal:

du -sh ~/Projects/my-app/.parcel-cache

Replace ~/Projects/my-app with your project's actual path; the ~ expands to your home folder. If the path contains spaces, quote everything after the ~/, like du -sh ~/"My Projects/my app/.parcel-cache".

How to clean it

Quit any running Parcel dev server: click its Terminal window and press Ctrl+C.
Open your project folder in Finder.
Press Cmd+Shift+. (period) so hidden files appear. Folders whose names start with a dot are invisible by default.
Drag the .parcel-cache folder to the Trash.
Empty the Trash to actually free the space.
The next time you run Parcel it rebuilds the cache. Expect that first build to be slower than usual.

Parcel has no cache-cleaning command; deleting the folder is the accepted method. If you only want to bypass the cache for one run, build with the --no-cache flag instead of deleting anything.

Will it come back?

Yes, immediately and by design. The first Parcel build after deletion recreates .parcel-cache, and because that build reprocesses everything, the folder is back to roughly its old size right away. That's fine for a project you're actively working on, since the cache is exactly what keeps your rebuilds fast. The lasting wins are the .parcel-cache folders in projects you haven't opened in months. Nothing ever triggers a build there, so the cache never regrows, and cleaning it is a one-time, permanent recovery.

Common questions

Why is my .parcel-cache folder so big?

It stores processed copies of every file Parcel touches, including dependencies from node_modules, plus the build graph that ties them together. Bigger apps and bigger dependency trees mean a bigger cache. Several hundred megabytes is normal for a mid-size project.

How do I find every .parcel-cache folder on my Mac?

In Terminal, run: find ~ -type d -name .parcel-cache -prune -exec du -sh {} + 2>/dev/null. It prints the size and path of each one. Searching your whole home folder can take a minute or two, so let it finish.

Should .parcel-cache be in my .gitignore?

Yes. It's machine-generated and specific to your Mac, so it doesn't belong in version control. Most Parcel setups already ignore it; check your .gitignore for a .parcel-cache line and add one if it's missing.

Parcel is throwing strange errors after an upgrade. Will clearing the cache help?

Often, yes. A stale cache written by an older Parcel version or plugin is a common cause of mysterious build failures, and deleting .parcel-cache is the usual first fix. You can also run one build with --no-cache to confirm the cache is the culprit before deleting it.