On July 16, 2026, Octo Browser announced support for UDP proxies. The feature is available starting with version 3.0.6.
Chrome and antidetect browsers based on it have historically not routed UDP through proxies. QUIC runs over UDP, and HTTP/3 runs over QUIC. Citing W3Techs, the company says that nearly 40% of websites supported HTTP/3 in July 2026, including Google, YouTube, Instagram, and Cloudflare. Regular Chrome would likely use HTTP/3 on such a site, while a profile behind a proxy without UDP support would fall back to HTTP/2. An anti-fraud system could spot the difference. WebRTC is another reason: requests to a STUN server use UDP. If the proxy does not pass them through, the browser either cannot determine its IP address or tries TCP as a workaround.
When you launch a profile or check a proxy manually, Octo automatically detects whether the proxy supports UDP. If it does, a UDP icon appears next to the IP address, and all traffic from the profile, including QUIC and WebRTC, goes through the proxy. No separate proxy-routing tool is needed.
There are limitations. UDP works only with SOCKS5 proxies, and relatively few providers offer it—sometimes only on certain plans. The company says most anti-fraud systems do not put much weight on this yet. In September, version 3.1 added Nodyx, a provider with UDP support, to Octo’s proxy shop.
What to do: Update the client to 3.0.6 or later and check whether your SOCKS5 proxy shows the UDP icon.
