Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallTo remove browser binaries downloaded by Puppeteer, first inspect the cache with npx @puppeteer/browsers list. To delete all browser downloads managed in that cache, run npx @puppeteer/browsers clear. For one browser build only, use the @puppeteer/browsers uninstall(options) API with its browser identifier, build ID, and cache directory.
This removes Puppeteer-managed browser downloads—not the Puppeteer npm package. The cache location may be customized, so verify it before clearing anything.
As an Amazon Associate I earn from qualifying purchases.
Find Puppeteer’s browser cache
Puppeteer’s standard cache is ~/.cache/puppeteer, a default used since Puppeteer v19.0.0. The location can differ if the project sets the cacheDirectory option or the PUPPETEER_CACHE_DIR environment variable. Check the project’s Puppeteer configuration and environment before running a cleanup command. See the Puppeteer configuration guide.
The distinction matters if several projects or Puppeteer versions share a cache: clearing it can remove browser builds other work expects to use.
#1 Best Overall
Inspect downloads before removing them
From the project directory, run:
npx @puppeteer/browsers listThis lists browser downloads in the managed cache; it does not delete anything. Check the output and confirm you are targeting the cache you intend to clean. The command is documented in the Puppeteer browsers API.
Choose the right cleanup method
| Method | What it removes | Use it when | Important caveat |
|---|---|---|---|
npx @puppeteer/browsers list |
Nothing; inspection only | You need to see what is cached first | It does not perform cleanup. |
npx @puppeteer/browsers clear |
All installed browser downloads managed in the cache | You want to clear the managed browser cache | It is broad and may affect other work using the same cache. |
@puppeteer/browsers uninstall(options) |
One specified browser build | You need selective removal | Requires the browser identifier, build ID, and matching cache directory. |
puppeteer.trimCache() |
Non-current Chrome and Firefox binaries according to current configuration | You want to prune older builds | It does not check whether another Puppeteer version sharing the directory needs those binaries. |
Clear every browser download in the cache
After confirming the cache location and that a full cleanup is intended, run:
Rank #2
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
npx @puppeteer/browsers clearThis clears all installed browsers managed in that cache. If it is shared across projects, consider the impact before proceeding; those projects may need to download a browser again. The command clears cached browser downloads. The documentation reviewed does not establish that it deletes browser profiles or other independent browser data, so treat profile cleanup as a separate task and inspect any custom profile location.
Uninstall only one browser build
The documented targeted method is the @puppeteer/browsers API’s uninstall(options) function. It needs the browser identifier, the exact build ID, and the cache directory containing that build; the platform can also be supplied. See the API reference for import and invocation details that match the version in your project.
Rank #3
The documented material does not provide a ready-to-run single-browser CLI command, so do not assume that a guessed command-line syntax is supported. Use the API reference for your installed version, and make sure its cache-directory value matches the cache you inspected.
Prune stale builds with trimCache()
puppeteer.trimCache() removes non-current Chrome and Firefox binaries based on the current Puppeteer configuration. It is not the same as clearing the whole cache: it preserves the binaries considered current by that configuration. However, it does not check whether a different Puppeteer version sharing the directory still needs a build. If multiple versions use the same cache, verify their requirements before trimming.
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
Browser downloads and the Puppeteer package are separate
This procedure concerns browser binaries, not uninstalling the JavaScript package. The puppeteer package downloads a compatible Chrome for Testing build during installation, while puppeteer-core does not download Chrome when installed. Removing the browser cache therefore does not itself uninstall Puppeteer from the project. See the Puppeteer installation guide.
The 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. Those are guide estimates, not current measurements, so actual space recovered can vary.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshooting cleanup
- The list or clear command does not show the expected browser: check
cacheDirectoryandPUPPETEER_CACHE_DIR. The project may be using a non-default cache. - A project downloads Chrome again after cleanup:
puppeteerdownloads a compatible browser during installation; removing the cache means a needed binary may have to be downloaded again. - You are unsure whether all builds can be removed: run the list command first, then choose between clearing all downloads, removing one build through the API, or trimming non-current Chrome and Firefox binaries.
- You want to remove a browser profile too: do not assume cache cleanup removes it. Check the profile’s configured or custom location separately.
- Selective uninstall fails or targets the wrong files: verify the browser identifier, exact build ID, and cache directory against the API documentation for your installed version.
Or skip the browser setup
If your goal is simply to capture a page rather than manage a local Puppeteer browser, ScreenshotNeo provides a screenshot API and MCP server. A single GET request can return a screenshot or PDF; its cleanup options remove cookie banners, popups, and chat widgets before the shot. Bot checks, blank pages, and failed loads are never billed, and AI agents can use its MCP server to take screenshots.
For example, save a WebP screenshot with cURL:
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 options and setup. The free plan includes 1,000 screenshots per month with no card required; paid plans start at $5 for 3,000. Sign up for ScreenshotNeo free.
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.
Free tools Windows power users keep installed
One-click scans. No signup required.
