Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
If chrome-headless-render-pdf reports that Chrome does not start or crashes immediately, first launch the exact Chrome executable yourself with the exact switches used by the package. That single comparison separates a browser or launch-configuration failure from a test harness, service, permissions, or environment failure. Then verify which binary the package selected, remove risky arguments, check the Linux user context, and confirm that your Headless mode still matches your Chrome version.
The exact cause cannot be identified without your operating system, Chrome version, complete command, executable path, and startup error. Use the sequence below to isolate it before changing PDF or rendering options.
1. Reproduce startup outside the package
Find the executable that chrome-headless-render-pdf is supposed to use. Do not assume that the first chrome on PATH is the intended installation. Common executable names include google-chrome, google-chrome-stable, chromium, and chromium-browser; the actual path varies by operating system and installation method.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Run that binary as the same operating-system user and with the same arguments supplied by the package. Start with a harmless URL and an explicit output location. For example, on Linux:
#1 Best Overall
- Powerful Linux Laptop: This IdeaPad Slim 3 Laptop comes pre-installed with Ubuntu Linux, offering fast performance, robust security, and a clean, user-friendly experience. Enjoy full customization, seamless hardware compatibility, and access to thousands of open-source apps. Whether you're working, creating, or coding, it's built to keep up with everything you do.
- A Multitasking Master: The latest AMD Ryzen 7 5825U processor (up to 4.5 GHz) delivers powerful performance with 8 cores and 16 threads for smooth multitasking. Integrated AMD Radeon Graphics provide crisp visuals for streaming, browsing, photo editing, and casual gaming. With smart machine intelligence, it adapts to your needs for a fast, responsive experience.
- 15.6" Full HD Display: The IdeaPad Slim 3 boasts an 88% screen-to-body ratio for a floating, edge-to-edge visual experience. TÜV Low Blue Light certification reduces eye strain, making it perfect for long work or study sessions.
- Military-Grade Durability: The smart IdeaPad Slim 3 combines portability and durability, letting you work, study, and play on the go. With a profile 10% slimmer than the previous generation, it's lightweight yet military-grade rugged, ready for anything, anywhere.
- Versatile Connectivity: Enjoy the security of a built-in webcam with a privacy shutter. Connect effortlessly with multiple ports: 2x USB A, 1x USB C, 1x HDMI, 1x SD Card Reader, 1x Headphone/Microphone combo. Bundle comes with Stylus Pen, 256GB Portable SSD and 5-in-1 Docking Station.
/usr/bin/google-chrome
--headless
--disable-gpu
--no-first-run
--no-default-browser-check
--print-to-pdf=/tmp/chrome-startup-test.pdf
https://example.comUse the equivalent executable and switches on macOS or Windows. The important variables are the executable, every switch, the user account, the working directory, and the environment—not the particular sample URL. Capture both standard output and standard error:
/usr/bin/google-chrome [the-package-switches] https://example.com
1>/tmp/chrome.stdout 2>/tmp/chrome.stderrIf this direct command fails, investigate Chrome installation, its profile directory, permissions, shared libraries, sandboxing, or the arguments. If it succeeds, Chrome itself can start in that context; move on to the harness and package configuration instead of reinstalling the browser blindly.
What the result means
| Direct launch result | Immediate focus | Next action |
|---|---|---|
| Fails with the same executable and switches | Browser installation or launch configuration | Check the path, permissions, dependencies, profile, user, and arguments. |
| Starts directly but fails through the package | Package selection, package arguments, or execution harness | Print the selected binary and simplify the job to a small script in the same user context. |
| Starts directly and through a small script, but fails in CI or a service | CI, service, container, display, filesystem, or environment differences | Compare identity, environment variables, mounted paths, and resource limits. |
2. Verify the binary and arguments chosen by chrome-headless-render-pdf
The package documents two controls that matter when automatic discovery or launch flags are suspected:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
--chrome-binaryselects an explicit Chrome or Chromium executable.--chrome-optionpasses a Chrome argument from the package command line.
Use the full path rather than relying on autodetection while diagnosing. Then add options one at a time. A diagnostic command has this general shape:
chrome-headless-render-pdf
--chrome-binary=/absolute/path/to/chrome
--chrome-option=--headless
--chrome-option=--disable-gpu
input.html output.pdfUse the exact input and output syntax from the version of the package you installed; the example shows the relevant flags, not a substitute for its local help text. Run chrome-headless-render-pdf --help and record the complete command in your bug report.
Check what Chrome is being used
Log or print the resolved executable before launching. On Unix-like systems, command -v google-chrome, command -v chromium, or which chromium reveals what the shell would choose, but the package may use its own discovery logic. Confirm the actual path in the package or driver log. On Windows, inspect the configured path rather than assuming the Start menu shortcut is the binary used by the process.
Rank #2
- Intel Core i5-10210U (up to 4.2GHz) - 1TB PCIe NVMe + 1TB HDD - 32GB DDR4 SDRAM
- 17.3" HD+ (1600x900) Display, Intel UHD Graphics 620
- Built in HD 720p Webcam with Microphone - Bluetooth Version4.2
- I/O Ports: 2x USB 3.1 (Data Only), 1x USB 2.0, 1x HDMI, 1x Headphone/Microphone Combo Jack
- Linux Mint Cinnamon 64-Bit - 6-Row Keyboard w/ Full Numberpad
Check that the executable exists, is executable by the launching user, and is compatible with the host architecture. A service account may see a different PATH and home directory from your interactive shell.
Recommended Free Tools
Reduce arguments to a known-good baseline
Remove custom switches temporarily, then add back only the options required by your workload. A malformed value, an obsolete flag, a duplicate profile directory, or a flag copied from another automation tool can make Chrome exit before the package receives a useful error. Keep a copy of the working and failing argument lists so the difference is explicit.
3. Reduce the harness before changing Chrome
When direct Chrome startup works, reproduce the package call in a minimal command or short script under the same user account. Do not begin with a CI runner, IDE task, background service, queue worker, or container entrypoint. Each layer can alter PATH, HOME, current directory, environment variables, file permissions, signals, and time limits.
- Run the direct Chrome command interactively.
- Run the smallest
chrome-headless-render-pdfcommand with one local or simple public page. - Run that same command from the intended service or CI context.
- Compare the executable path, arguments, user ID, home directory, writable temporary directory, and process limits.
If the minimal script works but the full application does not, add your application options back one group at a time. This identifies whether the failure occurs during browser startup, page navigation, JavaScript execution, or PDF generation.
4. Check the Linux user context—especially root
ChromeDriver troubleshooting documentation identifies running Chrome as the root user (administrator) on Linux as a common cause of startup crashes. Run the browser as a regular, non-root user whenever possible, and ensure that user can write to its temporary and profile directories.
Free tools Windows power users keep installed
One-click scans. No signup required.
Do not treat --no-sandbox as a routine repair. The same guidance calls using it to work around root execution unsupported and highly discouraged. If a container or service currently runs as root, change the process user, provide writable directories, and fix ownership and permissions instead. Only consider a sandbox change after you understand the security consequences and have a deployment-specific reason.
Rank #3
- Intel Core i5-1335U Processor (12M Cache, 12 Threads, up to 4.6 GHz) - 256GB Solid State Drive - 16GB DDR4 SDRAM
- 15.6" FHD (1920x1080) Non-Touch Anti-Glare Display - Intel UHD 620 Integrated Graphics - Stereo Speakers
- 720p HD Webcam with Privacy Shutter. Integrated Microphone - Intel Dual Band Wireless-AC (2x2) 8265, Bluetooth Version 4.2
- I/O Ports: 2x USB 3.0, 1x USB 3.1 Type-C 3.1, Headphone/Mic Combo Port, 4-in-1 Card Reader, HDMI, Kensington Mini-Lock Slot
- Linux Mint (Cinnamon) 64-Bit - Keyboard with Full NumberPad - Fast Charging
Useful checks on Linux
id
printf 'HOME=%snTMPDIR=%sn' "$HOME" "$TMPDIR"
ls -ld "$HOME" /tmp
ulimit -a
Look for a read-only home directory, a missing temporary directory, restrictive mount options, exhausted process or file-descriptor limits, and a profile left locked by another Chrome process. A dedicated writable profile can help isolate profile contention, but keep it separate for each concurrent browser process.
5. Check Headless version assumptions
Chrome’s Headless implementation has changed. The newer Headless mode was introduced in Chrome 112. Chromium documentation states that, as of Chrome M132, the old headless shell is no longer part of the Chrome binary and that users who depend on the former shell functionality should migrate to chrome-headless-shell.
This is a conditional compatibility check, not proof that every startup failure is a version problem. Record the installed version and the actual binary distribution:
/absolute/path/to/chrome --version
/absolute/path/to/chrome --headless --versionThen determine whether your package expects the former shell behavior or the newer Headless mode. If a deployment crossed the M132 boundary, test the documented chrome-headless-shell migration path or update the package and launch configuration together. Do not mix a shell binary, flags, and assumptions from a different Chrome installation without testing them directly.
6. Separate startup failures from rendering failures
Options such as --print-to-pdf, header and footer suppression, page margins, paper size, page ranges, scale, JavaScript budgets, animation budgets, and timeouts affect capture after Chrome has launched. They can characterize a rendering or navigation problem, but they do not establish a fix for a process that never starts.
Signs that Chrome started
- A Chrome process appears and remains alive long enough to create a DevTools or temporary profile connection.
- The error changes from “failed to start” to navigation, timeout, JavaScript, or PDF-output errors.
- A direct command creates a PDF, even if its layout is wrong.
Once startup is reliable, tune PDF settings separately. For example, test a simple page with default margins before adding custom page ranges, injected JavaScript, or long waits. This keeps output problems from obscuring process-launch diagnostics.
Rank #4
7. Common errors and targeted fixes
“Chrome doesn’t start or crashes immediately”
First run the exact executable and switches directly. If it fails there, inspect the binary, shared libraries, profile directory, user, and arguments. If it works directly, print the package’s resolved binary and simplify the harness.
Executable not found or permission denied
Replace autodetection with --chrome-binary=/absolute/path/to/chrome. Verify the path inside the same service, container, or CI image—not only in your login shell—and grant execute permission to the launching user.
Works locally but fails in CI or a service
Compare the user identity, PATH, HOME, temporary directory, working directory, architecture, mounted libraries, process limits, and signal handling. Re-run the minimal command inside the failing environment.
Fails only as root on Linux
Run as a regular user and make its profile and temporary directories writable. Avoid using --no-sandbox as the default workaround; it does not correct the underlying execution model and carries security implications.
Fails after a Chrome upgrade
Record the old and new versions, compare the selected binaries, and test Headless mode directly. If the deployment now uses Chrome M132 or later and depended on old headless-shell behavior, evaluate chrome-headless-shell or a package configuration compatible with the newer mode.
Chrome starts but the PDF is blank or times out
Treat this as a rendering or navigation investigation. Test a simple page, verify network access and JavaScript timing, then adjust the package’s timeout, page, margin, scale, range, and script options. A blank output does not by itself prove a startup failure.
Best Value
- 12th Intel Alder Lake N95 Processor – The GMKtec G3 S Mini PC is powered by the 12th Gen Intel N95 processor with 4 cores, 4 threads, 6MB cache and a burst frequency up to 3.4GHz. Compared with N100/N5105/N5100/N5095, the N95 delivers up to 36% overall performance improvement. Perfect for routine tasks, office work, and home entertainment, this compact mini desktop is more convenient than traditional bulky PCs.
- 8GB RAM & 256GB SSD Storage – Pre-installed with 8GB DDR4 memory and a fast 256GB M.2 2242 SSD, the G3 S mini desktop offers quicker startup, smoother multitasking, and faster file transfers. Enjoy seamless performance whether you’re working on multiple applications, browsing, or streaming content.
- Rich Interfaces & Connectivity – The G3 S mini computer comes equipped with USB 3.2 (up to 10Gbps), dual HDMI 2.0 (4K@60Hz), and a 3.5mm audio jack. With support for WiFi 5, Bluetooth 5.0, and Gigabit Ethernet (RJ45 1000MbE), it connects easily with monitors, projectors, printers, office equipment, and other peripherals, making it versatile for both home and business use.
- Dual 4K Display Support – Featuring upgraded Intel UHD Graphics (up to 1000MHz), the G3 S supports 4K video playback and AV1 decoding for a smooth viewing experience. With dual HDMI outputs, you can connect two 4K@60Hz displays simultaneously, enabling efficient multitasking for work and entertainment.
- GMKtec WARRANTY - GMKtec offers a 1-year limited GMKtec's warranty for each mini PC, starting from the date of the purchase. All defects due to design and workmanship are covered. With a professional after sales team always ready to attend to your needs, you can simply relax and enjoy your mini PC.
8. What to collect when the first checks do not isolate the cause
Provide these details to the package or infrastructure maintainer:
- Operating system, architecture, and whether the process runs in a container, CI runner, IDE, or service.
- Chrome or Chromium version and the full executable path.
- The complete
chrome-headless-render-pdfcommand, including every--chrome-option. - The direct Chrome command using the same executable and switches.
- Full standard error and package or driver logs, with secrets removed.
- The launching user, relevant
HOME/TMPDIRvalues, and whether the failure is reproducible outside the harness.
Without those facts, assigning a single cause would be speculation.
Or skip the browser setup
If your goal is a reliable website capture rather than maintaining a local Chrome process, ScreenshotNeo provides a website screenshot API and MCP server. It accepts consent banners before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be disabled. Bot checks, CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers identify the page verdict and billing status. Its MCP tools—take_screenshot, get_page_info, and capture_pdf—work with Claude, Cursor, and other MCP clients.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →One GET request returns PNG, JPEG, WebP, or a PDF. The API supports full-page captures with lazy images, CSS-selector element captures, dark mode, device presets and custom viewports, retina scale, PDF paper and margin controls, custom CSS and JavaScript, clicks, selector or network-idle waits, request and resource blocking, headers, cookies, user agents, authorization, timezone, geolocation, transparent backgrounds, resizing, TTL-based caching, signed public-image links, asynchronous jobs with signed webhooks, bulk capture of up to 100 URLs per call, and usage and OpenAPI endpoints.
cURL
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython
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)Node.js
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);See the ScreenshotNeo documentation for parameters and response headers. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots. Every feature is available on every plan, and yearly billing gives two months free. Create a free ScreenshotNeo account.
Frequently Asked Questions
Should I reinstall Chrome first?
No. Launch the same binary with the same switches outside the package first. Reinstall only when that direct reproduction points to the browser installation or its dependencies.
Can I use a different Chrome binary temporarily?
Yes, but make the choice explicit with the package’s --chrome-binary option and test that exact path directly. Record the version and distribution so the result is reproducible.
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 matchDoes a successful PDF prove that all pages will render correctly?
No. It proves that this browser process could start and complete this capture. Other pages may still expose navigation, JavaScript, network, or layout problems.
What should I do if several jobs launch Chrome at once?
Give concurrent processes separate writable profiles and temporary paths, then verify process and file-descriptor limits in the service context. Profile contention can look like an intermittent startup failure.
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.
