Windows 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 reinstallOutdated 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 matchPuppeteer is a Node.js library for automating browsers. To get a reliable start, install the package that matches how you manage browsers, use Puppeteer’s bundled browser unless you have a specific reason not to, and check browser dependencies and profile permissions when launch fails. The guidance below reflects Puppeteer 25.12.0 documentation checked October 3, 2026; verify the live requirements and troubleshooting pages when working with another release.
What is Puppeteer, and which browsers does it support?
Puppeteer is a Node.js browser-automation library. According to the project FAQ, Puppeteer supports Chrome and Firefox from v23.0.0 onward. Chrome uses the Chrome DevTools Protocol (CDP) by default; Firefox uses WebDriver BiDi by default. The project describes WebDriver BiDi as production-ready for both supported browsers and says it will continue supporting Chrome through CDP. Protocol support can differ, so do not assume every API behaves identically in both browsers. See the Puppeteer FAQ.
As an Amazon Associate I earn from qualifying purchases.
Why can’t Puppeteer find Chrome?
The standard puppeteer package normally downloads a compatible Chrome for Testing during installation. If your package manager blocks install scripts, that download may not happen, and launch can fail with a “Could not find Chrome” error. Follow the installation guide to install Puppeteer’s browser after package installation, or allow the install script according to your package manager’s policy.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
From Puppeteer v19 onward, the default browser cache is ~/.cache/puppeteer. Set PUPPETEER_CACHE_DIR to relocate it, and make sure the runtime user can read the browser files. The configuration API also documents browser-download and executable settings.
#1 Best Overall
Choose the package that fits browser ownership
| Package | Browser management | Use it when |
|---|---|---|
puppeteer |
Downloads a compatible browser and provides workflow defaults. | You want Puppeteer to manage the local browser installation. |
puppeteer-core |
Does not download Chrome; your application manages the browser or connects to a remote one. | You already manage a browser installation or use a remote-browser workflow. |
For puppeteer-core, supply an executable path or browser channel for a local browser, or configure the appropriate remote connection. The package distinction is described in the installation guide.
Why won’t Chrome launch on Linux or in a container?
Launch failures are often environment-specific. Check the browser dependencies, sandbox configuration, and writable directories rather than adding a broad set of flags.
Check shared libraries
Use ldd on the browser executable to identify unresolved shared-library dependencies. Install the dependencies appropriate to your distribution; package names differ across Linux distributions, so use the current Puppeteer troubleshooting guide and its links to Chromium’s maintained dependency lists instead of copying a package list from another system.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsKeep the sandbox configured
Chrome’s sandbox helps protect the host from untrusted page content. Configure it for the user and container environment. Puppeteer’s troubleshooting guide strongly discourages --no-sandbox; consider it only when you absolutely trust the content being loaded and understand the security trade-off.
Rank #2
- HTML CSS Design and Build Web Sites
- Comes with secure packaging
- It can be a gift option
Make profile and cache directories writable
Puppeteer needs a writable user-data directory. In containers, prefer a suitably configured non-privileged user and writable browser profile and cache locations. A permission problem can prevent startup even when the browser executable is present.
Check platform-specific constraints
- Ubuntu 23.10 and later: AppArmor user-namespace restrictions may interfere with Chrome for Testing.
- Windows: policy conflicts with Puppeteer’s default extension behavior or sandbox permissions can affect launch.
- Alpine Linux: Chrome is not supported out of the box.
These are targeted checks, not universal explanations. The official troubleshooting guide covers platform-specific cases and notes that some guidance relies substantially on community contributions.
Which Chrome version works with Puppeteer?
The browser bundled for the installed Puppeteer release is the compatibility baseline. Puppeteer pairs releases with specific browser releases to protect compatibility with the underlying automation protocols. The launch API allows a system Chrome channel or an explicit executable path, but the project only guarantees compatibility with its bundled browser. Use another installation when integration with an existing browser is necessary, and validate it in your actual environment. See LaunchOptions.
Can Puppeteer use Firefox?
Yes. The official FAQ says Firefox support begins with Puppeteer v23.0.0; Firefox uses WebDriver BiDi by default, while Chrome uses CDP by default. Select the browser explicitly when launching and check the current protocol and API support details for the feature you need. Do not assume that behavior documented for one browser protocol automatically applies to the other. See the FAQ and launch options.
Rank #3
What Node.js and TypeScript versions are required?
The Puppeteer 25.12.0 system requirements page lists Node.js 22.12 or later and TypeScript 5.0.1 or later when TypeScript is used. These are version-specific requirements, not timeless minimums. Check the current system requirements for the Puppeteer release and deployment platform you are using before updating a runtime image.
How do I interact with a page and take a screenshot?
A basic workflow is to launch a browser, create a page, navigate, wait for the state you need, interact, capture with Page.screenshot(), and close the browser. Puppeteer recommends locator APIs as the higher-level interaction approach; waitForSelector remains available as a lower-level DOM wait. The following runnable Node.js example uses the default bundled browser and writes a screenshot to disk.
const puppeteer = require('puppeteer');
(async () => {
const browser = await puppeteer.launch();
try {
const page = await browser.newPage();
await page.goto('https://example.com', { waitUntil: 'networkidle2' });
await page.screenshot({ path: 'page.png', fullPage: true });
} finally {
await browser.close();
}
})();Install the puppeteer package and run this script with Node.js. Navigation’s waitUntil option is a page-load condition, not a guarantee that every application-specific widget or late-changing element has finished rendering. If the target content has a known selector, wait for it before capturing.
Recommended Free Tools
Use a locator for interaction
Locators provide a higher-level way to find and interact with page elements. For example, after navigation you can use await page.locator('button').click() for a matching button. Choose a selector that identifies the intended control; a generic selector may match multiple elements or the wrong one.
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
Use waitForSelector for a lower-level DOM wait
When the immediate need is to wait for a matching element to appear in the DOM, await page.waitForSelector('.ready') is available. It waits for DOM presence, not necessarily for the page’s data or visual state to be complete. Use an application-specific condition where DOM presence alone is insufficient.
For current interaction and screenshot guidance, see Puppeteer’s page interactions and screenshot guide.
Which launch settings should I change?
Set the option that addresses the actual environment or symptom. Puppeteer’s LaunchOptions API documents browser selection, headless mode, command-line arguments, executable or channel selection, startup timeout, and userDataDir. Its configuration API covers browser downloads, cache location, and executable settings, including environment-variable overrides.
Free tools Windows power users keep installed
One-click scans. No signup required.
- Browser choice: select the browser you intend to automate, particularly when using Firefox.
- Headless mode: choose the mode your workflow needs rather than changing it as a general launch fix.
- Channel or executable path: use these to select an installed browser; remember the bundled browser is the guaranteed compatibility path.
- Startup timeout: adjust it when startup legitimately takes longer in the target environment.
userDataDir: point to a writable profile location when the default location is unsuitable.- Arguments: add only the arguments needed for the deployment; do not reflexively disable security protections.
Common Puppeteer errors and fixes
| Symptom | Likely cause | What to check |
|---|---|---|
| “Could not find Chrome” | Install scripts were blocked, browser download was skipped, or the runtime cannot access the configured cache. | Install Puppeteer’s browser using the installation guide, review package-manager install-script policy, and verify the cache path and permissions. |
| Browser executable exists but launch fails on Linux | Missing shared libraries or environment-specific launch restrictions. | Run ldd on the executable; check current distribution dependencies and the targeted platform issues in the troubleshooting guide. |
| Launch fails with profile or permission errors | The user-data or cache directory is not writable or accessible to the runtime user. | Choose a writable userDataDir and verify ownership and access for the browser process. |
Launch works only with --no-sandbox |
The environment’s sandbox is not configured or permitted correctly. | Fix sandbox and container/user configuration where possible. Disabling it is strongly discouraged unless the loaded content is absolutely trusted. |
| Custom Chrome launches but automation behaves inconsistently | The external browser may not match Puppeteer’s paired browser version. | Try the bundled browser to establish the supported baseline; validate the custom executable or channel independently. |
| Screenshot misses content or interaction occurs too early | Navigation completion did not mean the specific application state was ready. | Wait for a meaningful selector or use an appropriate locator before interacting or capturing. |
Or skip the browser setup
If your goal is simply a website screenshot rather than browser automation, ScreenshotNeo is a screenshot API and MCP server. Its one-call API example is:
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 parameters and response details. ScreenshotNeo accepts cookie or consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each of those steps can be turned off. Bot checks/CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers report the page verdict and billing status. An MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and any MCP client. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots.
Sign up for ScreenshotNeo’s free plan and get 1,000 screenshots a month with no card.
Frequently Asked Questions
Does Puppeteer work with TypeScript?
Yes. Puppeteer’s 25.12.0 system requirements list TypeScript 5.0.1 or later when TypeScript is used; check the live requirements page for later releases.
Can I use Puppeteer to connect to a browser managed elsewhere?
Yes. The project documents managed or remote-browser workflows with puppeteer-core, which does not download its own browser. Configure the browser connection appropriate to that workflow.
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.
