Flud proxy settings rest on one line of first-party documentation: the app's Google Play description says "Proxy Support for trackers and peers." Flud is the most-installed independent torrent app on Android, with more than ten million downloads, but its developer, Delphi Softwares, publishes no manual that we could find. The how-to pages that turn up in search are proxy vendors' marketing, not sources. So this guide is short by design, and most of it is about how to find out what Flud does on your own device rather than about menus.
The one documented sentence
"Proxy Support for trackers and peers" tells you two things: the app has a proxy setting, and the developer intends it to cover both tracker requests and peer connections. It does not say:
- which proxy types are offered;
- whether a username and password can be entered;
- where the setting is in the app;
- what happens to DHT, UDP trackers and uTP when a proxy is set;
- which torrent engine the app is built on, which would otherwise let you infer the rest.
The app's version number is not shown on its listing either; the listing says it was updated on 27 September 2026. Flud is proprietary, contains ads and offers in-app purchases, including a paid Flud+.
A managed phone is a different review
On a laptop or server, the egress question is answered by the host's network configuration and the client's settings. On a company phone it is answered by device management, and the order of questions changes:
- Is a torrent app allowed on managed devices at all? Many mobile policies say no, independent of content.
- What will it fetch? A distribution image, an open-source release, a public dataset. Record it.
- Which control routes the traffic? A proxy field inside one app is set by the user, can be changed by the user, and reports nothing to the management console. A device-level control the administrator enforces, such as the always-on VPN Android's management framework supports, is the one a reviewer can audit.
If the answer to the third question is an in-app proxy anyway, the test below is the evidence. Peer-to-peer traffic for lawful content is fine on ProxyForge residential exits and on dedicated ISP and datacenter addresses with no traffic meter. Whatever the route, sharing material without the right to distribute it is prohibited under our acceptable use policy.
What a metered exit means on a phone
The limits are the same as on any client, with one more meter in the picture:
- Two meters, not one. A proxy relays the same bytes, so the phone's own data usage does not change. A metered proxy then counts the download, and every seeded byte, on its meter as well. Our gigabyte definition is the one that applies on our side. The Play listing advertises an "option to download on WiFi only", which protects the data plan; it does nothing for the proxy meter.
- No UDP through ProxyForge. Treat our SOCKS5 endpoints as TCP only; UDP relay has not been verified. DHT, UDP trackers and uTP will not work through them, and an HTTP proxy cannot carry UDP.
- No encryption, and anything the app sends outside the proxy carries the phone's own address on whichever network it is on.
- Not a privacy tool. For copyright exposure, torrent client projects point users to a VPN; qBittorrent's wiki says so directly.
Our mobile proxies guide is about a different thing, exits on mobile carrier networks, and does not make a torrent on a phone any cheaper.
Test it at the access point
A phone cannot easily capture its own traffic, but the network it is on can. Connect the phone to a Wi-Fi network whose gateway is a Linux machine you control, such as a laptop running a hotspot, and capture on that machine's wireless interface, hiding the proxy connection:
sudo tcpdump -ni WIFI_INTERFACE 'host PHONE_IP and not (host PROXY_IP and tcp port PROXY_PORT)'
Then, in Flud, set the proxy and start a lawful torrent. Three outcomes are possible:
| What the capture shows | What it means |
|---|---|
| Nothing but DNS and unrelated app traffic | Trackers and peers both go through the proxy |
| TCP to many peer addresses on arbitrary ports | Peers are not proxied |
| UDP datagrams to many addresses | DHT or UDP trackers go direct |
Other apps on the phone will produce traffic too, so run the test with as little else installed or running as possible, and compare against a capture taken with Flud closed. If UDP goes direct, look for DHT and similar options in the app and turn them off, then capture again. Confirm the exit address the gateway presents with the proxy checker.
Still open after reading every source
For the record in the review, these remain open after reading every primary source available:
- supported proxy types and authentication;
- the menu path;
- DHT, UDP tracker and uTP behaviour with a proxy set;
- whether connections the proxy cannot carry are dropped or sent directly;
- the underlying engine and the current version number.
None of these is a finding that a feature is missing. Each is a reason to rely on the capture rather than on the setting.
Checklist for a managed device
- Torrent apps permitted on managed devices by mobile policy
- Content source recorded
- Routing control named: device-level and enforced, or in-app with a capture attached
- Capture at the access point shows no peer or UDP traffic outside the proxy
- Wi-Fi-only downloading on, and seeding limited
- Exit address recorded
Flud is one of the least documented clients in this series. BiglyBT, which also publishes an Android app, though one last updated in 2023, documents its desktop proxy behaviour more fully than any other. All fifteen are compared in torrent client proxy support compared.