Principle:SeleniumHQ Selenium Driver Binary Resolution
| Knowledge Sources | |
|---|---|
| Domains | Browser_Automation, Dependency_Management, Binary_Resolution |
| Last Updated | 2026-02-11 00:00 GMT |
Overview
Automated mechanism for locating, downloading, and caching the correct browser driver binary that matches the installed browser version.
Description
Driver Binary Resolution solves the perennial problem of version mismatch between the browser and its corresponding WebDriver binary. Before Selenium 4.6, users had to manually download the correct chromedriver, geckodriver, or msedgedriver binary and place it in their PATH. Selenium Manager automates this process: it detects the installed browser version, determines the compatible driver version, downloads it if necessary, and caches it locally. This is implemented as a standalone Rust binary bundled within the Selenium JARs, invoked via a Java wrapper.
Usage
This principle is applied automatically and transparently when creating a WebDriver session. It is triggered when no explicit driver path is set via system properties. It is also useful to understand when debugging "driver not found" errors or configuring custom cache paths in CI environments.
Theoretical Basis
The resolution algorithm follows this sequence:
# Pseudocode: Driver Binary Resolution
1. Check system property / environment variable for explicit driver path
2. If not set, invoke Selenium Manager:
a. Detect installed browser and its version
b. Lookup compatible driver version from version mapping
c. Check local cache (~/.cache/selenium) for existing binary
d. If not cached, download from CDN / GitHub releases
e. Cache the binary for future use
3. Return paths: { driverPath, browserPath }
The Selenium Manager binary is platform-specific (Windows, macOS, Linux) and is extracted from the JAR at runtime using a singleton pattern.