Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchespuppeteer is the higher-level package: a standard install downloads a compatible browser so you can start automating with fewer setup decisions. puppeteer-core provides the same Puppeteer automation API without downloading Chrome; choose it when you will manage the browser yourself or connect to a remote one.
What differs between the packages?
The key difference is browser installation and management, not a separate automation API. Both packages let you launch or connect to a browser, create pages, and control them through Puppeteer. The regular package supplies a managed-browser default; Core leaves browser selection and provisioning to your application.
As an Amazon Associate I earn from qualifying purchases.
| Question | puppeteer |
puppeteer-core |
|---|---|---|
| What is it for? | End-user automation with reasonable defaults. | A library for controlling a browser through the programmatic API. |
| Does installation download a browser? | Normally downloads a supported Chrome for Testing build and a headless-shell binary. | No. It does not automatically download Chrome. |
| Who manages the browser? | Puppeteer provides a convenient default browser setup, which can be customized. | You or your application must supply or manage a browser, or connect to a remote one. |
| What is needed to launch? | Usually no browser path is needed when using its downloaded browser. | Specify executablePath or channel when launching, or provide a valid endpoint when connecting remotely. |
| Typical fit | A local project where Puppeteer’s downloaded browser is acceptable. | A project with an already installed, provisioned, or remote browser. |
The official installation guide describes Core as appropriate for users connecting to a remote browser or managing browsers themselves.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Which package should you use?
Choose puppeteer for the straightforward default
Use the regular package if you want a local setup that installs a compatible browser as part of the normal Puppeteer installation flow. That reduces the browser-management work you need to do before running an automation script.
#1 Best Overall
Choose puppeteer-core when browser management is yours
Core is the better fit if your app provisions a browser, uses a browser already installed in its environment, or connects to a remote browser. You must ensure the selected browser is available and compatible, and provide the launch path or channel when launching locally. For remote use, use a valid browser endpoint and the appropriate connection method.
Install and run a basic script
Install the package that matches your setup:
npm install puppeteerOr install Core if you provide the browser yourself:
npm install puppeteer-coreThe page workflow is otherwise shared. The official getting-started guide demonstrates the same general workflow with either package. For Core, the launch call must identify a browser; replace the example path with the executable available in your environment.
Rank #2
import puppeteer from 'puppeteer';
const browser = await puppeteer.launch();
try {
const page = await browser.newPage();
await page.goto('https://example.com');
console.log(await page.title());
} finally {
await browser.close();
}With Core and a locally managed Chrome executable:
import puppeteer from 'puppeteer-core';
const browser = await puppeteer.launch({
executablePath: '/path/to/chrome',
headless: true,
});
try {
const page = await browser.newPage();
await page.goto('https://example.com');
console.log(await page.title());
} finally {
await browser.close();
}The launch API supports browser-selection options; check the launch method reference for the installed release and its compatibility requirements. The path above is an example, not a universal Chrome location.
Browser versions and compatibility
Puppeteer releases are paired with browser versions. That pairing helps avoid unexpected automation breaks when Chrome DevTools Protocol or WebDriver BiDi behavior changes. Do not assume a browser version supported by one Puppeteer release will match another; check the supported browsers table for the version installed in your project.
At the time of the Puppeteer documentation snapshot reflected in this article, the support page identified Puppeteer v25.12.0 with Chrome for Testing 154.0.8037.57 and Firefox 156.0.1. Those are version-specific mappings, not permanent guarantees. The FAQ says Puppeteer v23.0.0 onward supports Chrome and Firefox, with CDP used by default for Chrome and WebDriver BiDi by default for Firefox; feature support can differ by protocol, so consult the relevant protocol documentation before relying on a particular behavior.
The documented system requirements list Node 22.12+ and TypeScript 5.0.1+ when using TypeScript. Requirements are release-sensitive; verify the system requirements for your installed version.
Free tools Windows power users keep installed
One-click scans. No signup required.
Why can’t Puppeteer find Chrome?
A common cause is an installation environment that blocks package lifecycle scripts. Puppeteer’s normal browser download can be skipped in that case, leaving the package installed but no browser available at runtime.
- Check the package manager’s install-script policy. If scripts are disabled or blocked, allow Puppeteer’s postinstall script according to that package manager’s configuration.
- Install the browser manually. The official installation guide documents
npx puppeteer browsers installas a remedy when the automatic download did not run. - For Core, provide the browser explicitly. Core intentionally does not download Chrome, so set
executablePathorchannelfor a local launch, or use a valid remote browser endpoint. - Confirm the browser matches the Puppeteer release. Compare your package version with the official supported-browser table rather than assuming any locally installed Chrome is compatible.
See the installation guide for package-manager and browser-installation details.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Configuration differences to verify
Puppeteer has configuration files and environment options, but the configuration page in the Next documentation channel says those are ignored by puppeteer-core. Because that page is not the stable documentation channel, verify the behavior against the documentation for your installed release before depending on it: Puppeteer configuration.
Or skip the browser setup
If your goal is to get a website screenshot rather than build browser automation, ScreenshotNeo offers a website screenshot API and MCP server. A single request can return an image or PDF without you provisioning Puppeteer or a browser:
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →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.webpSee the ScreenshotNeo API documentation for request options. Cookie banners, popups and chat widgets are removed before the shot; bot checks, blank pages and failed loads are never billed. Its MCP server lets AI agents take screenshots, and 1,000 screenshots a month are free with no card; paid plans start at $5 for 3,000. Sign up for ScreenshotNeo’s free plan.
Frequently Asked Questions
Do Puppeteer and Puppeteer Core use different automation APIs?
They share Puppeteer’s browser automation workflow; the principal difference is whether the package supplies the browser-installation default.
Best Value
- Used Book in Good Condition
Does Puppeteer Core install Chrome?
No. Core does not automatically download Chrome; provide a browser or connect to one.
Can I use Puppeteer Core with a remote browser?
Yes. Core is intended for that use case, provided you connect using a valid browser endpoint.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
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.
