Is it safe to delete ~/.cache/puppeteer?
Your tools make it again on their own. The cost is a slower next run.
- What it is
- Puppeteer's own private copy of the Chrome browser, downloaded so it can automate a browser without depending on one already being installed. Puppeteer's documentation states browsers are cached at exactly this path since v19.0.0.
- Made by
- Puppeteer
- If you remove it
- Puppeteer re-downloads its private copy of Chrome the next time a project needs it, which requires an internet connection and can take several minutes. Until that download finishes, anything using Puppeteer fails to launch a browser. Check this folder's size in Spaceific to see how much has to come down again.
- How it comes back
- Run: npx puppeteer browsers install
npx puppeteer browsers install
The tool's own commands
npx @puppeteer/browsers clear“To clear all installed browsers, use theclearcommand.” Puppeteer “stores browsers in~/.cache/puppeteer”.From pptr.dev/browsers-api, read 3 Nov 2026.
The proof
- Verified by
- vendor documentation
- Checked on
- macOS 26.6.2, Chrome for Testing 150.0.7871.24
- Catalogue
- Spaceific's rules.json 1.2.0, 2 Nov 2026. The whole file.
Related
- User cache root
~/.cacheNo rule yet - Every rule
Spaceific shows this rule for this folder in the app, checks it again at the moment you act, and moves only to the Trash, with Put Back. What Spaceific is.