An active CleanProxies plan
Static ISP proxies for fixed US IPs, or rotating residential / mobile proxies for pools. The $4.99 trial works too.
Chrome has no proxy fields of its own. Open Settings → System → Open your computer's proxy settings, enter your CleanProxies host and port there, then type your username and password when Chrome asks. For a Chrome-only proxy, launch Chrome with --proxy-server or use an extension such as FoxyProxy or ZeroOmega.
Chrome is the browser most people check search results, ads and store pages in, so it's the quickest place to see a site the way a US visitor sees it. With a dedicated CleanProxies ISP IP, Chrome leaves from a real carrier address with a 0 fraud score, and the address stays the same every time you open it.
Static ISP proxies for fixed US IPs, or rotating residential / mobile proxies for pools. The $4.99 trial works too.
From the dashboard's proxy manager: host (or IP), port, username and password. Convert lists with the proxy list formatter.
Both products use the same setup in Google Chrome. What changes is how long an IP stays with you.
The best fit for everyday browsing: a 100% dedicated US ISP IP that stays the same all month, with unlimited bandwidth, so Chrome looks like one steady home connection and sites don't ask you to re-verify.
Dedicated static IPs registered to US and Canadian ISPs. The address stays the same for as long as you hold it, with unlimited bandwidth and HTTP(S) or SOCKS5 access.
Use a sticky residential line (5 to 60 minutes or 24 hours) to check a page from another country. A rotating line gives a new IP on new connections, which can log you out in the middle of a visit.
Residential IPs in 190+ countries with country, state and city targeting. Rotate on every request or hold a sticky session for up to 90 minutes; GB never expire.
Every product connects over HTTP(S); static ISP and ISP subnet proxies also run SOCKS5 and IP whitelisting. This is what the dashboard gives you to paste into Google Chrome.
IP:PORT:USER:PASSOne line per dedicated IP. With IP whitelisting on, the line is just IP:PORT and no password is sent.
HOST:PORT:USER:PASSGenerated in the proxy manager. The username carries the location and session you pick, so generate a new list to change them.
http://USERNAME:PASSWORD@HOST:PORTsocks5://USERNAME:PASSWORD@HOST:PORTUse http:// even for HTTPS websites; the TLS session still runs end to end. The socks5:// form is for static ISP and ISP subnet proxies.
Four steps, then check the exit IP with the free proxy checker.
Click the three-dot menu → Settings → System (or go to chrome://settings/system), then click Open your computer's proxy settings.
On Windows 10 and 11 that opens Network & internet → Proxy: next to Use a proxy server click Set up, turn it on, enter your CleanProxies host in Proxy IP address and the port in Port, and click Save. On macOS it opens the Network settings (see the Safari guide).
Load any page. Windows has no fields for proxy credentials, so Chrome asks for the proxy's username and password: paste them from the dashboard. A whitelisted ISP proxy connects without asking.
Open What is my IP? and confirm the address and location. To turn the proxy off later, switch off Use a proxy server in the same Windows screen.
Replace the highlighted placeholders with the values from your dashboard.
The system proxy applies to every app on the computer. To proxy Chrome alone, start it with --proxy-server. The flag takes a scheme, host and port but no credentials (Chrome ignores credentials embedded in proxy settings), so Chrome shows its sign-in prompt for the username and password. A separate --user-data-dir starts a new Chrome instance; without it, a Chrome that is already running ignores the flag.
& "C:\Program Files\Google\Chrome\Application\chrome.exe" `
--proxy-server="http://HOST:PORT" `
--user-data-dir="$env:TEMP\chrome-proxy"open -na "Google Chrome" --args \
--proxy-server="http://HOST:PORT" \
--user-data-dir="$HOME/chrome-proxy"google-chrome --proxy-server="http://HOST:PORT" --user-data-dir="$HOME/chrome-proxy".Open chrome://net-internals/#proxy to see the Effective proxy settings Chrome is using, then load What is my IP? to confirm the exit address. Run the WebRTC leak test too, because WebRTC can reveal your real IP.
Open What is my IP? through the proxy to see the address and headers a website receives, or paste up to ten lines into the free proxy checker to test connectivity, latency and exit IP.
Still stuck? Our 24/7 support team answers fast: contact us with the error and the line you used (leave the password out).
--user-data-dir, or quit Chrome completely before launching it with the flag.WebRtcIPHandling policy to disable_non_proxied_udp (or use an extension that does), then rerun the WebRTC leak test.Setup guides and best practices from the CleanProxies blog.
Setup guides for tools people run next to Google Chrome.
Proxies tab fields, why Chrome needs HTTP, list import, Test and WebRTC leak protection.
Setup guideProxy profiles, the lock icon for credentials, Auto Switch rules and HTTP vs SOCKS5.
Setup guideWindows proxy settings, the --proxy-server option, the sign-in prompt and SOCKS5 limits.
Setup guideManual proxy setup in Settings, exceptions, proxy logins, PowerShell and netsh winhttp.
Setup guideStraight answers about running CleanProxies in Google Chrome.
No. On Windows, macOS and most Linux desktops Chrome uses the computer's proxy settings. To give Chrome its own proxy, start it with the --proxy-server flag or use a proxy extension.