A blank Headless Chrome screenshot is a symptom, not a diagnosis. Before changing launch flags, verify the final URL, navigation response, DOM, application-ready state, viewport and capture bounds. Most failures come from capturing an error or redirect page, taking the image before client-side rendering finishes, clipping the content away, or running a page that needs graphics support unavailable in the runtime. The checks and fixes below let you identify which condition you actually have.
Start with evidence, not launch flags
A screenshot file being created only proves that Chrome captured something. It does not prove that the intended application rendered. Log the requested URL, final URL, response status, Chrome and Puppeteer versions, console errors and page errors. Puppeteer’s page.goto() returns the main resource response, which you can inspect; valid HTTP error statuses such as 404 or 500 do not necessarily make navigation throw, particularly when using chrome-headless-shell. See Puppeteer’s navigation documentation.
Diagnostic sequence for an empty image
1. Confirm the destination and response
Redirects, authentication failures and server error documents can all produce a valid-looking image. Compare the URL you requested with page.url() after navigation and print the response status. If the final URL is a login page, an error route or an unexpected redirect, fix routing or authentication before adjusting screenshot settings.
2. Confirm that the expected DOM exists
Inspect a stable application root or content selector. A single-page app can finish document navigation while its meaningful content is still absent. Choose a selector that appears only when the page state you need is rendered. Puppeteer’s waitForSelector resolves when a selector exists by default; adding { visible: true } also requires that it is not hidden with display: none or visibility: hidden. Read the behavior details in the Puppeteer API reference.
#1 Best Overall
- CRISP CLARITY: This 23.8″ Philips V line monitor delivers crisp Full HD 1920x1080 visuals. Enjoy movies, shows and videos with remarkable detail
- INCREDIBLE CONTRAST: The VA panel produces brighter whites and deeper blacks. You get true-to-life images and more gradients with 16.7 million colors
- THE PERFECT VIEW: The 178/178 degree extra wide viewing angle prevents the shifting of colors when viewed from an offset angle, so you always get consistent colors
- WORK SEAMLESSLY: This sleek monitor is virtually bezel-free on three sides, so the screen looks even bigger for the viewer. This minimalistic design also allows for seamless multi-monitor setups that enhance your workflow and boost productivity
- A BETTER READING EXPERIENCE: For busy office workers, EasyRead mode provides a more paper-like experience for when viewing lengthy documents
3. Wait for application readiness, not just navigation
domcontentloaded and networkidle are navigation milestones, not guarantees that a framework has finished rendering, a delayed request has returned or a timer has fired. Prefer an application-specific selector or a waitForFunction predicate. A fixed sleep can help prove that timing is involved, but it is less reliable and may waste time compared with waiting for the state that matters.
4. Check viewport, full-page and clipping settings
Set the viewport before navigation when responsive breakpoints affect the page. In Puppeteer, review fullPage and clip; fullPage defaults to false, while an accidental clip can exclude the application entirely. The ScreenshotOptions reference documents these bounds. For the command line, use --window-size=width,height.
5. Compare implementations only when the symptom is mode-specific
Modern --headless uses Chrome’s normal browser implementation. Since Chrome 132.0.6793.0, the former implementation is distributed separately as the chrome-headless-shell binary. Puppeteer supports headless: true for Headless Chrome and headless: 'shell' for Headless Shell. Reproduce the same URL in headful Chrome, unified Headless and Headless Shell, recording the exact browser and Puppeteer versions. A difference between modes is useful evidence; switching modes blindly is not a general fix. See Chrome’s Headless mode documentation.
6. Investigate graphics only for graphics-dependent pages
WebGL, WebGPU and other GPU-backed features can render differently in a container or virtual machine. Check the browser’s graphics status (for example, chrome://gpu) and compare a supported configuration for the exact operating system, container and Chrome version. Chrome’s WebGPU/WebGL testing guide shows a specialized GPU-oriented example and an environment reporting software-only graphics. Those arguments are workload-specific; they are not a universal cure for blank screenshots, and enabling unsafe features or disabling the GPU indiscriminately can create new failures.
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 minuteRank #2
- CRISP CLARITY: This 22 inch class (21.5″ viewable) Philips V line monitor delivers crisp Full HD 1920x1080 visuals. Enjoy movies, shows and videos with remarkable detail
- 100HZ FAST REFRESH RATE: 100Hz brings your favorite movies and video games to life. Stream, binge, and play effortlessly
- SMOOTH ACTION WITH ADAPTIVE-SYNC: Adaptive-Sync technology ensures fluid action sequences and rapid response time. Every frame will be rendered smoothly with crystal clarity and without stutter
- INCREDIBLE CONTRAST: The VA panel produces brighter whites and deeper blacks. You get true-to-life images and more gradients with 16.7 million colors
- THE PERFECT VIEW: The 178/178 degree extra wide viewing angle prevents the shifting of colors when viewed from an offset angle, so you always get consistent colors
A reliable Puppeteer capture pattern
The following script checks navigation, records useful diagnostics, waits for a visible application-ready marker and then captures the whole page. Replace the URL and selector with values belonging to your application. The selector is an example, not a requirement.
const puppeteer = require('puppeteer');
(async () => {
const url = 'https://example.com/';
const browser = await puppeteer.launch({ headless: true });
const page = await browser.newPage();
page.on('console', message => {
console.log('[console]', message.type(), message.text());
});
page.on('pageerror', error => {
console.error('[pageerror]', error.message);
});
await page.setViewport({ width: 1280, height: 900, deviceScaleFactor: 1 });
try {
const response = await page.goto(url, {
waitUntil: 'domcontentloaded',
timeout: 30_000,
});
console.log({
requestedUrl: url,
finalUrl: page.url(),
status: response ? response.status() : null,
});
await page.waitForSelector('#app[data-ready="true"]', {
visible: true,
timeout: 30_000,
});
await page.screenshot({
path: 'screenshot.png',
fullPage: true,
});
} catch (error) {
console.error('Capture failed:', error);
await page.screenshot({ path: 'failure-state.png', fullPage: true }).catch(() => {});
process.exitCode = 1;
} finally {
await browser.close();
}
})();If the page has no readiness attribute, use a stable element that only appears with the required content, or wait on a predicate such as a non-empty result count. A selector timeout should be treated as diagnostic information: save the failure-state image, inspect the DOM and review console output instead of simply increasing the timeout.
Command-line checks with Chrome
For a known viewport and a page that may render after a short delay, Chrome’s documented flags provide a bounded experiment:
chrome --headless --screenshot --window-size=1280,900 --timeout=5000 https://example.com/The --timeout value is a maximum wait before --screenshot, --dump-dom or --print-to-pdf captures, even if loading continues, as Chrome explains in its Headless command-line reference. It is not proof that your application is ready. Increase it only after confirming that the page is progressing. For code driven by JavaScript timers, test an appropriate --virtual-time-budget separately; virtual time advances timer-driven code, but it does not repair a failed request or missing selector.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #3
- Clear visuals. Fluid motion: A 144Hz refresh rate and 1ms MPRT deliver smooth, tear‑free motion across work, gaming, and streaming for clearer, more fluid viewing.
- Eye comfort: TÜV Rheinland 3‑star* certification reduces harmful blue light while preserving stunning color quality without compromise. *TÜV Rheinland 3-star eye comfort certification.
- Wide viewing angle: Get consistent views across a wide 178° /178° viewing angle.
- In-Plane Switching (IPS): See excellent color accuracy and consistency across wide viewing angles with In-plane Switching (IPS) technology.
- Ultra-thin bezels: Maximize your viewing experience with thin bezels.
Match the fix to the observed clue
| Observed clue | What to check | Appropriate response |
|---|---|---|
| Final URL is wrong or shows an error document | Redirect chain, authentication, response status and page URL | Correct the target, credentials or routing; handle the returned response explicitly. |
| DOM exists but application content is absent from the image | Application-specific selector and its visibility | Wait for the rendered state rather than relying only on navigation completion. |
| Content appears after a delay or timer | Loading state, delayed requests and timer-driven code | Wait for a meaningful condition; use a bounded CLI timeout or virtual-time budget when appropriate. |
| Image is tiny, clipped or captures an unintended region | Viewport, fullPage, clip and CLI window size |
Set dimensions deliberately and remove or correct unintended clipping. |
| Only one mode or binary differs | Chrome binary, Puppeteer version and Headless implementation | Run controlled comparisons between unified Headless, Headless Shell and headful Chrome. |
| Page specifically uses WebGL or WebGPU | Graphics feature status and runtime support | Investigate the GPU configuration for that workload; do not apply special flags blindly. |
Common failure messages and targeted fixes
“Waiting for selector failed”
The selector may be wrong, the request may have failed, or the app may have rendered an error state. Log the final URL and status, dump relevant HTML, listen for pageerror and console messages, and verify the selector in a normal browser. Only extend the timeout after establishing that the application is still progressing.
Navigation timeout
A slow third-party resource can keep navigation open even when the required content is already visible. Use a readiness selector after a sensible navigation milestone, and decide whether nonessential resources should be blocked. Do not hide a genuinely failed page by converting every timeout into a successful screenshot.
HTTP 404 or 500 with no thrown exception
Inspect the response returned by page.goto(). A browser can capture the server’s error document successfully, so status handling is part of screenshot correctness.
Works headful, blank in Headless
Record the exact binaries and versions, then compare unified Headless with Headless Shell. Check viewport-dependent CSS, feature detection and graphics status. Keep the comparison narrow so you know whether the difference comes from mode, runtime libraries or application logic.
Rank #4
- CURVED FOR ENHANCED ENGAGEMENT: An immersive viewing experience with a curved monitor that wraps more closely around your field of vision; It creates a wider view, enhancing depth perception and minimizing peripheral distraction
- SMOOTH PERFORMANCE FOR SEAMLESS CONTENT: Stay in the action when playing games, watching videos, or working on creative projects; The 100Hz refresh rate reduces lag and motion blur so you don't miss a thing in fast-paced moments¹
- MORE GAMING POWER: Gain the edge with optimizable game settings; Color and image contrast can be adjusted to see scenes more vividly and spot enemies hiding in the dark; Game Mode adjusts any game to fill the screen so you can view every detail²
- KEEP IT EASY ON THE EYES: Care for your eyes and stay comfortable, even during long sessions; Advanced eye comfort technology certified by TÜV reduces eye strain by minimizing blue light and reducing irritating screen flicker²
- INCREASED VERSATILITY: Connect to more; Plug devices straight into your monitor for increased flexibility, making your computing environment even more convenient
WebGL canvas is empty while ordinary HTML works
Confirm that the page actually requires WebGL/WebGPU and inspect graphics capability before changing flags. A software-only environment may not provide the feature or performance the page expects. Use a supported graphics setup for your OS and browser version, and keep specialized launch arguments limited to that test.
Reliability and performance practices
- Use deterministic readiness: expose a data attribute or stable root when your application has finished rendering, rather than guessing a universal sleep.
- Keep diagnostics with artifacts: store the final URL, status, browser version, viewport, console output and failure-state screenshot alongside each failed run.
- Control dimensions deliberately: choose one viewport for regression tests and set device scale factor consciously; responsive breakpoints can change both layout and content.
- Separate page failure from capture failure: a blank image after a 500 response is an application or routing problem, not a screenshot API problem.
- Bound waits: every navigation and readiness wait should have a timeout and an actionable error path, so CI does not hang indefinitely.
- Use full-page capture selectively: it can require additional layout and memory work. Capture the viewport when that is all the test needs, and use
fullPagefor documents whose complete height matters.
Or skip the browser setup
ScreenshotNeo provides a website screenshot API and MCP server for developers. A single request returns PNG, JPEG, WebP or PDF. Before capture it accepts cookie or consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups and chat widgets; each cleanup step can be switched off. Only clean shots are billed: bot checks or CAPTCHAs, blank pages, timeouts, failed loads and cache hits cost nothing, and the response reports the result in X-Page-Verdict and X-Billed headers.
Use the API documentation at https://screenshotneo.com/docs/ for the current parameter list. This basic call captures a URL without managing a Chrome process:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpimport requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://example.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://example.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);For workflows that need more control, ScreenshotNeo supports full-page captures with lazy images loaded, CSS-selector element captures, dark mode, 12 device presets or custom viewports, retina scale, PDF paper size/margins/orientation/page ranges, HTML/CSS-to-image, custom CSS and JavaScript, pre-capture clicks, hidden selectors, waits for selectors or network idle, ad/tracker/request-type blocking, custom headers/cookies/user agents/Authorization, timezone and geolocation, transparent backgrounds, resizing, configurable-TTL caching, signed links, asynchronous jobs with signed webhooks, bulk capture of up to 100 URLs per call, a usage API and an OpenAPI specification. Parameter names used by other screenshot APIs also work, which can simplify migration.
Its MCP server exposes take_screenshot, get_page_info and capture_pdf to Claude, Cursor and other MCP clients. Plans are:
Best Value
- 【INTEGRATED SPEAKERS】Whether you're at work or in the midst of an intense gaming session, our built-in speakers provide rich and seamless audio, all while keeping your desk clutter-free.
- 【EASY ON THE EYES】 Protect your eyes and enhance your comfort with Blue-Light Shift technology. This feature reduces harmful blue light emissions from your screen, helping to alleviate eye strain during long hours of use and promoting healthier viewing habits.
- 【WIDEN YOUR PERSPECTIVE】Our sleek minimal bezel design ensures undivided attention. The nearly bezel-free display seamlessly connects in a dual monitor arrangement, delivering an unobstructed view that lets you focus on more at once, completely distraction-free.
| Plan | Included shots per month | Price |
|---|---|---|
| Free | 1,000 | $0, no card |
| Starter | 3,000 | $5 |
| Growth | 15,000 | $15 |
| Pro | 60,000 | $39 |
| Scale | 250,000 | $99 |
| Business | 1,000,000 | $249 |
Yearly billing gives two months free, and every feature is available on every plan. If you want to stop maintaining browser launch flags and readiness plumbing, sign up for the free 1,000-shot monthly plan; no credit card is required.
Frequently Asked Questions
Should I always add a long delay before taking a screenshot?
No. A selector or application predicate that represents the required rendered state is more precise and usually less flaky than a universal sleep.
Does a successful PNG prove that the page returned HTTP 200?
No. Inspect the navigation response and final URL; Chrome can capture an error document or redirect destination.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
When is GPU troubleshooting relevant?
Investigate graphics when the page depends on WebGL, WebGPU or another GPU-backed feature. Ordinary HTML screenshots do not justify applying specialized GPU flags.
Which Headless mode should I use?
Use the mode your project supports, record the Chrome and Puppeteer versions, and compare implementations only when the failure appears mode-specific.
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.
