From your apps: SOCKS5 UDP
Point any app or library that supports SOCKS5 UDP ASSOCIATE at the pool's SOCKS5 endpoint, with your proxy username and password. HTTP proxies carry TCP only.
socks5://USER:PASS@HOST:PORTUDP proxies
Proxies that carry UDP as well as TCP: residential, mobile, ISP and datacenter, paid per GB. Use UDP from your apps over SOCKS5, or from a whole device, browser included, through a VPN profile.
- SOCKS5 UDP for apps and code
- HTTP/3 and WebRTC in the browser, through VPN access
- UDP to any port except a few abused services
- HTTP/3 (QUIC)From your proxy's IP
- WebRTCSame address as your proxy
- DNS lookupsAnswered near the proxy
- IPv6No address shown
Pools that carry UDP
Pay-per-GB pools with UDP. Prices are per GB of traffic.
- Datacenter proxiesfoxtrot$0.69 per GBUDP via SOCKS5See pricing
- ISP proxieslitport$0.99 per GBUDP via SOCKS5See pricing
- Mobile proxieslitport$5.49 per GBUDP via SOCKS5See pricing
- Residential proxieskilo$1.19 per GBUDP via SOCKS5See pricing
Some package proxies carry UDP too. The VPN profiles page shows it for each proxy.
Two ways to use UDP
From a browser or a whole device: VPN access
Browsers send only TCP through a proxy setting. Link the proxy to a WireGuard VPN profile and the device's UDP goes through the proxy too: HTTP/3, WebRTC calls and meetings, and games.
AllowedIPs = 0.0.0.0/0, ::/0Why a browser needs the VPN
Chrome and other Chromium browsers relay only TCP through SOCKS5 and HTTP proxies. A VPN profile carries everything the device sends.
| Browser proxy setting | VPN profile on a proxy with UDP | |
|---|---|---|
| Websites over TCP | Browser proxy settingThrough the proxy | VPN profile on a proxy with UDPThrough the proxy |
| HTTP/3 (QUIC) | Browser proxy settingNot used: falls back to HTTP/2 | VPN profile on a proxy with UDPThrough the proxy |
| WebRTC calls and meetings | Browser proxy settingCan go around the proxy and show your real IP, or is limited to TCP | VPN profile on a proxy with UDPThrough the proxy |
| Other apps on the device | Browser proxy settingNot covered | VPN profile on a proxy with UDPThrough the proxy |
Source: Chromium network documentation.
Check your browser with our WebRTC and HTTP/3 leak test.
Good to know
- UDP goes through the SOCKS5 endpoint. HTTP proxies carry TCP only.
- UDP can reach any destination port except a few commonly abused services: SNMP, NetBIOS, SIP, SSDP and memcached.
- Pools without UDP refuse it, and apps fall back to TCP.
- VPN profiles are included with every proxy at no extra cost.
Frequently asked questions
Yes, on the pay-per-GB pools listed above and on some package proxies. UDP goes through the SOCKS5 endpoint; HTTP proxies carry TCP only.
Not through the browser's proxy setting: Chrome sends only TCP through SOCKS5 and HTTP proxies, so HTTP/3 falls back to HTTP/2 and WebRTC can go around the proxy. Link the proxy to a WireGuard VPN profile instead: the browser's HTTP/3 and WebRTC traffic then leaves through the proxy's IP.
Any destination port except a few commonly abused services: SNMP, NetBIOS, SIP, SSDP and memcached.
No. The pools listed above carry UDP; the others refuse it, and apps fall back to TCP.
Turn the VPN on and open our leak test. It shows the address WebRTC gives to websites and whether HTTP/3 arrives from your proxy's IP.