The short answer
Yes. Rebuilt or re-downloaded automatically when needed.
What is it?
Puppeteer, Google’s Node.js library for controlling Chrome, downloads a matching Chrome for Testing (and sometimes chrome-headless-shell) into ~/.cache/puppeteer when you install it in a project. Every Puppeteer version you install can add another browser build. Typically a few hundred MB per version.
What happens if you delete it?
The browser is downloaded again the next time you run npm install in a project that uses Puppeteer, or when you run npx puppeteer browsers install chrome. Nothing else is lost.
How to remove it properly
Move the folder to the Trash in Finder (Go › Go to Folder… ~/.cache/puppeteer). To keep only some versions, open it and remove the older version folders inside.
Quit the app that uses it, then move it to the Trash. Empty the Trash when you’re sure.
How MoreRoom helps
MoreRoom recognises this item, shows its real size and when it was last used, and labels it “Safe to remove”. In the free version you can move it to the Trash in one click, with Undo; Pro collects every safe item at once.
Frequently asked questions
Is it safe to delete the Puppeteer browser cache (~/.cache/puppeteer)?
Yes. Rebuilt or re-downloaded automatically when needed. The browser is downloaded again the next time you run npm install in a project that uses Puppeteer, or when you run npx puppeteer browsers install chrome. Nothing else is lost.
Will Puppeteer browsers come back after I delete it?
Yes. The browser is downloaded again the next time you run npm install in a project that uses Puppeteer, or when you run npx puppeteer browsers install chrome. Nothing else is lost.
How do I remove Puppeteer browsers properly?
Move the folder to the Trash in Finder (Go › Go to Folder… ~/.cache/puppeteer). To keep only some versions, open it and remove the older version folders inside.