uninstall to remove managed browser runtimes from the Extension.js cache.
This only removes browsers that Extension.js installed in its managed cache root. It does not touch system Chrome, system Edge, or any browser installed outside that cache.
When to use uninstall
- You want to reclaim disk space from managed browsers you no longer need.
- You are resetting a managed browser install to force a fresh download on next
install. - You are cleaning up continuous integration (CI) caches or switching browser targets.
Canonical usage
For a single browser, use the positional form:--all to remove every managed browser target.
Usage
Arguments and flags
| Flag / argument | What it does | Default |
|---|---|---|
[browser-name] | Remove a single managed browser such as chrome, chromium, edge, or firefox | unset |
--browser <browser> | Explicit flag form of the browser argument | unset |
--all | Remove all managed browser runtimes from the Extension.js cache | disabled |
--where | Print the resolved cache root, or browser-specific managed paths | disabled |
Examples
Remove managed Chrome for Testing
Remove all managed browsers
Show the managed uninstall path for Firefox
Best practices
- Use
--allin CI teardown to clean up managed browsers after test runs. - Use
--wherefirst to confirm what will be removed before scripting bulk uninstalls. uninstallis safe for system browsers — it only removes Extension.js-managed cache folders.
Behavior notes
- If you set
EXT_BROWSERS_CACHE_DIR, uninstall uses that custom cache root.
Next steps
- Reinstall managed browsers with
install. - Review browser targeting with
devandstart. - Learn about Running other browsers with custom binary paths.

