To list browser builds managed in Puppeteer’s browser cache, run npx @puppeteer/browsers list. In Node.js, use getInstalledBrowsers({cacheDir}) from @puppeteer/browsers. Neither method is a complete inventory of every browser installed on your computer: they report what is present in the cache directory being checked.
List browsers in Puppeteer’s cache from the command line
Run the documented CLI command from a terminal:
npx @puppeteer/browsers listThis lists browser builds found in the Puppeteer browser cache. It is the quickest way to check which managed builds are available without writing a script. If the result is empty or unexpected, first verify which cache directory your installation uses.
List cached browsers from Node.js
For a script or diagnostic tool, call getInstalledBrowsers and pass the cache directory that contains the managed installations:
import {getInstalledBrowsers} from '@puppeteer/browsers';
const browsers = await getInstalledBrowsers({
cacheDir: '/path/to/puppeteer-cache',
});
console.log(browsers);The function returns metadata for browser installations in that directory. The exact metadata fields depend on the installed package’s API and types; consult those types if your script needs to read a particular field. See the @puppeteer/browsers API documentation for the CLI and browser-management API.
#1 Best Overall
What the listing includes—and what it does not
These commands enumerate Puppeteer-managed browser builds in a cache. They do not promise to search operating-system application folders, package-manager databases, directories on PATH, containers, or remote browser services. If your goal is “what is in Puppeteer’s cache?”, use the CLI or API. If your goal is “what browsers are installed anywhere on this machine?”, that requires a separate, operating-system-specific inventory.
Launching a system Chrome is a different task from listing cached browsers. Puppeteer’s launch options let you select a regular Chrome installation using a release channel or specify a binary with executablePath. These options select a browser to launch; they are not a general browser-discovery API. The LaunchOptions documentation describes these choices. The @puppeteer/browsers documentation says system-browser launching is limited to Chrome/Chromium.
Rank #2
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
Find the cache directory Puppeteer is using
Since Puppeteer v19.0.0, its default browser cache is $HOME/.cache/puppeteer. That default can be changed through Puppeteer configuration or the PUPPETEER_CACHE_DIR environment variable. The API also accepts an explicit cacheDir, so make the directory in your script match the one used for installation.
The standard puppeteer installation workflow downloads Chrome for Testing by default. puppeteer-core does not download Chrome and is intended for setups where the browser is managed separately; provide a channel or executablePath when launching it. See Puppeteer’s installation guide and configuration documentation.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #3
Choose the right method for the question
| Method | Answers | Scope |
|---|---|---|
npx @puppeteer/browsers list |
Which builds are in the managed cache? | Quick command-line inventory of the browsers cache. |
getInstalledBrowsers({cacheDir}) |
What browser metadata is in this chosen cache? | Programmatic inventory of the directory you specify. |
channel or executablePath at launch |
Which known system Chrome should Puppeteer launch? | Launch selection, not an inventory of installed browsers. |
Check browser compatibility by Puppeteer version
The set of browser versions compatible with Puppeteer changes by release. The Puppeteer supported-browser table for v25.12.0 maps that release to Chrome for Testing 154.0.8037.57 and Firefox 156.0.1. Treat those as version-specific mappings, not as a promise that another Puppeteer release uses the same browser versions; check the current supported browsers table for the release you have installed.
Puppeteer supports Chrome and Firefox. Its older headless mode is distributed separately as chrome-headless-shell beginning with Puppeteer v21.6.0, according to the installation guide.
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
Troubleshoot an empty or incorrect listing
- The CLI reports no installed browsers: check whether the browser was installed into a different cache, under another user account, or with a different environment or configuration. The CLI only lists the cache it is using.
- The Node.js result is empty: confirm that
cacheDirpoints to the directory containing the managed browser installations. An explicit but incorrect path will not find installations in another cache. - You installed
puppeteer-coreand expected a downloaded browser: that package does not download Chrome. Manage the browser separately, then usechannelorexecutablePathto launch the system Chrome. - You need to know whether a system browser exists: the cache listing cannot establish that. Check the relevant operating-system locations or package manager, then provide the known Chrome channel or executable path when launching.
- A browser version does not match expectations: compare the installed Puppeteer release with the supported-browser table for that release rather than assuming a version mapping from another release still applies.
Or skip the browser setup
If your actual goal is to capture a webpage rather than inspect a local browser cache, ScreenshotNeo can return a screenshot or PDF with one GET request. Its API accepts the page URL and returns PNG, JPEG, WebP, or PDF output. The API uses the same parameter names as other screenshot APIs, which can make switching easier. See the ScreenshotNeo API documentation.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo accepts cookie and consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers report the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots.
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 →Sign up for ScreenshotNeo’s free plan to try 1,000 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.
