Discord has no proxy setting. Not on desktop, not in the browser build, not on mobile. Searching its settings for one is a genuinely common waste of ten minutes, so that's the first thing worth saying plainly.
You can still route it, in three different ways, and they suit different situations.
Option one: the system proxy
The Discord desktop app is built on Chromium, which means it follows whatever proxy your operating system is set to use. Set the proxy in Windows or macOS and Discord picks it up with no further work.
Routing Discord through the system setting
- 1
- 2
Close Discord completely
Fully quit it from the system tray, not just the window. Discord keeps running in the background and holds its old connection.
- 3
Reopen it
It reads the system setting at startup.
The trade-off is that this proxies everything on the machine that follows the system setting, including your browsers. That's fine if it's what you wanted and annoying if you only cared about Discord.
Windows also has no field for proxy credentials, so an authenticated proxy will start producing login prompts. The authentication guide covers the ways around that.
Option two: launch Discord with a flag
Chromium's command line options work on the Discord desktop app, which lets you proxy that one process and leave the rest of the computer alone.
On Windows, right-click your Discord shortcut, choose Properties, and add the flag to the end of the Target box, after the closing quote and a space:
"C:\Users\you\AppData\Local\Discord\Update.exe" --processStart Discord.exe --proxy-server="http://198.51.100.7:8080"
For a SOCKS5 proxy, change the scheme:
--proxy-server="socks5://198.51.100.7:1080"
Then close Discord fully and start it from that shortcut.
The flag will not take a username and password
This is Chromium's flag, and Chromium deliberately ignores credentials written into it. There's no formatting trick that makes it work. If your proxy needs a login, run a local relay with no password on 127.0.0.1 and point the flag at that instead.
Option three: use Discord in a browser
The web version at discord.com/app is a full Discord client, and it obeys whichever proxy that browser is using. That makes it the easiest way to run Discord through a different address than the rest of your machine, since Firefox keeps its own proxy settings entirely separate from Windows.
Voice works in the browser build too, with the same UDP caveat below.
Voice is the part that breaks
This deserves its own section because it surprises people who have everything else working.
Discord voice runs over UDP. HTTP proxies carry TCP only and have no way to represent UDP at all. So the moment your text chat is nicely proxied, voice is doing one of two things: failing to connect, or quietly going out over your real connection.
That second behaviour is the one to be aware of. It means a setup that looks completely proxied can still be announcing your actual address the moment you join a voice channel.
What each method actually covers
| Method | Text and images | Voice | Rest of the computer |
|---|---|---|---|
| System proxy | Proxied | Not carried | Also proxied |
--proxy-server flag | Proxied | Not carried | Untouched |
| Browser build | Proxied | Not carried | Untouched |
| VPN | Proxied | Proxied | Also routed |
UDP is the dividing line. Only a full tunnel carries voice.
If voice matters and so does the address it comes from, a proxy is the wrong tool and a VPN is the right one. That's a straight answer even though we sell proxies, because pointing someone at a product that structurally cannot do the job wastes their money.
Which proxy type to use
Discord holds a persistent connection open the whole time it's running, which is different from a browser making short requests. That changes what works.
Datacenter or ISP proxies suit it well: stable, fast, and no per-gigabyte cost for a connection that stays open all day.
Residential proxies work but are the wrong shape for it. You're paying per gigabyte for a long-lived connection, and the residential exits themselves are less stable than a datacenter line, which shows up as reconnects.
Free proxies will disconnect you repeatedly. Discord reconnects gracefully, so it's usable for light text chat, and it'll be visibly worse than no proxy at all. Our free proxy list is measured rather than promised, and what that data shows is that nothing on it should be holding a persistent connection.
Checking it worked
Discord doesn't tell you which address it's using, so check indirectly. With the proxy applied, open any page in the same browser (for the web build) or check your system-wide address (for the system proxy method) and confirm it's the proxy's.
Test the proxy itself first with our proxy checker. A dead proxy makes Discord sit on "Connecting" forever, which looks exactly like a Discord outage and sends people to the wrong status page.