Table of Contents
Introduction
Portable mode makes it so that all qBittorrent config files get stored and read from one "portable" directory, to make it easy to migrate and share settings between qBittorrent installations. It also makes it possible to use qBittorrent without installing to- and reading configs from system directories. This feature is most useful for Windows users in general.
NOTE: Only available for version 4.2.1 and above.
Linux
Use --profile=path/to/config/dir --relative-fastresume, where path/to/config/dir is the folder where you want your portable config to be stored or read from, if the config files already exist inside it.
Alternatively, create a folder literally named profile in the same directory as the qBittorrent executable, and just run the executable without the --profile and --relative-fastresume flags. The effect is the same as above, inside the profile directory. However, this is usually not what you want unless you are testing a build of qBittorrent you've compiled yourself in a directory that does not require elevated privileges.
NOTE: there are a bunch of caveats and pitfalls associated with portable mode and the --relative-fastresume flag in particular. Refer to the man page for more information and things to watch out for about these options. If just you want to use multiple configurations, use --profile=path/to/config/dir or --configuration=config-name-here. TODO: work on the new, complete man page is not yet finished.
Windows
- Place the qBittorrent binaries (
qbittorrent.exeandqbittorrent.pdb) anywhere you want in your PC. You can extract them from the setup.exefile using 7-zip or similar (setup files are just fancy self-extracting archives). - Create a folder called
profilein the same directory as theqbittorrent.exeandqbittorrent.pdbfiles. - Execute
qbittorrent.exe. It will initialize the needed configuration files within theprofilefolder and use them during execution.
- Note: You can copy qBittorrent configuration files from any installation, portable or not, to the matching directories inside the
profiledirectory. When started, qBittorrent will use those files if they exist. You can of course move theprofiledirectory around including to different machines, and anyqbittorrent.exestarted beside it will use those configs. Beware that some settings that deal with specific paths may not work out of the box when migrating, because paths may not be exactly the same and may not exist across machines.
General
- Installing qBittorrent
- Frequently Asked Questions (FAQ)
- qBittorrent options (current and deprecated)
- How to use qBittorrent as a tracker
- How to use portable mode
- Anonymous mode
- How to bind your vpn to prevent ip leaks
Troubleshooting
External programs
Search plugins
Themes
Translation
WebUI
WebUI API
| State | Version |
|---|---|
| Current | qBittorrent >= 5.0 |
| Previous | qBittorrent v4.1.0 - v4.6.x |
| Previous | qBittorrent v3.2.0 - v4.0.x |
| Obsolete | qBittorrent < v3.2.0 |
WebAPI clients
Alternate WebUI
Reverse proxy setup for WebUI access
WebUI HTTPS configuration
- Let's Encrypt Certificates + Caddy2 Reverse Proxy
- Let's Encrypt certificates + NGINX reverse proxy - Linux
- Let's Encrypt certificates - Linux
- Self-signed SSL certificates - Linux
Linux
- Running qBittorrent without X server (WebUI only)
- Running qBittorrent without X server (WebUI only, systemd service set up, Ubuntu 15.04 or newer)
- OpenVPN and qBittorrent without X server
Development
- Coding style
- Contributing
- How to write a search plugin
- Using VSCode for qBittorrent development
- Setup GDB with Qt pretty printers
- How to debug WebUI code
Compilation
*BSD, Linux
- Alpine Linux
- CentOS 8.x
- Debian / Ubuntu and derivatives (CMake)
- Debian / Ubuntu and derivatives (autotools/qmake)
- Docker
- FreeBSD (no GUI)
- Fully static binaries on Linux (glibc or musl)
- Raspberry Pi OS / DietPi
- Raspbian for LeMaker Banana Pro