Know where your links can go.
Windows requirements, browser profiles, and the boundaries of default link handling.
Windows requirements
Browter runs on Windows 10 22H2 and Windows 11 23H2 or later, with packages for x64 and ARM64. Install at least one real browser for fallback links. The wheel needs at least two enabled browser or profile entries; two profiles in one browser can satisfy that requirement.
Browsers and profile entries
Browter discovers browsers registered with Windows. Profile discovery reads local metadata for Chrome, Edge, Brave, Vivaldi, Chromium, and Firefox, including supported Chrome, Edge, and Brave channels. It does not create profiles or sign you into them. Create and configure profiles in the browser first, then rescan in Browter.
Use Settings → Browsers to rescan for discovered profile entries, add a browser manually, and test launches. Profile names are labels: the executable and arguments determine what opens. Browser updates, portable installations, custom data locations, and managed-device policies can affect discovery or launching.
Which links reach Browter?
Known limitations and practical workarounds ↗
- HTTP and HTTPS links handed to Browter through Windows default associations.
- Supported local HTML files when their Windows file association uses Browter.
- A browser’s internal links can remain inside that browser.
- Embedded viewers and apps with their own browser preferences can bypass Windows defaults.
- Custom protocols do not automatically become Browter web links.
Browter makes an explicit destination choice. Version 1.0 does not automatically route work domains or source apps to profiles, and browser profiles do not guarantee security isolation or the correct website login.