Can You Delete the .nuxt Folder? Yes, It's Safe

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

**/.nuxt

Yes, you can delete the .nuxt folder. It holds compiled build artifacts for one Nuxt project, and Nuxt rebuilds it from scratch the next time you run the dev server or a build. You lose nothing except a slightly slower first startup while it regenerates.

What it is

.nuxt is a hidden folder that Nuxt, the Vue framework, creates in the root of every project. When you run nuxt dev or nuxt build, the framework compiles your pages, components, and configuration into intermediate files it can actually serve: generated route definitions, auto-import maps, TypeScript declarations, and bundler output all land here. It's a working directory, not part of your source code, which is why Nuxt's own starter templates keep it out of version control.

The folder gets rewritten constantly: every dev session and every build drops fresh files into it. How big it gets tracks the size of your app. A small project might hold a few dozen megabytes; a large one with many pages and dependencies can reach several hundred. Multiply that by every Nuxt project on your Mac, including the ones you abandoned a year ago, and it starts to add up.

Is it safe to delete?

Deleting .nuxt is safe. Nothing in it is yours: no source code, no content, no configuration. The entire folder is derived from your project files, so Nuxt rebuilds it automatically the next time you run npm run dev or npm run build. The only cost is that first startup, which takes longer because the compiled files are gone and Nuxt has to produce them again.

One thing to watch: don't delete it while the dev server is running. Nuxt actively reads and writes files in there during a session, and pulling them out from under it can produce confusing errors until you restart. Stop the server, delete the folder, start again. Diskmack finds .nuxt folders across all your projects automatically and cleans them the safe way.

How to check its size

In Finder: In Finder, choose Go > Go to Folder (or press Command-Shift-G), type your project's path with /.nuxt on the end, for example ~/Projects/my-app/.nuxt, and press Return. Select the folder and press Command-I to see its size. If you're browsing the project normally and can't see it, press Command-Shift-Period to show hidden files.

In Terminal:

du -sh ~/Projects/my-app/.nuxt

Replace ~/Projects/my-app with your project's actual path; the ~ stands for your home folder. If the path has spaces in it, type du -sh followed by a space, then drag the .nuxt folder from Finder into the Terminal window and press Return; Terminal fills in the path with the right escaping.

How to clean it

Stop the Nuxt dev server if it's running: click into the terminal window running it and press Control-C.
Open your project folder in Finder.
Press Command-Shift-Period if hidden files aren't showing. The .nuxt folder appears slightly grayed out.
Drag .nuxt to the Trash, or right-click it and choose Move to Trash.
Empty the Trash to actually reclaim the space.
Next time you run npm run dev or npm run build, Nuxt recreates the folder on its own.

There is one .nuxt folder per project. If you have several Nuxt projects on your Mac, each has its own copy, and the abandoned projects are the best candidates for cleaning because theirs will never grow back.

Will it come back?

Yes, and immediately. The next nuxt dev or nuxt build recreates the folder in full, because Nuxt cannot run without it. Deleting it from an active project only buys you space until the next time you work on that code. Where the space stays reclaimed is in dead projects: an abandoned Nuxt app never regenerates its .nuxt folder, so that cleanup is permanent.

Common questions

Will deleting .nuxt break my project?

No. Everything in it is generated from your source files, and the next dev server start or build recreates it. Your first startup afterward will be slower while Nuxt recompiles. That's the whole cost.

What about the .output folder?

In Nuxt 3, nuxt build writes the deployable production bundle to .output, while .nuxt holds the intermediate files. Both are generated and both come back on the next build, so .output is equally fine to remove as long as you're not about to deploy from it.

Should .nuxt be in .gitignore?

Yes, and Nuxt's starter templates put it there by default. If .nuxt shows up in your git status, add it to .gitignore. Committing build output bloats the repository and guarantees merge noise for no benefit.

Can I delete .nuxt from every project at once?

Yes, provided none of them has a dev server running. Each project rebuilds its own copy the next time you run it. The copies in projects you no longer touch won't come back at all, which makes them the most rewarding to clear.