Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteChrome Headless Shell is the standalone chrome-headless-shell binary for Chromium’s older headless implementation. It runs without a visible window and is designed for unattended work such as loading pages, reading the DOM, taking screenshots, creating PDFs and scraping rendered content. It is smaller and can start faster than full Chrome, but it does not reproduce every browser feature.
Since Chrome milestone 132, the old headless implementation is no longer included in the regular Chrome binary. If your automation depends on that implementation, obtain and launch the separate Headless Shell binary. Use unified Chrome Headless instead when you need extensions, complete Chrome behavior or high-fidelity end-to-end testing.
What Chrome Headless Shell actually is
Chromium defines headless operation as running Chromium in a headless or server environment. In practical terms, there is no desktop window to paint or interact with, but the browser still loads pages, executes JavaScript, builds a DOM and renders output.
Headless Shell is not a different web engine. It is a lightweight wrapper around Chromium’s //content module. That narrower wrapper has substantially fewer dependencies than the full Chrome browser. The result is a useful automation binary for Linux servers, containers and CI workers where a display server and the rest of Chrome’s desktop integration are unnecessary.
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 minute#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.
What it can do
- Navigate to HTTP or HTTPS pages and wait for them to render.
- Evaluate JavaScript and extract metadata or DOM content.
- Capture rendered pages as PNG, JPEG or other bitmap output through automation tools.
- Print pages to PDF.
- Run scraping and monitoring jobs that need JavaScript execution rather than just downloading HTML.
- Expose control through the Chrome DevTools Protocol or libraries such as Puppeteer.
What it is not
It is not a drop-in replacement for a normal interactive Chrome session. Compatibility with browser-level features is intentionally narrower, and the exact behavior can differ from what a user sees in regular Chrome.
Chrome 132 changed how old headless works
Before Chrome 132, the old headless implementation could be selected from the Chrome binary. In milestone 132, Chrome removed that implementation from the Chrome binary. The old behavior continues as a separate chrome-headless-shell executable.
Precompiled Headless Shell builds became available through Chrome for Testing beginning with milestone 118. This gives automation teams a supported way to pin a browser version without installing a full desktop Chrome package. A deployment that previously relied on an older --headless behavior should therefore check which executable it launches, rather than assuming that “headless” always means the same implementation.
Headless Shell versus unified Chrome Headless
Current Puppeteer makes the choice explicit:
| Puppeteer setting | Browser launched | Best fit |
|---|---|---|
headless: 'shell' |
Standalone chrome-headless-shell |
Fast, unattended page loading, extraction, screenshots, PDFs and scraping when the complete Chrome feature set is unnecessary. |
headless: true |
Unified Chrome Headless, the real Chrome browser without a visible window | High-fidelity application tests and jobs that need Chrome behavior or browser extensions. |
headless: false |
Visible Chrome | Interactive debugging, manual workflows and tests that require a desktop window. |
Choose Headless Shell when
- Startup time and a small dependency footprint matter.
- The workload is server-side and unattended.
- You need rendered DOM, screenshots or PDFs, but not extensions.
- You can tolerate differences from a normal Chrome session.
- Your containers or CI images should avoid desktop-browser dependencies.
Choose unified Chrome Headless when
- You test a web application end to end and accuracy against regular Chrome is the priority.
- The test uses browser extensions.
- It depends on browser features that the
//content-based shell does not expose. - A failure must match what a user’s ordinary Chrome session would experience as closely as possible.
“Faster” is a relative engineering trade-off, not a guaranteed benchmark number. Puppeteer describes the shell as currently more performant for tasks that do not need the complete feature set, while also warning that it does not completely match regular Chrome.
Recommended Free Tools
Install a compatible browser
The simplest route is the full puppeteer package. Its installation downloads a compatible Chrome for Testing build and a matching chrome-headless-shell binary. Pin the package version in your project so CI and production do not silently move to a different browser revision.
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.
If you use puppeteer-core, no browser is downloaded automatically. You must obtain Headless Shell yourself, store it in your image or build artifact, and provide its executable path. This is often preferable for tightly controlled containers, but it makes version management your responsibility.
Launch Headless Shell with Puppeteer
Install Puppeteer in a Node.js project:
npm install puppeteerThen select the shell explicitly:
import puppeteer from 'puppeteer';
const browser = await puppeteer.launch({ headless: 'shell' });
try {
const page = await browser.newPage();
await page.goto('https://example.com', { waitUntil: 'networkidle2', timeout: 90000 });
console.log(await page.title());
console.log((await page.content()).slice(0, 500));
} finally {
await browser.close();
}The script launches the downloaded shell, waits for network activity to settle, prints the title and a fragment of the rendered HTML, and closes the process even if navigation fails.
Take a screenshot or print a PDF
import puppeteer from 'puppeteer';
const browser = await puppeteer.launch({ headless: 'shell' });
try {
const page = await browser.newPage();
await page.setViewport({ width: 1440, height: 900, deviceScaleFactor: 1 });
await page.goto('https://example.com', { waitUntil: 'networkidle2', timeout: 90000 });
await page.screenshot({ path: 'page.png', fullPage: true });
await page.pdf({ path: 'page.pdf', format: 'A4', printBackground: true });
} finally {
await browser.close();
}networkidle2 is useful for ordinary pages, but analytics, WebSockets and advertising can keep a page active indefinitely. For those sites, wait for a meaningful selector or use a bounded delay instead:
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →await page.goto(url, { waitUntil: 'domcontentloaded', timeout: 90000 });
await page.waitForSelector('[data-page-ready]', { timeout: 30000 });Use a separately managed executable
With puppeteer-core, pass the path to the binary you downloaded and pinned:
import puppeteer from 'puppeteer-core';
const browser = await puppeteer.launch({
headless: 'shell',
executablePath: process.env.CHROME_HEADLESS_SHELL
});
const page = await browser.newPage();
await page.goto('https://example.com', { waitUntil: 'domcontentloaded' });
console.log(await page.title());
await browser.close();Use an absolute path in production and verify that the file is executable. Keep the browser revision compatible with the Puppeteer version you deploy.
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.
Command-line and DevTools Protocol use
Headless Shell can also be started directly with remote debugging enabled, then controlled through the Chrome DevTools Protocol. A typical server launch supplies a writable user-data directory and a debugging port:
chrome-headless-shell --headless --remote-debugging-port=9222 --user-data-dir=/tmp/headless-profile https://example.comIn a container, provide a writable temporary directory and enough shared memory for the pages you process. Do not expose the debugging port to an untrusted network: anyone who can reach it may control the browser and read data available to its session.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Options that make automation reliable
Wait for the page you need, not an arbitrary global delay
- Use
domcontentloadedfor a quick DOM operation. - Use
networkidle2for pages whose important resources finish loading. - Prefer
waitForSelectorfor a known application-ready marker. - Always set finite navigation and selector timeouts so a stuck page cannot consume a worker forever.
Control viewport and rendering inputs
Set viewport width, height and device scale factor before navigation when screenshots are part of the output. If the page changes with locale, timezone, cookies or user agent, configure those inputs deliberately and record them with the result.
Reuse browsers carefully
Launching one browser for every URL adds startup cost. A long-lived browser with a fresh page per job is usually more efficient, but close pages and clear sensitive state between tenants. For strong isolation, use separate browser processes or profiles and accept the extra startup overhead.
Make failures observable
Log the target URL, browser revision, navigation phase, timeout type and HTTP response status. Save a diagnostic screenshot or HTML only when it is safe to retain page data. Distinguish a page that loaded an error screen from a browser process that failed to start.
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
Common problems and fixes
“Could not find Chrome” or an executable-path error
Cause: puppeteer-core does not download a browser, or the path is wrong. Fix: install puppeteer, or download Headless Shell separately and set an absolute executablePath. Confirm execute permission inside the runtime image.
The script launches the wrong headless implementation
Cause: a generic headless: true setting or an old Chrome binary is being used. Fix: use headless: 'shell' for the standalone binary, or use headless: true intentionally for unified Chrome Headless. Check the actual executable and browser revision in logs.
Pages time out
Cause: a never-ending request, consent flow, slow origin or bot challenge. Fix: use a finite timeout, wait for a specific selector, block unnecessary resources where appropriate, and capture diagnostics. Increasing the timeout alone can hide an application failure.
Fonts, images or sandbox errors appear in containers
Cause: missing runtime libraries, fonts, permissions or shared memory. Fix: start from a Chromium-compatible base image, install required font and graphics packages, provide writable temporary storage, and follow your container platform’s sandbox guidance. Avoid disabling the sandbox unless the deployment is isolated and you understand the security cost.
The screenshot differs from regular Chrome
Cause: Headless Shell does not provide complete regular-Chrome behavior. Fix: run the same job with unified Chrome Headless. If the discrepancy concerns an extension or browser-level API, the shell is the wrong execution target.
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.
Or skip the browser setup
For a straightforward website screenshot, ScreenshotNeo provides a hosted API instead of making you package Chromium, fonts and container dependencies. It accepts cookie and consent banners before capture and removes more than 60 known consent platforms, newsletter popups and chat widgets; each cleanup step can be turned off. Bot checks, CAPTCHAs, blank pages, timeouts, failed loads and cache hits are not billed, and response headers identify the page verdict and whether the request was billed. Its MCP server provides take_screenshot, get_page_info and capture_pdf tools for Claude, Cursor and other MCP clients.
One request returns an image or PDF:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the complete parameter list in the ScreenshotNeo documentation. The service supports full-page and element captures, device presets, retina scale, dark mode, custom CSS and JavaScript, selector or network-idle waits, request blocking, headers, cookies, user agents, timezone, geolocation, transparent backgrounds, resizing, chosen cache TTLs, signed image links, asynchronous webhooks and bulk capture of up to 100 URLs per call.
The free plan includes 1,000 screenshots a month with no card. Paid plans start at $5 for 3,000 shots; every feature is available on every plan. Create a free ScreenshotNeo account.
How to decide
Use chrome-headless-shell when you control the runtime, need rendered browser automation and value a smaller, potentially faster process over complete Chrome fidelity. Use unified Chrome Headless when extensions or realistic end-to-end behavior are requirements. If the task is simply obtaining clean screenshots or PDFs and you do not want to maintain a browser runtime, the hosted ScreenshotNeo request avoids that setup.
Frequently Asked Questions
Does Headless Shell include a graphical user interface?
No. It is intended for unattended operation without a visible browser window.
Is chrome-headless-shell the same as Chrome Headless?
No. Headless Shell is the standalone binary for the older implementation; unified Chrome Headless runs the full Chrome browser without displaying a window.
Why does Puppeteer use headless: ‘shell’?
That explicit value tells Puppeteer to launch the standalone chrome-headless-shell implementation rather than unified Chrome Headless.
Can I use browser extensions with Headless Shell?
It is not the appropriate choice when extension support is required; use unified Chrome Headless or visible Chrome instead.
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.
