Skip to content

Feature request: Per-torrent download/upload speed limits #83

@j94nnzhlejt6

Description

@j94nnzhlejt6

Is your feature request related to a problem? Please describe.

Yes. I use qbitwebui as my main qBittorrent Web UI replacement, but I couldn’t find a way to set download/upload speed limits for a specific torrent from the torrent list, context menu, or torrent details view.

This is inconvenient when one large torrent saturates the connection or storage/NAS bandwidth and I want to throttle only that torrent without changing the global speed limits for the whole qBittorrent instance.

qBittorrent itself supports per-torrent limits via the Web API (dl_limit, up_limit, torrents/setDownloadLimit, torrents/setUploadLimit), so it would be useful to expose this in qbitwebui as well.

Describe the solution you'd like

I would like to be able to set per-torrent download and upload speed limits directly from qbitwebui.

Possible UI options:

  • Add a "Speed limits" / "Set speed limits" action to the torrent context menu.
  • Add editable Download limit and Upload limit fields in the torrent details panel.
  • Support common units like KiB/s and MiB/s.
  • Allow 0 or an "Unlimited" option to clear the limit.
  • Ideally support setting limits for one selected torrent and multiple selected torrents.

Example flow:

  1. Right-click a torrent.
  2. Choose "Speed limits".
  3. Enter:
    • Download limit: 10 MiB/s
    • Upload limit: 1 MiB/s
  4. Save.
  5. qbitwebui calls the qBittorrent API for the selected torrent hash(es).

It would also be useful if the torrent list could optionally show the current per-torrent dl_limit and up_limit values as columns.

Describe alternatives you've considered

Currently I can work around this by:

  • Opening the default qBittorrent Web UI only when I need to set per-torrent speed limits.
  • Calling the qBittorrent Web API manually with torrents/setDownloadLimit and torrents/setUploadLimit.
  • Using global speed limits instead.

These workarounds are inconvenient because they require leaving qbitwebui or applying a global limit when I only want to throttle a single torrent.

Additional context

My setup:

  • qbitwebui running in Docker
  • qBittorrent-nox running separately
  • qBittorrent version: 5.1.0
  • qbitwebui used as the main UI

This feature would make qbitwebui more complete as a qBittorrent Web UI replacement, especially for users who manage large downloads and need to throttle individual torrents.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions