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 matchIncorrect Chromium Headless screenshots usually come from mixing four different layers: the requested window size, the page’s CSS viewport, the virtual display and device scale factor, and the moment the capture occurs. Measure each layer separately, then change only the setting that is wrong. Start by recording your exact browser build and launch path; headless behavior and screen emulation are version-sensitive.
Identify which dimension is actually wrong
Before changing flags, create a minimal reproduction and record:
- Chrome or Chromium version and the binary name.
- Headless mode (
--headless,--headless=new, or a separatechrome-headless-shellbinary). - Operating system or container image.
- Automation library and version, if using Puppeteer or another client.
- Every launch argument and screenshot API call.
- Expected CSS viewport dimensions and expected output bitmap dimensions.
Then distinguish these measurements:
| Layer | How to inspect it | What it controls |
|---|---|---|
| Window bounds | CLI --window-size or automation launch options |
Initial browser window dimensions |
| CSS viewport | window.innerWidth, window.innerHeight |
Layout breakpoints and CSS pixels available to the page |
| Virtual screen | Headless screen information, including size, scale factor, orientation and work area | Display-aware page behavior and device metrics |
| Bitmap | Image metadata or an image editor | Physical pixel dimensions of the saved PNG, JPEG or WebP |
| Capture state | Load events, selectors, network idle and timing flags | Whether content is complete when the shot is taken |
A screenshot that is exactly twice as wide or tall often indicates a device-scale-factor relationship, but do not assume that until you compare the bitmap with the CSS viewport and configured screen. A page that looks zoomed can instead have a CSS viewport or responsive breakpoint problem.
Check the headless implementation and version first
Headless packaging changed substantially. Chromium’s README says precompiled headless shell binaries have been distributed as chrome-headless-shell through Chrome for Testing from milestone 118. From milestone 132, the old Headless implementation is no longer part of the Chrome binary, so --headless=old has no effect. If a guide tells you to use that switch, verify that it applies to your binary.
Recommended Free Tools
#1 Best Overall
- 1,000mcg of Chromium Per Tablet
- Chromium From Chromium Picolinate
- 240 Tablets In Each Bottle
- Non-GMO, Gluten Free, and Soy Free
- Made in a GMP Compliant, FDA Registered Facility
Virtual headless screen configuration is documented as available in stable Chrome beginning with version 142. Older builds may reject or ignore newer screen options. Include the exact build in bug reports and reproduce with the same binary in your CI container.
Set a predictable viewport with the CLI
For a single target bitmap, use a positive integer width and height with --window-size and capture with --screenshot:
chrome --headless --screenshot --window-size=412,892 https://developer.chrome.com/Chrome’s documented CLI path writes screenshot.png by default. The current command handler expects the comma-separated values as plain positive dimensions. Values such as 1280px, missing numbers, reversed separators or nonpositive values are invalid; malformed values are logged and ignored, which can leave the default size in effect.
- Run the command with an explicit output filename while debugging.
- Read the saved image dimensions rather than trusting the filename or command line.
- Open DevTools-style JavaScript in the page (or use automation) to print
window.innerWidthandwindow.innerHeight. - Compare all three values before changing scale settings.
Changing --window-size changes the requested window. It does not by itself define a realistic multi-monitor environment or guarantee a particular physical-pixel ratio.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Rank #2
- High-potency Chromium supports sugar, fat and protein metabolism (1)
- Helps maintain blood sugar levels already within a normal range(1)
- Easy dose of just one tablet a day ' an excellent choice for vegetarians
- Non-GMO
- During the summer months products may arrive warm but Amazon stores and ships products in accordance with manufacturers' recommendations, when provided.
Configure a virtual screen when display behavior matters
Use --screen-info when the page must behave as though it is on a particular display. Chrome documents a virtual headless screen that is independent of physical monitors. Screen information can describe resolution, scale factor, orientation, work area and multiple displays.
This is different from merely asking for a 1280-by-800 screenshot. A display-aware application may inspect screen properties, place windows relative to work areas or react to orientation. Configure those properties only when your test requires them.
For a browser that is already running, the DevTools Protocol provides Emulation.addScreen and Emulation.removeScreen for dynamic monitor changes. Chrome documents these capabilities as supported in Puppeteer. They are appropriate for automation that tests monitor insertion, removal or changing display characteristics rather than one static image.
Why is my headless Chrome screenshot twice the expected size?
Measure the configured screen’s scale factor and the bitmap dimensions. A scale factor can cause a CSS viewport of 800 pixels to produce a bitmap around 1600 physical pixels, depending on the emulation and capture path. The correct remedy is to align the desired output with the device-scale-factor or virtual-screen configuration—not to shrink the page with CSS or browser zoom.
Rank #3
- CHROMIUM PICOLINATE: Most optimally absorbed form of essential nutrient Chromium
- HIGH POTENCY: Provides 1,000 mcg of Chromium Picolinate per Vegetarian Tablet
- ROOTED IN WELLNESS: Carlyle provides premium, honest supplements in your pursuit to healthy living
- CARLYLE MANUFACTURERS: Laboratory Tested, Trusted Ingredients, Superior Quality, 100% Guaranteed!
- VEGETARIAN FORMULA: Naturally free of Gluten, Artificial Flavor, Artificial Sweetener, & Non-GMO
- If the CSS viewport is wrong, fix viewport or window configuration.
- If the CSS viewport is right but the bitmap ratio is wrong, inspect device scale factor and screen emulation.
- If both dimensions are right but text or controls appear enlarged, inspect page zoom, CSS transforms and responsive breakpoints.
- If only some assets look soft, check the asset’s intrinsic resolution and image scaling separately from the browser bitmap.
Capture the screen information and devicePixelRatio in the same run. Treat the ratio as a diagnostic measurement, not a universal “set this flag” answer; the correct setting depends on whether you launch Chrome directly, through Puppeteer, or through CDP.
Separate resolution problems from capture timing
A correctly sized bitmap can still be visually incomplete. Chrome’s --timeout option defines the maximum wait in milliseconds before --screenshot captures, even if loading continues. A short timeout can leave web fonts, lazy images or client-rendered content unfinished.
--virtual-time-budget advances timer-driven page code. It can help deterministic pages that rely on timers, but it is a readiness control, not a resolution control. Do not use either flag to compensate for a scale mismatch.
Use an explicit readiness condition in automation
- Wait for a stable selector that proves the relevant component rendered.
- Wait for fonts or images when they affect layout.
- Use a measured delay only when the page has no reliable readiness signal.
- For network-heavy pages, use a network-idle policy carefully; analytics or streaming requests may never become idle.
Choose the control that matches your goal
| Approach | Best for | Limit |
|---|---|---|
--window-size plus --screenshot |
One static screenshot at a target size | Does not model a complete multi-display environment |
--screen-info |
Display size, scale, orientation and work-area behavior | Version-sensitive and more configuration than a one-off shot |
CDP Emulation.addScreen/removeScreen |
Runtime monitor-change tests | Requires a running automation/CDP session |
| Puppeteer screen integration | Keeping screen state in browser tests | Requires compatible Chrome and Puppeteer versions |
--timeout or --virtual-time-budget |
Controlling when content is captured | Does not set resolution or scale |
Troubleshooting common failures
The requested size is ignored
Check that the argument is exactly --window-size=WIDTH,HEIGHT, with two positive integers and no CSS units. Look at stderr for a parse warning and verify the output file dimensions. A malformed value may be ignored rather than terminating the browser.
Rank #4
- 3rd Party Lab Tested for Purity & Quality
- No Artificial Color, Flavor or Sweetener, No Preservatives, No Sugar, No Starch, No Corn, No Soy, No Egg, No Lactose, No Gluten, No Wheat, No Yeast, No Fish
- 1000 mcg (1mg) of Chromium Picolinate per Tablet - 240 Tablets / Servings per bottle
- Non-GMO & Gluten Free
- TOP QUALITY GMP CERTIFIED PRODUCTS - All Best Naturals products are manufactured in accordance with Good Manufacturing Practices (GMP), among the highest standards in the world -- Proudly Made in USA -- Purity & Potency.
--headless=old changes nothing
On Chrome milestone 132 and later, old Headless is no longer in the Chrome binary. Use the current headless implementation or the separately distributed chrome-headless-shell where that is the intended runtime.
The page uses the wrong responsive breakpoint
Log window.innerWidth and window.innerHeight. If they differ from the intended CSS viewport, correct the launch or emulation settings before touching page CSS. Also check whether the page has a viewport meta tag when testing mobile layouts.
The bitmap is larger than the viewport
Compare bitmap-to-viewport ratios and inspect devicePixelRatio and virtual-screen scale. Align the scale configuration with your required physical-pixel output. Do not reduce the page with a transform; that changes the content rather than the capture model.
Content is clipped or blank
Check capture timing, lazy loading and navigation errors. Increase the documented timeout or wait for a selector that proves the page is ready. A blank page, failed load or bot check is a page-state problem, not evidence that the viewport is incorrectly scaled.
Best Value
- CHROMIUM PICOLINATE: Receive this essential trace mineral in this high potency formula
- VEGETARIAN FORMULA: Each tablet delivers 1,000 mcg of Chromium Picolinate
- EXPERTLY CRAFTED: Our professional formula is backed by our commitment to purity and potency
- HORBAACH MANUFACTURERS: Laboratory Tested, Trusted Ingredients, Superior Quality, 100% Guaranteed!
- NATURALLY FREE OF: Gluten, Wheat, Milk, Lactose, Artificial Flavor, Preservatives & Non-GMO
Results differ between local and CI
Compare binary versions, container base images, flags, automation-library versions, fonts, locale, timezone and screen configuration. Keep a minimal reproduction and record expected CSS and bitmap dimensions for every environment.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
ScreenshotNeo provides a website screenshot API and MCP server when you want a rendered image without maintaining Chromium launch flags. A GET request returns PNG, JPEG, WebP or PDF. Before capture it accepts cookie/consent banners and removes more than 60 known consent platforms, newsletter popups and chat widgets; each step can be disabled.
Only clean shots are billed. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads and cache hits cost nothing, and the response identifies the result with X-Page-Verdict and X-Billed headers. Its MCP server exposes take_screenshot, get_page_info and capture_pdf to Claude, Cursor and other MCP clients.
Use the API documentation at https://screenshotneo.com/docs/ for all options, including viewport and device presets, full-page and element capture, dark mode, retina scale, PDF settings, custom CSS and JavaScript, clicks, waits, blocking rules, headers, cookies, user agents, authorization, timezone, geolocation, transparent backgrounds, resizing, cache TTL, signed links, asynchronous webhooks, bulk capture of up to 100 URLs per call, usage reporting and the OpenAPI specification.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
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}`);Every feature is included on every plan: 1,000 screenshots per month are free with no card; paid plans start at $5 for 3,000 shots, with yearly billing providing two months free. Create a free ScreenshotNeo account to try the no-card tier.
Verification checklist
- Browser build, binary and headless implementation recorded.
- Launch arguments validated, especially
--window-size. - CSS viewport measured in the page.
- Virtual screen and scale factor measured when display behavior matters.
- Bitmap dimensions read from the actual output file.
- Readiness condition and timeout documented separately from resolution settings.
- Local and CI runs use comparable fonts, versions and flags.
Frequently Asked Questions
Does increasing --window-size improve screenshot quality?
It changes the requested window dimensions, not the intrinsic quality of page assets. Quality and physical bitmap size also depend on device scale and the capture path.
Can I use screen emulation for a normal one-page screenshot?
Yes, but it is usually unnecessary. Use it when the page or test reads display properties, orientation, work area or multiple monitors; otherwise a validated window size is simpler.
Which flag makes a page finish rendering?
No single flag guarantees readiness. Use --timeout or virtual time where appropriate, and prefer a selector or other page-specific readiness condition in automation.
Free tools Windows power users keep installed
One-click scans. No signup required.
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.
