Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

To override system proxy settings in Google Chrome for one desktop session, launch Chrome with --proxy-server="http://HOST:PORT"; Chrome normally follows the operating system proxy instead of offering a separate consumer proxy panel. Enterprise policy, an existing Chrome process, or an incorrect proxy scheme can prevent the override from taking effect.

The right method depends on whether the change should last for one test session, route only selected destinations, apply to one user, or be enforced across an organization. Command-line switches are usually best for a temporary Chrome-only test; PAC files and managed policies are better for selective or persistent routing.

Key takeaways

  • Chrome desktop normally sends users from chrome://settings/system to the operating system’s proxy settings rather than providing a general per-profile proxy editor.
  • A temporary Chrome-only proxy can be set with --proxy-server="http://HOST:PORT" and refined with --proxy-bypass-list.
  • Chrome must often be fully closed before a new command-line proxy takes effect, and a separate --user-data-dir is the safest way to run an isolated test instance.
  • A PAC file can select DIRECT, PROXY, or SOCKS5 separately for different destinations, but a DIRECT fallback allows traffic to bypass the proxy.
  • Organizations should use the current ProxySettings enterprise policy; the older ProxyMode policy is deprecated.
  • A Chrome proxy does not automatically cover every Chrome service, ChromeOS system component, Android application, VPN path, WebRTC path, or other application.

What does overriding the system proxy in Chrome actually mean?

Overriding the system proxy means making Chrome use proxy instructions different from the proxy configured for Windows, macOS, Linux, or ChromeOS. The scope depends on the configuration method.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Configuration Typical scope Best use Main limitation
Operating-system proxy Potentially many applications and services One consistent network proxy for a device Does not provide a Chrome-only override
Chrome command-line switch The Chrome process launched with the switch Temporary testing or a local debugging proxy Requires relaunching Chrome and can be superseded by policy
PAC file Connections governed by that PAC configuration Routing different destinations through different paths PAC logic can be difficult to debug
Proxy extension Browser proxy behavior controlled by the extension Convenient manual switching between known configurations Requires sensitive permissions and may be blocked or overridden
Enterprise policy Managed Chrome installations Persistent organizational control Users may not be able to change the setting
VPN Usually device or network level An encrypted tunnel for broader traffic Not equivalent to a browser-level HTTP or SOCKS proxy

Chrome’s manual proxy switches and bypass rules are documented in Chromium’s proxy configuration documentation. A local tool such as Charles Proxy, Fiddler, Burp Suite, mitmproxy, or Squid must already be running and listening; Chrome does not create that proxy for you.

Can Chrome use a proxy without changing Windows or macOS?

Yes. A separate Chrome launch can use --proxy-server without changing the operating system’s proxy setting. The normal Chrome settings page does not generally provide that independent consumer control.

To inspect Chrome’s normal system-proxy path, open Chrome and enter:

chrome://settings/system

Look for Open your computer’s proxy settings, or an equivalent label supplied by the operating system and Chrome release. Selecting that control changes the operating system’s proxy configuration, not merely Chrome’s configuration.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

ChromeOS is different. ChromeOS exposes proxy controls in network settings, and managed ChromeOS devices can receive global or per-network proxy configuration. The ChromeOS proxy documentation also describes differences involving extensions, DNS, authentication, Android applications, and system services.

What is the quickest Chrome-only proxy command?

Use Chromium’s manual proxy switch when you need one temporary Chrome session to use a proxy that differs from the system configuration:

chrome --proxy-server="http://HOST:PORT"

Replace HOST with the proxy hostname or IP address and replace PORT with the listening port. For a local HTTP debugging proxy on port 8080, the command becomes:

chrome --proxy-server="http://127.0.0.1:8080"

The proxy scheme matters. Common forms include:

http://proxy.example.com:8080
https://proxy.example.com:8443
socks4://proxy.example.com:1080
socks5://proxy.example.com:1080

The scheme describes how Chrome connects to the proxy. The scheme does not simply mean that every website must use the same protocol. Obtain the correct scheme from the proxy operator or local debugging tool.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Do not assume that putting https:// before a proxy address automatically makes ordinary proxying secure. An HTTPS destination, an HTTPS connection to a proxy, and an HTTPS-forward proxy are different concepts. The proxy software must support the selected protocol and authentication behavior.

Keep the proxy value in quotation marks when the command shell or address contains characters that could be interpreted specially. Do not place proxy usernames or passwords in a shared shortcut, shell history, batch file, PAC URL, or screenshot.

How do you launch Chrome with a proxy on Windows?

On Windows, launch the correct Chrome executable from Command Prompt or PowerShell, then add the proxy switch after the executable path.

Command Prompt

"C:Program FilesGoogleChromeApplicationchrome.exe" ^
  --proxy-server="http://127.0.0.1:8080" ^
  --proxy-bypass-list="localhost;127.0.0.1"

PowerShell

& "C:Program FilesGoogleChromeApplicationchrome.exe" `
  --proxy-server="http://127.0.0.1:8080" `
  --proxy-bypass-list="localhost;127.0.0.1"

Some installations use C:Program Files (x86)GoogleChromeApplicationchrome.exe. Per-user installations, custom deployments, and managed installations can use different paths. If the command fails, locate the installed chrome.exe rather than assuming either example is universal.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Chrome desktop shortcut

  1. Right-click the Chrome shortcut and choose Properties.
  2. On the Shortcut tab, find the Target field.
  3. Append the switches after the closing quotation mark around the executable path.
"C:Program FilesGoogleChromeApplicationchrome.exe" --proxy-server="http://127.0.0.1:8080"

The switches must be outside the executable path’s closing quotation mark. Adding them inside the quoted path makes Windows treat them as part of the filename.

How do you launch Chrome with a proxy on macOS?

On macOS, run Chrome’s executable inside the application bundle from Terminal:

/Applications/Google Chrome.app/Contents/MacOS/Google Chrome 
  --proxy-server="http://127.0.0.1:8080" 
  --proxy-bypass-list="localhost;127.0.0.1"

For a SOCKS5 proxy listening locally on port 9050, use:

/Applications/Google Chrome.app/Contents/MacOS/Google Chrome 
  --proxy-server="socks5://127.0.0.1:9050"

macOS may send a new launch request to an already running Chrome process. Quit Chrome completely before testing. If Chrome still appears to reuse an existing session, launch an isolated profile:

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
/Applications/Google Chrome.app/Contents/MacOS/Google Chrome 
  --user-data-dir="$HOME/chrome-proxy-profile" 
  --proxy-server="http://127.0.0.1:8080"

The separate profile prevents the test launch from sharing the normal profile’s running process and browsing state. Treat the profile as a test profile, especially if the proxy performs HTTPS inspection.

How do you launch Chrome with a proxy on Linux?

Linux installations commonly expose Chrome as google-chrome or google-chrome-stable; Chromium installations may use chromium or another package-specific name.

google-chrome 
  --proxy-server="http://127.0.0.1:8080" 
  --proxy-bypass-list="localhost;127.0.0.1"

For an isolated test profile:

google-chrome 
  --user-data-dir="$HOME/.config/google-chrome-proxy-test" 
  --proxy-server="http://127.0.0.1:8080"

Shell variables such as HTTP_PROXY and HTTPS_PROXY are not a reliable replacement for Chrome’s browser-level proxy switch. Those variables can affect command-line programs and other software, while Chrome’s proxy configuration follows Chromium’s own network settings.

How do you add proxy bypass rules in Chrome?

Add --proxy-bypass-list when particular destinations must connect directly instead of through the proxy:

What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
chrome --proxy-server="http://127.0.0.1:8080" 
  --proxy-bypass-list="localhost;127.0.0.1;*.internal.example"

Useful examples include:

localhost;127.0.0.1
*.internal.example
<local>

A larger private-address example is:

localhost;127.0.0.1;192.168.*;10.*;172.16.*;172.17.*;172.18.*;172.19.*;172.20.*;172.21.*;172.22.*;172.23.*;172.24.*;172.25.*;172.26.*;172.27.*;172.28.*;172.29.*;172.30.*;172.31.*

Command-line bypass rules can use semicolons or commas, while operating-system proxy settings use platform-specific formats. Do not copy a bypass pattern between Chrome’s command line, a PAC file, Windows, macOS, and ChromeOS without checking the syntax described in Chromium’s bypass-rule documentation.

A bypass rule sends matching traffic directly. A bypass rule does not send matching traffic through a second proxy. Direct connections can expose the local network path and use local DNS behavior, so a broad wildcard can create unexpected privacy or data-leak consequences.

Hostname and IP-literal matching can also differ. The ChromeOS proxy guidance specifically notes that an IP literal in a bypass list may not exempt the hostname associated with that IP. Test both the hostname and IP form when the distinction matters.

When should you use a PAC file instead of a fixed proxy?

Use a proxy auto-configuration (PAC) file when routing must vary by hostname, URL, internal network, or fallback condition. A PAC file is JavaScript that returns a proxy instruction for each request.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Also popular on Amazon
TP-Link AC1200 WiFi Router Dual Band Wireless Internet Router (Archer A54) | 4 x 10/100 Mbps Fast Ethernet Ports, EasyMesh Compatible, Support Guest WiFi, Access Point Mode, IPv6 & Parental Controls
  • Dual-band Wi-Fi with 5 GHz speeds up to 867 Mbps and 2.4 GHz speeds up to 300 Mbps, delivering 1200 Mbps of total bandwidth¹. Actual speeds cannot exceed your internet plan and vary based on conditions, distance, and obstacles such as walls.
  • Dual-band routers do not support 6 GHz.
  • Covers up to 1,000 sq. ft. with four external antennas for stable wireless connections and optimal coverage.
  • Supports IGMP Proxy/Snooping, Bridge and Tag VLAN to optimize IPTV streaming
  • Access Point Mode - Supports AP Mode to transform your wired connection into wireless network, an ideal wireless router for home.
function FindProxyForURL(url, host) {
  if (isPlainHostName(host) ||
      shExpMatch(host, "*.internal.example")) {
    return "DIRECT";
  }

  return "PROXY proxy.example.com:8080; DIRECT";
}

DIRECT means connect without a proxy. PROXY host:port selects an HTTP proxy, while SOCKS5 host:port selects a SOCKS5 proxy.

The example’s DIRECT fallback is convenient but means Chrome can connect without the proxy when the proxy is unavailable. A PAC file intended to enforce proxy use should not include a direct fallback unless that failure behavior is deliberate.

For managed Chrome, a PAC policy can look like this:

{
  "ProxyMode": "pac_script",
  "ProxyPacUrl": "https://proxy.example.com/proxy.pac",
  "ProxyPacMandatory": true
}

Under the enterprise policy model, ProxyPacMandatory prevents fallback to a direct connection when the PAC script is invalid or unavailable. The exact policy deployment and supported platforms should be checked in the Chrome Enterprise ProxySettings documentation.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Are proxy extensions a reliable Chrome-only solution?

Proxy extensions can make switching between several proxy configurations easier, but extensions are not a universal override. An extension needs permission to control proxy settings, and an enterprise policy can take precedence over extension settings.

On ChromeOS, extension-set proxies are disabled in Incognito by default unless the user explicitly allows the extension to run in Incognito. Extension behavior and priority are described in the ChromeOS proxy documentation.

Use only an extension from a source you trust. A proxy-control extension can potentially redirect browsing traffic or expose sensitive browsing data. A malicious, abandoned, or poorly maintained extension is a poor choice for credentials, financial activity, or corporate traffic.

How should an organization configure Chrome’s proxy?

Organizations should use the current ProxySettings enterprise policy for persistent, administrator-controlled configuration. The policy supports these modes:

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
ProxyMode value Effect Typical purpose
direct Never use a proxy Explicitly disable proxy use
system Use the operating system’s proxy Follow device configuration
auto_detect Use automatic discovery such as WPAD Network-managed discovery
fixed_servers Use explicitly defined proxy servers Fixed HTTP, HTTPS, or SOCKS routing
pac_script Use a PAC file Conditional routing and fallback logic

The Chrome Enterprise ProxySettings policy reference documents the supported modes, proxy server values, PAC settings, and bypass-list fields. A policy can override user settings, and Chrome may ignore command-line or extension proxy choices when policy controls the proxy.

Windows policy example

The documented Windows policy location is:

SoftwarePoliciesGoogleChromeProxySettings

A JSON-style policy value for a fixed local proxy can contain:

{
  "ProxyMode": "fixed_servers",
  "ProxyServer": "127.0.0.1:8080",
  "ProxyBypassList": "localhost;127.0.0.1"
}

Deployment mechanisms differ on macOS and Linux, so administrators should use the management system and Chrome packaging appropriate to the platform rather than copying an unverified file path from another operating system.

Use ProxySettings for new deployments. Chrome Enterprise documents the older ProxyMode policy as deprecated in favor of ProxySettings.

Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

What is ProxyOverrideRules in Chrome?

ProxyOverrideRules is a newer managed-policy option for selective proxy routing. Chrome Enterprise documents ProxyOverrideRules for Chrome version 144 and later on Windows, macOS, Linux, and ChromeOS.

The policy evaluates destination matchers and conditions before falling back to ProxySettings. The documented precedence gives ProxyOverrideRules priority over ProxySettings, the chrome.proxy extension API, and manual user settings.

Because ProxyOverrideRules requires a supported Chrome version and managed-policy context, administrators should verify the deployed browser version and policy support before using it. The current behavior and precedence are documented in the Chrome Enterprise ProxyOverrideRules reference.

How is Chrome proxy configuration different on ChromeOS?

ChromeOS proxy configuration can affect more than ordinary browser tabs. Depending on the network and management configuration, proxy behavior can interact differently with Chrome traffic, operating-system services, Google Play, Android applications, updates, enrollment, and DNS.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

ChromeOS can receive global or per-network proxy settings. Authenticated proxies may require bypasses for system traffic because browser-stored credentials may not be available to every ChromeOS service.

DNS behavior depends on the proxy type and component. ChromeOS documentation states that DNS resolution generally occurs on the proxy server for ChromeOS proxy configurations, except for SOCKS4, subject to the documented behavior. That does not justify a universal claim that every Chrome proxy mode prevents DNS leakage. HTTP proxying, SOCKS proxying, PAC routing, WebRTC, and non-browser traffic can follow different paths.

ChromeOS users should consult the ChromeOS proxy configuration and priority guidance before assuming that a browser proxy covers Android or system traffic.

How do you tell whether Chrome is managed?

Open chrome://management to see whether Chrome is managed and open chrome://policy to inspect policies applied to the browser.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
chrome://management
chrome://policy

The Chrome Help guidance for managed browsers recommends these pages for identifying management status and viewing applied policies.

If --proxy-server appears ineffective, inspect chrome://policy for proxy-related policies before repeatedly changing the command. A managed policy can deliberately prevent a user-level proxy override.

How do you verify that Chrome actually used the proxy?

A page loading successfully does not prove that Chrome used the intended proxy. Verify the effective route with several independent checks:

Also popular on Amazon
Sale
ASUS RT-AX1800S Dual Band WiFi 6 Extendable Router, Subscription-Free Network Security, Parental Control, Built-in VPN, AiMesh Compatible, Gaming & Streaming, Smart Home
  • New-Gen WiFi Standard – WiFi 6(802.11ax) standard supporting MU-MIMO and OFDMA technology for better efficiency and throughput.Antenna : External antenna x 4. Processor : Dual-core (4 VPE). Power Supply : AC Input : 110V~240V(50~60Hz), DC Output : 12 V with max. 1.5A current.
  • Ultra-fast WiFi Speed – RT-AX1800S supports 1024-QAM for dramatically faster wireless connections
  • Increase Capacity and Efficiency – Supporting not only MU-MIMO but also OFDMA technique to efficiently allocate channels, communicate with multiple devices simultaneously
  • 5 Gigabit ports – One Gigabit WAN port and four Gigabit LAN ports, 10X faster than 100–Base T Ethernet.
  • Commercial-grade Security Anywhere – Protect your home network with AiProtection Classic, powered by Trend Micro. And when away from home, ASUS Instant Guard gives you a one-click secure VPN.
  1. Compare the observed public IP and request behavior with the proxy disabled and enabled.
  2. Visit a destination that should be proxied and confirm that the proxy tool or server records the connection.
  3. Visit a destination listed in the bypass rules and confirm that the destination connects directly.
  4. Check the proxy’s connection log for the requested hostname, destination port, and authentication result.
  5. Open chrome://policy if the observed route does not match the command or PAC file.

Testing both a proxied and bypassed destination is important. A public-IP check alone may not reveal that one hostname was accidentally excluded or that another Chrome component used a different route.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Why does Chrome ignore --proxy-server?

Chrome usually ignores an apparent command-line override because the new process did not start with the switch, an existing process reused the old session, a policy controls the proxy, or the proxy value is invalid.

  1. Close Chrome completely. Quit every Chrome window. On Windows, check that no chrome.exe processes remain if the flag is not taking effect. Use the appropriate process tools on macOS or Linux.
  2. Check the executable path. Confirm that the command launches the intended Chrome installation rather than Chromium, another channel, or a wrapper.
  3. Check the quoting. On Windows, place switches after the closing quote around the executable path.
  4. Use a separate profile. Add --user-data-dir to prevent an existing profile process from being reused.
  5. Inspect policy. Review chrome://management and chrome://policy.
  6. Check the destination. Make sure the tested URL is not in the bypass list.
  7. Confirm the proxy type and listener. Verify the address, port, scheme, firewall rules, and whether the proxy is bound only to localhost or another interface.

What causes ERR_PROXY_CONNECTION_FAILED?

ERR_PROXY_CONNECTION_FAILED means Chrome could not establish a usable connection through the configured proxy; the error does not identify one single cause.

  • The proxy application is not running.
  • The hostname or port is wrong.
  • The proxy listens only on a different interface.
  • A firewall blocks the local or remote connection.
  • The proxy requires authentication.
  • The selected HTTP, HTTPS, SOCKS4, or SOCKS5 scheme is wrong.
  • The proxy can accept Chrome’s connection but cannot reach the requested destination.

Test the proxy listener locally and permit only the required application or port under the applicable security policy. Do not broadly disable security software as a troubleshooting shortcut.

How should you handle proxy authentication loops?

Authentication loops usually indicate that the proxy’s authentication method, credentials, or connection context is incompatible with the request. Proxy environments can use username-and-password prompts or enterprise mechanisms such as Kerberos and NTLM.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Chrome documentation discusses proxy authentication contexts including Negotiate, NTLM, Digest, and Basic in Chrome’s proxy authentication guidance. Confirm the authentication method required by the proxy and whether the proxy accepts credentials from the Chrome process being tested.

Basic authentication can expose credentials if the connection to the proxy is not appropriately protected. Never embed credentials directly in a shared shortcut, command history, PAC URL, batch file, or support screenshot.

What should you do about HTTPS certificate errors?

A forward proxy that inspects HTTPS traffic may require a trusted certificate authority to be installed on the client. A certificate warning does not mean that ignoring the warning is a safe fix.

Install and manage the organization’s inspection certificate through its approved process, verify that the proxy is correctly configured, and avoid bypassing certificate warnings. A misconfigured inspection proxy can expose sensitive traffic or cause applications to fail even when ordinary HTTP requests work.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Does a Chrome proxy hide DNS requests and cover all traffic?

No. Proxy coverage and DNS behavior depend on the proxy type, PAC result, Chrome component, operating system, and whether the traffic is actually generated by the browser.

HTTP proxying, SOCKS4, SOCKS5, PAC decisions, WebRTC, Chrome services, downloads, extensions, and operating-system traffic can have different routing characteristics. A bypass rule explicitly sends matching traffic directly. ChromeOS also documents platform-specific DNS behavior rather than a universal privacy guarantee.

A Chrome proxy is therefore not automatically equivalent to a VPN. A VPN usually operates at device or network level, while a Chrome proxy is intended for browser-level routing. Choose a VPN when the requirement is an encrypted broader tunnel; choose a proxy when the requirement is browser debugging, per-destination routing, or leaving other applications untouched.

Which method should you choose?

Choose the least complex method that matches the required scope and control.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Need Best approach Trade-off
One temporary Chrome session Command-line flags Chrome must be relaunched and the command can be misconfigured
A repeatable setting for one user Shortcut or launcher containing flags The proxy applies whenever that shortcut is used
Different routing by destination PAC file or supported managed ProxyOverrideRules Rules are more complex to troubleshoot
Convenient manual switching Trusted proxy extension Requires proxy-control permission and may be blocked by policy
Organization-wide enforcement ProxySettings enterprise policy Users may be unable to change the configuration
All applications, not only Chrome Operating-system proxy or VPN Changes more than Chrome
HTTP request inspection Local debugging proxy such as Charles, Fiddler, mitmproxy, or Burp Suite HTTPS inspection requires careful certificate setup and these tools may be excessive for simple browsing

Do not choose a generic VPN simply because the goal involves a different public IP. A VPN is a poor fit when the actual requirement is a local HTTP/SOCKS listener, per-URL routing, or inspection of browser requests.

How do you restore normal Chrome behavior?

Close the specially launched Chrome instance and reopen Chrome normally after testing.

  1. Remove --proxy-server, --proxy-bypass-list, and any --user-data-dir flags from the shortcut or launcher.
  2. Open Chrome normally and repeat the proxy verification test.
  3. Disable or remove a proxy extension if the extension supplied the override.
  4. Restore the operating system’s proxy settings if the system-proxy page was changed.
  5. Delete the temporary test profile only after confirming that it contains no data you need.
  6. For managed Chrome, ask the administrator to change or remove the policy; a user cannot reliably roll back an enforced policy locally.

Use a separate test profile whenever possible. A separate profile makes it easier to remove test flags, extensions, certificates, cookies, and proxy-related state without disturbing the normal Chrome profile.

Frequently Asked Questions

Can Chrome use a proxy without changing the Windows or macOS proxy?

Yes. Launch Chrome with --proxy-server="http://HOST:PORT" to set a proxy for that Chrome launch without changing the operating system’s proxy setting. Chrome must often be fully closed first, and an enterprise policy can override the command.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

How do I bypass the Chrome proxy for localhost?

Add --proxy-bypass-list="localhost;127.0.0.1" to the Chrome launch command. The bypass sends localhost traffic directly rather than through another proxy, and hostname and IP matching should be tested separately when both forms are used.

Why does Chrome ignore my proxy command?

Chrome may ignore the command because another Chrome process is already running, the switch was added to the wrong executable or shortcut, the proxy scheme or port is invalid, the test URL is bypassed, or an enterprise policy controls the proxy. Check chrome://management and chrome://policy.

Does a Chrome proxy affect other applications?

A command-line Chrome proxy is intended for the launched Chrome process and does not configure other applications. ChromeOS system services, Android applications, VPN traffic, WebRTC, and other components may follow different routing rules.

Is a proxy the same as a VPN?

No. A Chrome proxy provides browser-level HTTP or SOCKS routing, while a VPN generally creates a device- or network-level tunnel. Use a proxy for browser debugging or selective routing and a VPN when broader encrypted network routing is the actual requirement.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

The Bottom Line

For a temporary Chrome-only override, close Chrome and launch an isolated instance with --proxy-server="http://HOST:PORT", adding a narrowly scoped --proxy-bypass-list only when necessary. Use a PAC file for conditional routing and the current ProxySettings policy for managed deployments. Verify the route through the proxy’s logs and Chrome’s policy pages, then remove the flags or temporary profile to restore normal behavior.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply. Prices as of November 16, 2026 11:24 pm GMT.