How to Use Custom Proxies with Browser Use

A Browser Use walkthrough shows how to run your own proxy with Browser Use Cloud and check that the browser is really exiting where you expect. It covers bring-your-own proxies, which Browser Use Cloud supports alongside its managed residential proxies. The walkthrough doesn't present them as a new release.

You take the hostname, port, protocol, username, and password from your proxy provider and put them in a .env file. Then you pass them as customProxy in the browser settings when you create an agent run with the Python SDK. The example task opens ipwho.is and returns the IP and country code. You then compare that with what the run's browser actually loaded, because a curl from your laptop only tests your laptop's route. The guide's test run reported a US exit.

The same credentials work with Playwright. One script launches a local Chromium with the proxy. Another creates a Browser Use cloud browser with customProxy and attaches over connect_over_cdp().

You choose the exit country and sticky session settings with your provider. A custom proxy overrides Browser Use's proxyCountryCode setting, and browser locale and timezone don't pick the exit. On cost, Browser Use lists managed proxy traffic at $5/GB. BYO is your provider's rate plus $0.20/GB Browser Use egress, billed separately from your provider. Using $1 to $4/GB prepaid residential rates, the guide estimates one browser-hour plus 1 GB at about $1.22 to $4.22, against $5.02 managed.