Puppeteer’s executablePath() returns the default executable location computed for the selected browser setup. There is no single path that applies to every installation: the result depends on the browser and build, the configured cache directory and platform, and whether you use a managed download, an explicit executable path, or a Chrome release channel. In the current API references, identified as Puppeteer 25.12.0, the documented configuration default is ~/.cache/puppeteer unless overridden. Puppeteer’s configuration reference and browser path options describe the relevant inputs.
Which executable path does Puppeteer use?
It depends on how you select the browser. A standard puppeteer installation normally uses the browser Puppeteer manages and downloads. Its default executable path is computed from that browser installation and configuration. A configured executable path can instead point to a specific file, while a Chrome channel asks Puppeteer to use a regular system installation of that release channel.
| Setup | Who selects the executable | Where Puppeteer looks |
|---|---|---|
Managed browser with puppeteer |
Puppeteer computes a path for the selected browser and build. | The configured browser cache and the executable’s location inside its extracted download. |
Explicit executablePath |
Your launch options or environment configuration specify the path. | The file at that supplied path. |
Chrome channel |
Puppeteer resolves the requested release channel. | A known system location for that channel’s regular Chrome installation. |
puppeteer-core |
Your launch options must specify an executable path or channel. | The selected external executable; do not assume the full package’s download and configuration defaults apply. |
The executablePath() API answers where the selected setup expects the executable to be. Do not treat the returned string alone as proof that the file exists or that it can successfully launch.
How Puppeteer computes a managed-browser path
For a Puppeteer-managed browser, the public @puppeteer/browsers API describes path computation in terms of four inputs: browser, buildId, cacheDir and platform. The platform is auto-detected when not specified. The browser provider determines where its executable sits relative to the extracted download, so the final path is not just a universal cache-directory string. See the computeExecutablePath options and the computeExecutablePath API.
Free tools Windows power users keep installed
One-click scans. No signup required.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
The Puppeteer configuration reference documents path.join(os.homedir(), '.cache', 'puppeteer') as the default cache directory and PUPPETEER_CACHE_DIR as an environment-variable override. The final executable location is derived from the cache, browser, build and platform rather than being the cache directory itself. If a null cache directory is used through the browser API, the computed executable path is relative to the extracted download location—for example, ./chrome-linux64/chrome. That example is not a promise that every browser, platform or build uses the same relative path.
Configuration files and environment variables
For the full puppeteer package, the effective configuration can include the configuration file and process environment. The documentation says environment variables override applicable configuration-file values. The documented settings include executablePath, cacheDirectory, the default browser and download-skipping options. Check the installed package version and the environment of the process that actually launches Puppeteer; a shell, build step and deployed service can have different values.
PUPPETEER_EXECUTABLE_PATH can override the auto-computed executable path, and PUPPETEER_CACHE_DIR can override the cache directory. Browser selection and download behavior can also be affected by browser-specific settings. The configuration guide documents these settings and precedence between environment variables and configuration-file values.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
How explicit paths and Chrome channels change the result
Explicit executable path
Passing executablePath in launch options selects that executable instead of the bundled browser. The path must be valid in the runtime environment, and you are responsible for ensuring the file is accessible and compatible with the installed Puppeteer version. A configured PUPPETEER_EXECUTABLE_PATH can also redirect the executable path used by the full package.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Chrome release channel
Passing a Chrome channel selects a regular system installation of that channel from a known location. The separate computeSystemExecutablePath() API checks known locations for the requested release channel and throws if the expected executable is absent. The reviewed API references do not give a complete cross-platform list of those locations, so do not infer a particular OS path from the channel name alone. See LaunchOptions and computeSystemExecutablePath.
What changes with puppeteer-core?
puppeteer-core is not interchangeable with the full puppeteer package for browser setup. The PuppeteerNode API reference states that when using puppeteer-core, options.executablePath or options.channel must be provided. Its configuration files and environment-variable configuration are ignored, according to the configuration guide. Set the browser selection in the launch options rather than relying on the full package’s managed-download defaults.
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
For example, this launch fragment makes the choice explicit:
const browser = await puppeteer.launch({
executablePath: '/path/to/chrome',
});Replace the example path with an executable that exists in the process environment. If you prefer a system Chrome channel, provide channel instead. See the PuppeteerNode reference.
Check the effective path and browser setup
- Identify the package and version. Check whether the project uses
puppeteerorpuppeteer-core, and inspect the installed version. The current API pages referenced here identify as Puppeteer 25.12.0; options and defaults can differ across versions. - Inspect runtime configuration. Check
PUPPETEER_EXECUTABLE_PATH,PUPPETEER_CACHE_DIR,PUPPETEER_BROWSER, and relevant browser download settings in the actual process environment. Inspect the effective configuration file if using the full package. - Check launch options. Look for
executablePathorchannelpassed tolaunch(). Either can mean the process is not using the default managed binary. - For a managed browser, verify the installation inputs. Confirm the selected browser and build ID, the cache directory used during installation and runtime, and the platform. Also confirm the browser download was not skipped.
- For a channel, verify the installation. Confirm that the requested Chrome release channel is installed where Puppeteer expects to find it. A missing expected executable can cause system-path computation to throw.
- Verify the file and launch separately. Check that the computed or configured path exists and is readable in the runtime environment, then test launching it. A computed path is not itself a successful-launch guarantee.
Why a path works locally but fails after deployment
One common cause is a mismatch between the environment that installed the browser and the environment that runs the application. Starting in Puppeteer v19.0.0, the configuration guide says browser downloads are stored in ~/.cache/puppeteer by default to support a global cache. If a package is packed during a build and moved to a fresh location, that cache may not move with it. The guide’s suggested remedy is to set a different cacheDirectory and reinstall Puppeteer so the browser is installed there.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
For deployment, make the browser installation and runtime agree on the cache location, and ensure the browser download occurs in the environment or artifact that will actually use it. This is particularly important when the runtime has a different home directory or filesystem from the build environment.
Compatibility is separate from path resolution
A path can point to a real executable and still fail because the browser is not compatible with the Puppeteer version. Puppeteer says compatibility is guaranteed only with its bundled browser. When you choose an external Chrome or Chromium executable, you take on the compatibility risk. The browser documentation also gives a similar warning about custom providers. See LaunchOptions and the browser management guide.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Troubleshooting common executable-path failures
| Symptom | Likely cause | What to check or change |
|---|---|---|
| “Could not find Chrome” or a missing executable error | The managed browser was not downloaded, the configured cache differs from the install cache, or an explicit path is wrong. | Check whether downloads were skipped, verify the effective cache directory and browser/build, and confirm the executable exists in the runtime environment. |
| Works on a developer machine but not in deployment | The deployment image or moved package does not include the browser cache used at build time. | Align installation and runtime cache locations. Consider a configured cache directory and reinstalling Puppeteer as described in the configuration guide. |
| Channel lookup throws | The requested system Chrome release channel is absent from Puppeteer’s expected known location. | Install the requested channel in the relevant runtime environment or select a different installed executable explicitly. |
puppeteer-core launches without a browser selection |
Code assumes full-package defaults that do not apply to puppeteer-core. |
Supply executablePath or channel in launch options. |
| The file exists but launch fails | The executable may be inaccessible, incompatible, or otherwise unable to start in that environment. | Check runtime permissions and launch conditions, then use the bundled browser if you need Puppeteer’s documented compatibility guarantee. |
Or skip the browser setup
If your goal is to capture website screenshots rather than automate Chrome itself, ScreenshotNeo offers a screenshot API. One GET request can return an image or PDF without installing or locating a browser in your application. See the API documentation.
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 →Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
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 not billed. Its MCP server lets AI agents take screenshots, and the free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. Sign up for ScreenshotNeo free.
Frequently Asked Questions
Does Puppeteer’s executablePath() guarantee that Chrome exists?
No. It returns the path computed for the selected setup; check that the file exists and can launch in the runtime environment.
Why is Puppeteer looking in ~/.cache/puppeteer?
The configuration reference documents that as the default cache directory, starting with Puppeteer v19.0.0. A configured cache directory or PUPPETEER_CACHE_DIR can change it.
Does Puppeteer work with any installed Chrome version?
Puppeteer guarantees compatibility with its bundled browser, not arbitrary external Chrome or Chromium executables.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →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.
