Playwright proxy setup

How to set up a proxy in Playwright

Configure a NobleProxy dedicated static residential proxy in Playwright with the exact fields the app asks for, then run its connection check before real tasks.

Quick answer

Add your NobleProxy host, port, username, and password to Playwright's proxy settings, choose HTTP or SOCKS5, save, and run the built-in proxy check before you start tasks.

Exact field-by-field setup
HTTP and SOCKS5 supported
One proxy per profile
Connection check before tasks

When this is the right fit

  • Exact field-by-field setup
  • HTTP and SOCKS5 supported
  • One proxy per profile

Who this page is for

Configure a NobleProxy dedicated static residential proxy in Playwright with the exact fields the app asks for, then run its connection check before real tasks.

Add your NobleProxy host, port, username, and password to Playwright's proxy settings, choose HTTP or SOCKS5, save, and run the built-in proxy check before you start tasks.

Playwright proxy fields

Proxy type / protocolHTTP or SOCKS5 - both supported on every NobleProxy endpoint
Host / endpointThe host exactly as issued in your NobleProxy dashboard
PortThe port paired with your endpoint in the dashboard
UsernameYour NobleProxy credential (case sensitive)
PasswordYour NobleProxy credential (case sensitive)
Static or rotatingStatic - the same exit IP every session by design

Field labels vary slightly between app versions; the NobleProxy values never change.

Step-by-step: connect Playwright to NobleProxy

  1. 1

    Set the proxy on the context

    Pass proxy: { server: 'http://host:port', username, password } when creating the browser context, using your dashboard values.

  2. 2

    Match the protocol prefix

    Use http:// or socks5:// in the server value to match the endpoint protocol you chose at purchase.

  3. 3

    Create one context per profile

    Give each managed profile its own context with its own endpoint so identities never share an IP.

  4. 4

    Confirm the exit IP

    Load an IP echo page inside the context and verify the reported address is the endpoint.

Connection check

  1. 1Run the check or test inside the tool after saving the proxy
  2. 2Confirm the reported IP matches your assigned endpoint, not your home IP
  3. 3Load one real target page and confirm it renders normally

Working connection

The tool reports the endpoint IP or country, and target pages load without credential prompts.

Broken connection

A refused connection, timeout, or repeated credential prompt means the host, port, username, or password does not match the dashboard values exactly.

Sources

Facts last reviewed 2026-09-01.

Tool-specific limitations to plan around

Playwright accepts a proxy object with server, username, and password fields at the browser or browser-context level, so each context can carry its own endpoint. The server value takes a protocol prefix such as http:// or socks5://.

  • Context-level proxies need the browser launched without a proxy of its own; a browser-level proxy overrides context settings.
  • SOCKS5 in Playwright works at the browser level; confirm the protocol your run needs before choosing the endpoint.

Keep the mapping one-to-one

Record which profile uses which endpoint before you start. When every task or profile has one stable residential endpoint, its session history stays consistent across restarts and team handoffs.

195+ countries
99.9% uptime guarantee
Unlimited bandwidth
4.9/5 from 127 ratings

Frequently asked questions

Which proxy protocols does Playwright support?

NobleProxy endpoints support HTTP and SOCKS5. Pick the protocol Playwright asks for in its proxy dialog; both use the same host, port, username, and password.

Where do I find the proxy host and port for Playwright?

Use the host, port, username, and password exactly as issued in your NobleProxy dashboard. Enter them in the same fields Playwright shows in its proxy configuration screen.

Should each Playwright profile get its own proxy?

Yes. Map one dedicated static residential proxy to one profile and keep that mapping stable. Reusing the same endpoint for many profiles links their sessions together.

Choose one stable proxy for every active profile

Buy self-serve now, or talk with us about a larger agency inventory.