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 matchPC 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 & 11Some links on this page are affiliate links: if you buy through them we may earn a commission, at no extra cost to you.
Starting Chrome is not the same as opening a website. Selenium creates or controls a browser session when you create a Chrome driver; your script must then navigate explicitly, usually with driver.get("https://example.com"). If the navigation call is already present, check that execution reaches it, that its URL includes http:// or https://, and whether Chrome is running headlessly or the page is simply not ready when your test checks it.
What happens when Selenium starts Chrome
There are two distinct operations: creating a WebDriver session and navigating a page. ChromeDriver controls Chrome as a separate executable. Creating the driver launches or connects to a browser session; it does not, by itself, tell that session which website to visit. Selenium’s API uses a separate navigation command, get(url), for that.
That means a blank tab or new-tab page after startup is not, on its own, proof that navigation failed. The useful question is whether your program actually issued the navigation command and what happened after it did. ChromeDriver’s official “Get started with ChromeDriver” example shows driver setup and get as separate steps.
Recommended Free Tools
Minimal Python example
This example makes the two operations explicit. It assumes Selenium is installed and Chrome is available in the environment where the script runs.
#1 Best Overall
from selenium import webdriver
driver = webdriver.Chrome()
try:
driver.get("https://example.com")
print("Current URL:", driver.current_url)
print("Page title:", driver.title)
finally:
driver.quit()If Chrome opens but remains on a blank or new-tab page, begin by checking whether the script reached the driver.get line. If it did, check the URL and then investigate startup, headless configuration, and timing as separate possibilities rather than assuming one cause.
Check the navigation call before debugging Chrome
First confirm the code path. A setup function may successfully create the driver and then return, skip a later branch, or encounter an error before navigation. Add a temporary log immediately before the call and another after it. If the first appears and the second does not, inspect the exception or hang around navigation; if neither appears, the issue is earlier in the program flow.
Next, pass a complete URL. Selenium’s get(url) API reference specifies that the URL must include a protocol, such as http:// or https://. A bare value like example.com is not the same as an explicit web address for this command.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #2
# Use a complete URL
driver.get("https://example.com")Remove the leading space before driver.get if copying this single line into Python code; it belongs at the indentation level of the surrounding block. In the complete example above, the call is correctly indented within try.
For diagnosis, temporarily use a known complete URL and print the current URL or title immediately afterward. This helps separate “the script never asked Chrome to navigate” from “the request was made but the content I expected is not visible.” It does not, by itself, prove that a particular website or all of its dynamic content has finished loading.
Use this diagnostic sequence
- Verify the setup call completes. Confirm driver creation returns a usable session rather than stopping with a startup error.
- Verify execution reaches navigation. Put a log immediately before
driver.get; confirm the call is not inside a skipped conditional or after an earlier return. - Check the URL string. Include
https://orhttp://and inspect the actual value passed at runtime, not only the value you intended to pass. - Check whether execution is headless. A headless browser does not show a normal Chrome window, even when Selenium navigates a page. The official Selenium headless example still makes an explicit
driver.getcall. - If Chrome fails to start or behaves differently in a harness, isolate startup. Try launching the same Chrome binary directly with the same startup switches. Check the ChromeDriver log to see which binary was selected.
- On Linux, check the account running Chrome. ChromeDriver’s troubleshooting guidance identifies running Chrome as root as a common startup-crash cause. Run it as a regular user; do not treat
--no-sandboxas a supported fix. - If navigation was requested but the expected content is absent, investigate synchronization and the driver separately. Selenium’s troubleshooting guide identifies poor synchronization as its most common Selenium-related error and notes that underlying browser drivers can also be responsible.
Tell startup, navigation, and timing problems apart
| What you observe | What it points to | What to check next |
|---|---|---|
| No Chrome session, or Chrome exits immediately | A browser startup or driver problem is more likely than a missing navigation command. | Reproduce with the same Chrome binary and switches outside the test harness, then inspect the ChromeDriver log. |
| A Chrome window opens on a new tab | The session exists, but this alone does not show whether your code requested a page. | Confirm the program reaches get and passes a complete URL. Check for headless configuration if you expected a visible window. |
| The navigation line runs, but expected page content is absent | The request may have occurred while the test checks too soon, or browser-driver behavior may be involved. | Review synchronization and the underlying driver; compare behavior across browsers if that helps isolate a driver-specific issue. |
These observations are diagnostic distinctions, not a ranking of causes for every setup. In particular, seeing a blank tab does not tell you whether navigation was omitted, headless mode was enabled, startup was incomplete, or the test moved on before the page was ready.
When Chrome crashes or differs in CI, an IDE, or a service
ChromeDriver recommends reducing the environment to the browser itself: launch the same Chrome binary directly, include the same startup switches, and inspect chromedriver.log to verify which binary ChromeDriver selected. This is useful when local interactive runs work but a test runner, service, or CI environment does not. The purpose is to find whether the difference appears before Selenium attempts page navigation or after it.
On Linux, pay particular attention to the user account. ChromeDriver’s official troubleshooting page states: “A common cause for Chrome to crash during startup is running Chrome as root user (administrator) on Linux.” The same guidance says the --no-sandbox workaround is unsupported and highly discouraged. Prefer running Chrome as a regular user instead of using that flag to mask a startup problem.
What headless mode changes—and what it does not
Headless mode explains why you may not see a browser window; it does not automatically navigate to a website. The official Selenium headless example configures headless operation and still calls driver.get separately. Therefore, if the only symptom is “I do not see Chrome,” check whether headless mode is intentional. If the symptom is “the requested page was never loaded,” verify navigation and troubleshoot the request or the test separately.
If the page is requested but the test sees no content
Once the navigation line has run, shift from session creation to synchronization. Selenium’s troubleshooting documentation calls poor synchronization its most common Selenium-related error. A page can be in the process of loading or rendering when a test checks for the expected result, so inspect what the test waits for and when it checks it.
Also keep the browser driver in view. Selenium’s troubleshooting guidance notes that problems in the underlying browser drivers can be reported as Selenium issues. If the same sequence behaves differently across browsers, that comparison can help isolate a driver-specific problem; it does not establish that ChromeDriver is always at fault. Record the actual URL, the point where execution stops, and whether the issue occurs outside the test harness before changing startup flags.
Or skip the browser setup
If your actual goal is a screenshot rather than interactive browser automation, ScreenshotNeo is a website screenshot API and MCP server. A single request can return an image or PDF; it is not a substitute for Selenium when you need to interact with a page or test browser behavior.
For example, this cURL call saves a WebP screenshot of a page:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for request options. Cookie banners, popups, and chat widgets are removed before the shot; bot checks, blank pages, and failed loads are never billed. Its MCP server lets AI agents take screenshots. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000. Sign up for free.
Frequently Asked Questions
Does a blank tab prove that ChromeDriver is broken?
No. It only shows what is visible in the browser at that moment. Confirm that navigation was called before treating the blank tab as evidence of a browser-driver failure.
Should I add --no-sandbox to fix Chrome startup on Linux?
ChromeDriver’s troubleshooting guidance describes that workaround as unsupported and highly discouraged. Its recommendation is to run Chrome as a regular user.
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.
