Setting a SOCKS5 Proxy in Chrome Without Breaking Every Other Tab
The short answer
On desktop, Chrome uses the operating system proxy settings unless you launch it with a proxy flag or use an extension. SOCKS5 handles any protocol and does not rewrite headers. Chrome has no field for a SOCKS5 username and password, so a credentialled proxy needs the system settings on macOS or an extension.
A SOCKS5 proxy is the least intrusive way to send one browser somewhere else: it opens a raw connection at the TCP level, so it does not care whether the traffic is HTTP, HTTPS or something else, and it does not add or rewrite headers. The setup is four lines of work. The reason people get stuck is that Chrome on desktop has no proxy screen of its own, and no place to type a SOCKS5 username and password.
What Chrome actually does with proxy settings
Chrome reads the proxy configuration from the operating system on Windows, macOS and Linux. Where the system says "use this proxy", Chrome uses it, and every tab and every profile follows. The setting is per machine, not per site, so the common surprise is that turning it on for one supplier portal also sends your bank, your webmail and your office tools through the same address.
There are three ways around that, and they differ in scope rather than in quality. A launch flag gives one Chrome instance its own proxy. An extension can switch per tab or per domain. A separate Chrome profile with its own shortcut keeps work and proxied browsing in different windows, which is the tidiest arrangement for a long-running task.
Method one: the operating system proxy
On Windows, open Settings, Network and Internet, Proxy, then Manual proxy setup, enable it and enter the address and port with the SOCKS5 type where offered. On macOS, open System Settings, Network, the active connection, Details, Proxies, then enable SOCKS5 Proxy and enter the server and port.
This is the method that survives a Chrome restart, and on macOS it is also the only built-in place that stores a SOCKS5 username and password. Its cost is scope: everything that respects the system proxy now uses that address, including apps you had forgotten about.
Method two: a launch flag, for one instance only
Quit Chrome completely, then start it with the proxy switch pointing at your SOCKS5 endpoint, for example: chrome --proxy-server="socks5://203.0.113.10:1080". On Windows you can put that in the Target field of a desktop shortcut; on macOS you can run it from Terminal with the full application path.
Method three: the credential problem
If your SOCKS5 endpoint requires a username and password, Chrome cannot take them from a flag or from its own dialog. For HTTP proxies Chrome shows a sign-in prompt and remembers it for the session; for SOCKS5 there is no prompt at all, so the request simply fails or the browser reports a proxy error.
Two routes work. On macOS, enter the credentials in the system SOCKS5 proxy panel, where they are stored and used. On Windows, the system proxy panel has no credential fields for SOCKS5, so the practical answer is an extension that uses Chrome's proxy API and supplies the credentials itself. On Linux, the same applies through the desktop environment's proxy settings.
Method four: a PAC file when only some sites should go through
A proxy auto-configuration file is a small script the browser runs for each request, returning the proxy to use or "direct". It is the only built-in way to send one domain through the proxy and everything else straight out, without an extension. Point Chrome at the file with --proxy-pac-url, or set it in the system proxy panel.
Worked example: one portal, one shortcut, no change to the rest of the day
A bookkeeper needs one supplier portal that refuses her country. Everything else on her laptop, including the accounting package and the bank, must keep using her normal connection. The system proxy is the wrong tool, because it would send all of that through the address as well.
She creates a second Chrome profile called "portal", makes a desktop shortcut with --proxy-server="socks5://198.51.100.24:1080" --profile-directory="Profile 2", and uses only that window for the portal. The flag applies to that shortcut, the profile keeps the portal cookies separate from her everyday browsing, and the rest of the machine never changes.
The address is a single Static Pro IP at $10 for the 30-day term. Because it is static rather than rotating, the portal's "remember this device" prompt works the second time she signs in, which is the practical difference between a fixed address and a pool.
The four setups, and what each one affects
| Method | Scope | Keeps after restart | SOCKS5 credentials | Best for |
|---|---|---|---|---|
| System proxy (Windows or macOS) | Every app that respects it | Yes | macOS yes, Windows no | A machine dedicated to the task |
| Launch flag --proxy-server | That Chrome process | No | Not supported | A separate shortcut for one job |
| Extension using the proxy API | Configurable, per tab or domain | Yes | Yes | Credentialled SOCKS5, or per-site routing |
| PAC file | Per request, by rule | Yes | No | One domain through, everything else direct |
Whichever you choose, a private static address is what keeps the exit the same between sessions: $10 for one IP on a 30-day term, replaced free if it stops working inside the term.
Prove it worked before you rely on it
- 1Load a page that echoes your IP address and confirm it is the proxy, not your home connection.
- 2Check the exit country matches the one you bought, because a mislabelled address is a refundable fault.
- 3Visit a site you know enforces HTTPS and confirm the padlock and certificate are intact.
- 4Open a page that requires a login, and complete it, so you find out now whether the address survives a session.
- 5Test a non-browser app on the same machine if you used the system proxy, and confirm it is not broken.
- 6Close Chrome completely and reopen it, then recheck the address. A flag that was not applied looks identical to a proxy that is down.
- 7Write down which method you used, so the next person does not add a second proxy on top of the first.
Where this connects on this site
- Addresses that support SOCKS5 on a fixed 30-day term are listed on STATIC Pro IPs with SOCKS5 access
- For blocks that are not about the address, see unblocking sites in Chrome specifically
- To choose between DNS, proxy, VPN and a remote desktop, start with the method-by-block comparison
What this will not do
- A proxy does not hide the browser itself. Your screen size, fonts, time zone and installed extensions still describe your device, and a site that checks those can still tell something is unusual.
- SOCKS5 is not encrypted by the proxy. HTTPS protects the content of your requests; the proxy sees the destination and the port, not the contents of an encrypted page.
- This will not defeat a block enforced by a device profile on a managed machine, because that policy also controls the proxy setting.
- No setup here guarantees a destination accepts the address, and a static IP is not sold as anonymity: it is a fixed address that belongs to one buyer.
- Proxy credentials are a password. Anyone who has them can use the address, and every session they open counts against the same reputation.
Questions this page gets asked
- Does Chrome support a SOCKS5 username and password?
- Not through the launch flag and not through a built-in dialog. macOS system proxy settings can store the credentials, and an extension that uses Chrome's proxy API can supply them. On Windows, the system proxy panel has no SOCKS5 credential fields.
- What is the difference between SOCKS5 and an HTTP proxy?
- SOCKS5 forwards any TCP connection and does not interpret the traffic, so it works for more than web pages and does not rewrite headers. An HTTP proxy understands web requests, which lets it add headers and handle caching, but it is limited to HTTP and HTTPS traffic.
- Why do I get a proxy error only on some sites?
- Usually a routing rule: a PAC file that sends that domain direct, an extension with an exclusion list, or a site that refuses the address. Test the same site with the proxy applied to everything, which separates a rule problem from an address problem.
Last reviewed 2026-10-26. Written for readers in the United States and elsewhere; rules about access, email and consent differ by country, and nothing on this page is legal advice.