PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteTo remove browser binaries Puppeteer downloaded, run npx @puppeteer/browsers clear. That clears all installed browsers managed by the Puppeteer browsers CLI. If you mean removing Puppeteer from your project, uninstall the package separately with your package manager; removing the package and clearing its browser cache are different tasks.
First decide what you want to uninstall
Puppeteer and the browser it downloads are separate. The puppeteer package normally downloads Chrome for Testing and chrome-headless-shell. Removing that package is a project dependency change; it is not the command for clearing downloaded browser binaries.
| What you want to remove | What to do | Effect |
|---|---|---|
| Every installed browser managed by the browsers CLI | npx @puppeteer/browsers clear |
Clears all installed browsers in the CLI-managed cache. |
| Non-current Chrome and Firefox binaries in the configured cache | Use Puppeteer’s trimCache() API |
Removes non-current versions, keeping current binaries according to Puppeteer’s configuration. |
| The Puppeteer dependency in your project | Remove the package with your package manager | Removes the project dependency; handle the browser cache separately if you also want to clear it. |
How to remove the Chrome browser Puppeteer downloaded
Inspect the installed browsers first
If you want to see what is installed before deleting anything, use the browsers CLI’s list command:
npx @puppeteer/browsers listThis is optional. It is useful when you want to check which browsers the CLI manages before clearing them.
Recommended Free Tools
#1 Best Overall
Clear all CLI-managed browser installs
Run:
npx @puppeteer/browsers clearThis is the broad cleanup option: it removes all installed browsers managed by that CLI, rather than just a particular old version. Use it when you no longer need those local browser binaries. If you still run Puppeteer locally afterward, it may need to download a browser again.
How to remove only non-current cached browsers
For ongoing cache cleanup, Puppeteer exposes trimCache(). It removes non-current Chrome and Firefox binaries from the configured cache while preserving current browser binaries according to Puppeteer’s configuration. This is narrower than clearing every installed browser.
Use caution if multiple Puppeteer versions share the same cache: trimCache() does not check whether another version needs a binary before removing it. A cleanup that is appropriate for one project may therefore affect another project using that shared cache.
Rank #2
Where is the Puppeteer browser cache?
Starting with Puppeteer v19.0.0, the documented default cache directory is $HOME/.cache/puppeteer. Do not assume that path applies to your installation: the cacheDirectory setting or the PUPPETEER_CACHE_DIR environment variable can move the cache. Check your project and environment configuration before looking for installed browser files.
Use the Puppeteer browser CLI or API when possible rather than manually deleting a directory. A configured cache may be in a different location, and deleting files directly can remove binaries another project expects to use.
Does uninstalling Puppeteer delete Chrome?
Removing the Puppeteer package and removing downloaded browser binaries are separate operations. Package removal is handled by your project’s package manager; use the Puppeteer browser-management CLI or API to manage its downloaded browsers. Do not assume that removing one automatically performs the other.
If you remove the browser binaries but later run Puppeteer in a setup that expects a locally managed browser, the browser may need to be installed again.
Keep automating without a locally downloaded browser
If you want to continue browser automation without Puppeteer managing a local browser download, Puppeteer recommends puppeteer-core for remote browser connections or separately managed browsers. You can provide a locally managed executable explicitly as well. Puppeteer says its downloaded browser is the one it works best with; it does not guarantee the same behavior with other browser versions.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Or skip the browser setup
If your task is simply to capture website screenshots—not to run a custom Puppeteer automation script—you can use ScreenshotNeo instead of installing and maintaining a local browser. It provides a screenshot API and an MCP server for AI agents.
For example, request a screenshot with one GET call (replace YOUR_API_KEY with your key):
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo documentation for request options and response details. Cookie banners, popups, and chat widgets are removed before the shot; bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots. The Free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000. Sign up for ScreenshotNeo’s free plan.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshooting
The browser is still taking up space after package removal
Removing a project dependency is not the same operation as clearing the browser cache. Check the configured cache location and use npx @puppeteer/browsers clear if you want to remove all browser installs managed by the CLI.
The clear command does not seem to target the cache you expected
Check whether cacheDirectory or PUPPETEER_CACHE_DIR sets a custom location. The default path applies only when the cache has not been configured elsewhere.
Best Value
- Used Book in Good Condition
A different project stops finding its browser after trimming
Projects may share a cache while using different Puppeteer versions. Since trimCache() does not check whether another version needs a removed binary, install the browser version required by the affected project again or avoid trimming a shared cache without checking those projects’ needs.
Puppeteer downloads a browser again
That can happen if you run a setup that expects Puppeteer’s locally downloaded browser after clearing the cache. If you intend to continue automating, configure a browser that you manage separately or use the documented puppeteer-core approach for remote or separately managed browsers.
Download-size context
Puppeteer’s installation documentation estimates Chrome for Testing downloads at about 170 MB on macOS, 282 MB on Linux, and 280 MB on Windows. These are platform-specific download-size estimates, not a guarantee of how much disk space an uninstall will recover: your cache may contain multiple browser versions or other files.
Free tools Windows power users keep installed
One-click scans. No signup required.
Frequently Asked Questions
Can I remove just one browser version instead of clearing the whole cache?
The browser-management API exposes an uninstall(options) operation for browser removal. Choose it when you need a targeted removal rather than the CLI’s clear-all operation.
Can I keep using Puppeteer with a browser installed outside its cache?
Yes. Puppeteer documents puppeteer-core for remote connections or separately managed browsers, and a locally managed executable can be supplied explicitly. Compatibility with other browser versions is not guaranteed.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
