Where Does Selenium Manager Store Drivers?
Selenium Manager driver cache on every OS, the flag that moves it, and when deleting it fixes session errors.
Last updated
Modern Selenium downloads browser drivers automatically through Selenium Manager into a cache folder outside your project. Each driver version gets its own files, so Chrome updates keep working without hand maintained driver copies.
The location follows OS cache conventions and moves with a command line flag or config option. A stale or half downloaded driver is a classic cause of session startup failures. Clearing the cache forces a clean redownload, which fixes most of those in one step.
Where Selenium stores this, by platform
%userprofile%\.cache\selenium
Default under the user profile. The --cache-path flag overrides it, which is authoritative on build agents. Delete the folder with no tests running to force fresh driver downloads.
~/.cache/selenium
Selenium uses the home .cache directory here rather than Library/Caches. Same versioned driver files as other platforms.
~/.cache/selenium
Follows the XDG cache home. Browser binaries themselves stay wherever your package manager put them; only the drivers live here.
Frequently asked questions
Selenium fails to start a session after a browser update. What do I delete?
Clear the Selenium Manager cache folder with no tests running, then run again. Manager downloads a matching driver on next launch, which resolves most version mismatch errors.
How do I change where Selenium Manager stores drivers?
Pass the --cache-path flag or set the equivalent in your Selenium config. Manager uses that directory for all driver downloads from then on.
Notice an outdated path? Let us know.