BrowseRouter is a free, open-source Windows utility that automatically sends links to different web browsers based on rules you define. It's especially useful if you keep work, personal, development, or privacy-related browsing in separate browsers or browser profiles and are tired of Windows opening every link in the same place. Instead of copying a URL, opening another browser, and pasting it there, BrowseRouter makes that decision for you.

What BrowseRouter Does

BrowseRouter sits between Windows and your web browsers and decides which browser should handle a link. You set BrowseRouter as the default handler for web links, then create rules that match URLs and tell it which installed browser to launch.

Why Someone Would Use BrowseRouter

Windows normally expects you to pick one default browser. That's fine if you actually use one browser for everything. Plenty of us don't. We certainly don’t.

A work PC might have Edge signed into a Microsoft 365 account, Chrome signed into personal Google accounts, and Firefox set up with developer extensions. Clicking a link from Outlook, Teams, Slack, Discord, or another desktop application can then become mildly annoying because Windows blindly sends it to whichever browser happens to be the default.

BrowseRouter fixes that by looking at the address first.

For example, you could send GitHub links to Firefox, Microsoft 365 links to Edge, and everything else to Chrome. The important part is that you make that choice once in the configuration instead of making it every time you click a link.

How the Routing Rules Work

BrowseRouter uses a text-based configuration rather than a big graphical rules editor. You define the browsers you want available, tell BrowseRouter where their executables are located, and then create URL-matching rules that determine which one gets launched.

The basic logic is essentially:

"Does this URL match one of my rules? If yes, open it with the browser assigned to that rule. If not, use my fallback browser."

Suppose you use Edge for work and Firefox for development. Your configuration could be arranged so URLs containing your company's domain go to Edge, while GitHub and localhost addresses go to Firefox.

The exact syntax matters, so it's worth starting with only two or three rules. Test them before building a monster configuration with 40 entries and then wondering which rule ate your link.

Example: Configure Edge to Open 365 and Chrome to Google

This is probably the most useful everyday configuration simply because of the integration of these services into each browser.

First, you open the config.json file in the downloaded package and, with a text editor, simply set each browser like this:


"browsers": {
"edge": "%ProgramFiles(x86)%\\Microsoft\\Edge\\Application\\msedge.exe",
"chrome": "%ProgramFiles%\\Google\\Chrome\\Application\\chrome.exe"
}

And then tell it what it should do, like this.

"urls": {
"*office.com*": "edge",
"*microsoft365.com*": "edge",
"*sharepoint.com*": "edge",
"*google.com*": "chrome"
}

Your fallback shoudl look something like this: (The * means everything)

// Everything that does not match a rule above opens in Chrome.
"*": "chrome"

Useful Features Worth Knowing

The biggest feature is URL-based routing, but the ability to supply browser arguments is what gives BrowseRouter considerably more flexibility than simply choosing between Chrome and Firefox.

You can build configurations around:

Because the configuration is stored as text, it's also easy to back up once you have everything working. That's worth doing before making major changes. One typo in a configuration file is much easier to recover from when the working copy is sitting right next to it.

Here a list of some of the cooler things yyou can do once you get used to editing the config file:

• Open sites in Edge InPrivate using the --inprivate argument.
• Open sites in Chrome Incognito using --incognito.
• Use different browser profiles so work links can open under a work account while personal links use another profile.
• Use Firefox Multi-Account Containers to send matching sites directly to a named container, such as Work.
• Route by website so Microsoft 365 opens in Edge, Google services in Chrome, and GitHub in Firefox.
• Route localhost and development sites to a browser set up specifically with developer extensions and tools.
• Route links based on the application they came from. For example, links clicked in Microsoft Teams can go to Edge while links from Outlook go to Firefox.
• Pass browser command-line arguments, which opens the door to new windows, special profiles, private modes, and other options supported by the selected browser.
• Create a fallback browser for URLs that don't match any of your special rules.
• Use wildcard URL matching so you can route an entire domain instead of creating rules for individual pages.
• Enable logging to see what BrowseRouter is doing, which is particularly handy when a rule isn't behaving the way you expected.
• Enable or silence notifications so you can see when BrowseRouter handles a link without necessarily getting a Windows ding every time.

How to Set Up BrowseRouter

Start simple. Install or extract BrowseRouter and set it as the Windows default application for web links as required by the program.

Clicking the EXE will then start the process of setting BrowseRouter as the “default” browser. T

Next, configure the browsers you actually use. Don't add every browser installed on the machine just because you can. Two browsers and a few rules are much easier to troubleshoot than an elaborate setup created on day one.

Then add one obvious test rule. GitHub is a good example because it's easy to recognize whether the correct browser opened. Click a GitHub link from an application outside the browser and confirm that BrowseRouter sends it where expected.

Once that's working, add your work domains, development addresses, or other special cases one at a time.

Finally, configure the fallback behavior for URLs that don't match anything. The fallback is important because most links probably don't need special treatment.

Why Change the Configuration?

The supplied or basic configuration is really only a starting point. BrowseRouter becomes useful when its rules reflect how you actually use your PC.

If Edge is where you're authenticated for work, route company links there. If Firefox contains all your web-development extensions, route localhost there. If Chrome is where your personal Google account lives, send Google services there.

The point isn't to create clever rules. It's to remove repeated little decisions.

A good BrowseRouter configuration should eventually become something you forget is running. You click a link and it opens in the right place.

Limitations and Things to Watch

The biggest downside is the text-based configuration. Anyone comfortable editing INI, JSON, YAML, or similar configuration files probably won't care, but users expecting a Windows GUI with "Add Rule" and "Choose Browser" buttons may find the setup less friendly than it needs to be.

Rule order and overly broad matches can also cause trouble. A rule that matches more URLs than intended can send links to the wrong browser, so specific rules are generally easier to troubleshoot than clever catch-all patterns.

Browser profiles deserve some testing too. Command-line profile arguments and browser behavior can vary, particularly when that browser is already running. Test an important workflow before assuming every link will always create exactly the session or window you expect.

BrowseRouter also won't be worthwhile for everyone. If you use one browser 99 percent of the time, setting up URL-routing rules solves a problem you probably don't have.

Geek Verdict

BrowseRouter tackles one very specific Windows annoyance: one default browser isn't enough when different parts of your online life belong in different browsers.

We like that the routing happens automatically and that custom browser arguments allow more advanced setups involving profiles, development environments, and private windows. The text configuration also makes it appealing to geeks who would rather edit a few rules than run another bloated background utility with a giant interface.

The downside is the same thing. Configuration files aren't particularly friendly to beginners, and complicated routing setups can require some trial and error.

If you regularly copy a link because Windows opened it in the wrong browser, BrowseRouter makes sense. Set up a handful of sensible rules, keep a backup of the working configuration, and then forget about it until you install yet another browser you swear you're only testin