For most legacy sites that need Internet Explorer behavior, the current Selenium path is Microsoft Edge in IE mode, driven with Selenium’s Internet Explorer driver classes. Selenium ended official support for standalone Internet Explorer in June 2022; standalone IE 11 automation remains a constrained Windows-only option, not a generally supported browser target. First determine whether the site needs IE-specific behavior, then choose the matching setup and validate it before relying on test results.
Choose the browser path that matches the compatibility need
| Option | Use it when | Support and platform | Main trade-off |
|---|---|---|---|
| Edge IE mode with Selenium IE driver classes | The site needs IE rendering or behavior, and an Edge-based environment is available. | Selenium recommends IE mode for IE sites. Its January 18, 2022 announcement reported Microsoft’s commitment to support Edge IE mode through 2029 in the context of Windows 10 retirement; that announcement-era statement is not a newly verified 2026 lifecycle guarantee. Selenium’s 2022 announcement | Requires Edge IE mode policy and site-list configuration, plus confirmation that the site actually opened in compatibility mode. |
| Standalone IE 11 with IE Driver Server | A controlled legacy Windows environment must test the actual IE 11 browser. | Selenium no longer officially supports standalone IE. Its IE driver documentation identifies IE 11 on Windows 10 as tested; older combinations may work but are unsupported. Selenium IE Driver Server documentation | Windows-only, configuration-heavy, and susceptible to focus-related native mouse-event problems. |
| Regular Edge WebDriver | The workflow does not need IE-specific behavior. | Use EdgeDriver with Selenium; its major version must match the Edge browser’s major version. Selenium Manager is the default driver-management mechanism in current bindings. Selenium Edge documentation Selenium Manager documentation | Does not reproduce IE rendering or behavior. |
Selenium’s IE-specific documentation states: “As of June 2022, Selenium officially no longer supports standalone Internet Explorer.” The IE Driver remains usable for Edge’s IE Compatibility Mode. Selenium IE documentation
As an Amazon Associate I earn from qualifying purchases.
Run a site in Edge IE mode with Selenium
Configure IE mode outside the test code first. An administrator may need to enable IE mode through the organization’s Windows and Edge policies and include the target site in its site list. Selenium’s setup does not itself guarantee that a URL will open in compatibility mode, so verify the browser’s mode and exercise the site’s critical workflows.
- Confirm the requirement. Identify the specific site functionality that depends on IE behavior. If the workflow works in standard Edge, use regular Edge WebDriver instead.
- Configure the host. Apply the organization’s Edge IE mode policy and site-list settings for the target URL.
- Use the IE driver API. Selenium’s Java example uses
InternetExplorerOptionswithInternetExplorerDriver, attaches to Edge, and optionally sets the Edge executable path:
InternetExplorerOptions options = new InternetExplorerOptions();
options.attachToEdgeChrome();
// Optional when Edge is not discoverable in this environment:
// options.withEdgeExecutablePath("C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe");
WebDriver driver = new InternetExplorerDriver(options);
driver.get("https://legacy.example.com");The example uses Java and the Selenium WebDriver API. Selenium documents automatic Edge discovery with IE Driver 4.5.0 and later in the described configurations; provide the executable path only when the target host requires it. Consult the IE driver configuration reference for language-specific bindings and current API details.
#1 Best Overall
- Validate the mode and workflow. Confirm the target site is running in IE mode, then test the interactions that motivated IE coverage—especially navigation, forms, authentication, and any legacy controls your application uses.
- Keep the environment controlled. Because IE mode configuration is host- and policy-dependent, record the browser, driver, policy, and site-list setup used for repeatable runs.
Set up standalone IE 11 only for a controlled legacy host
Selenium documents IE Driver Server as tested with IE 11 on Windows 10. Older browser and operating-system combinations may work, but Selenium does not support them. Follow your organization’s change-control process before altering Windows security settings or the registry.
Required environment checks
- Use Windows; the IE Driver is Windows-only.
- Make the IE Driver Server executable available to the environment, for example by adding its location to
PATH. - Use the driver binary matching the browser architecture. Selenium’s downloads page lists both 32-bit and 64-bit binaries and labels 32-bit Windows IE as recommended. The page listed IE Driver Server 4.14.0.0 when accessed October 3, 2026; check the current downloads page rather than assuming that version remains current. Selenium downloads
- Set Protected Mode to the same state for every security zone.
- Disable Enhanced Protected Mode for IE 10 and later.
- Set browser zoom to 100%. On Windows 10, set display scaling to 100% as Selenium directs.
- For IE 11, create the documented
FEATURE_BFCACHEregistry key valueiexplore.exeas a DWORD with value0, using the registry path appropriate to the system architecture. Verify the exact path in Selenium’s documentation before making the change.
Selenium’s documentation covers these requirements and their registry paths in its IE Driver Server setup instructions. Do not use ignoreProtectedModeSettings as the first fix: Selenium describes it as a best-effort workaround that can lead to flaky, unresponsive, or hung sessions. Matching the actual zone settings is preferable.
Why standalone IE runs can be unreliable
IE’s native mouse events may not work as expected if the browser window is not focused. A local test machine may therefore need to remain visible, focused, and dedicated during a run. This limits the usefulness of treating standalone IE as an unattended, high-throughput browser target.
Automate ordinary Edge separately
When the application does not need IE behavior, use Selenium’s normal Edge WebDriver support. Selenium says EdgeDriver’s major version must match the Edge browser’s major version. Selenium Manager is built into current bindings as the default browser and driver management mechanism; explicit paths remain an option where environment constraints require them. Edge WebDriver documentation Selenium Manager documentation
Do not treat a passing regular Edge test as evidence that an IE-only behavior works. Conversely, do not maintain standalone IE coverage if ordinary Edge accurately represents the workflow under test.
Troubleshoot common failures
| Symptom | Likely cause | What to check or change |
|---|---|---|
| Session creation or browser startup fails | Driver unavailable, wrong architecture, or incomplete environment setup. | Confirm the IE Driver Server executable is available through the environment (such as PATH), that the binary architecture matches the browser, and that required IE settings are applied. Selenium IE Driver Server documentation |
| A click focuses an element but does not activate it | IE native mouse events may fail when the window is not focused. | Run in a visible, focused, dedicated session where practical. Selenium IE Driver Server documentation |
| Click coordinates or element positions are wrong | Browser zoom or Windows display scaling differs from the documented setting. | Set zoom to 100% and, on Windows 10, display scaling to 100%. Selenium IE Driver Server documentation |
| Protected Mode exception | Security-zone settings are inconsistent. | Set Protected Mode consistently across zones. Avoid bypassing the check as the first response because that may destabilize sessions. Selenium IE driver documentation |
| IE 11 hangs or fails to connect | The documented back-forward cache registry setting may be missing or applied to the wrong architecture-specific path. | Verify the FEATURE_BFCACHE key, DWORD name and value against Selenium’s instructions for the host architecture. Selenium IE Driver Server documentation |
| Standard Edge session fails with a driver mismatch | EdgeDriver and Edge major versions differ. | Align their major versions or use Selenium Manager if it suits the environment. Edge WebDriver documentation Selenium Manager documentation |
Capture a screenshot when a test fails
A screenshot can help distinguish a page-rendering failure from a locator or interaction problem. For Selenium-managed browsers, save the screenshot from the failing session where possible so the evidence reflects the browser state under test. A screenshot API is a separate option for capturing a URL outside that Selenium session; it does not replace IE-mode or standalone-IE compatibility testing.
Rank #4
Or skip the browser setup
If you need a clean capture of a public page rather than proof of IE-specific behavior, ScreenshotNeo provides a website screenshot API and MCP server. One GET request returns an image or PDF. Its screenshot API accepts a URL, and the documentation describes its request options.
Free tools Windows power users keep installed
One-click scans. No signup required.
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://legacy.example.com -o shot.webpScreenshotNeo accepts cookie or consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; those steps can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and each response identifies the page verdict and billing status in headers. Its MCP server offers take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients. The Free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots. Sign up for free.
Plan long-term coverage around the actual dependency
Selenium’s official direction is Edge IE mode rather than active support for standalone IE. Its January 18, 2022 announcement recommended testing IE sites in Edge IE mode and reported Microsoft’s then-stated support horizon through 2029 in the context of Windows 10 retirement. Microsoft’s lifecycle commitments can change, so consult current Microsoft lifecycle guidance before using that date as a planning guarantee. The same announcement described the June 15, 2022 retirement date as applying to certain Windows 10 versions, not every Windows installation. Selenium’s announcement
For new or continuing coverage, document which application behavior truly requires IE compatibility, keep the IE-mode policy and site list under change control, and isolate standalone IE testing to environments that specifically require the actual IE 11 browser. Selenium’s stable version was 4.49.0 on September 9, 2026; version numbers and driver downloads change, so verify the current project pages when setting up a new environment. Selenium downloads
Frequently Asked Questions
Does Selenium still support Internet Explorer?
Selenium ended official support for standalone Internet Explorer in June 2022. Its IE Driver documentation still covers Edge IE Compatibility Mode, while standalone IE 11 is a constrained legacy option.
Can a screenshot API verify that a site works in IE mode?
No. A URL screenshot is not a substitute for running the site in the browser mode and environment whose compatibility behavior you need to test.
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.
