The most technical feature that separates SOCKS5 from an HTTP proxy is its ability to carry UDP traffic. An HTTP proxy works over TCP only; it cannot forward UDP packets in any way. This difference is decisive in gaming, voice calls and some DNS scenarios.
The UDP ASSOCIATE Command
In SOCKS5, UDP transport is started with the CMD=0x03 (UDP ASSOCIATE) command. The mechanism differs from TCP:
A critical detail: the TCP connection is the UDP session's "lifeline". If the client does not keep the TCP connection open, the relay closes.
The UDP Packet Header
UDP packets are not sent directly; a small SOCKS5 header is prepended to every packet:
This extra header ensures UDP packets are routed to the correct target through the relay. The header size adds a few bytes of overhead per packet.
The Support Problem: Missing in Most Places
Although UDP ASSOCIATE is defined in the RFC, it is not widely supported in practice. The reasons are operational:
| Party | Typical situation | Why |
|---|---|---|
| Commercial proxy providers | Usually disabled | The difficulty of abuse and resource management |
| Client libraries | Partial support | Complex to implement compared to TCP |
| Browsers | None | They do not need it |
| A server you set up yourself | Configurable | You have full control |
The phrase "we support SOCKS5" may not include UDP support. If you need UDP, ask about it explicitly and test it during the trial.
Which Scenarios Require It?
Jobs that require UDP
- The real-time traffic of online games.
- Voice and video call protocols.
- Carrying DNS queries over the proxy.
- Some streaming protocols.
- QUIC / HTTP-3 based connections.
Jobs that do not require UDP
- Web scraping and data collection.
- Social media account management.
- API integrations.
- SEO and price tracking.
- Ad verification.
For the relationship between proxies and gaming, see does a proxy reduce ping in games article; there we also covered UDP's role in game traffic.
A Note on QUIC and HTTP/3
The modern web is increasingly moving to the QUIC protocol, and QUIC runs over UDP. If your proxy does not carry UDP, the client automatically falls back to TCP-based HTTP/2. This usually works without problems, but in some cases it produces extra latency.
Because almost every site offers an HTTP/2 fallback, this is not a problem in practice. Even so, it is worth knowing about this behaviour in latency-sensitive work.
Testing
Testing UDP support from the command line is not as easy as testing TCP. The quickest way is to get written confirmation from the provider and try it with your real application during the trial.
Summary
SOCKS5 can carry UDP traffic with the UDP ASSOCIATE command — something an HTTP proxy cannot do at all. However, support is not widespread; most commercial providers keep UDP disabled. For work such as web scraping, account management and data collection you do not need UDP. In scenarios such as gaming, VoIP and DNS tunnelling it is indispensable and must be confirmed before purchase. For product details, see our SOCKS5 proxy page .