The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →For a headless Chrome screenshot at a fixed size, pass --window-size=WIDTH,HEIGHT with --headless --screenshot, then give Chrome the page URL. For example: chrome --headless --screenshot --window-size=412,892 https://example.com/. This sets the capture dimensions; it does not, by itself, prove that a browser window was maximized, entered fullscreen, or that the page’s Fullscreen API worked.
Choose the right meaning of “fullscreen”
The right setting depends on what you need to test. A fixed-size screenshot, a virtual display, a maximized browser window, and a web page entering fullscreen are related but distinct cases.
As an Amazon Associate I earn from qualifying purchases.
| Goal | Use | What it controls |
|---|---|---|
| Capture at fixed dimensions | --window-size=WIDTH,HEIGHT with --screenshot |
The size used for the screenshot. Chrome’s command-line reference documents this pattern and uses 412 × 892 as an example. Chrome Headless command-line reference. |
| Configure a virtual display | --screen-info=… |
Virtual screen properties such as origin, size, scale factor, orientation, and work area. Chrome for Developers’ virtual-screen guide. |
| Test a maximized or fullscreen window | --start-maximized or --start-fullscreen, with an appropriate virtual screen if needed |
Window behavior rather than only the screenshot dimensions. The virtual-screen guide calls out work area and scale factor as considerations. |
| Test a page’s Fullscreen API | Use the page’s own fullscreen behavior, such as element.requestFullscreen() |
Whether web content enters fullscreen; a screenshot’s dimensions alone do not verify this. |
Set the size for a headless screenshot
- Choose the width and height you want to capture, in pixels. The official example is 412 × 892; use dimensions appropriate to your test rather than treating that example as a recommendation.
- Run Chrome with
--headless,--screenshot, and--window-size=WIDTH,HEIGHT, followed by the URL. - Open the resulting screenshot and verify the captured dimensions and page layout. If you need to test a screen or window state, use the virtual-screen approach below instead of relying on image dimensions.
chrome --headless --screenshot --window-size=412,892 https://example.com/Chrome also documents --timeout to set a maximum wait before capture and --virtual-time-budget to fast-forward time-dependent page code. These options affect capture timing, not the configured dimensions. See the command-line reference for the current option details.
Configure a virtual screen or window state
Use --screen-info when the test depends on display properties beyond a screenshot’s width and height. Chrome’s guide describes configuring virtual screen origin, size, scale factor, orientation, and work area. Virtual screens are separate from the host’s physical displays.
#1 Best Overall
- SLIM. LIGHTWEIGHT. READY TO GO: The all-new slim design is perfect for busy lives on the go.
- SKILLFULLY DESIGNED. MILITARY TOUGH: Built with premium craftsmanship to withstand the occasional drop or ding.
- ALL-DAY, ALL-IN-ONE CHARGING: Power through your school day – and beyond – with a long-lasting 12-hour battery.¹
- 3X FASTER THAN THE PREVIOUS GENERATION OF WIFI: Crush your schoolwork in record time with Wi-Fi that’s three times faster than the previous generation of Wi-Fi.
- YOUR PHONE AND CHROMEBOOK WORK BETTER TOGETHER: Easily transfer files between devices, and control your phone right from your Chromebook.
The guide documents virtual-screen configuration in stable Chrome starting with version 142. Confirm the Chrome version installed in your local environment or CI before depending on this option. Its examples use 800 × 600 and 600 × 800 displays to illustrate configuration; those are example values, not universal test sizes. Refer to Configure virtual screens in Headless mode for the supported syntax and examples.
For maximized or fullscreen window tests, the guide lists --start-maximized and --start-fullscreen. Choose the switch that matches the behavior under test, and account for work area and scale factor where they matter. Do not infer that a page’s Fullscreen API succeeded merely because the captured image has the expected dimensions.
Rank #2
- FOR HOME, WORK, & SCHOOL – With an Intel processor, 14-inch display, custom-tuned stereo speakers, and long battery life, this Chromebook laptop lets you knock out any assignment or binge-watch your favorite shows..Voltage:5.0 volts
- HD DISPLAY, PORTABLE DESIGN – See every bit of detail on this micro-edge, anti-glare, 14-inch HD (1366 x 768) display (1); easily take this thin and lightweight laptop PC from room to room, on trips, or in a backpack.
- ALL-DAY PERFORMANCE – Reliably tackle all your assignments at once with the quad-core, Intel Celeron N4120—the perfect processor for performance, power consumption, and value (2).
- 4K READY – Smoothly stream 4K content and play your favorite next-gen games with Intel UHD Graphics 600 (3) (4).
- MEMORY AND STORAGE – Enjoy a boost to your system’s performance with 4 GB of RAM while saving more of your favorite memories with 64 GB of reliable flash-based eMMC storage (5).
Use Chrome arguments with Puppeteer or Selenium
When a framework launches Chrome, pass the relevant Chrome arguments through its launch or browser options rather than running the bare command separately. Chrome’s headless documentation provides official examples for Puppeteer’s headless: true and Selenium’s Chrome options with --headless. The example below shows the Puppeteer launch pattern for a fixed-size capture.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteconst browser = await puppeteer.launch({
headless: true,
args: ['--window-size=412,892']
});
const page = await browser.newPage();
await page.goto('https://example.com/');
await page.screenshot({ path: 'shot.png' });
await browser.close();For Selenium, add --headless and --window-size=WIDTH,HEIGHT to the Chrome options passed to the driver. Consult the framework’s documentation for the exact API in the version you use. Chrome’s headless behavior and framework examples are documented in Chrome Headless mode.
Rank #3
- Storage: 16GB Flash Memory
- OS: Chrome OS
- Screen Size: 11.6"
Understand headless Chrome version behavior
Current headless Chrome shares its implementation with headful Chrome. Since Chrome 132.0.6793.0, the older headless implementation is offered as a separate chrome-headless-shell binary. This distinction matters if a CI job or script explicitly invokes the legacy shell; check which binary and version your test actually launches. See Chrome Headless mode.
Troubleshoot incorrect size or fullscreen behavior
- The screenshot is not the dimensions expected: Check that
--window-size=WIDTH,HEIGHTis present in the arguments passed to the Chrome process that performs the capture. In an automation framework, confirm the launch options reach that process. - The image has the expected dimensions, but the window is not fullscreen: The screenshot size and window state are different concerns. Test the state with
--start-maximizedor--start-fullscreenand a suitable virtual screen where needed. - The page does not enter fullscreen: A browser window switch does not establish that page code using the Fullscreen API succeeded. Test the page’s actual fullscreen action and verify the behavior required by your test.
- Screen-aware layout differs from the target: A width and height alone do not configure scale factor, orientation, work area, or screen origin. Use virtual-screen configuration when those properties are part of the test.
--screen-infois unavailable: Check the Chrome version. The guide lists stable support beginning with version 142.- A time-sensitive page is captured too early: Adjust capture timing with the documented
--timeoutor--virtual-time-budgetoptions as appropriate; neither changes the requested dimensions.
Or skip the browser setup
For a one-call website capture, ScreenshotNeo returns a screenshot or PDF from a URL. Its API removes supported cookie and consent banners, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and responses identify the page verdict and billing status in headers. An MCP server provides screenshot tools for AI agents and other MCP clients.
Use the ScreenshotNeo API documentation for available parameters and response behavior.
Outdated 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 matchWindows 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 reinstallRank #4
- Intel Celeron N4120: 4 Cores & Threads, 1.1GHz Base Clock, Up to 2.6GHz Boost Clock, 4MB Cache, Intel UHD Graphics 600. The perfect combination of performance, power consumption, and value helps your device handle multitasking smoothly and reliably with four processing cores to divide up the work.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpThe free plan includes 1,000 screenshots per month with no card required; paid plans start at $5 for 3,000. Sign up for ScreenshotNeo’s free plan.
Frequently Asked Questions
Does `–window-size` make a headless Chrome window fullscreen?
No. It sets capture dimensions. Use the appropriate window-state or virtual-screen options when the test is about maximizing or fullscreen behavior.
What is the minimum stable Chrome version for `–screen-info` virtual screens?
Chrome’s virtual-screen guide says stable support starts with version 142.
Does Chrome’s headless screenshot size verify the web Fullscreen API?
No. Verify the page’s actual Fullscreen API behavior separately.
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.
