Beat IP-based blocks
Real residential addresses avoid the datacenter-range blocklists that headless browsers hit almost immediately on protected sites, so pages load with content instead of challenges.
Integration Scraping framework
Playwright Proxy Setup
Playwright drives a real browser, which is powerful for scraping dynamic sites but easy to fingerprint by IP. Routing each browser context through ProxyOmega residential proxies gives every page a real consumer address, with clean per-context authentication and built-in geo-targeting. This guide shows the exact proxy config and the session patterns that keep automation running.
- 200+countries
- 1.5M+residential IPs
- SOCKS5on every port
Playwright
What is Playwright?
Playwright is a browser-automation framework from Microsoft that drives Chromium, Firefox, and WebKit through a single API, available in Python, Node.js, Java, and .NET. It launches a real browser, executes JavaScript, waits for network activity, and interacts with the page the way a person would, which makes it a strong choice for scraping single-page apps and any site that renders content client-side.
Its architecture separates the browser, the browser context, and the page. A browser context is an isolated session with its own cookies, cache, and storage, roughly equivalent to a fresh incognito profile. That boundary is important for proxying: you attach a proxy to a context (or to the whole browser at launch), so you can run several contexts, each with its own exit IP, inside one browser process.
Because Playwright renders like a real client, it defeats a lot of the client-side checks that trip up plain HTTP scrapers. What it cannot hide on its own is the network address every request comes from, and a browser fetching dozens of subresources from one datacenter IP is a clear automation signal.
Playwright
Why Playwright needs residential proxies
A headless browser loads a page plus all its subresources (scripts, images, XHR/fetch calls) from a single IP in a tight burst. Anti-bot systems correlate that fingerprint with the source address, and a datacenter IP quickly earns CAPTCHAs, block pages, or throttling. Residential IPs make the browser look like an ordinary visitor.
ProxyOmega assigns each context a real consumer IP and can pin or rotate it as needed. Combined with Playwright's genuine browser fingerprint, a residential IP is often the difference between a clean 200 with full content and a challenge page.
Per-context IPs
Assign a different proxy to each browser context to run parallel sessions, each from its own IP, inside a single Playwright process. Isolated cookies plus isolated IPs mean cleaner concurrency.
Localized rendering
Geo-target the exit IP and the site serves the same currency, language, and inventory a local user sees. Pair with Playwright's locale and timezone options for a consistent regional profile.
Stable multi-step flows
Sticky sessions hold one IP across a login, navigation, and checkout so the target does not flag a mid-session IP change.
Playwright
Using ProxyOmega with Playwright
Playwright takes a proxy object with server, username, and password fields. Set it on new_context to scope the proxy to that context, or on launch to apply it browser-wide. The username carries your targeting parameters (below, -country-us) and the password is your dashboard API key.
For Budget Unlimited, point server at http://residential.proxyomega.com:10000. Any port from 10000 to 10199 works, and each serves HTTP, HTTPS, and SOCKS5 on the same port. The example uses the Python sync API; the async API and the Node.js API take the identical proxy object shape.
from playwright.sync_api import sync_playwright
# Targeting params attach to the username, dash-separated.
USERNAME = "user123-country-us"
PASSWORD = "your_dashboard_api_key" # account API key from the dashboard
with sync_playwright() as p:
browser = p.chromium.launch(headless=True)
# Proxy is scoped to this context. Give each context its own
# proxy to run parallel sessions from different IPs.
context = browser.new_context(
proxy={
"server": "http://residential.proxyomega.com:10000",
"username": USERNAME,
"password": PASSWORD,
},
locale="en-US",
timezone_id="America/New_York",
)
page = context.new_page()
page.goto("https://api.ipify.org?format=json", timeout=60000)
print(page.inner_text("body")) # shows your residential exit IP
browser.close()Playwright
Rotating vs sticky sessions
Because a proxy binds to a context, the simplest rotation strategy in Playwright is to create a new context per unit of work. On Budget Unlimited the pool also rotates on the dashboard interval, so a fresh context generally lands on a fresh IP.
When a flow spans several pages and the target ties state to the source IP, hold one address with a sticky session. Add -session-<id> to the username, optionally with -ttl-<minutes>, and reuse that id for the life of the context. Start the next context with a new id to get a new IP.
Rotating per context
Create a new browser context (optionally without a session parameter) for each task. Combined with the dashboard rotation interval, each context loads from a different residential IP. Best for scraping many independent pages in parallel.
Sticky per session
Add -session-shop42-ttl-15 to the username to hold one IP for fifteen minutes across a login and its follow-up pages. Keep the same context alive for the flow, then rotate the id for the next one.
Playwright
Which ProxyOmega plan to pick
Browser automation moves more bytes than plain HTTP scraping because it loads full pages and subresources. Pick based on how much bandwidth and targeting precision you need.
| Workload | Plan | Why |
|---|---|---|
| General dynamic-site scraping | Budget Unlimited (:10000) | Unlimited bandwidth suits full page loads; rotating pool and country targeting cover most jobs. |
| Heavy pages or many parallel contexts | Premium Unlimited (:8000) | Dedicated 200Mbps-1Gbps throughput keeps render-heavy sessions fast under concurrency. |
| City/state/ASN precision | Platinum (:20228) | Pay-per-GB with the finest geo-targeting for localized rendering tests. |
| Mobile-rendered targets | Mobile (:20229) | Real 4G/5G IPs for sites that serve a different experience to carrier traffic. |
| Whitelisted fixed IP | Static ISP (:30000) | One stable US (Dallas) address for targets that require a consistent source IP. |
Playwright
Troubleshooting
Playwright surfaces proxy problems as navigation errors or challenge pages. These are the common causes and fixes.
407 Proxy Authentication Required
Playwright reports this as ERR_PROXY_CONNECTION_FAILED or an auth error. Check that password is your dashboard API key and that the username's targeting parameters are valid for the plan. A parameter that does not apply to a product (for example an ASN parameter on Budget Unlimited) rejects the entire username.
net::ERR_TUNNEL_CONNECTION_FAILED
Usually a malformed server value or a blocked port. Use the http:// scheme with a port in the 10000-10199 range for Budget Unlimited, and confirm the host matches your plan's endpoint.
Connection reset after auth
If IP whitelisting is enabled on your account, add the machine running Playwright to the allowlist in the dashboard. Requests from an address not on the list are dropped once whitelisting is active.
Navigation timeouts
Residential latency plus full page rendering can exceed the default timeout. Raise it on goto (for example timeout=60000) and prefer wait_until='domcontentloaded' over 'networkidle' on ad-heavy pages.
FAQ
Frequently asked questions
Can I use a different proxy for each browser context?
Yes. The proxy binds to the context, so you can pass a different proxy object to each new_context call and run parallel sessions from different IPs inside one browser process.
Does the same config work in the Node.js version of Playwright?
Yes. The proxy object with server, username, and password is identical across the Python, Node.js, Java, and .NET APIs. Only the surrounding language syntax changes.
Should I set the proxy at launch or at new_context?
Use new_context when you want per-session IPs, which is the common scraping case. Set it at launch only when every context should share the same proxy configuration.
How do I target a country?
Append -country-<code> to the proxy username, for example user123-country-gb. Pair it with Playwright's locale and timezone_id for a consistent regional fingerprint.
Why does the site still show a CAPTCHA?
IP is only part of the fingerprint. Keep a realistic locale, timezone, and user agent, avoid networkidle waits that hammer the page, and use sticky sessions so the IP does not change mid-flow.
What is the proxy password?
It is your account API key from the ProxyOmega dashboard, not your login password. Store it in an environment variable rather than in source.
Give every Playwright context a real IP Start routing today.
Residential proxies in 200+ countries, SOCKS5 on every port.
ProxyOmega