To remove browser binaries downloaded by Puppeteer, run npx @puppeteer/browsers clear. To keep the current browser but remove older cached versions, use Puppeteer’s trimCache() API. Removing the Puppeteer package from your project is a separate package-manager task and does not mean the browser cache has been cleared.
First decide what you want to uninstall
- The downloaded browser: remove browser binaries in Puppeteer’s cache with the browsers CLI or API.
- The Puppeteer dependency: remove the package through the package manager used by your project. The browsers CLI command is not a package-removal command.
- A browser installed for your whole computer: Puppeteer’s cache commands manage Puppeteer-installed browsers, not a general system-wide browser installation.
How do I remove the Chrome browser Puppeteer downloaded?
To inspect the browsers managed by the CLI, run:
npx @puppeteer/browsers listTo clear all installed browsers managed by that CLI, run:
As an Amazon Associate I earn from qualifying purchases.
npx @puppeteer/browsers clearThis is the broad cleanup option: it clears all installed browsers in the managed cache, rather than only one old version. Use it when you no longer need those downloaded browser binaries. If you still need Puppeteer automation, be prepared to install or provide a browser again before running it.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →How do I remove only older cached browsers?
Puppeteer’s trimCache() API removes non-current Chrome and Firefox binaries from the configured cache, keeping the current browser binaries according to Puppeteer’s configuration. It is a better fit than clearing everything when you want to retain the current browser for automation.
#1 Best Overall
Use care if multiple Puppeteer versions share the same cache: trimCache() does not check whether another version needs a binary before removing it. Check your projects’ cache-sharing arrangement before trimming a shared cache.
Where is the Puppeteer browser cache?
Starting with Puppeteer v19.0.0, the documented default cache directory is $HOME/.cache/puppeteer. That is a default, not a guarantee: the cacheDirectory configuration option or PUPPETEER_CACHE_DIR environment variable can point Puppeteer to another location. Check those settings before attempting manual cleanup or concluding that the cache is empty.
Rank #2
Puppeteer’s installation guide estimates Chrome for Testing download sizes at about 170 MB on macOS, 282 MB on Linux, and 280 MB on Windows. These are download-size estimates, not a promise about the space a particular machine will recover; actual cache contents depend on installed browsers and versions.
Does uninstalling Puppeteer delete Chrome?
Removing the Puppeteer package and removing the browser binaries are distinct tasks. Do not assume that removing the project dependency also clears its browser cache. Use Puppeteer’s browser-management CLI or API for the downloaded binaries, and use your project’s package manager to remove the dependency. Package-removal commands vary by package manager, so follow the instructions for the one your project uses.
Keep automating without a local Puppeteer download
If you want to continue browser automation without having Puppeteer manage a local browser download, Puppeteer recommends puppeteer-core for remote browser connections or separately managed browsers. A separately managed local executable can be supplied explicitly. Puppeteer says its downloaded browser is the one it works best with and does not guarantee identical behavior with other browser versions, so verify compatibility for your setup.
Or skip the browser setup
If your goal is to capture website screenshots rather than run browser automation, ScreenshotNeo offers a screenshot API and MCP server. A single GET request can return a PNG, JPEG, WebP, or PDF; its documented cleanup can accept consent banners and remove known consent platforms, newsletter popups, and chat widgets before capture. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed, and responses identify the page verdict and billing status. Its MCP server lets AI agents use screenshot tools directly.
For a quick API call, see the ScreenshotNeo documentation:
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpThe free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. Sign up for 1,000 free screenshots a month with no card.
Quick Recap
Best Value
- Used Book in Good Condition
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.
