How to Change Chrome Proxy Settings on Windows, Mac, Linux

How to Change Chrome Proxy Settings on Windows, Mac, Linux

Kevin Wu
April 21, 2026· Updated October 9, 2026· 11 min read

The tricky part of how to change Chrome proxy settings is usually not the steps. It is choosing the right settings entry. Chrome usually uses the system proxy, but an extension, launch option or policy can control its configuration instead. Google's chrome.proxy documentation lists system as one proxy mode, and the official Windows, macOS, and GNOME documentation places proxy controls in system network settings.[1][2][3][4]

That is why closing and reopening Chrome often does not reset anything. The proxy server, PAC script, or bypass list may still be active at the operating system level. What you need to change is often the system network layer, not Chrome itself.

Key Takeaways

  • Chrome usually follows the system proxy instead of storing a separate browser-only proxy configuration.[1][2][3][4]
  • Common proxy modes include auto-detect, PAC script, manual proxy, and direct connection.[1][2][3][4]
  • A proxy can change routing, but it does not mean traffic is encrypted by default; if you need encryption or full tunnel protection, proxy settings alone are not enough.[1][2][3][4]
  • Troubleshooting usually comes down to the proxy address, port, authentication, bypass list, and PAC script.
  • On work or school networks, settings may be managed by an administrator and overwritten by policy.

These instructions cover Windows 10/11, macOS with System Settings, and Ubuntu Desktop using GNOME’s Network panel. Record your installed OS and Chrome versions; menu wording can differ. They are organized from the cited official documentation and have not undergone a complete end-to-end test. Change only a configuration you own or have permission to manage.

How do Chrome proxy settings work? First, understand why there is no separate switch

Google's developer documentation divides Chrome proxy modes into direct, auto_detect, pac_script, fixed_servers, and system. For most users, the common real-world case is simple: Chrome uses the system proxy.[1]

That means when you search proxy inside Chrome, the page that opens is usually the operating system's proxy panel, not a browser-specific control center.

The system panel is only one input. An extension with the proxy permission can set Chrome’s configuration, and command-line options can affect the fallback to system settings. A policy can also control the effective configuration. Consequently, an empty system proxy panel does not by itself prove Chrome is using a direct connection.[1]

Before editing, open chrome://policy to inspect applied policies and their source, and review installed proxy-controlling extensions. Record any approved launch options with the configuration owner. If settings are locked, supplied by your organization, or repeatedly restored, ask IT to identify the controlling layer; do not remove policies or disable a managed extension to force a different route.[5]

If a proxy you never set keeps reappearing on a personal device, treat it as a wider security question and run the broader online safety checks for extensions, accounts and installed software.

How can you check whether Chrome is using a proxy?

The quickest path is:

  1. Open Chrome;
  2. Go to Settings;
  3. Search for proxy;
  4. Open the system proxy settings;
  5. Check whether the mode is auto-detect, script, manual, or off.

This matters especially at work. You may think no proxy is enabled, while the system is actually using auto-detection or a PAC script.

Before changing anything, privately record the current mode, server and port, PAC URL, bypass list and active network. Obtain missing values from the trusted proxy owner. Keep passwords out of screenshots and shared notes. Choose one permitted website and task for a before/after comparison, and save work in other apps because a system-level change may affect them.

How to change Chrome proxy settings on different systems

Microsoft's documentation describes three main Windows paths: automatic detection, setup script, and manual proxy server.[2]

For the Windows 11 layout described by Microsoft, use this sequence; Windows 10 may expose the fields directly rather than through a setup dialog.[2]

Steps 2–4 below are alternatives: complete only the mode approved by the network owner.

  1. Open Settings > Network & internet > Proxy and record all existing automatic and manual settings.
  2. For approved auto-detection, set Automatically detect settings as instructed by the network owner; this option does not require inventing a server address.
  3. For PAC, open Set up or Edit beside Use setup script, enable it, enter the supplied script URL and select Save.
  4. For a manual proxy, open its setup dialog, enable Use a proxy server, enter the supplied address and port, preserve approved exceptions and select Save.
  5. Reopen the panel to confirm the saved values, then test the same permitted task in Chrome. Change only the chosen mode; do not clear other network requirements as an extra troubleshooting step.

Windows: automatic detection

Use this when a company or campus network already provides proxy settings. If the network depends on auto-detection, typing a random manual address may break connectivity.

Windows: setup script

Use this when IT gives you a PAC file URL. PAC files can decide whether a request should use a proxy based on the URL or domain.

Windows: manual proxy

You need to know:

  • The proxy server address or IP;
  • The port;
  • Whether a username and password are required;
  • Which addresses should bypass the proxy.

If you only know half of that information, do not force it.

Mac

Apple's path is clear: System Settings > Network > select your current network > Details > Proxies.[3] There you can configure auto-discovery, PAC, HTTP, HTTPS, and SOCKS proxies, plus hosts and domains that should bypass the proxy.[3]

Common Mac mistakes include filling in the server and port but forgetting:

  • Authentication details;
  • Internal domains that should connect directly;
  • Whether you are editing the network interface currently in use.

Apply the change to that network service only:

  1. Record its existing enabled proxy types, PAC URL, server fields and bypass list.
  2. Enable the owner-approved discovery, PAC or manual option; for manual entries, use the supplied protocol, address, port and authentication rather than copying one value into every field.
  3. Select OK, reopen that service’s Proxies panel to confirm the saved settings, and test the same permitted Chrome task.[3]

Changing Wi-Fi settings does not establish what an Ethernet service uses. Check the service actually carrying the comparison request.

Linux

GNOME documentation groups proxy settings into None, Manual, and Automatic, with the entry in the Network Proxy panel.[4] On this desktop, check Chrome’s controlling configuration before assuming it follows these settings.

This example is for Ubuntu’s GNOME desktop, using the upstream GNOME instructions; it is not a universal Linux menu path.[4]

  1. Open the Activities overview, search for Network, and open the Network Proxy control.
  2. Record the current method. Choose Manual only with approved per-protocol addresses and ports, or Automatic with the supplied configuration URL.
  3. Reopen the control after changing it to check the stored method and fields, then make a new request in Chrome to the same permitted target.

Other desktop environments and application-specific settings need their own documentation. Do not infer that terminal tools or every application consume this panel.

4 things people confuse in Chrome proxy settings

1. A proxy is not the same as encryption

A proxy forwards requests. It does not encrypt everything by default. If you want broader traffic protection, check whether the tool provides encryption, tunneling, and unified connection protection, not only whether it has a proxy.

A proxy address or PAC script chooses where requests go; it is not a guarantee of an encrypted connection to that proxy. A VPN is not a substitute for correcting the proxy address, credentials, or PAC rules, and it does not override managed-device policy. If you still need an encrypted tunnel for personal browsing, AethoVPN can carry that traffic while HTTPS stays enabled; once connected, confirm which applications and DNS requests actually use the tunnel before relying on its coverage. Create your account with an email code to set up that tunnel.

When the unresolved issue is application coverage, compare system proxy scope with a TUN route. A setting used by Chrome is not proof that every app uses it. This comparison does not authorize replacing a required organizational route.

2. A PAC script is not automatically more reliable

PAC is flexible, but it can fail because the script URL is down, rules conflict, or workplace policy changes.

3. The browser loading pages does not prove the proxy is correct

Sometimes only part of the traffic is not following the route you expected. You may need to check IP results, DNS behavior, and the bypass list together.

4. Closing Chrome does not clear the system proxy

The setting is often stored in the operating system, not the browser.[2][3][4]


How can you tell whether the change worked?

I recommend this order:

  1. Confirm the system proxy mode;
  2. Check the server address, port, and authentication;
  3. Check whether a PAC script is active;
  4. Review whether the bypass list excludes your target site;
  5. Run an IP check last.

If nothing changes on a company network, policy override is a common reason. That does not mean you clicked the wrong button. It may mean the device is managed.

Use a new request to the same hostname in the same Chrome profile after saving the change. Repeat the original task, preserve HTTPS validation, and record any proxy, authentication or certificate error. A PAC rule may send the task site and an IP-check site along different paths, so the IP result is only evidence about that request; it does not prove DNS behavior, every site’s route or coverage of other apps.

How do you disable a temporary proxy and restore the baseline?

  1. Return to the same configuration layer and network service. In Windows, restore the recorded switch states and any changed manual address, port, exceptions or PAC URL, then save. Turn off a temporary manual or script option only if it was originally off; restore auto-detection to its recorded state.
  2. On macOS, turn off only the proxy options you temporarily enabled, restore the original fields and select OK. On GNOME, restore the recorded method and values; select None only if direct access was the approved baseline.[2][3][4]
  3. Reopen the settings and repeat the original permitted task with a fresh Chrome request. Confirm that required internal services still work.
  4. If the prior state was itself a managed proxy, restore it rather than forcing every switch off. Persistent overrides or certificate warnings go to the responsible owner.

Stopping Chrome or a separate VPN is not restoration of these settings. Retain a private record of what changed and whether the original task recovered; do not claim success from a saved switch alone.

Summary

  • How to change Chrome proxy settings is mostly about changing the system proxy, not finding a hidden browser switch.[1][2][3][4]
  • Windows, Mac, and Linux support auto-detection, PAC, or manual proxy modes, but the controls live in system network settings.
  • A proxy can change the request path, but it does not automatically provide encryption or full privacy protection.
  • Troubleshooting usually focuses on the address, port, authentication, PAC script, and bypass list.

FAQ

Does Chrome have its own independent proxy settings?

For regular users, usually not through a standalone standard interface. Chrome mostly calls the system proxy.[1]

Why did another browser change after I changed Chrome?

You probably changed the system proxy, which other browsers may also use. Check each browser’s routing settings before assuming the change applies only to Chrome.

Are Chrome proxy settings and a VPN the same thing?

No. A proxy mainly changes the forwarding path. Encryption and broader connection protection depend on the tool you use.

What is a PAC script?

It is an automatic proxy configuration script that decides which URLs should use a proxy and which proxy they should use.[1][2][3][4]

Why is the proxy still active after I close Chrome?

Because the setting may be stored in the operating system, so exiting the browser does not remove it.

What if I cannot change the proxy on a company computer?

It is probably controlled by administrator policy. Confirm whether the device is managed, then contact IT.

Why does Chrome ignore an empty system proxy panel?

An extension, launch option or policy may control the effective configuration. Inspect the controlling layer and ask its owner; an empty system panel is not proof of direct access.[1][5]


Disclaimer

This article is for general network configuration and privacy education only. Proxy policies on enterprise, campus, and managed devices may be controlled by administrators.

Sources

  1. Chrome for Developers, chrome.proxy API: https://developer.chrome.com/docs/extensions/reference/api/proxy
  2. Microsoft Support, Use a proxy server in Windows: https://support.microsoft.com/en-gb/windows/use-a-proxy-server-in-windows-03096c53-0554-4ffe-b6ab-8b1deee8dae1
  3. Apple Support, Enter proxy server settings on Mac: https://support.apple.com/guide/mac-help/enter-proxy-server-settings-on-mac-mchlp25912/mac
  4. GNOME Help, Define proxy settings: https://help.gnome.org/gnome-help/net-proxy.html
  5. Chrome Enterprise and Education Help, View a device's current Chrome policies: https://support.google.com/chrome/a/answer/9024365?hl=en

Sources checked 9 October 2026.


Related Articles:

Start your 3-day free trial

Sign up to experience all premium features at no cost.

*Available only to new users. Each user is limited to one trial.

How to Change Chrome Proxy Settings on Windows, Mac, Linux | AethoVPN