Playwright Proxy Authentication: Per-Browser or Per-Context

Per browser or per context: which one to pick

A proxy in launch() applies to the whole browser, so all its contexts and pages leave from one IP. A proxy in new_context() applies to that context only, so one browser process can run several isolated sessions, each from a different IP.

Pick per-browser for a single job or a test run that needs one location. Pick per-context for parallel workers, one account per context, or a list of IPs you walk through. Cookies and storage are already separate per context; the proxy is the part that has to be set on top.

• Sources:
• Playwright: Network, HTTP proxy
• Playwright: Browser.new_context, proxy option

launch() vs new_context() at a glance

Source: Playwright documentation, Network and Browser.new_context pages, read on 13 November 2026. The browser-flag row is the Chromium command-line form; use the proxy object when you need a login.

• Sources:
• Playwright: Network, HTTP proxy
• Playwright: Browser.new_context, proxy option

One proxy for the whole browser (Python)

# pip install playwright   then   playwright install chromium
from playwright.sync_api import sync_playwright

proxy = {
    "server": "http://HOST:PORT",   # HTTP endpoint from My assets
    "username": "LOGIN",
    "password": "PASSWORD",
}

with sync_playwright() as p:
    browser = p.chromium.launch(proxy=proxy)   # every context in this browser uses it
    page = browser.new_page()
    page.goto("https://ipinfo.io/json")
    print(page.inner_text("body"))             # shows the proxy's exit IP
    browser.close()

Example only: replace HOST, PORT, LOGIN and PASSWORD with the values from My assets.

One proxy per context, several in parallel (Python)

# pip install playwright   then   playwright install chromium
import asyncio
from playwright.async_api import async_playwright

PROXIES = [  # one entry per IP, copied from My assets
    {"server": "http://HOST:PORT", "username": "LOGIN_1", "password": "PASSWORD_1"},
    {"server": "http://HOST:PORT", "username": "LOGIN_2", "password": "PASSWORD_2"},
]

async def check(browser, proxy):
    context = await browser.new_context(proxy=proxy)   # this context only
    try:
        page = await context.new_page()
        await page.goto("https://ipinfo.io/json")
        print(proxy["username"], await page.inner_text("body"))
    finally:
        await context.close()

async def main():
    async with async_playwright() as p:
        browser = await p.chromium.launch()            # no proxy on the browser itself
        await asyncio.gather(*(check(browser, x) for x in PROXIES))
        await browser.close()

asyncio.run(main())

Example only: replace HOST, PORT, LOGIN and PASSWORD with the values from My assets.

The same in Node.js

// npm i playwright   then   npx playwright install chromium
import { chromium } from 'playwright'

const proxies = [ // one entry per IP, copied from My assets
  { server: 'http://HOST:PORT', username: 'LOGIN_1', password: 'PASSWORD_1' },
  { server: 'http://HOST:PORT', username: 'LOGIN_2', password: 'PASSWORD_2' },
]

const browser = await chromium.launch() // no proxy on the browser itself
await Promise.all(proxies.map(async (proxy) => {
  const context = await browser.newContext({ proxy }) // this context only
  try {
    const page = await context.newPage()
    await page.goto('https://ipinfo.io/json')
    console.log(proxy.username, await page.textContent('body'))
  } finally {
    await context.close()
  }
}))
await browser.close()

Example only: replace HOST, PORT, LOGIN and PASSWORD with the values from My assets.

HTTP or SOCKS5 in the server field

The server field accepts both http:// and socks5:// addresses, but the username and password fields are described for HTTP proxies. Chromium's own SOCKS5 client sends only the "no authentication" method, so a SOCKS5 proxy that wants a login does not work in Chromium even if you fill in the fields.

So for Chromium use the HTTP endpoint of your proxy. On Proxy302 that is port 2222 on proxy.proxy302.com. Which protocol an asset accepts depends on the product, so look at the protocol shown for the asset in My assets. If you need SOCKS5 with a login in a browser anyway, see the guide linked below.

• SOCKS5 with a login in Chrome and Edge

• Sources:
• Playwright: Browser.new_context, proxy option
• Chromium source: socks5_client_socket.cc
• Proxy302 product facts and price list

Check that the proxy is really used

1. Step 1

   Run the one-proxy script above without a proxy first and note your own IP from ipinfo.io/json.

2. Step 2

   Add the proxy object and run again. The ip field should now be the proxy's exit IP, and the country should match the one you chose.

   Expected result The IP and country in the JSON differ from your own.

3. Step 3

   For per-context, print the IP for every context. Two contexts with two different static IPs should show two different addresses.

4. Step 4

   If the result is your own IP, the proxy object was passed to a different call than the one that created the page. Check which browser or context the page came from.

Test the login outside the browser first

# HTTP endpoint (the one Chromium can log in to)
curl -x http://LOGIN:PASSWORD@HOST:PORT https://ipinfo.io/json

# SOCKS5 endpoint (works in curl, not in Chromium with a login)
curl -x socks5h://LOGIN:PASSWORD@HOST:PORT https://ipinfo.io/json

Example only: replace HOST, PORT, LOGIN and PASSWORD with the values from My assets.

When Playwright and the proxy disagree

How to do it with Proxy302

For one fixed address per context, a static ISP IP fits: it does not rotate during the lease, costs US$0.50 for 1 day and US$7.99 for 30 days (about US$0.27 a day), and you can buy up to 100 in one order. For many different IPs from one pool, rotating residential costs US$1.50 per GB on the Budget line; with no session set, each new connection gets a new IP.

In both cases choose the HTTP protocol when you generate or buy, so the same login can go straight into the Playwright proxy object. The Playwright page has the setup and the rest of the options.

• Playwright with Proxy302
• static ISP proxies
• rotating residential proxies

• Sources:
• Proxy302 product facts and price list

Steps in Proxy302

1. Step 1

   Open the static ISP page (or rotating residential), choose the country and HTTP as the protocol, review the cost and pay from the wallet.

2. Step 2

   Open My assets and copy host, port, username and password. For several contexts, buy or generate several assets.

3. Step 3

   Put the values into the proxy object as server (http://HOST:PORT), username and password.

4. Step 4

   Confirm the exit with https://ipinfo.io/json from inside Playwright, as in the examples above.

Playwright proxy FAQ

Read next

Playwright proxies

Playwright proxy setup with username and password: static datacenter IPs for tests and CI, rotating residential from US$1.50/GB when a site blocks servers.

View options and pricing

Puppeteer proxy setup

Set an HTTP proxy in Puppeteer with --proxy-server, page.authenticate and browser contexts, and check the exit IP.

Selenium proxies

Selenium proxy with username and password in Chrome: HTTP proxy in ChromeOptions plus Selenium's BiDi auth handler, no extensions. Static datacenter IPs for test runs.

View options and pricing

SOCKS5 login in Chrome

Chrome has no SOCKS5 login, but a static ISP per-IP lease also works on HTTP port 2222 with the same login.

Browser Use Proxy: Run an Agent Through an HTTP Proxy

How to run a Browser Use agent through an HTTP proxy: the current ProxySettings API, one proxy per agent, Playwright and Playwright MCP options, time zone and language, and common errors.