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 errorsUse your automation framework’s browser installer unless you have a specific reason to manage Chrome yourself. Puppeteer downloads a compatible Chrome for Testing build, Selenium requires a compatible Chrome/ChromeDriver pair (or supported automatic management), and Playwright downloads its own Chromium build. In every framework, current Chrome Headless is enabled with --headless; it is Chrome’s normal implementation running without visible UI, not a separate browser download.
This guide covers installation on developer machines and CI, version matching, Linux dependencies, the separate chrome-headless-shell binary, verification, and failure recovery. Version requirements change, so treat the commands as current guidance for the framework version you install and check its support matrix before pinning production images.
Choose the installation path first
| Framework or use case | What to install | Best starting command | Important qualification |
|---|---|---|---|
| Puppeteer | Puppeteer plus its downloaded Chrome for Testing (and headless shell) | npm i puppeteer |
Install scripts must be allowed to run, or the browser download can be skipped. |
| Selenium/WebDriver | Chrome for Testing and a matching ChromeDriver, or supported automatic management | Install your WebDriver framework, then add the headless Chrome option | Browser and driver versions must be compatible; pin both for deterministic CI. |
| Playwright | Playwright’s supported Chromium build | npx playwright install |
Branded Google Chrome and Microsoft Edge can be used when already installed, but Playwright does not install them by default. |
| Only the former headless implementation | chrome-headless-shell |
Use the framework’s shell option or Chrome for Testing distribution | This is a distinct binary, available through Chrome for Testing starting with Chrome 132.0.6793.0; it is not the default choice for most users. |
What “Headless Chrome” means today
Chrome 112 changed Headless so Chrome uses the regular Chrome implementation while creating platform windows that are not shown. Launch it with --headless. The older, separate implementation is now distributed as chrome-headless-shell. Therefore, installing “Chrome Headless” normally means installing Chrome (often Chrome for Testing through your framework) and selecting headless mode at runtime.
For direct command-line checks, the official Chrome examples are:
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 →#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.
- Linux:
google-chrome --headless - macOS:
open -a "Google Chrome" --args --headless - Windows:
start chrome --headless
Those commands prove that the binary starts; automation still needs a framework, a page URL, and usually additional flags or dependencies in CI.
Install Headless Chrome with Puppeteer
Standard installation
- Install a supported Node.js release. Puppeteer 25.12.0 lists Node 22.12 or newer; verify the requirement for the version you select.
- In your project directory, run
npm i puppeteer. Puppeteer normally downloads a compatible Chrome for Testing build andchrome-headless-shell. - Create a smoke test:
const puppeteer = require('puppeteer');
(async () => {
const browser = await puppeteer.launch({ headless: true });
const page = await browser.newPage();
await page.goto('https://example.com', { waitUntil: 'networkidle2' });
console.log(await page.title());
await browser.close();
})();headless: true is Puppeteer’s default. Use headless: false to debug with a visible window, or headless: 'shell' when you explicitly want the headless-shell binary.
When the browser download is missing
pnpm, Yarn Berry, Bun, and Deno configurations can block dependency install scripts. That leaves Puppeteer installed but no browser in its cache, commonly producing “Could not find Chrome.” Allow the install script according to your package manager, or follow Puppeteer’s configuration guidance to run the browser download separately and to set a custom cache directory.
On Debian or Ubuntu, Puppeteer’s browser CLI can install Chrome and required system packages:
npx puppeteer browsers install chrome --install-depsThis command requires root privileges. Use it in a controlled image build, not as an unexplained fix on a production host.
Install for Selenium and WebDriver
Match the browser and driver
Selenium drives Chrome through WebDriver. Use a Chrome for Testing binary with the corresponding ChromeDriver, or use your framework’s supported automatic browser/driver management. Avoid old instructions that download an arbitrary driver URL: compatibility is a version concern, and Chrome for Developers recommends matched Chrome for Testing and ChromeDriver binaries.
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.
Enable headless mode
The exact language binding differs, but the Chrome option is the same. A Java example is:
ChromeOptions options = new ChromeOptions();
options.addArguments("--headless");
WebDriver driver = new ChromeDriver(options);
driver.get("https://example.com");
System.out.println(driver.getTitle());
driver.quit();In CI, pin the Chrome for Testing and ChromeDriver versions in the image or lockfile. A locally auto-updating desktop Chrome is convenient for interactive work but can make test results change without a code change.
PC 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 & 11Crashes, 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 minuteInstall Chromium for Playwright
Full browser install
Install Playwright in your project, then download its supported browser:
npm install -D playwright
npx playwright installPlaywright manages the Chromium revision it expects. It can launch branded Google Chrome or Microsoft Edge when those channels are present, but it does not install branded browsers by default.
Headless-shell-only CI install
If your tests do not select a branded channel and need only the shell in CI, use Playwright’s documented reduced install:
npx playwright install --with-deps --only-shell--with-deps installs Linux dependencies where supported. Confirm that your Playwright version exposes this option before baking it into a long-lived image.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →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.
Prepare Linux hosts and containers
Check the layers of requirements
- Operating system and architecture: Puppeteer 25.12.0 lists Chrome for Testing support on Windows x64, macOS x64/arm64, Debian/Ubuntu Linux x64/arm64, and openSUSE/Fedora Linux x64/arm64.
- System libraries: Minimal Linux images often lack the graphics, font, NSS, or audio libraries Chrome expects. Use the framework’s dependency installer where available.
- Archive tools: Puppeteer’s requirements identify
unzip/tarneeds for unpacking downloaded binaries. - Privileges: Dependency installation generally needs root; browser execution itself should run with the least privilege practical.
These are framework-specific requirements, not a universal promise for every Chrome installation. Google’s current desktop Chrome page lists Windows 10+ on Intel (Windows 11+ on ARM), macOS 13 Ventura+, and 64-bit Ubuntu 18.04+, Debian 10+, openSUSE 15.5+, or Fedora 39+; those branded-desktop requirements are distinct from framework browser matrices.
Container launch considerations
Run a smoke test inside the same image and user account used by CI. If the image policy prevents sandboxing, your security team may require a narrowly scoped configuration rather than simply adding broad flags. Do not copy --no-sandbox into every environment without understanding the isolation trade-off.
Verify the installation before writing tests
- Print the framework, Node/runtime, operating-system, and CPU architecture versions.
- Run one navigation test against a stable, simple page and close the browser in a
finallyblock. - Record the browser version and, for WebDriver, the driver version in CI logs.
- Repeat the test as the non-interactive CI user; a browser that works only in your desktop account is not an installed CI dependency.
- For screenshots or PDFs, wait for the page condition your test needs (selector, network idle, or a bounded delay) instead of assuming that process startup means the page is ready.
Troubleshooting common failures
“Could not find Chrome” or an empty browser cache
Cause: an install script was blocked, a custom cache path is wrong, or the browser download was intentionally disabled.
Fix: allow the package’s install script, run the framework browser installer explicitly, and confirm the runtime user can read the cache. For Puppeteer, use its configuration documentation when choosing a non-default cache.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
WebDriver session creation or “session not created” error
Cause: ChromeDriver and Chrome are incompatible, or the selected binary is not the one your driver expects.
Fix: install a matched Chrome for Testing/ChromeDriver pair or enable the WebDriver manager supported by your binding. Print both versions before the test starts.
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
Browser starts locally but crashes in Linux CI
Cause: missing shared libraries, fonts, archive utilities, an incompatible architecture, or a restricted container.
Fix: use --with-deps for Playwright or --install-deps for Puppeteer on Debian/Ubuntu, inspect the image’s package and architecture list, and run the same smoke test in the final image.
Recommended Free Tools
Pages hang or return blank output
Cause: navigation is waiting indefinitely, the target site blocks automation, a required resource fails, or the page needs an interaction before rendering.
Fix: set explicit navigation and overall timeouts, wait for a meaningful selector, capture console and network errors, and test the URL interactively. A successful Chrome launch does not guarantee that a particular site will render for an automated client.
Unexpected differences after a rebuild
Cause: an auto-updated browser, unpinned framework revision, changed fonts, or a different OS image.
Fix: pin the framework/browser pair (and driver for WebDriver), record versions, and rebuild from a known image. Update deliberately, then review visual and functional test changes.
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.
Performance, reliability, and cost decisions
- Reuse a browser process: launch once per worker and create isolated pages or contexts rather than starting Chrome for every assertion.
- Control concurrency: more pages increase CPU, memory, and file-descriptor pressure; size worker counts from measurements in your CI image.
- Keep waits bounded: selector waits and network-idle waits should have explicit limits so a stalled third-party request cannot consume the entire job.
- Choose shell versus full browser intentionally: shell-only downloads can reduce CI footprint when your framework supports them, while full Chromium is safer when tests exercise normal browser behavior or channels.
- Pin for repeatability: framework-managed downloads are simplest; WebDriver needs especially careful browser/driver matching.
Or skip the browser setup
ScreenshotNeo provides a website screenshot API and MCP server when you need a rendered image or PDF rather than a locally managed test browser. One GET request is enough:
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 documentation for all options. The equivalent Python and Node.js requests are:
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);Before capture, it accepts cookie/consent banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be disabled. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers identify the page verdict and billing status. Its MCP server exposes take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients. The Free plan includes 1,000 screenshots per month without a card; paid plans start at $5 for 3,000 shots. Create a free ScreenshotNeo account.
Frequently Asked Questions
Can I use my installed Google Chrome with Playwright?
Yes. Playwright can target branded Google Chrome or Microsoft Edge when installed, but its normal installer downloads Playwright-managed Chromium instead.
Is chrome-headless-shell required for Puppeteer?
No. Puppeteer’s normal headless mode uses its downloaded compatible Chrome for Testing build. Select the shell explicitly only when that separate implementation meets your use case.
Should I install Chrome system-wide or in the project?
Prefer the framework-managed, project or image-scoped browser for reproducible automation. A system browser is reasonable when your organization centrally patches and pins it, but record its version and driver pairing.
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.
