qBitX is a native macOS remote client for qBittorrent. It connects to a remote qBittorrent WebUI/API server and does not run or bundle qBittorrent locally.
The goal is to provide a macOS-first experience for managing torrents on a remote server, with local path mapping so downloaded content can be opened from Finder when the remote download directory is mounted or synced locally.
qBitX is in early development. Core remote-control workflows are implemented, but the app is not yet a full replacement for qBittorrent WebUI or other mature remote clients.
- Connect to a remote qBittorrent WebUI instance.
- View torrents with native macOS sidebar filters.
- Combine status, category, and tag filters.
- Switch between a three-column macOS layout and a WebUI-style table layout.
- Sort torrents by common fields in table/list views.
- Add torrents from magnet/URL input or local
.torrentfiles. - Open
.torrentfiles with qBitX from macOS. - Drag and drop
.torrentfiles into the app. - Pause, resume, delete, recheck, and reannounce torrents.
- View torrent details and file lists.
- Configure remote-to-local path mappings.
- Open or reveal mapped local files in Finder.
- Edit a subset of qBittorrent server preferences through the remote API.
- Localized UI for English, Simplified Chinese, and Traditional Chinese.
- macOS 26.3 or later, as currently configured in the Xcode project.
- Xcode 26.4 or later, as currently used by the project.
- A reachable qBittorrent server with WebUI enabled.
On the remote qBittorrent host:
- Enable WebUI in qBittorrent settings.
- Set the WebUI address, port, username, and password.
- Ensure the macOS machine running qBitX can reach that host and port.
- If you use HTTPS or a reverse proxy, use the externally reachable WebUI URL in qBitX.
qBitX uses qBittorrent Web API v2 endpoints.
Remote servers often save files under paths such as:
/downloads/movies
If that remote directory is mounted locally, for example at:
/Volumes/Media/movies
add a local path mapping in qBitX:
Remote path: /downloads/movies
Local path: /Volumes/Media/movies
After that, qBitX can open or reveal downloaded files from the torrent file list.
Open the project in Xcode:
xed qBitX.xcodeprojSelect the qBitX scheme and build/run.
From the command line:
xcodebuild -project qBitX.xcodeproj -scheme qBitX -destination 'platform=macOS' buildRun tests:
xcodebuild -project qBitX.xcodeproj -scheme qBitX -destination 'platform=macOS' testBefore publishing binaries, configure your own signing identity, bundle identifier, notarization workflow, and release distribution channel. This repository is prepared for source publication; packaged app releases still need project-specific signing and distribution setup.
- qBitX is a remote client. It does not download torrent payload data itself unless you explicitly open local mapped files.
- Server profile data is currently stored in local app preferences. Treat this as development-stage behavior.
- Prefer HTTPS or a trusted private network when connecting to a remote qBittorrent WebUI.
- Do not publish logs, screenshots, or sample configuration that contain real WebUI credentials, hostnames, cookies, or private paths.
- Broader qBittorrent preferences coverage.
- Tracker, peer, and content-priority management.
- Better multi-selection operations.
- More complete add-torrent options.
- Keychain storage for server credentials.
- Packaging, signing, and release automation.
qBitX is free software licensed under the GNU General Public License v3.0 or later. See LICENSE.
qBitX is an independent project and is not affiliated with the qBittorrent project.