Flud proxy settings on Android: what the listing promises, and how to check it

Flud proxy settings rest on one sentence in its Play Store listing: “Proxy Support for trackers and peers.” That line is the only primary source we found. Which proxy types, whether it takes a password, where the setting sits in the app, what happens to DHT: no developer documentation covers any of it, and the how-to pages that turn up in search are proxy sellers’ marketing. We are a proxy seller too, so we will stick to what we can show you, and give you a way to check the rest with your own meter.

Checked against the Flud Play listing (updated 27 September 2026) in October 2026. This page is short because the facts are.

The fine print, phone edition

• Double meter on mobile data. Every proxied byte counts twice: on your carrier’s allowance and on ours. Residential is metered per GB, and so is traffic past a shared IP’s allowance, so a torrent you seed pays both ways. The metering explainer has our counting rule.
• No UDP through us. Treat our SOCKS5 as TCP only: UDP relay is unverified on our gateways, so DHT, UDP trackers and uTP will not work through us. HTTP proxies never carry UDP.
• No encryption. A proxy relays; it does not lock anything.
• Anything outside the proxy is your phone’s IP. And for copyright-type worries, the qBittorrent project’s wiki recommends a VPN. See proxy vs VPN.
• Lawful content only. Using our proxies to share files you have no right to share is not allowed; the acceptable use policy has the rules.

What is confirmed

• Android only, from the developer Delphi Softwares.
• The most-installed independent Android torrent app: 10M+ downloads and a 4.6 rating on Play.
• Play labels it “Contains ads” and “In-app purchases”; a paid Flud+ exists.
• “Proxy Support for trackers and peers”, per the listing.
• “Has option to download on WiFi only”, also per the listing. On a metered proxy, that is the most useful switch in the app.

What is not

• The menu path to the proxy setting.
• Which proxy types it offers, and whether SOCKS5 takes a password.
• What happens to DHT and UDP trackers behind the proxy.
• The torrent engine underneath, and the current version number.
• Whether Flud honours the Android Wi-Fi proxy.

On that last one: Android passes the Wi-Fi proxy to apps, and it is up to each app to use it. Our Android proxy guide covers why many apps simply ignore it.

Find it, then prove it

1. Look through Flud’s settings for the proxy section. If it offers SOCKS5, pick it, and enter the IP, port and credentials from your dashboard.
2. Switch on Wi-Fi only, so a test on mobile data cannot surprise you.
3. Download one small legal torrent: a Linux image for a single-board computer, an open dataset, an Internet Archive item.
4. Open the usage view in your dashboard. If usage rose by roughly the torrent’s size, peers went through the proxy. If it barely moved, only the trackers did, or nothing did, and every peer saw your phone’s real IP.
5. For the tracker side, a tracker-based IP check (a test torrent whose tracker echoes back the address it saw) shows which IP the tracker got.

What a phone seed costs

Say you grab a 1.5 GB Linux image on your phone and let Flud seed it to 0.5 before you swipe it away. With peers proxied, that is at least 2.25 GB through the proxy. The smallest residential order covering it is 3 GB, at $15.60. Cap the upload, stop at a ratio, and do not leave a phone seeding through a per-GB line overnight.

Verdict

On a phone, the cheap and honest route to a Linux image is your home Wi-Fi, direct, or the project’s HTTP mirror in the browser. A proxy in front of Flud is worth trying only when you need that one app on a different IP, and only after the meter test above proves the peers really go through it. If it fails the test, a desktop client with documented proxy settings is the fix; the qBittorrent guide is a good start.

Quick answers