BitTorrent proxy settings, meaning the settings in the BitTorrent company's own desktop client rather than the protocol in general, are documented in one help article. It is short and unambiguous about the part it covers: the menu path, the four proxy types, and that "Peer communication proxying is not supported with standard HTTP proxies, and UDP proxying is only supported with SOCKS5." Everything else a reviewer would want to know about this client and a proxy is undocumented, and this page says so rather than filling the gap from older guides.
This article is deliberately shorter than our guides to clients with source code or fuller documentation. There is less that can be stated as fact.
Which BitTorrent this is about
The name is shared by the protocol and by a product line from the company that created it. This page is about the product: BitTorrent Classic for Windows, BitTorrent Web for Windows and Mac, and an Android app. The client is proprietary. Its help centre has separate installation articles for Classic and Web.
The last public desktop release note is "BitTorrent 7.11.0 For Windows (build 46555) November 22, 2022". Newer build numbers are not published, so we do not quote any. The Android app is updated regularly.
Before anyone opens the settings
On a managed machine, three things should be settled first, and none of them is a proxy question:
- Whether BitTorrent is permitted on this network, by whoever owns the egress policy.
- What is being distributed. A distribution's install image, an open-source release, a public-domain archive item, a research dataset. Write the source down.
- Whether this client passes software intake. It is proprietary and ad-supported in its free tier. The vendor's own help centre says antivirus tools may flag it "due to 3rd party offers we make in the installation process. Note that these offers are fully optional." Someone should decline those offers deliberately, and record that they did.
For the record, ProxyForge allows peer-to-peer traffic for lawful content on its residential exits and on dedicated, unmetered ISP and datacenter addresses. Using a ProxyForge exit to share material without the right to distribute it is not permitted under the acceptable use policy.
What the vendor documents
The path is Options > Preferences > Connection, where Proxy Server Type offers SOCKS4, SOCKS5, HTTP Connect and HTTP. The text is identical to the µTorrent help article, which is useful: one review covers both clients' documented behaviour.
Read together with how the protocols work, that gives a short table:
| Type | Peer connections | UDP (DHT, UDP trackers, uTP) |
|---|---|---|
| HTTP | Not proxied, per the vendor | Not proxied |
| HTTP Connect | Tunnelled as TCP, where the proxy allows the port | Not proxied |
| SOCKS4 | Tunnelled as TCP | Not proxied |
| SOCKS5 | Tunnelled as TCP | Client can relay it, if the proxy server supports UDP |
Two things narrow that table on our network. ProxyForge gateways accept HTTP, HTTPS and SOCKS5, so SOCKS4 does not apply. And our SOCKS5 endpoints should be treated as TCP only, since UDP relay through them has not been verified; DHT, UDP trackers and uTP will not work through our proxy even though the client supports relaying them. The protocol background is in SOCKS5 vs HTTP proxy.
The costs and limits that apply anyway
Whatever the client, a metered proxy that carries peers carries the whole file in, and the whole file out again for every copy you seed. A 4 GB image at a seeding ratio of 1.0 is at least 8 GB through the gateway, plus overhead and discarded pieces. Our definition of a metered gigabyte is published. A proxy also encrypts nothing, and anything the client sends outside it shows the machine's real address.
If the goal is the file rather than the swarm, the project's HTTPS mirror is cheaper and simpler: one transfer, a published checksum, no upload. If the goal is privacy from rightsholders, a proxy is the wrong tool, and client projects say as much; qBittorrent's wiki points those users to a VPN.
What we could not confirm
These are gaps in the primary sources, not findings that the features are absent:
- Authentication. The help article does not mention a username or password field.
- Per-traffic switches. Whether trackers and peers can be proxied separately.
- Fallback. Whether connections the proxy cannot carry, UDP in particular, are dropped or sent directly.
- BitTorrent Web. Whether it has proxy settings at all.
- Current pricing of the ad-free tier. The help centre and the related µTorrent compare page disagree, so check the vendor's site on the day.
The fallback question is the one a reviewer cannot sign without. It can be answered on your own machine in a few minutes.
A ten-minute check on Windows
Start the client with the proxy configured and a lawful torrent running. Open Resource Monitor, go to the Network tab, tick the BitTorrent process, and read the TCP Connections list. Every remote address should be the gateway. Then run a capture with Wireshark on the same machine and hide the proxy connection with a display filter:
not (ip.addr == PROXY_IP and tcp.port == PROXY_PORT)
What remains is traffic the proxy did not carry. Datagrams to many different remote addresses are DHT or UDP trackers going direct; turn those features off in the client and run the capture again. Record the exit address the gateway presents with the proxy checker.
Checklist for the change record
- Product and edition recorded, with the 2022 release-notes gap noted
- Installer offers declined, by name of the person who installed it
- BitTorrent approved on this network; content source recorded
- Proxy Server Type SOCKS5, or HTTP Connect with a tested port
- Authentication method confirmed on the build, or IP allowlisting used
- Capture attached, showing nothing outside the proxy endpoint
- Seeding limits set; expected gigabytes include upload
How this client sits next to the other fourteen is in torrent client proxy support compared.