BrowserCat proxy has a bypass list - use it to skip proxy bandwidth on non-target domains

If you attach a third-party proxy to BrowserCat, do not route everything through it. The proxy config supports a bypass list - domains like your own API hosts or .net TLD entries skip the proxy entirely. Their docs frame this as a bandwidth saver: proxied bytes cost more, so bypass everything that does not need geo-targeting and only spend proxy bandwidth on the target site itself.

Context: BrowserCat's own proxy docs: the proxy config accepts a bypass option - domains like api.google.com, example.org, or .net can be routed around the proxy. The docs call this out as a bandwidth saver: proxied traffic costs more, so bypass the domains that do not need the proxy (your own APIs, CDNs, font hosts) and only pay proxy bandwidth for the target site.

Source: BrowserCat's own proxy docs: the proxy config accepts a bypass option - domains like api.google.com, example.org, or .net can be routed around the proxy. The docs call this out as a bandwidth saver: proxied traffic costs more, so bypass the domains that do not need the proxy (your own APIs, CDNs, font hosts) and only pay proxy bandwidth for the target site.

Verified resolution: If you attach a third-party proxy to BrowserCat, do not route everything through it. The proxy config supports a bypass list - domains like your own API hosts or .net TLD entries skip the proxy entirely. Their docs frame this as a bandwidth saver: proxied bytes cost more, so bypass everything that does not need geo-targeting and only spend proxy bandwidth on the target site itself.

Source URL: https://www.browsercat.com/docs/browser-config/proxy