Proxies for Minecraft put a different IP address between your client and the server, so the server, its plugins, and its ban list see that address instead of your home connection. Minecraft is unusual among games here, because Java Edition talks to servers over plain TCP, which means a SOCKS5 proxy can carry the entire session rather than just the launcher and the website. That single fact is why "Minecraft proxies" is a real product category while "Fortnite proxies" mostly means a VPN in disguise.
Because a lot of this traffic crosses our own network, we see both ends of it: what people buy a proxy for on Minecraft, and what comes back when it breaks. The support tickets sort into a few piles: alts kicked on join by an AntiVPN plugin, proxies that died in the middle of a session, and people who bought a proxy to lift a ban that was never tied to their IP in the first place. This page is the practical version: what "proxy" even means in Minecraft, why Java works and Bedrock does not, how servers detect and kick proxy addresses, which type to buy, how to wire it in, and where a proxy stops being the right tool.
What proxies are best for Minecraft?
For playing Java Edition on a server you care about, residential or ISP proxies, held on one sticky address per account. Large servers run AntiVPN plugins that flag hosting ranges, so datacenter IPs get kicked at login, and a residential address reads as a normal home player. ISP (static residential) is the best fit for a single account you keep for months, since the server sees the same address every day. Datacenter is fine only for reaching a blocked launcher page or a small private server with no checks, and Bedrock Edition needs a UDP-capable tunnel rather than a plain proxy of any type.
"Minecraft proxy" means three different things
The phrase is ambiguous, and half the frustration in this topic comes from people reading the wrong answer.
- A network proxy for the player. Your client connects to a proxy, and the proxy connects to the server. This is the subject of this page.
- A server-side proxy for a network of servers. BungeeCord, Waterfall, and Velocity are "proxy servers" in the Minecraft admin sense: one public address that routes players to several backend servers (lobby, survival, minigames). If you are an operator searching for how to set one up, that is software configuration on your own machines and has nothing to do with residential IPs.
- An alt account. In some communities "running through a proxy" is shorthand for playing on a second account. Alts are a reason people buy network proxies, but the account and the address are separate purchases and separate problems.
The rest of this page is about the first meaning, and it uses the second and third only where they intersect.
Java is TCP, Bedrock is UDP, and that decides everything
Most competitive games send their live traffic over UDP, and a proxy pulled from a list cannot carry UDP at all. Minecraft splits down the middle.
Java Edition connects to servers over TCP, port 25565 by default. The server list ping, the login handshake, chunk data, movement, chat, all of it is one TCP stream. A SOCKS5 proxy relays TCP natively, so the whole game session can ride the proxy: the server sees the proxy's address for everything, and a ban on that address is a ban on the proxy, not on you.
Bedrock Edition (Windows 10 and 11, consoles, phones) runs on RakNet, a UDP protocol, on port 19132 (19133 for IPv6). HTTP, HTTPS, and SOCKS4 proxies move only TCP. SOCKS5 defines UDP relaying, but almost no free SOCKS5 proxy implements it and the Bedrock client has no proxy field to point at one anyway. Routing Bedrock needs an OS-level tunnel and a proxy that genuinely forwards UDP, or a VPN. On consoles it means a router that does the tunnelling.
Which edition a plain proxy can actually carry
| Feature | Java Edition | Bedrock Edition |
|---|---|---|
| Transport | TCP, port 25565 | UDP (RakNet), port 19132 |
| SOCKS5 proxy carries the game | yes | no |
| HTTP proxy carries the game | no | no |
| Proxy setting in the client | no, use launch arguments, a mod, or Proxifier | no, tunnel at OS or router level |
| Where a ban lands | account, and often IP | account, and often IP |
Java is the edition the proxy market is built for. Bedrock is a VPN or router job, and any page telling you to paste a SOCKS5 address into Bedrock is describing something that does not exist.
Minecraft Wiki, Java Edition client command line arguments and Bedrock Edition protocol
Why people use proxies for Minecraft
The reasons are concrete, and they split into ones a proxy solves and ones it only pretends to.
- Keeping alts separate. Every Minecraft account is a separate purchase, and people legitimately own several: a main, a PvP alt, a test account for a build. Big servers link accounts that share an address, so a second account logging in from the same home connection is a second account waiting to inherit the first one's flags. One clean IP per account keeps them apart.
- Server-side IP bans. The vanilla server ships a ban-ip command that writes your address to banned-ips.json, and plugin suites do the same at scale. An IP ban blocks an address, not a person, so it also blocks the sibling, the roommate, and the whole shared connection. A different address restores access for the people the ban was never aimed at. Using it to evade your own ban is against the rules of every server that matters, and we cover why it fails anyway below.
- Reaching the game on a locked network. Schools, dorms, and offices block the launcher domains, the session servers, or port 25565 outright. A proxy tunnels the client around the block. This is the one case where a free proxy is a fair first try.
- Pinging and scraping servers. Server list sites, status trackers, and network monitors send thousands of status pings. Each one is a tiny TCP handshake, and a single address doing it at volume looks like a scanner, so the work gets spread across rotating IPs.
- Latency, which does not work. A lot of "Minecraft proxy" searches are really about ping. A proxy adds a hop, so it cannot cut latency; at best a proxy in the server's own region costs only a few milliseconds. The fixes for ping are a wired line and a server near you.
How servers actually detect a proxy
Mojang and Microsoft do not ban IP addresses at the platform level. The reporting system added to Java Edition in 2022 issues account bans from online play, and those follow the account wherever it logs in from. Every IP decision is made by the server you join, and the tooling there is mature.
The standard mechanism is an AntiVPN plugin (AntiVPN, ProxyFlow, FoxGate, and a dozen others) that fires on the login event, sends your address to an IP reputation API such as proxycheck.io or IPWarner, and kicks you before the handshake completes if the answer says hosting, proxy, or VPN. The check is a database lookup on the address's network, so it does not care how fast your proxy is or how well it hides your headers. A datacenter IP is flagged because it belongs to a datacenter, full stop. Popular minigame networks like Hypixel and CubeCraft try to block VPN and proxy connections outright, and smaller servers copy their plugin list.
The second layer is alt detection: plugins that record which accounts log in from which addresses and link them. Two accounts on one IP become one entry, and a punishment on either can be applied to both. This is the whole reason the one-IP-per-account rule exists.
The third layer is behavior. Anticheat systems (Hypixel's Watchdog is the famous one) judge what your client does: movement, reach, click patterns. They ban the account, and a fresh address does nothing about a fresh ban for the same behavior. A proxy solves the address layer and nothing else.
Login event
your IP arrives
AntiVPN lookup
hosting range? kick
Alt linker
shared IP? grouped
Anticheat
behavior, not IP
Which proxy type fits Minecraft
Four types show up in Minecraft work, and the AntiVPN lookup is what separates them.
Datacenter proxies are cheap and fast, and they are exactly what reputation APIs are built to flag. Against any server running an AntiVPN plugin they are kicked at login. They still work for reaching a blocked launcher page, or for a private server run by friends who check nothing.
Residential proxies are real home connections. They pass the reputation lookup because they are what the lookup is trying to distinguish proxies from, and they can be pinned to a country so your exit sits near the server. Held sticky, one address carries one account for a whole session. Rotating, they spread status pings across many addresses. If the category is new, what is a residential proxy explains where the addresses come from.
ISP proxies are static residential: registered under a consumer ISP, hosted on datacenter-grade hardware, and yours for as long as you keep them. This is the cleanest home for a main account you play every day, because the server sees the same ordinary address at every login and never a reason to look twice.
Mobile proxies are carrier addresses shared by many real phones. They are the hardest to flag and rarely necessary for Minecraft, since residential already clears the checks that matter.
| Minecraft job | Proxy type | Why |
|---|---|---|
| Playing on a large server through a proxy | Residential or ISP, sticky | Passes the AntiVPN lookup, one address per account |
| A main account you keep for months | ISP (static residential) | Same home-looking IP every day |
| Several alts on one network | Residential or ISP, one IP each | Defeats alt linking by address |
| Pinging or scraping many servers | Rotating residential | Spreads status requests across addresses |
| Reaching the launcher on a blocked network | Datacenter or free | Only the block matters, nothing checks the IP |
| Bedrock, any job | UDP tunnel or VPN | A plain proxy cannot carry RakNet |
How to route Java Edition through a proxy
The client has no proxy screen, so the routing happens at one of three layers. Pick the one that matches your version and your tolerance for mods.
Launch arguments. The Java client accepts --proxyHost, --proxyPort (default 8080), --proxyUser, and --proxyPass as game arguments, and they configure a SOCKS proxy for the client. In practice they are unreliable for the server connection on modern versions, and players report the game attempting the proxy and failing with protocol errors. Treat them as a first try, not the answer.
A mod that wires the JVM proxy settings into the game connection. Java has always had system-wide SOCKS settings (-DsocksProxyHost, -DsocksProxyPort, and -Djava.net.socks.username plus -Djava.net.socks.password for authenticated proxies), but the Netty pipeline Minecraft uses for server connections ignores them. The RespectProxyOptions mod on Modrinth adds that support, so with the mod installed you set those four JVM arguments in your launcher profile and the server connection follows them. It supports SOCKS4 and SOCKS5.
An OS-level tool. Proxifier on Windows and macOS, or proxychains on Linux, captures the Java process itself and forces every connection it opens through your SOCKS5 proxy, no mod and no version dependency. Add a rule for javaw.exe (or the launcher's bundled runtime), point it at your proxy with the username and password, and start the game. This is the method that works for every Java version and every modpack, and our proxychains guide covers the Linux side.
Whichever layer you use, confirm the exit before you join anything: paste the proxy into our proxy checker to see its country, latency, and anonymity, and remember that latency from the checker is only the first leg. Pick an exit in the same region as the server, so the second leg stays short.
Minimal JVM arguments for the RespectProxyOptions route:
-DsocksProxyHost=203.0.113.10
-DsocksProxyPort=1080
-Djava.net.socks.username=user
-Djava.net.socks.password=pass
Proxifier rule for the mod-free route:
application: javaw.exe
action: proxy SOCKS5 203.0.113.10:1080 (with credentials)
everything else: direct
For Bedrock there is no equivalent inside the game. On Windows an OS-level tunnel with a proxy that forwards UDP is the only proxy path, and on consoles the tunnel has to live in the router. Most people who need Bedrock routed end up with a VPN, and that is the honest recommendation.
How many IPs, sticky versus rotating
Size the order from the job, not from a round number.
For playing and for alts the rule is one clean, sticky IP per account, held for the whole session and ideally for the life of the account. Rotating an address under a live session drops the TCP connection, which the game experiences as a disconnect, and rotating between logins gives the alt linker a new address to record next to your account each time. Static is the point.
Playing and alts (one sticky IP each, never shared):
main -> 198.51.100.20 ISP, held for months, near the server
PvP alt -> 198.51.100.21 ISP, held for months, near the server
build alt -> 198.51.100.22 residential sticky, same region
Server pinging (rotating residential, sized by request rate):
find the rate where one address starts getting refused,
stay under it, and add addresses to raise throughput.
For status pings and scraping, size by request rate: find the pace at which a single address starts being refused or throttled, stay under it, and add addresses for throughput. Rotating residential takes the counting off your plate, because each ping leaves from a fresh exit. Our pricing is pay-as-you-go with a balance that does not expire, and Minecraft is light on bandwidth (chunk data on join, then small packets), so a modest amount of data covers a lot of play.
Free versus paid for Minecraft
Two situations, opposite answers, and the line between them is whether an account you care about is involved.
You only need to reach the game on a blocked network, or test a connection. A free proxy can do it, and a dead exit costs you a ten-second swap. Our free proxy list is re-checked every few minutes across 100+ countries and lists SOCKS5 entries specifically, which is the protocol Java needs. Vet a candidate with the proxy checker first. We wrote up the whole free side, including what breaks and when, in free proxies for Minecraft.
You are playing on a real server with a real account. Free proxies are almost entirely datacenter addresses, which the AntiVPN lookup kicks on sight, and most of them die within minutes, which the game experiences as a disconnect in the middle of whatever you were doing. There is a smaller security point too: Java multiplayer encrypts the session after the login handshake and verifies you against the session servers rather than sending your password to the game server, so a proxy operator cannot lift your account from game traffic the way a hostile web proxy lifts a cookie. The launcher's Microsoft login is HTTPS as well. The real cost of free here is not theft, it is the kick and the drop. Paid residential starts at $0.44/GB pay-as-you-go with no KYC, and a session's worth of play is a small fraction of a gigabyte.
Keeping accounts and addresses clean
A handful of habits keep a Minecraft proxy setup out of the ban list.
- Use residential or ISP for any server that runs checks. Assume the big ones all do. A datacenter address is a kick, not a gamble.
- One account per address, one address per account. Alt linking is by IP. Never let two accounts share an exit, and never let one account wander across exits between logins.
- Match the exit to the server's region. A German player on a German server through a Brazilian exit has bought themselves lag and a login pattern that looks like a stolen account.
- Do not reuse public or burned addresses. A free list entry has already been used by everyone else who found it, and reputation APIs remember.
- Do not expect a proxy to beat anticheat or a ban. Watchdog and its cousins judge behavior and ban accounts. Ban evasion breaks the rules of the server, and the second account usually goes faster than the first.
- Own your alts. Accounts from "alt generators" are stolen or cracked, they do not pass the session servers, and a clean IP does nothing for a login the game itself refuses.
Where a proxy stops and the rules start
A proxy is one input, and for Java Edition it is a more powerful one than in almost any other game, because it carries the whole session. It fixes the address layer: which IP a server, its AntiVPN plugin, and its alt linker see, and whether your accounts share a network. It does not fix an account ban, a hardware fingerprint on a modded server, a Bedrock client that cannot be pointed at it, or the physical distance to a server on another continent.
For a quick connection test or a blocked network, start free with the free proxy list and the proxy checker. For playing, for alts, and for anything you want to last, clean residential held sticky per account, at $0.44/GB pay-as-you-go, or ISP addresses for the accounts you keep, is what holds. Route Java through the mod or through Proxifier, give every account its own address near the server, and the server sees an ordinary player instead of a proxy.
Sources
- Minecraft Wiki, Java Edition client command line arguments (
--proxyHost,--proxyPort,--proxyUser,--proxyPass): minecraft.wiki - Minecraft Wiki, Bedrock Edition protocol (RakNet over UDP, port 19132): minecraft.wiki
- RespectProxyOptions on Modrinth, which adds JVM SOCKS proxy support to the client's Netty pipeline: modrinth.com
- Oracle, Java Networking and Proxies (
socksProxyHost,socksProxyPort,java.net.socks.username): docs.oracle.com - SpigotMC, AntiVPN plugin (login-time IP reputation lookups that kick proxy and VPN connections): spigotmc.org
- Minecraft Forum, routing Minecraft through a SOCKS proxy (the launch-argument route failing on 1.16.3): minecraftforum.net