Most free proxies cannot carry Minecraft. On 27 September 2026 we tested 4,229 proxies that our own free list showed as working. Almost none refused Minecraft's port outright. The proxies themselves were the problem: only 1,433 could open a tunnel at all, the HTTP ones took a median 6.7 seconds to open one, and only 23 of 2,086 SOCKS5 proxies passed UDP, which Bedrock needs.
This page shows what we measured, which free proxies are worth trying for Java Edition, what it takes to point the game at one, and what to use when free is not enough.
What Minecraft needs from a proxy
Minecraft Java Edition talks to a server over TCP, on port 25565 unless the server sets another one. Bedrock Edition servers listen on port 19132, over UDP. So a proxy for Minecraft has one job: carry that connection, on that port, fast enough for a live game.
Proxy types differ in exactly that:
| Proxy type | Java Edition (TCP) | Bedrock Edition (UDP) |
|---|---|---|
| HTTP | only through a CONNECT tunnel | no |
| SOCKS4 | yes | no |
| SOCKS5 | yes | only if it relays UDP |
An HTTP proxy is built for web pages. It can carry other traffic only through a CONNECT tunnel, and some are set to open tunnels to port 443 alone: that is the default configuration of Squid, an open-source proxy server. SOCKS proxies carry any TCP connection. Only SOCKS5 can carry UDP, with a command called UDP ASSOCIATE, and the proxy has to actually relay the packets (RFC 1928).
What we measured on 4,229 free proxies
We took our free proxy list at 14:32 UTC on 27 September 2026, when it showed 19,491 proxies as working. From our server, we asked each SOCKS proxy on it, and a random 1,500 of the HTTP ones, to open a tunnel to a site on port 443, then one on port 25565, the Minecraft default. Each SOCKS5 proxy was also asked to relay one UDP packet.
| Proxy type | Tested | Opened a tunnel | Median time to open one |
|---|---|---|---|
| HTTP | 1,500 of 17,487 | 179 (11.9%) | 6.7 seconds |
| SOCKS5 | all 2,086 | 886 (42.5%) | 1.2 seconds |
| SOCKS4 | all 643 | 368 (57.2%) | 0.9 seconds |
A second run 14 minutes later, on a list that had grown to 21,800, gave the same picture: 11.5, 41.9 and 52.0 percent opened a tunnel. Three things stand out.
Most listed proxies did not open a tunnel. Of the 1,500 HTTP proxies, 674 did not accept a connection within 8 seconds, and 498 accepted it but never answered. A proxy that answered our checker minutes earlier can be busy, full or gone by the time you use it.
Few refused the port. Of the 179 HTTP proxies that opened a tunnel to port 443, only 3 refused port 25565 outright, each with a 403, and no SOCKS5 proxy refused it by rule. A proxy can also block a port without a word, and that looks the same as one still trying, so we can only count refusals. And 21 HTTP and 196 SOCKS5 proxies reported a connection to that port where nothing answers: a free proxy's "connected" proves little.
Speed was the obstacle. The HTTP proxies that worked took a median 6.7 seconds to open one tunnel, and only 19 of the 179 did it in under a second. SOCKS was faster: a median 1.2 seconds for SOCKS5 and 0.9 seconds for SOCKS4. The checks of our own engine agree: a request through a working free proxy took a median 11 seconds on its last check, and 4.4 seconds for those that speak SOCKS5. These are times from our server in the United States, not game pings, but a proxy that needs seconds to answer once cannot keep a live game smooth.
Free proxies also come and go. Between May and 28 September 2026 our engine took 767,233 free proxies off its list for not answering, and 469,417 of those never answered a single check. 297,816 worked at least once, but most of those sat on 802 addresses with 20 or more ports each. On the other addresses, a quarter lasted less than 25 hours and half less than 10 days, counted from the day we first saw them. That count leaves out Amazon's networks and one June evening when our checker failed. Most of those we tested sit on datacenter networks: 3,258 of 4,229.
Which free proxies to try for Java Edition
Start with SOCKS, and filter hard. Our list can show SOCKS5 proxies only, and its API filters by protocol, latency and lifetime uptime, which is the filter that matters most for a game:
curl "https://hproxy.com/api/proxy-list?format=txt&protocol=socks5&max_latency_ms=1000&min_uptime_pct=90"
Then test each candidate before you point the game at it. Our proxy checker connects through the proxy for real and shows whether it answers, over which protocols, how fast, and where it exits. A SOCKS proxy that answers in well under a second is the only kind worth trying.
Expect to repeat this. A free proxy that works tonight may be gone tomorrow, and when it goes, the game connection goes with it.
How to point Minecraft Java Edition at a SOCKS proxy
Minecraft has no proxy setting in its menus, and Java's own proxy settings do not reach the game either. Oracle documents -DsocksProxyHost and -DsocksProxyPort as settings that send "all TCP connections" of a Java program through a SOCKS proxy, and many guides tell players to add them to the launcher's JVM arguments. Since version 1.7.2, the game ignores them for its connection to a server.
Mojang's bug tracker has had this open since 2013 as MC-38872, "Minecraft ignores java proxy parameters". It is confirmed and lists versions up to 1.21. One player there found out from the server log: "the server log join message showed my connection as coming from my home IP address, not from the VPS proxy."
So with those settings alone, the server still sees your own address. The Windows "Use a proxy server" switch fails for the same reason: the game's connection to a server does not follow Java's proxy settings at all. In a 2016 Stack Exchange thread on this, the accepted answer used the settings only for the login and sent the game itself "through an encrypted SSH tunnel rather than via SOCKS."
Two kinds of tools are built to reach the game connection. We did not test either with the game:
- A mod that adds the settings to the game. RespectProxyOptions, a Fabric mod on Modrinth, says it adds "full SOCKS-proxy support to the Minecraft client". Its only release is for 1.20.1, from August 2023.
- A program that forces the game through a proxy. Proxifier, for Windows and macOS, lets network applications "that do not support working through proxy servers" use a SOCKS or HTTPS proxy.
If you run your own server, its log shows the address each player joins from. That is the surest check of the route.
Bedrock Edition: the UDP problem
Bedrock is where free proxies fail almost completely. Only a SOCKS5 proxy can relay UDP, and in our test few really did:
- 786 of the 2,086 SOCKS5 proxies said yes to the UDP command;
- 665 of those named relay port 0, an address nothing can be sent to;
- 23 passed a real packet, a DNS question and its answer: 1.1 percent.
A proxy that says yes and relays nothing looks fine until the game does not connect. Our UDP proxy checker sends a real packet through the relay and counts a yes without a packet as a no.
"Proxy" inside Minecraft means something else too
Server operators run software called a proxy in front of their game servers, such as Velocity and BungeeCord. When it restarts, players see its message: "Proxy shutting down." from Velocity, or "The proxy server is restarting" from BungeeCord. Nothing on your side caused it; reconnect in a minute. Our guide to proxies for Minecraft covers that side: running Velocity, and the rules big servers set for players.
GeyserMC calls itself a proxy too: it bridges Bedrock players to Java servers. None of these change your address or route your connection, which is what this page is about.
Whether a server lets players in from proxy addresses is a rule of that server. We do not cover getting around a ban.
When free is not enough
A free proxy is fine for a first try. For a stable game connection you want what free proxies rarely have: one address that stays the same for the whole session, a login of your own, and, for Bedrock, UDP that really passes.
Our residential lines come as HTTP or SOCKS5. On Residential Premium, a sticky session holds one exit for up to 24 hours, and a SOCKS5 line can open UDP relays. That matters for Bedrock: of the 786 free SOCKS5 proxies that said yes to UDP, only 23 passed a packet. Residential Premium starts at $1.00 per GB, and purchased gigabytes have no scheduled expiry date (residential proxies).
How we tested
On 27 September 2026 we ran the test twice from our own server, on the proxies our free proxy list API returned at that moment. Each proxy was asked for a tunnel to example.com on port 443, then on port 25565, where example.com takes no connections: a proxy that allows the port tries and waits, and one that forbids it can refuse at once or drop the request without a word. We counted only refusals, so the silent ones say nothing about the port, among them the 81 HTTP proxies that took no second connection. Each SOCKS5 proxy was then asked for a UDP relay, and one DNS question went through it to a public DNS server.
We sent nothing to any Minecraft server. The timeouts were 8 seconds to reach a proxy, 10 seconds for each answer and 5 seconds for the DNS answer through a UDP relay. The engine figures come from the records of our free proxy engine on the same day. The archive counts and lifespans come from a query on 28 September.
Sources
- IETF: RFC 1928, SOCKS Protocol Version 5 (UDP ASSOCIATE and the reply codes) and RFC 9110 (CONNECT), read 27 September 2026.
- Minecraft ports: the Paper server.properties reference (Java, 25565), the Microsoft Bedrock Dedicated Server properties (19132) and GeyserMC's setup guide and common issues (Bedrock uses UDP, Java TCP), read 27 September 2026.
- Mojang: MC-38872, "Minecraft ignores java proxy parameters", read 27 September 2026. Stack Exchange: Using SOCKS with Minecraft (2016).
- Oracle: Java networking properties (socksProxyHost), read 27 September 2026.
- The two routes, in their own words: RespectProxyOptions on Modrinth and Proxifier, read 27 September 2026.
- Squid: cf.data.pre (the default tunnel rule). Velocity: documentation and messages. BungeeCord: messages. GeyserMC: README. Read 27 September 2026.
- HProxy: our free proxy test and engine records of 27 September 2026, the lifespan query of 28 September 2026, the free proxy list API, plan lines and terms.
