What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
A white screenshot is a symptom, not a diagnosis. First check that Chrome and ChromeDriver have compatible major versions, set an explicit headless viewport, and wait for the page-specific content you expect—not merely for navigation to finish. Then compare the live DOM and browser logs with the screenshot to determine whether the page failed to render or the capture failed.
1. Record the environment and check Chrome–ChromeDriver compatibility
Before changing flags, write down the Selenium version, Chrome version, ChromeDriver version, operating system, container or CI environment, and the exact Chrome arguments. A browser update does not guarantee that the driver was updated with it.
As an Amazon Associate I earn from qualifying purchases.
Selenium’s Chrome documentation says Chrome and ChromeDriver must match at the major-version level. If those major versions differ, update or pin a compatible pair before investigating page-specific rendering. A mismatch is a check to perform, not proof that it caused every white screenshot.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problems2. Set a deliberate headless mode and viewport
Use a supported headless argument for the Chrome version installed in the environment. Selenium lists --headless=new among commonly used Chrome arguments; verify against the actual browser rather than assuming an old flag or copied configuration works everywhere. Selenium’s Chrome guide
#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
Set the window size explicitly instead of relying on maximize behavior in a headless session. Match the intended viewport and responsive breakpoint: a narrow viewport can cause the site to serve a different layout or defer different content. Chrome’s headless documentation demonstrates screenshot capture using --window-size.
Minimal Python reproduction
This example establishes a fixed viewport, navigates to a URL, waits for a site-specific selector, and saves a screenshot. Replace the URL and selector with the page and content your test actually needs.
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
from selenium import webdriver
from selenium.webdriver.chrome.options import Options
from selenium.webdriver.common.by import By
from selenium.webdriver.support.ui import WebDriverWait
from selenium.webdriver.support import expected_conditions as EC
options = Options()
options.add_argument("--headless=new")
options.add_argument("--window-size=1440,1000")
driver = webdriver.Chrome(options=options)
try:
driver.get("https://example.com")
WebDriverWait(driver, 30).until(
EC.visibility_of_element_located((By.CSS_SELECTOR, "main"))
)
driver.save_screenshot("page.png")
finally:
driver.quit()The selector is only an example: choose an element that proves the relevant page state has rendered. If the application updates the element after it first appears, wait for the specific text, attribute, or state your screenshot requires.
Free tools Windows power users keep installed
One-click scans. No signup required.
3. Wait for the application, not just navigation
WebDriver’s normal navigation wait targets document.readyState reaching complete. That does not guarantee that a JavaScript single-page application has finished fetching data, rendering components, or revealing the content you intend to capture. Selenium calls out this distinction in its browser options documentation.
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.
Use an explicit wait for a page-specific condition: an expected element becoming visible, a loading indicator disappearing, or a known application state appearing. Do not treat an arbitrary sleep as proof of readiness; it can be too short on a slow run and waste time on a fast one.
4. Compare the DOM and logs with the screenshot
Collect evidence immediately before capture. The current URL, readiness state, page title, body text, expected selector visibility, and browser or driver logs help distinguish a page-load problem from a screenshot-output problem.
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
print("URL:", driver.current_url)
print("Ready state:", driver.execute_script("return document.readyState"))
print("Title:", driver.title)
print("Body text:", driver.find_element(By.TAG_NAME, "body").text[:1000])
print("Main visible:", driver.find_element(By.CSS_SELECTOR, "main").is_displayed())Adapt the selector check if the page does not have a main element, and handle a missing selector as diagnostic information rather than letting that check hide the original failure. Chrome also documents dumping the DOM for inspection in its headless guide.
- Expected content is absent from the DOM: investigate navigation, application scripts, failed resources, and site-specific behavior. The screenshot may accurately reflect a page that never reached the expected state.
- Expected content is present and visible in the DOM, but the image is white: investigate the capture and rendering setup, including the exact Chrome version, headless argument, viewport, and whether the symptom persists on a minimal page.
- The image is not the expected size: check the configured viewport and the screenshot dimensions before attributing the problem to the site.
DOM inspection and screenshot inspection answer different questions; use both. A DOM dump does not prove what pixels Chrome captured, and a white image alone does not show whether the application rendered its content.
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.
5. Isolate the failure one variable at a time
- Run the same minimal script against a simple known page, then against the target page.
- Keep the browser, driver, viewport, and headless argument fixed while comparing results.
- If only the target fails, inspect its page-specific readiness condition, scripts, resources, and behavior in the execution environment.
- If the simple page also produces a white screenshot, focus on the browser/driver setup and capture path.
- Change one setting at a time and retain the smallest reproducer that still fails.
A Selenium issue report describes a white-screen symptom in headless mode, but a reported issue does not establish one universal cause or workaround: SeleniumHQ issue #14544, reported September 27, 2024.
Common failure patterns and fixes
| What you observe | What to check next |
|---|---|
| Chrome and ChromeDriver have different major versions | Update or pin a compatible pair, then repeat the same minimal capture. |
| Page title or body is present, but the app content is missing | Wait for the app’s own rendered state and inspect navigation, scripts, and resources. |
| The page works visibly but the headless screenshot is blank | Set the headless argument and viewport explicitly, collect logs, and compare with a minimal page. |
| The screenshot uses an unexpected layout | Set a viewport matching the desired responsive breakpoint rather than relying on maximize behavior. |
| A fixed delay sometimes works and sometimes does not | Replace it with an explicit wait tied to the content or state required for capture. |
Performance and reliability considerations
Page-specific explicit waits make tests depend on a meaningful readiness condition rather than a guessed delay. Keep the viewport and browser/driver versions stable when comparing runs, and capture logs and DOM evidence in the same run as the image so intermittent failures are easier to classify. No single flag or workaround is established for all white screenshots; the evidence should identify which layer failed in your setup.
Or skip the browser setup
For a one-request capture, ScreenshotNeo accepts a URL and returns an image or PDF. Its clean-shot flow accepts cookie or consent banners like a visitor and removes 60+ known consent platforms, newsletter popups, and chat widgets before capture; each step can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and the response identifies the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, or any MCP client. See the ScreenshotNeo API documentation.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://example.com -o shot.webpScreenshotNeo offers 1,000 screenshots per month free with no card; paid plans start at $5 for 3,000. Learn about ScreenshotNeo or sign up free.
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.
