What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
To remove browsers downloaded by Puppeteer, first check the cache with npx @puppeteer/browsers list. To delete every browser download in that cache, run npx @puppeteer/browsers clear. To remove only one browser build, use the @puppeteer/browsers API’s uninstall(options) method with the browser, build ID and cache directory. These steps remove cached browser binaries, not the Puppeteer npm package.
Find the Puppeteer browser cache
Puppeteer’s default browser cache is ~/.cache/puppeteer, a default used since Puppeteer v19.0.0. Your installation may use another directory: check the project’s Puppeteer configuration for cacheDirectory and check whether PUPPETEER_CACHE_DIR is set. Use the same cache location when inspecting or removing downloads.
The puppeteer package downloads a compatible Chrome for Testing build during installation. puppeteer-core does not download Chrome when installed, though browser binaries may be managed separately.
Inspect downloaded browsers before deleting them
From the project directory, run:
npx @puppeteer/browsers list
This lists browser downloads in the managed cache; it does not remove anything. Confirm that you are inspecting the intended cache, particularly if projects share a custom cache directory.
#1 Best Overall
Clear all browsers in the cache
To remove all browser downloads managed in the cache, run:
npx @puppeteer/browsers clear
This is a broad cleanup: it removes all installed browsers in that cache, not just the build used by the current project. Check whether other projects or Puppeteer versions depend on the same directory first. The documented operation concerns cached browser binaries; it does not establish that separate browser profiles or other independent browser data are deleted.
Uninstall one browser build
For selective removal, use the @puppeteer/browsers API’s uninstall(options) method. It requires the browser identifier, build ID and cache directory; a platform can also be supplied. The cache directory must match the location where that build was installed.
Rank #2
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
The documented material does not give a single-browser CLI command or a ready-to-run API invocation. Consult the API reference for the package version you use to confirm its import and invocation details rather than guessing a command.
Crashes, 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 minutePC 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 & 11Prune non-current browser versions with trimCache()
puppeteer.trimCache() is a narrower cleanup option: it removes non-current Chrome and Firefox binaries according to the current configuration. It is not a safe substitute for checking shared-cache dependencies. The method does not check whether another Puppeteer version using the same cache still needs those binaries.
Choose the right cleanup method
| Method | What it does | Best suited to | Important caution |
|---|---|---|---|
npx @puppeteer/browsers list |
Inspects browser downloads in the cache. | Checking what is installed before cleanup. | It does not delete anything. |
npx @puppeteer/browsers clear |
Removes all browsers managed in the cache. | Clearing the entire browser cache. | It affects every browser download in that cache. |
uninstall(options) |
Removes a specified browser build. | Selective removal. | Requires the browser, build ID and matching cache directory. |
puppeteer.trimCache() |
Removes non-current Chrome and Firefox binaries according to current configuration. | Pruning older builds. | It does not check whether other Puppeteer versions sharing the cache need them. |
Browser downloads and package removal are different
Clearing the browser cache does not uninstall Puppeteer from your project. If you mean to remove the JavaScript package too, handle that separately through your project’s package manager. Conversely, removing the package is not the documented method for clearing browser downloads retained in the cache.
Rank #3
The official installation guide estimates the automatically downloaded Chrome for Testing binary at approximately 170 MB on macOS, 282 MB on Linux and 280 MB on Windows. These are guide estimates, not current measurements; actual disk space recovered depends on the browser builds present in your cache.
Troubleshooting
The list or clear command does not show the browser I expected
Check cacheDirectory in Puppeteer configuration and the value of PUPPETEER_CACHE_DIR. A command run against a different cache will not inspect or clear the directory containing the browser you are looking for.
A project downloads Chrome again after cleanup
The puppeteer package downloads a compatible Chrome for Testing build at installation. If that package or a setup step installs the browser again, the cache can be repopulated. puppeteer-core does not download Chrome when installed.
Rank #4
- Brand: Wiley
- Set of 2 Volumes
- A handy two-book set that uniquely combines related technologies Highly visual format and accessible language makes these books highly effective learning tools Perfect for beginning web designers and front-end developers
Selective uninstall cannot find the build
Verify the browser identifier and build ID, then check that the API call uses the exact cache directory containing the installation. For import and invocation syntax, follow the API reference for your installed @puppeteer/browsers version.
Another project stops finding its browser
If projects share a cache, clearing all browsers or trimming non-current builds can remove binaries another project expects. Inspect the cache and check the configurations of projects that use it before broad cleanup.
You want to delete browser profiles too
The documented cache cleanup describes browser binaries and does not establish whether separate profiles are removed. Treat profile cleanup as a separate task and inspect the custom profile location used by your application.
Free tools Windows power users keep installed
One-click scans. No signup required.
Or skip the browser setup
If your goal is to capture website screenshots rather than run browser automation, ScreenshotNeo returns an image or PDF through a single API request. Its clean-capture steps accept consent banners and remove more than 60 known consent platforms, newsletter popups and chat widgets before capture; each step can be turned off. Bot checks, blank pages, timeouts, failed loads and cache hits are not billed, and the response identifies the page verdict and billing status in headers. An MCP server provides screenshot and page-information tools for AI agents.
Example cURL request (replace the URL with the page you need):
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 API documentation for request options. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots. Sign up for 1,000 free screenshots a month with no card.
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.
Recommended Free Tools
