Free tools Windows power users keep installed
One-click scans. No signup required.
If chrome-headless-render-pdf reports that Chrome does not start or crashes immediately, first run the exact Chrome executable with the exact switches outside your test, service, or CI harness. That single comparison separates a browser or launch-configuration failure from an environment failure. Then verify the executable selected by the package, inspect every argument, check the Linux user context, and confirm that your Chrome version still matches the headless mode your setup expects.
Start with a reproducible launch test
The package is a Node.js PDF renderer that launches Chrome. Do not begin by changing PDF margins, JavaScript delays, or random flags. Those settings affect rendering after startup, not whether Chrome can create a process.
- Find the executable that the job actually uses. Record its absolute path, Chrome version, operating-system user, working directory, and complete argument list.
- Run that executable directly from a normal user command prompt, using the same switches. Use a temporary profile so an existing profile or locked session cannot confuse the result.
- Capture the process output and exit code. A direct failure points first to the browser installation or launch configuration. A successful direct launch moves the investigation to the harness, service, permissions, environment variables, or timing.
Linux example
Substitute the path and switches from your job; do not copy flags that your application does not use:
/usr/bin/google-chrome --headless --disable-gpu --no-first-run --user-data-dir=/tmp/chrome-startup-check about:blankUse the same Chrome binary, not merely another browser installed on the machine. ChromeDriver troubleshooting guidance specifically recommends checking the binary recorded in its driver log and reproducing from a normal user’s command prompt.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →#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.
Windows example
"C:Program FilesGoogleChromeApplicationchrome.exe" --headless --disable-gpu --no-first-run --user-data-dir="%TEMP%chrome-startup-check" about:blankIf this command exits cleanly, repeat it with the package’s real switches. A test with different flags does not prove that the package launch is healthy.
Verify which Chrome chrome-headless-render-pdf selected
Automatic discovery can select an unexpected installation, an old binary, or no usable binary at all. The package README exposes two controls that matter directly here:
--chrome-binaryselects an explicit executable when autodetection is wrong or incomplete.--chrome-optionpasses a Chrome argument. Use it to reproduce the flags from your known-good direct command.
Print or log the resolved path and final argument array at startup. Check for quoting errors, duplicated switches, a stale profile directory, and flags injected by a wrapper or CI image. If your programmatic API builds options, inspect the resulting array rather than the source defaults alone.
Minimal command-line diagnostic
chrome-headless-render-pdf \
--chrome-binary=/usr/bin/google-chrome \
--chrome-option=--headless \
--chrome-option=--user-data-dir=/tmp/pdf-check \
input.html output.pdfUse the option spelling documented by the version you installed. If the command-line interface rejects an option, run the package’s help command and compare its installed README with your deployment version; the inspected documentation does not establish a universal compatibility matrix.
Recommended Free Tools
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
Reduce the environment before changing Chrome
When direct Chrome startup succeeds, simplify the failing job until only the renderer remains:
- Run the same command as the same operating-system account used by the service or CI job.
- Run a tiny script that renders one local, static HTML file.
- Remove the IDE, test runner, worker pool, container entrypoint, and background service one at a time.
- Reintroduce those layers individually while preserving the logged executable and switches.
This branch commonly exposes a missing HOME directory, unwritable temporary storage, a service account with a different PATH, a read-only profile location, an outdated container image, or a timeout that kills Chrome before the handshake. Fix the first failing layer instead of adding unrelated browser flags.
Check the Linux user context
ChromeDriver troubleshooting documentation states: “A common cause for Chrome to crash during startup is running Chrome as root user (administrator) on Linux.” Run the renderer as a regular user with a writable home and temporary directory. Verify with the identity command used by your environment and compare it with the account that succeeds interactively.
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 currently runs as root, prefer changing the container user, filesystem ownership, and sandbox permissions. Only investigate a narrowly documented, security-reviewed exception with your platform owner.
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 →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
Check headless mode and Chrome version
Headless behavior changed over time. Chromium documents the newer Headless mode beginning with Chrome 112. As of Chrome M132, the old headless shell is no longer part of the Chrome binary; users of that former shell functionality should migrate to the separately distributed chrome-headless-shell. These milestones do not prove a cause by themselves. Match the installed version, the binary distribution, and the mode your package expects.
- Record
google-chrome --version(or the equivalent executable command). - Determine whether your deployment calls Chrome’s current headless mode or expects the legacy shell.
- Compare the actual binary on the failing host with the one used in development.
- After a browser upgrade, rerun the direct same-binary, same-switch test before changing application code.
A version transition is a useful lead only when its version and error match; do not label it the cause without that evidence.
Keep startup separate from PDF rendering
Once Chrome starts, investigate output settings independently. The package documents PDF controls for margins, paper size, page ranges, scale, JavaScript budgets, and animation budgets. Chrome’s command-line PDF options include --print-to-pdf, header/footer suppression, and --timeout. These can characterize a page-load or rendering problem, but they do not establish a startup fix.
Startup failure symptoms
- The process exits before a debugging connection or renderer is available.
- The driver reports that Chrome crashed during startup or cannot obtain a session.
- A direct launch with the same executable and switches fails immediately.
Rendering or capture symptoms
- Chrome starts, but the PDF is blank, incomplete, or timed out.
- Changing page size, margins, wait budgets, or JavaScript settings changes output.
- The browser remains alive long enough to load a page or expose a debugging endpoint.
Use the symptom boundary to avoid masking a launch defect with a larger render timeout.
Rank #4
Common failures and targeted fixes
| Symptom | Likely branch | Action |
|---|---|---|
| Direct command fails immediately | Executable or launch configuration | Check the path, permissions, dependencies, profile directory, and switches; test the installation outside the package. |
| Direct command works, service fails | Harness or execution identity | Run under the service account, compare environment variables and writable directories, then reduce wrappers. |
| Only Linux root jobs crash | User context and sandbox | Run as a regular user; do not default to --no-sandbox. |
| Failure follows a Chrome upgrade | Headless distribution or mode | Check the version and whether legacy shell functionality now requires chrome-headless-shell. |
| Chrome starts but PDF is wrong | Rendering configuration | Inspect page settings, wait budgets, JavaScript, animations, and PDF flags separately. |
| Autodetection chooses the wrong browser | Package selection | Set --chrome-binary explicitly and log the resolved path. |
Make the diagnosis reliable in CI and services
- Pin or deliberately update the browser image; record the version in every failure artifact.
- Create a unique, writable user-data directory per concurrent job to prevent profile locks.
- Preserve Chrome stderr, package logs, exit status, and the final argument list.
- Use the same user, PATH, HOME, locale, proxy, and filesystem permissions in the reproduction as in production.
- Run one minimal local HTML case before testing remote pages, authentication, or complex JavaScript.
- Set timeouts only after startup is proven; a longer timeout cannot repair a process that never launched.
Or skip the browser setup
If your goal is a dependable website image or PDF rather than maintaining a local Chrome process, ScreenshotNeo provides a single HTTP request and an MCP server for Claude, Cursor, and other MCP clients. It accepts cookie and consent banners before capture, removes more than 60 known consent platforms plus newsletter popups and chat widgets, and bills only clean shots: bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed. Each response identifies the result with X-Page-Verdict and X-Billed headers.
For a direct call, see the ScreenshotNeo documentation:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpThe same endpoint supports PNG, JPEG, WebP, and PDF output, with options for full-page lazy-image loading, CSS-element capture, device presets, custom viewport and retina scale, PDF paper and page ranges, custom CSS and JavaScript, clicks, selector waits, network-idle waits, blocked resources, headers, cookies, user agents, authorization, timezone, geolocation, transparent backgrounds, resizing, chosen cache TTLs, signed image links, asynchronous webhooks, bulk capture of up to 100 URLs per call, and a usage API. Its parameter names are compatible with those used by other screenshot APIs, which can simplify migration.
Python
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}`);The Free plan includes 1,000 shots each month with no card. Paid plans start at $5 for 3,000 shots; yearly billing gives two months free. Sign up for the free ScreenshotNeo plan.
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 minuteWindows 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 reinstallWhat to collect when the first checks do not isolate the cause
Ask for the operating system and architecture, Chrome version, exact executable path, complete command or package options, user identity, package version, full startup error and stderr, whether the direct same-binary test succeeds, and whether the failure occurs only in CI, a container, an IDE, or a service. Without those details, the cause remains undetermined rather than safely attributable to one flag.
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.
Frequently Asked Questions
Should I add --no-sandbox to make Chrome start?
No. First stop running Chrome as root on Linux and correct the user, permissions, and sandbox environment. The documented guidance describes the workaround as unsupported and highly discouraged.
Does increasing the PDF timeout fix an immediate Chrome crash?
No. Timeout and PDF settings apply after startup. Reproduce the executable and switches directly before tuning rendering budgets.
When do I need chrome-headless-shell?
Check the installed version and your dependency’s expected mode. Chromium says the former headless shell stopped being part of the Chrome binary at M132; migrate only when your setup relies on that legacy functionality.
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.
