LibreTorrent: a full-featured BitTorrent client for Android

What LibreTorrent solves on a phone

Desktop torrent clients assume a machine that stays on, a filesystem you control and a window you can leave open. Android breaks all three assumptions. LibreTorrent is an Android application that puts a full BitTorrent engine inside that environment, with the features the README lists: BitTorrent 2.0 and WebTorrent support, per-file selection, moving files while a download is running, auto-moving finished files to another folder or an external drive, sequential downloads for streaming, an Atom/RSS manager for automatic downloads, torrent creation, magnet links, and the usual transport and discovery set (DHT, PeX, encryption, LSD, UPnP, NAT-PMP, µTP).

The audience is narrow and specific. It is for people who want a torrent client on a phone, tablet or Android TV device, and who care that it is free software under GPL-3.0 rather than a closed binary. The topics on the repository say the same thing: android, free-torrent-client, open-source-torrent-client. If you only ever download on a laptop, this project is not aimed at you.

The architecture: libtorrent4j plus an Android shell

The engine is not written from scratch. The README states the app is based on libtorrent4j, a Java binding around libtorrent. Everything that makes a torrent client work, peer connections, piece picking, DHT, encryption, comes from that layer. LibreTorrent supplies the Android side: the UI, the storage handling, the background service behaviour, the settings, and the Android-specific integrations that a C++ library cannot provide.

That split explains most of the feature list. Sequential downloads for streaming are a libtorrent piece-priority strategy surfaced as a toggle. IP filtering in eMule dat and PeerGuardian formats is a libtorrent filter fed from files the app loads. Proxy support for trackers and peers is a libtorrent session setting. The repository layout matches: app/ holds the Android module, while build.gradle, gradle.properties, settings.gradle and gradlew define the Gradle build, and key.properties.example is the template for signing keys. There is no server component, no CLI and no desktop target anywhere in the top-level entries.

Installing LibreTorrent and running a first download

The README offers several distribution channels: F-Droid, OpenAPK, APKMirror, Google Play, Aptoide, and a direct APK mirror. The F-Droid badge links to the package org.proninyaroslav.libretorrent. Pick the channel before you pick the build, because the README carries a warning: on Android 12 and later, the Google Play version does not have permission to access all files, and the README tells you to use another version, F-Droid or the direct APK, instead.

If you take the direct APK, the README gives a SHA-256 fingerprint certificate to check it against:

B0:88:D4:72:A9:80:18:64:5C:DE:EF:8E:93:33:8D:58:B3:F2:38:92:18:7F:DF:63:F7:39:58:38:1E:27:E5:83

Compare that string with the certificate of the APK you downloaded before installing. It is the only integrity check the README documents.

Once installed, the first real use is a magnet link or a .torrent file. The README lists HTTP\S and magnet links as supported inputs, and per-file selection as a download option. So the flow is: hand the app a magnet link, let it resolve metadata, then choose which files to fetch before starting. For a streamable file, the sequential download option changes piece order so playback can begin before the whole torrent finishes. For unattended use, the Atom/RSS manager plus auto-downloading is the feature to configure, and scheduling lets you restrict when transfers run.

Building from source is a different path. The repository is a Gradle project with gradlew and gradlew.bat at the root and key.properties.example as the signing template, but the README does not document a build procedure, so treat source builds as something you work out from the repository rather than follow from instructions.

Where LibreTorrent is the wrong tool

The Google Play storage restriction is the clearest failure mode, and it is documented by the project itself rather than discovered by users. On Android 12 and later, the Play build cannot access all files. If your workflow depends on writing finished torrents to an arbitrary folder or an external drive, the Play build is the wrong one and the README says so.

Two other boundaries are structural. There is no desktop client: the related searches asking for LibreTorrent on PC or Windows have no answer inside this repository, which contains an Android app module and nothing else. And there is no iOS target either, so the iOS searches are equally unanswerable here. A third boundary is less obvious. A phone is a poor seedbox. Android kills background processes, throttles network activity and manages storage aggressively. The app has scheduling and battery-related settings, but a device that sleeps is not a machine that seeds around the clock. If your requirement is long-term seeding or a remote-accessible instance, a desktop client or a headless server is the correct answer, and LibreTorrent is not.

LibreTorrent against qBittorrent, BiglyBT and Flud

The comparison that matters is not feature checklists but where the client runs. qBittorrent is a desktop application; it has no Android build in this material, and LibreTorrent has no desktop build. Choosing between them is choosing a platform, not a feature set. BiglyBT is a Java torrent client with an Android presence, so it is the closer comparison in platform terms, but the README here does not describe BiglyBT's internals and this material contains nothing about how the two differ in engine design. Flud is another Android client, and again the only thing this material establishes is that both are Android torrent clients; nothing here compares their engines or storage handling.

What can be said from the repository itself is narrower and more useful. LibreTorrent is GPL-3.0, its engine is libtorrent4j, and it exposes the libtorrent feature set (DHT, PeX, encryption, LSD, UPnP, NAT-PMP, µTP, IP filtering, proxy) alongside Android concerns like RSS auto-downloading, scheduling, streaming and Android TV. If your selection criteria are licence and engine lineage, that is the concrete basis for a decision. If they are UI preference or download speed, this material gives you nothing to compare, and you should test the candidates yourself on your own device.

Maintenance, releases and the GPL-3.0 obligation

The repository is not archived, and the last push was on 2026-07-24. The most recent release listed is 4.1.1, dated 2026-07-24, following 4.1 on 2026-07-14 and 4.0.1 on 2025-08-12. That pattern shows a 4.0 line that sat for about a year before a 4.1 cycle arrived within ten days of the previous release. Upgrade cost for a user is low: the app installs from an app store or an APK, and the README documents no migration steps, no configuration format to convert and no breaking change between these releases. The NEWS.md file exists at the repository root if you want release-by-release detail, but the README does not summarise it.

The licence is GPL-3.0, and the README states it plainly: LibreTorrent is free software, you may redistribute and modify it under the terms of the GNU General Public License, version 3 or later, and it comes with no warranty. For a user, that means no cost and no warranty. For anyone redistributing a modified build, the copyleft terms apply to the derivative work, including the requirement to provide the source. This is a description of the licence text, not legal advice; read LICENSE.md and the GPL itself if you plan to ship a modified version.

Editorial conclusion

Adopt LibreTorrent if you want a copyleft Android torrent client with BitTorrent 2.0, WebTorrent, RSS auto-downloading and Android TV support, and you accept that the Google Play build cannot reach all files on Android 12 and later. If you need a desktop client, a headless seedbox or an iOS app, look elsewhere: the repository contains only an Android app. Before installing, verify the SHA-256 certificate fingerprint B0:88:D4:72:A9:80:18:64:5C:DE:EF:8E:93:33:8D:58:B3:F2:38:92:18:7F:DF:63:F7:39:58:38:1E:27:E5:83 against the direct APK you download, and check whether the build you pick can access the storage location you intend to use.

Frequently asked questions

Official sources

1. License: GPL-3.0
2. Project website
3. proninyaroslav/libretorrent on GitHub
4. README
5. Releases