Playwright Proxy: One Authenticated IP per Browser Context

Why Playwright needs a proxy

Playwright drives a real browser, but every page it loads still leaves from your machine's IP. Run many contexts from one server and the site sees one address doing the work of many visitors. The usual reply is HTTP 429 Too Many Requests — the server telling you to slow down — or a block.

Proxy support is built in. You can set one proxy for the whole browser or a separate proxy for each browser context, so parallel workers leave through different IPs. Playwright documents the username and password fields for HTTP proxies.

Use HTTP for password-protected proxies in Chromium. Chrome supports no authentication method for SOCKS5 and won't use credentials written into proxy settings, so a socks5:// server with a password fails in Chromium even though Playwright accepts socks5:// addresses.

• MDN — 429 Too Many Requests
• Playwright docs — Network: HTTP proxy
• Playwright API — browserType.launch(): proxy option
• Chromium — Proxy support in Chrome

Recommended Playwright setup

Scroll horizontally with the arrow keys to read all content.

The button below opens Static Datacenter Proxies with the AI and automation use case. Choose Region, Term, Protocol and Quantity (up to 100 IPs at a time) before you pay.

• Proxy302 console — Static Datacenter Proxies

Which Proxy302 proxy to buy

Scroll horizontally with the arrow keys to read all content.

Prices in US dollars. Top up your wallet once and pay any line from it. Nothing renews automatically — renew in My assets to keep an IP.

• Proxy302 pricing

Set up Playwright proxies in 5 steps

1. Choose the region and term

   The button below opens Static Datacenter Proxies (Per IP and term) with the AI and automation use case. Under Connection settings pick the Region, choose a Term and set Protocol to HTTP. Set Quantity to the number of IPs you need (one for each parallel worker, up to 100 at a time). Then click Review cost and generate.

2. Copy each IP

   In My assets, Copy gives a ready line in host:port:user:password form. Put host and port in PROXY_HOST and PROXY_PORT, user and password in PROXY_USER and PROXY_PASS — environment variables keep the password out of your code.

3. Add the proxy to Playwright

   Use the code below. A proxy on newContext() gives each worker its own IP; a proxy on launch() applies one IP to the whole browser. The server must be http://host:port.

4. Check the exit IP

   The script opens api.ipify.org and prints the IP the site sees.

   Expected result The printed IP is the proxy's address, not your server's.

5. If a site blocks datacenter IPs

   Open Rotating Residential Proxies instead: set Line to Budget, use Add traffic to buy a package (from 1 GB), then set Exit mode to Global rotation for new exits on new connections, or to Choose region / sticky IP to stay in one country or city. Rotating residential connects through proxy.proxy302.com:2222 for HTTP.

Playwright proxy with username and password (Node.js)

Scroll horizontally with the arrow keys to read all content.

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

// From Proxy302 → My assets → Copy (host:port:user:password)
const { PROXY_HOST, PROXY_PORT, PROXY_USER, PROXY_PASS } = process.env

const browser = await chromium.launch()
// One proxy per browser context: each parallel worker gets its own exit IP
const context = await browser.newContext({
  proxy: {
    server: `http://${PROXY_HOST}:${PROXY_PORT}`, // HTTP: Chromium can't send a SOCKS5 password
    username: PROXY_USER,
    password: PROXY_PASS,
  },
})
const page = await context.newPage()
await page.goto('https://api.ipify.org?format=json')
console.log(await page.textContent('body')) // {"ip":"..."}: the proxy's exit IP, not your server's
await browser.close()

Checked on 2026-10-18 with Playwright 1.63.0 and Chromium 153 against a local password-protected proxy: the right credentials loaded the page, a wrong password loaded nothing. Swap the IP-check URL for your target.

• Local proxy fixture run
• Playwright API — browserType.launch(): proxy option

The same in Python

Scroll horizontally with the arrow keys to read all content.

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

# From Proxy302 → My assets → Copy (host:port:user:password)
proxy = {
    "server": f"http://{os.environ['PROXY_HOST']}:{os.environ['PROXY_PORT']}",
    "username": os.environ["PROXY_USER"],
    "password": os.environ["PROXY_PASS"],
}

with sync_playwright() as p:
    browser = p.chromium.launch(proxy=proxy)  # or browser.new_context(proxy=proxy) per worker
    page = browser.new_page()
    page.goto("https://api.ipify.org?format=json")
    print(page.text_content("body"))  # the proxy's exit IP
    browser.close()

Playwright for Python takes the same proxy dictionary in launch() or new_context(). Syntax-checked; the Node.js version above was run end to end.

• Playwright docs — Network: HTTP proxy

Quick fixes

Playwright proxy FAQ

Related setups

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

Geo testing proxies

Geo proxies for testing: see your website as visitors in other countries and cities see it — prices, language, banners — with matching locale and time zone.

View options and pricing

Fast fixed IPs for APIs, tests and monitors

Fast datacenter proxies with fixed IPs, low latency and high concurrency — the lowest cost per IP for APIs, testing and bulk jobs. Pick the country; pay per IP and term.

View options and pricing