Logo
Tutorials
March 2, 2026
8 min

Microsoft Edge proxy settings: a step-by-step setup guide

Alanta Kaminskaite
Microsoft Edge proxy settings: a step-by-step setup guide
Resumen
Learn how to set up, change, and fix proxy settings in Microsoft Edge on Windows and macOS, using manual, PAC, command-line, and browser extension methods.

Key takeaways

  • Microsoft Edge is built on Chromium and uses your operating system's network settings by default, so on Windows you configure an Edge proxy through Windows Settings, and on macOS through System Settings.
  • You have four practical ways to point Edge at a proxy: the Windows manual proxy panel, an automatic setup script (PAC file), Edge command-line flags for a single browser session, and a browser extension that stores credentials per profile.
  • Have four details ready before you start: the proxy host, the port, your username and password (or an allowlisted IP), and the protocol, which is usually http and sometimes socks5.
  • Match the proxy type to the task: rotating residential for location-accurate research, static residential or ISP for stable signed-in sessions, and datacenter for fast access to public content.

Microsoft Edge does not ship a proxy field of its own. Because it shares the system network stack, the proxy you set applies to Edge and to every other app that reads the same settings. This guide walks through each setup method on Windows and macOS, shows the command-line flags that scope a proxy to one Edge session, and ends with a troubleshooting checklist for the errors people hit most often.

What are Microsoft Edge proxy settings?

Microsoft Edge proxy settings are the configuration that tells Edge to route its web traffic through an intermediary server instead of connecting to sites directly. A proxy server receives the request from Edge, forwards it to the target site, and returns the response, so the site sees the proxy's IP and location rather than your own.

Edge is a Chromium-based browser, and its network stack uses the system network settings by default. Two consequences follow. On Windows, the Edge proxy is the Windows proxy, so the option inside Edge simply opens the Windows page. And a system proxy applies to every app that reads it, not Edge alone, so a proxy scoped to Edge only needs the command-line method or a browser extension covered later in this guide.

People route Edge through a proxy to test how a site renders for a user in another market, to check localized prices and search results, to verify publicly served ads, to keep research browsing on a separate IP, and to add a layer of privacy between the browser and the sites it visits.

What you need before you set up an Edge proxy

Gather four things before you open any settings panel. Having them ready turns a fiddly setup into a two-minute job.

  1. The proxy host and port. This is the address Edge connects to, in host:port form. With Proxy-Cheap, rotating residential uses a shared gateway: proxy-us.proxy-cheap.com:5959 for the US pool and proxy-eu.proxy-cheap.com:5959 for the EU pool. Static products (static residential, ISP, datacenter) give you a unique host and port per proxy, copied from the dashboard. If you are not sure where to read these values, see how to find a proxy server address.
  2. Your credentials. Either a username and password, or an allowlisted IP. Rotating residential authenticates with a username and password. Static residential, ISP, datacenter, and mobile products also support IP allowlist authentication, which skips the login prompt entirely when you connect from a known IP.
  3. The protocol. Proxy-Cheap supports HTTP and SOCKS5 across the product line. HTTP is the most compatible choice for a browser. Use SOCKS5 when you specifically need it, and set it through a PAC file or the command line, since the Windows manual panel is built around HTTP proxies.
  4. A way to verify. A page that echoes the connection back, such as ipinfo.io/json, so you can confirm the exit IP and country changed after setup.

One rule throughout: keep your username and password in their own fields. Do not paste them into a shared address bar or a screenshot you might share.

How to set up a proxy in Microsoft Edge on Windows

On Windows, the fastest route is the manual proxy panel. You can open it straight from Edge, which keeps you from hunting through the Settings app.

Diagram showing a request from Microsoft Edge passing through the Windows system proxy setting to the Proxy-Cheap gateway, out to the target website, and back to the browser with the proxy IP shown.

Edge reads the Windows system proxy, so each request routes through the Proxy-Cheap gateway to the target site and returns through a different exit IP.

  1. Open Edge, click the three-dot menu in the top right, and choose Settings.
  2. In the left menu, select System and performance, then click Open your computer's proxy settings. This opens the Windows Proxy page directly.
  3. Under Manual proxy setup, click Edit next to Use a proxy server.
  4. Toggle Use a proxy server on. Enter the Proxy IP address (for example, proxy-us.proxy-cheap.com) and the Port (for example, 5959).
  5. Optional: in the exceptions box, list any addresses that should connect directly. The label reads "Use the proxy server except for addresses that begin with the following entries. Use semicolons (;) to separate entries." Tick Don't use the proxy server for local (intranet) addresses if you want internal sites to skip the proxy.
  6. Click Save and restart Edge so it picks up the change.

You can reach the same page without going through Edge: press Windows + I, then go to Network & internet and select Proxy.

After you save, open a new Edge tab and visit ipinfo.io/json. If the IP and country match the proxy you entered, Edge is routing correctly. If a login prompt appears first, that is the proxy asking for your username and password, which the authentication section below explains.

How to use automatic proxy setup or a PAC script in Edge

Many networks hand out proxy details through a configuration file rather than a fixed address. A PAC file (proxy auto-config) is a small script that tells the browser which proxy to use for each request, which is handy when the right proxy depends on the destination.

Edge supports two automatic options on the same Windows Proxy page:

  • Automatically detect settings. Leave this on if your network advertises a proxy through WPAD. Edge will discover the configuration without any manual entry.
  • Use setup script. Turn this on, paste the script address (the PAC file URL, such as https://example.com/proxy.pac) into the Script address field, and click Save.

Use a PAC file when an administrator gives you one, or when you want different sites to take different routes from a single rule set. If both a setup script and a manual proxy are configured, the script usually takes priority, so pick one method to avoid confusion.

How to set a proxy for Edge only with command-line options

The manual and PAC methods change the system proxy, which every app inherits. To scope a proxy to a single Edge session and leave the rest of your system on a direct connection, launch Edge with command-line flags. These flags come straight from Microsoft's Edge documentation and override the system settings for that session only.

The core flag is --proxy-server. It accepts three forms:

:: 1) One proxy for all traffic

msedge.exe --proxy-server="proxy-us.proxy-cheap.com:5959"

 

:: 2) A different proxy per scheme

msedge.exe --proxy-server="http=proxy-us.proxy-cheap.com:5959;https=proxy-us.proxy-cheap.com:5959"

 

:: 3) A direct connection, no proxy at all

msedge.exe --proxy-server="direct://"

 

To point a session at a PAC file instead, use --proxy-pac-url:

msedge.exe --proxy-pac-url="https://example.com/proxy.pac"

 

To send most traffic through the proxy but let some hosts connect directly, pair --proxy-server with --proxy-bypass-list. The list is semicolon-separated and accepts trailing-domain and IP patterns:

msedge.exe --proxy-server="proxy-us.proxy-cheap.com:5959" --proxy-bypass-list="*.example.com;127.0.0.1;localhost"

 

To launch Edge with no proxy even when the system has one set, use --no-proxy-server. It overrides any other proxy option:

msedge.exe --no-proxy-server

 

On Windows you can run these from a shortcut (paste the flag after the quoted path in the shortcut's Target field) or from PowerShell:

# Close all Edge windows first, then launch a fresh session with the proxy.

Start-Process "msedge.exe" -ArgumentList '--proxy-server="proxy-us.proxy-cheap.com:5959"'

 

One gotcha trips people up here: Edge reuses an already-running process, so a new flag is ignored if an Edge window is already open. Close Edge completely before launching with a flag, or add --user-data-dir="C:\edge-proxy-profile" to start an isolated session that does not collide with your main browser. The command-line route also has no field for a username and password, so a protected proxy still shows the login prompt on the first request.

How to set up an Edge proxy on macOS

On a Mac, Edge reads the macOS network settings, so you configure the proxy at the system level:

  1. Open the Apple menu and choose System Settings.
  2. Select Network, click your active connection (Wi-Fi or Ethernet), then click Details.
  3. Open the Proxies tab.
  4. Tick the proxy type you need. Choose Web Proxy (HTTP) and Secure Web Proxy (HTTPS) for an HTTP proxy, or SOCKS Proxy for SOCKS5. For a PAC file, tick Automatic Proxy Configuration and paste the script URL.
  5. Enter the server host and port. If the proxy needs a login, tick Proxy requires password and add your username and password.
  6. Click OK, then Apply, and restart Edge.

The command-line flags from the previous section work on macOS too. Launch Edge from the Terminal with the same --proxy-server flag, pointing at the Edge binary inside the application bundle, when you want a session-only proxy without touching the system settings.

How to add a proxy with a browser extension

Because Edge is built on Chromium, it runs extensions from the Microsoft Edge Add-ons store and from the Chrome Web Store. A proxy extension is often the most convenient option: it applies to Edge only, stores your username and password so you skip the repeated login prompt, and lets you switch between proxies in a couple of clicks without reopening any settings panel.

The Proxy-Cheap browser extension installs in Edge the same way it does in Chrome. It handles HTTP and SOCKS5 imports, central proxy management, quick profile switching, and WebRTC protection so the browser does not reveal a local IP outside the proxy. For users who want a proxy in Edge but not across the whole machine, an extension is usually simpler than juggling command-line flags.

One caveat: an extension only proxies the browser it runs in, so other apps keep using the direct connection or system proxy. That is the point if you want isolation, and a limitation if you expected machine-wide coverage.

How to enter a proxy username and password in Edge

The Windows manual proxy panel has fields for the host and port, but none for credentials. When a proxy needs a login, Edge handles it with a prompt rather than a settings field. The first time you load a page through the proxy, Edge shows a sign-in box asking for your username and password. Enter them, and Edge remembers them for the rest of the session.

That prompt corresponds to the 407 Proxy Authentication Required response. If you keep seeing it, one of three things is usually true:

  • The username or password is wrong. Re-copy both from your dashboard, watching for trailing spaces.
  • You are on IP allowlist authentication and the device's IP is not on the list. Add the current IP in the dashboard, or switch that proxy to username and password.
  • Another app cleared the saved credentials. Re-enter them, or use a browser extension that stores them permanently.

For credentials you do not want to retype, two routes avoid the prompt. IP allowlist authentication ties the proxy to a known IP on static residential, ISP, datacenter, and mobile products, so no login is needed from that machine. A browser extension stores the username and password in the profile and sends them automatically. On protocol choice, the Windows manual panel and most extensions assume an HTTP proxy. For SOCKS5, configure it through a PAC file, the command line (--proxy-server="socks5://host:port"), or the macOS SOCKS Proxy field.

How to change, reset, or turn off the proxy in Edge

Turning a proxy off is the same path as turning it on. Open Settings > System and performance > Open your computer's proxy settings in Edge, or Network & internet > Proxy in Windows Settings, then toggle Use a proxy server off and click Save. Switch off Use setup script and Automatically detect settings as well if either is on. Restart Edge.

To clear the system proxy from the command line, two commands cover it. The first shows what is currently set; the second resets the WinHTTP proxy to a direct connection:

netsh winhttp show proxy

netsh winhttp reset proxy

 

A frequent complaint is that Edge keeps changing the proxy back, often flipping from automatic to manual after a restart, or re-adding a server you removed. That behavior almost always comes from outside Edge: a group policy (the ProxySettings policy), a VPN or security app that rewrites the system proxy, or leftover malware-style settings. Check for a managed policy first, disable any app that manages connections, and run netsh winhttp reset proxy to clear a stuck value. Since the setting is system-wide, the fix lives in Windows, not in the browser.

Common Microsoft Edge proxy problems and how to fix them

When Edge will not connect through a proxy, the error usually points straight at the cause. Work down this list from the top:

  • "Can't connect to the proxy server" (ERR_PROXY_CONNECTION_FAILED). The host or port is wrong, or the proxy is not reachable. Re-check the address and port, confirm the proxy is active in your plan, and try http:// before anything else.
  • The login prompt keeps returning (407). Wrong username or password, or an IP that is not on your allowlist. Re-copy the credentials, and if you use IP authentication, confirm the sending IP matches the one on file.
  • The page loads but shows the wrong country. The exit location does not match what you ordered. Re-check the gateway or the specific IP you selected, and confirm your plan covers that region. You can verify the live exit IP and country with the steps in how to test proxies.
  • Browsing is slow. A residential IP routes through a real consumer connection, so it runs a little slower than a datacenter IP by design. For speed on public content, a datacenter proxy is the better fit; for location accuracy, residential is worth the small latency cost.
  • It works in another browser but not Edge. A flag from an earlier session may be overriding the system proxy. Close every Edge window, confirm no leftover --proxy-server flag sits in your shortcut's Target field, and reopen Edge.
  • The proxy works on a test page but a real site errors out. A generic check page says nothing about one specific site. Test against the actual site you care about, and if a datacenter IP struggles, move that task to a residential or mobile IP.

The pattern across all of these: read the error first, confirm the host and port, then verify the exit IP. Those three checks locate almost every Edge proxy problem in under a minute.

Which Proxy-Cheap proxy fits your Edge setup?

Every method above is the same regardless of which proxy you plug in, but the result you should expect depends on the proxy type. Match the product to what you are doing in Edge:

What you do in EdgeBest fitWhy
Location-accurate research and localized pricingRotating residentialNew IP per request from real consumer connections across many regions
Signed-in sessions and account-bound workStatic residential (ISP)The same trusted IP held for the whole session
Long-lived sessions with flexible loginISP proxiesStatic or rotating, username and password or IP allowlist
Fast access to public, unprotected pagesDatacenterHigh throughput and predictable per-IP cost
Mobile-first platforms and appsMobileReal carrier IPs for mobile-network tasks
Heavy, sustained browsingUnlimited bandwidthUnmetered transfer across many locations

 

Matrix mapping Proxy-Cheap product lines to Microsoft Edge use cases: rotating residential, static residential, ISP, datacenter, mobile, and unlimited bandwidth.

Pick the proxy type by the job in Edge: rotating residential for location-accurate research, static residential or ISP for signed-in sessions, datacenter for speed on public pages.

A quick way to choose: if a site changes its content by visitor or location, use a rotating residential or mobile IP so Edge sees what a local user sees. If you need the same IP to persist across a signed-in session, use a static residential or ISP proxy. If the target is public and you care most about speed, a datacenter IP is the efficient pick, and for heavy daily browsing an unlimited bandwidth plan keeps the meter from running.

Proxy-Cheap covers all of these on pay-as-you-go and per-IP plans, with no setup costs and cancel anytime. Generate your credentials in the dashboard, enter the host and port in Edge using the method that fits your platform, and verify the exit IP before you rely on it for real work.

Preguntas frecuentes

No. Edge is Chromium-based and uses your operating system's network settings by default. On Windows, the option inside Edge (Settings > System and performance > Open your computer's proxy settings) simply opens the Windows Proxy page. The exception is the command line, where Edge flags override the system proxy for a single session.

Click the three-dot menu, choose Settings, select System and performance in the left menu, then click Open your computer's proxy settings. That takes you to the Windows Proxy page where both automatic and manual options live. On macOS, the same menu points you to System Settings > Network.

Not through the system settings, since both browsers read the same system proxy. To give Edge its own proxy, launch it with the --proxy-server command-line flag or install a proxy extension in Edge only. Either method scopes the proxy to that browser without changing the system-wide setting the other browser uses.

Because the proxy is system-wide, something outside Edge is usually rewriting it: a group policy, a VPN or security app, or a setup script. Check for a managed ProxySettings policy, close apps that manage your connection, and run netsh winhttp reset proxy to clear a stuck value. The fix lives in Windows, not the browser.

Run netsh winhttp show proxy in Command Prompt to see the system proxy, then open ipinfo.io/json in Edge to confirm the live exit IP and country. If the IP matches your proxy and the country is right, Edge is routing correctly. If your real IP shows, the proxy is not applied.

On Android, Edge uses the device's network proxy rather than a browser setting. Open the Wi-Fi network's advanced options, set the proxy host and port there, and Edge will follow. For a proxy that travels across networks, a proxy app or the device VPN settings is the more reliable route on mobile

A proxy routes specific traffic, such as your browser's, through another IP, while a VPN routes the whole device through an encrypted tunnel. A browser proxy is lighter and faster for tasks like location-accurate testing and research, since it skips full-device encryption. A VPN covers every app at once but adds overhead.

A little, depending on the proxy type. Datacenter IPs add minimal latency and suit public, high-throughput pages. Residential and mobile IPs route through real consumer connections, so they run slightly slower in exchange for location accuracy. Choosing the right type for the task keeps the slowdown unnoticeable in normal browsing.

You can configure a free proxy the same way, but expect more failures, slower speeds, and frequent location mismatches. Free proxies also offer little assurance about how your traffic is handled. A paid proxy on a self-serve plan returns more consistent results and clearer terms, which matters once the proxy is doing real work.

Yes. The Windows manual panel is built around HTTP proxies, but you can use SOCKS5 by setting it in a PAC file, on the command line with --proxy-server="socks5://host:port", or in the macOS SOCKS Proxy field. Proxy-Cheap supports HTTP and SOCKS5 across its product line.