What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Chrome Headless’s command-line --screenshot captures the requested screenshot dimensions; it does not automatically measure and capture the whole document. --window-size=WIDTH,HEIGHT sets those dimensions, not a full-page mode. For a full-page image, use browser automation such as Puppeteer’s fullPage: true, or configure a DevTools Protocol capture beyond the viewport.
Why the command-line screenshot shows only the viewport
Chrome’s documented command-line reference describes --screenshot as saving a screenshot of the target page. It also documents --window-size, which sets the dimensions used for the capture. The reference does not document a full-document capture switch. Chromium’s command handler passes the parsed width and height to screenshot parameters, consistent with a fixed-size capture rather than automatic page-height detection. Chrome Headless command-line reference · Chromium command handler
As an Amazon Associate I earn from qualifying purchases.
That means a taller --window-size can request a taller screenshot, but it does not guarantee that Chrome will determine the page’s full height or include every below-the-fold element. Capture timing is a separate concern: even a correctly sized capture can miss content that has not loaded or appeared yet.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Choose the right method for the result you need
| Method | Use it for | Important limitation |
|---|---|---|
CLI --screenshot with --window-size |
A simple screenshot at specified dimensions | The documented CLI options do not provide full-document capture. |
Puppeteer fullPage: true |
A full-page image through browser automation | Delayed, lazy-loaded or scroll-triggered content may need page-specific handling. |
DevTools Protocol Page.captureScreenshot |
Low-level screenshot control beyond the viewport | Set appropriate capture bounds and check compatibility with the Chrome version in use. |
CLI --print-to-pdf |
A printable document rather than an image | The output is a PDF, not a screenshot image. |
Capture a full page with Puppeteer
Puppeteer’s documented fullPage screenshot option requests an image of the full page and defaults to false. The following runnable example uses Puppeteer 25.12.0’s API. Install Puppeteer in your project with npm install puppeteer, then save this as capture.js and run node capture.js https://example.com.
#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
const puppeteer = require('puppeteer');
(async () => {
const url = process.argv[2];
if (!url) {
throw new Error('Usage: node capture.js https://example.com');
}
const browser = await puppeteer.launch({ headless: true });
try {
const page = await browser.newPage();
await page.goto(url, { waitUntil: 'networkidle2' });
await page.screenshot({ path: 'page.png', fullPage: true });
console.log('Saved full-page screenshot to page.png');
} finally {
await browser.close();
}
})().catch((error) => {
console.error(error);
process.exitCode = 1;
});networkidle2 waits for a period with no more than two network connections, but it is not proof that an application has finished all asynchronous work. If the page renders content after an API call, waits for user interaction, or loads images only as they approach the viewport, wait for the relevant selector or trigger the page behavior before capturing. Puppeteer’s ScreenshotOptions interface documents fullPage and the related capture options.
When to use DevTools Protocol directly
The DevTools Protocol’s Page.captureScreenshot supports captureBeyondViewport, whose documented default is false. A protocol client needs to enable beyond-viewport capture and provide suitable page bounds; setting the flag alone is not a substitute for defining the intended capture region. This is a lower-level route than Puppeteer and requires attention to the protocol supported by the particular Chrome build.
Rank #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
The DevTools Protocol documentation is tip-of-tree and can change without a backwards-compatibility guarantee. Consult the Page.captureScreenshot reference alongside the protocol version used by your browser.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Make sure the intended page state exists before capture
Full-page capture concerns the capture bounds, not whether the page has completed rendering. Chrome’s CLI provides --timeout and --virtual-time-budget to control when a capture occurs. These timing controls do not guarantee that every site’s asynchronous work, animation, or user-triggered content is complete. For automation, prefer waiting for a meaningful selector or application-specific ready state when possible.
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.
- Lazy images: A page may load images only as they approach the viewport. A full-page screenshot request does not guarantee every lazy image has been populated.
- Scroll-triggered sections: Some pages create or reveal content only after scrolling. Trigger that behavior before capture if the content must appear.
- Continuously active pages: Analytics, polling or long-lived requests can make generic network-idle waits unreliable. Wait on the content needed for the screenshot instead.
Chrome Headless version and packaging
Check which browser binary your script or command actually launches before adapting an older tutorial. The Chromium project states that precompiled headless_shell binaries became available through Chrome for Testing in M118. From M132, the old Headless implementation is no longer part of the Chrome binary, and --headless=old has no effect; users relying on old Headless should migrate to the separately distributed chrome-headless-shell. These are Chromium project version milestones, not measures of how frequently users encounter viewport-only screenshots. See the Headless Chromium README.
Troubleshoot a clipped or incomplete screenshot
- Only the initial viewport appears: If using the CLI, that is consistent with its documented fixed-dimension screenshot behavior. Use Puppeteer
fullPage: trueor configure a DevTools Protocol capture region beyond the viewport. - The image is taller but still cuts off the page:
--window-sizechanges requested dimensions; it does not automatically calculate the document’s full height. Use a full-page-capable automation method. - Lower sections are present but images or content are missing: Wait for the relevant content and trigger lazy or scroll-based loading before capture. A full-page option does not guarantee application-level readiness.
- The screenshot is unexpectedly small or clipped despite the intended dimensions: Verify the exact command, the Chrome binary and version, page readiness, and any framework wrapper or viewport emulation. The documented behavior alone cannot diagnose a specific local setup.
- An old Headless command behaves differently on a newer installation: Check whether the tutorial expects the old implementation. Chromium’s M132 change means
--headless=oldno longer selects it in the Chrome binary; use the supported Headless implementation or the separately distributed shell as appropriate.
Or skip the browser setup
ScreenshotNeo offers a one-request screenshot API, with PNG, JPEG, WebP or PDF output. For example, this cURL request saves a WebP screenshot; see the ScreenshotNeo API documentation for parameters such as full-page capture and output format.
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
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpScreenshotNeo accepts cookie or consent banners before capture and removes more than 60 known consent platforms, newsletter popups and chat widgets; each of those steps can be turned off. Bot checks, blank pages, timeouts, failed loads and cache hits are not billed, and response headers report the page verdict and billing status. An MCP server exposes screenshot tools for AI agents, including Claude, Cursor and other MCP clients. The free plan includes 1,000 shots a month with no card; paid plans start at $5 for 3,000 shots.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesSign up for ScreenshotNeo’s free plan: 1,000 screenshots a month, no card required.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Sources
- Chrome for Developers: Chrome Headless command-line reference (last updated 2024-10-21 UTC).
- Chromium project: Headless Chromium README.
- Puppeteer: ScreenshotOptions interface (version 25.12.0).
- Chrome DevTools Protocol: Page.captureScreenshot (tip-of-tree).
- Chromium project: headless_command_handler.cc.
Frequently Asked Questions
Does increasing --window-size take a full-page screenshot?
No. It changes the requested screenshot dimensions; it does not automatically measure the document height.
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.
Does Puppeteer’s fullPage: true load every lazy image?
Not necessarily. It requests full-page capture, but lazy or scroll-triggered content may need to be loaded before the screenshot.
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.
