> ## Documentation Index
> Fetch the complete documentation index at: https://anyip.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# UDP Proxy Support

> Learn how to use UDP with anyIP proxies and test compatibility with QUIC/HTTP3

anyIP proxies support **UDP (User Datagram Protocol)**, enabling advanced use cases like HTTP/3, QUIC, and modern streaming protocols.

<Note>
  **Beta Feature**

  UDP support is currently in beta. To enable UDP for your account, please [contact support](https://anyip.io/account/) through the dashboard.
</Note>

### 🕵️‍♂️ Enhanced Stealth

Using UDP proxies significantly improves your stealth profile. Modern browsers and apps increasingly rely on UDP-based protocols (like QUIC/HTTP3).

* **Blend In:** Most real residential traffic uses QUIC. If you force TCP-only (HTTP/1.1 or HTTP/2), your traffic pattern looks distinct from regular users.
* **Modern Footprint:** Supporting UDP makes your bot or scraper indistinguishable from a standard Chrome or mobile user.

## 🚀 How UDP Support Works

Unlike TCP, which is connection-oriented, UDP is connectionless and often used for speed-critical applications (VoIP, gaming, streaming).

* **Protocol:** UDP is supported **ONLY via SOCKS5**.
* **Port:** Same port as TCP (`1080`).
* **Authentication:** Standard username/password authentication works for UDP.

<Warning>
  **Compatibility Warning**

  Not all proxy clients or software support UDP over SOCKS5. Many standard HTTP libraries (like Python `requests` or standard `curl`) **do not** support UDP proxying.
</Warning>

## 🛠 How to Test UDP Compatibility

The best way to test if your setup is correctly tunnelling UDP traffic is to check for **HTTP/3 (QUIC)** support, which runs exclusively over UDP.

### Step-by-Step Test

1. **Configure your browser** or client to use our proxy via **SOCKS5**.
2. **Visit this test page:** [https://cloudflare-quic.com/](https://cloudflare-quic.com/)
3. **Check the result:**
   * **Success:** You see the message: **"your browser used HTTP/3"**.
   * **Failure:** You see: "your browser used HTTP/1.1" or "HTTP/2".

<Tip>
  **Reload Required?**

  Browsers often attempt TCP/HTTP2 first. If you don't see HTTP/3 immediately, **reload the page a few times** to force the browser to switch to the QUIC protocol.
</Tip>

### Why am I seeing HTTP/1.1 or HTTP/2?

If the test page shows HTTP/1.1 or HTTP/2, it means your connection is falling back to TCP. This usually happens because:

* Your proxy client is configured for `HTTP` instead of `SOCKS5`.
* Your software/browser does not support **UDP Associate** (the SOCKS5 command for UDP).
* The target website has not advertised HTTP/3 support yet (unlikely for the test page).