The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Puppeteer’s supported-browser table is the authoritative starting point for matching a Puppeteer release with Chrome for Testing or Firefox. For example, the current documentation snapshot pairs Puppeteer v25.12.0 with Chrome for Testing 154.0.8037.57 and Firefox 156.0.1. Those values change as Puppeteer releases, so check the live table for your exact version before upgrading or deploying.
How to find the browser version for your Puppeteer release
- Find your installed Puppeteer version. Run
npm ls puppeteerin the project directory, or inspect thepuppeteerentry in your package manifest or lockfile. - Open the official Puppeteer supported browsers table and locate that release.
- Use the listed browser build for the browser family you intend to automate: Chrome for Testing or Firefox.
- If your exact Puppeteer version is absent from the table, Puppeteer documents using the browser version for the immediately prior listed Puppeteer release.
The live documentation snapshot cited here lists Puppeteer v25.12.0 with Chrome for Testing 154.0.8037.57 and Firefox 156.0.1. Treat this as a dated snapshot, not a permanent compatibility guarantee: consult the live table when selecting versions.
What the comparison means
Release-to-browser mapping
The table is release-specific. Puppeteer bundles its releases closely with browser releases because browser changes can affect the automation protocols beneath the API. A matching table entry is a safer starting point than assuming any recent Chrome or Firefox build will behave the same way.
Chrome and Firefox use different default protocols
Puppeteer uses the Chrome DevTools Protocol (CDP) by default with Chrome, and WebDriver BiDi by default with Firefox. Both browsers are supported from Puppeteer v23.0.0 onward. Protocol behavior is one reason browser versions should be chosen from the supported mapping rather than by recency alone.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errors#1 Best Overall
- google search
- google map
- google plus
- youtube music
- youtube
History explains older version differences
Puppeteer v20.0.0 marked the move from Chromium downloads to Chrome for Testing. Firefox stable-release support began with v23.0.0; earlier supported Firefox builds were Nightly. If you are maintaining an older project, do not assume its browser expectations match those of a current release.
Use a pinned browser for repeatable runs
For reproducible local development and CI, pin Puppeteer and its browser rather than relying on whichever browser happens to be installed on a machine. Puppeteer says it tests and guarantees Chrome for Testing binaries, and its launch documentation says Puppeteer works best with the Chrome for Testing version downloaded by default. If you choose a system-installed browser instead, check the mapping and run your own automation tests in the target environment; the documentation does not establish that arbitrary browser builds are interchangeable.
Rank #2
- Easily control web videos and music with Alexa or your Fire TV remote
- Watch videos from any website on the best screen in your home
- Bookmark sites and save passwords to quickly access your favorite content
The @puppeteer/browsers CLI can install a specific Chrome for Testing version or the latest build for a milestone or channel. For example, install an exact version with:
npx @puppeteer/browsers install chrome@154.0.8037.57For the latest build on a channel, use the documented channel form, for example:
Rank #3
- Secure & Free VPN
- Built-in Ad Blocker
- Fast & Private browsing
- Secure private mode
- Cookie-dialogue blocker
npx @puppeteer/browsers install chrome@stableUse an exact version when matching a known environment matters; a channel such as stable is useful when you intentionally want the current channel build. See the official browser management documentation for supported install syntax and options.
Check Node.js and platform requirements separately
A correct browser match does not establish that the project runtime or deployment platform is supported. The current Puppeteer system requirements page lists Node 22.12 or later and documents supported operating systems and architectures. Check those requirements independently of the browser mapping, especially when moving between developer workstations, containers, and CI runners: Puppeteer system requirements.
Rank #4
- FEATURES
- ✓ Simple and elegant UI Design
- ✓ Bookmarks Import & Export
- ✓ Multi-Tabs Manage
- ✓ Disabled Javascript Mode
Why the browser binary may be missing after installation
Puppeteer’s installer downloads Chrome for Testing and, since v21.6.0, a chrome-headless-shell binary. Browser downloads can be controlled through Puppeteer configuration. Some modern package managers block install scripts by default, which can prevent those downloads and leave Puppeteer installed without its expected browser binary.
If launch fails because the executable is absent, check whether install scripts were allowed, review Puppeteer’s browser-download configuration, then run the appropriate installation step for your project. The official installation guide describes download behavior and configuration.
Free tools Windows power users keep installed
One-click scans. No signup required.
Best Value
- Google search engine.
Troubleshooting version and launch problems
- Your Puppeteer version is not in the table: use the browser version listed for the immediately prior Puppeteer release, then verify the result with tests in your own environment.
- The browser executable is missing: check whether package-manager policy blocked install scripts or configuration disabled downloads; install the expected browser binary as described in the installation guide.
- A system Chrome or Firefox behaves differently: compare its exact version with the supported-browser table. Prefer Puppeteer’s downloaded Chrome for Testing build when practical, and test any alternative browser in the actual deployment environment.
- Browser launches but automation behavior breaks after an upgrade: verify both the Puppeteer release and browser build, then consider protocol differences—CDP is the Chrome default and WebDriver BiDi is the Firefox default.
- Installation or launch fails on a new machine: verify Node.js version, operating system, and architecture against the system requirements in addition to checking the browser version.
Or skip the browser setup
If your goal is a website screenshot rather than browser automation, ScreenshotNeo provides a website screenshot API and MCP server. Its one-call GET endpoint returns an image or PDF without requiring you to install and manage a browser locally. 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 removes cookie banners, newsletter popups, and chat widgets before capture; 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 per month with no card, and paid plans start at $5 for 3,000. Sign up for 1,000 free screenshots a month, with no card required.
Frequently Asked Questions
Does the supported-browser table apply to every browser installed on my computer?
No. It provides the supported version mapping; a system-installed browser still needs to be checked against that mapping and tested in your target environment.
Can I use Puppeteer with Firefox?
Yes. Puppeteer supports Firefox from v23.0.0 onward and uses WebDriver BiDi by default for Firefox.
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.
