Open-source project
XITRIX/iTorrent avatar
XITRIX/iTorrent

No official way to install it outside the EU, and analytics records your provider's country

Torrent client for iOS 16+

3,381 stars312 forksSwiftMIT

At a glance

What is it?
iTorrent is a torrent client for iOS with a built-in player, Files app integration and a WebDAV server, distributed through five different channels because the platform will not host it. Its installation badges route through a third-party redirect service, its support warning rules out every sideload method but two, and its own privacy section lists what it collects, starting with the country of your internet provider.
Who is it for?
iTorrent suits someone on iOS who wants a torrent client with a real player and system file integration and is willing to install it outside the official store, because there is no version of this app that Apple hosts. Two things to settle before you do.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository received new commits within the last day.
What is it written in?
Mainly Swift, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • XITRIX/iTorrent3,381 ★ · +119
Star history
Repository2026-09-242026-11-15
XITRIX/iTorrent3.3k3.4k

119 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Five installation channels, and one of them exists only in the EU

The top of this readme is five download badges before a single word of description, and the fifth of them is a straight link to the release artefacts. The other four are all ways of getting around the platform.

Then there is a section with the most honest heading in the document: installation for EU citizens. It explains that because the platform allows third-party app stores in the EU and a few other countries, the app is available through the alternate store, with its own badge and its own manifest file kept separate from the general one.

And then the sentence that explains the other four badges: for everyone else, unfortunately, there is no official way to install the app, so you will need to sideload it using one of two named tools, with links at the top if you already have one of them installed on your phone.

The fifth badge is for a jailbroken device and points at an installation-manifest scheme rather than a file, and the last is the release artefacts themselves, which implies building and signing it.

So the readme leads with a distribution problem rather than a feature list, which is the correct order of information for this kind of app.

Four of the five buttons route through someone else's redirect service

There is a detail in those badge links that is worth reading before you tap one.

The alternate-store badge, the sideloading-store badge and the jailbreak badge all point at a redirect service hosted on somebody else's account, with the real destination passed along as a parameter. Only the release link goes directly to this project's own hosting.

The reason is in the schemes themselves: alternate-store installs, sideloading-store installs and installation manifests are all custom URL schemes, and some contexts will not launch one directly from a link. So the author routes through a page that redirects.

The practical consequence is that four of the five ways to install this app involve a third-party host deciding where you land, and that decision is made at click time rather than baked into the readme. Anyone reviewing an install path for a sideloaded application should weigh that the same way they would weigh any other link they did not write, and the release artefacts remain the one channel with nothing in between.

One warning excludes every sideload method the author did not name

Under the installation section there is a warning callout, and it is unusually firm.

It says the only officially supported ways to sideload the app are the two named tools. If you sideload it any other way, there are no guarantees it will work as intended, and no technical support will be provided.

That is the right thing to say and an unusual thing to find. A sideloaded app that is installed through an unsupported path, or through a tool that has since changed its manifest format, will often fail in ways that look like bugs in the app. Saying so up front converts a support burden into a documented boundary.

It also bounds what the project can accept as an issue. If the failure mode depends on how you installed it, and only two installations are supported, then the install path is part of the bug report whether the author says so or not.

Everything else on this page is written in the same register: the feature list ends with a placeholder, the library credits name the author's own forks, and the privacy section lists fields rather than summarising them.

The last item in the feature list is three question marks

The feature list is a bullet list of fifteen real capabilities, and the sixteenth entry is three question marks.

It is the last line before the localisation section, and it is clearly deliberate. There is a joke in it, but it is also a small editorial decision that says more than a feature list normally would: this is a hobby project that knows exactly what it is.

The fifteen above it are not hobby-scale though. Background downloads, a lock-screen progress indicator on the system's live activity and its dynamic island, a built-in player with AirPlay and picture in picture, and the one that tells you what kind of project this is: sequential download, so you can start watching a film while it is still loading. Progressive playback of an incomplete download is the feature a desktop client made on a phone had to have.

The rest is system integration rather than invention. Adding a torrent from the share sheet, adding a magnet link straight from the browser, storing files where the Files app can see them, sharing out of the app, a notification on completion, choosing which files inside a torrent to fetch, an RSS reader, and a WebDAV server, which means the phone can serve files to your network over that protocol.

The library list is two lists, and three of the ten entries are the author's own forks

There are ten libraries credited, and the list is worth reading for who is behind each one.

The BitTorrent engine is the well-known C++ library. The cryptography library is a fork. The player binding is a third-party wrapper. Then three entries are the author's own projects: an architecture library, a wrapper library, and an HTTP server. After those come a small XML parsing library and two text rendering helpers.

So a third of the credited libraries are this developer's own code, and one of them is a fork of an HTTP server, which is the dependency behind the WebDAV feature. The analytics SDK is the tenth and the only one from a large commercial platform.

That fork of the cryptography library is not a stylistic choice on this platform, where you cannot link the system copy, and it is the reason the app can make network requests at all. But it does mean the security of the client rests on a fork that one person maintains, which is the trade every app making that choice makes and that a readme crediting the fork by its own name makes visible.

The list also tells you what the app is written in: an Xcode project, a workspace beside it, and three app targets.

Analytics collects the country of your internet provider

The readme has an important information section, and the first field in it is the one that stops you.

It says the app uses an analytics product and collects two things from your device: the country of your internet provider, and the time of the app's working session. It then says all of this presents as statistics and cannot be used to get someone's personal information.

Country of your internet provider is not location, it is the country the network points appear to originate from. It is a coarse location derived from a network address, and it is the closest thing to a location field in the list. There is no visible reason a torrent client needs it.

The reassurances are also worth reading carefully. The claim that the data cannot be used to identify someone is a property of the analytics platform rather than of the app, and the section links to that platform's own documentation rather than to anything specific about this app.

What is not there is as important as what is: no way to turn analytics off, no switch in the settings list, and no link to a privacy policy. For an application whose entire download history is sensitive, that gap is the part to raise with the author.

Crash reports carry device orientation and free memory, and the same gap applies

The second half of that section covers crash reporting, with six fields listed.

They are the device model, the device orientation, the free space in memory and storage, the system version, the time of the crash, and a detailed log of the thread where the problem occurred.

Each is defensible on its own. A crash log without the thread's state is much harder to read, and orientation and free space do explain a lot of crashes. Taken together they are a device fingerprint with a timestamp: which model, which way it was being held, how much memory was free, and what the system was running.

The section ends with the same reassurance and the same link to the platform's own documentation, and again there is no mention of a setting to disable it.

So the privacy position of this application is: two analytics fields, six crash fields, no documented opt-out, and two paragraphs pointing at somebody else's documentation. That is not a hidden practice, which is worth saying, because the alternative in this category is usually worse. It is also not a complete answer.

Three app targets and a directory called Submodules

The repository layout tells you what this project is before the readme does.

There is the main application directory, a second directory for the television variant, and a third for the progress widget, which is the target that produces the lock-screen and dynamic island indicator. Three targets from one project.

Beside them sit both an Xcode project and an Xcode workspace, and the workspace exists because the dependencies arrive as submodules rather than through a package manager. The submodule directory is named for exactly that, and the module file is committed at the root.

So the dependency story is git submodules checked into a directory, which is why the workspace is needed, which is why three of the credited libraries are forks, and why the readme credits them individually instead of listing a resolved package manifest.

The last thing the tree tells you is the release scheme. Every tag carries the application version and then a build number after a dash, so the newest is the second point two of the second line, build one. That is the convention platforms expect from a binary you upload, and it is why the release artefacts are the most direct install route available.

Editorial conclusion

iTorrent suits someone on iOS who wants a torrent client with a real player and system file integration and is willing to install it outside the official store, because there is no version of this app that Apple hosts. Two things to settle before you do. Decide how you will install, because the project's own warning says it will not support a method other than the two named sideloading apps, and a third-party redirect sits in that path. Then read the analytics section closely and decide about it yourself, since the list includes the country of your internet provider for a client that has no use for it, and the readme offers no way to turn it off. The feature set itself is unremarkable and complete, including sequential playback and a WebDAV server on your phone.

Frequently asked questions

What does iTorrent do?

It is an ordinary torrent client for iOS with Files app integration: background downloads, a lock-screen progress widget, a built-in player with AirPlay and picture in picture that can begin playing before a download finishes, adding torrents and magnet links from the share sheet, choosing which files to fetch, an RSS reader, and a WebDAV server that serves files from the phone.

How do I install iTorrent on my iOS device?

In the EU and a few other countries it is on the alternate app store, with its own badge on the page. Everywhere else the readme says there is no official way and you must already have one of two sideloading apps installed; there are also buttons for a jailbreak installation manifest and for the release artefacts.

Is iTorrent safe to use?

The repository does not answer that. It does state what the app's analytics and crash reporting collect: the country of your internet provider and session times, plus on a crash the device model, orientation, free memory and storage, the system version, the time, and a thread's log. No opt-out is documented.

Is uTorrent no longer safe?

Nothing in this repository discusses other torrent clients. It is one application, and it makes no comparison with anything: it names no alternative and claims nothing about competitors.

itorrent alternative

This repository names none. It describes its own app, a torrent client with a built-in player, Files app integration, a WebDAV server and an RSS reader, distributed outside the official store through an alternate store, two sideloading apps, or a jailbreak manifest.

Official sources

  1. Issues
  2. License: MIT
  3. README
  4. Releases
  5. XITRIX/iTorrent on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/xitrix-itorrent.svg)](https://hysenlabs.com/projects/xitrix-itorrent)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/xitrix-itorrent.svg)](https://hysenlabs.com/projects/xitrix-itorrent)

Was this useful?