starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

Prevent repeating moving partial completed torrents back and forth #13693

New issue

Open

opened 2026-02-22 00:13:44 -05:00 by deekerman · 6 comments

deekerman commented

2026-02-22 00:13:44 -05:00

Owner

Originally created by @Snake883 on GitHub (Aug 3, 2022).

Suggestion

Option A:
Do not move completed files to incomplete folder.
This will mean some of the files will be stored in the completed folder, and others in the incomplete folder.

Option B:
Allow for disabling the "keep incomplete torrents in" option per torrent.

Use case

When a torrent is partially complete (not all files are selected to be downloaded), it moves the entire contents from the incomplete folder to the completed folder.

The example I have is when downloading large multi-season TV episodes. I might not select to download all files/seasons/episodes all at once (because I have bandwidth allotment). For example, I might just download the first season from the torrent, and next month download the next season from the torrent.

When the first season is complete, QBT will move the torrent objects to the "completed" folder/drive. But when I download the next season, it moves all the object from "completed" back to "incomplete".

I have my incomplete torrents on a SSD drive, and my completed torrents on a parity drive. Moving back and forth is not ideal.

Extra info/examples/attachments

qBittorrent v4.4.3.1 Web UI

Originally created by @Snake883 on GitHub (Aug 3, 2022). ### Suggestion **Option A:** Do not move completed files to incomplete folder. This will mean some of the files will be stored in the completed folder, and others in the incomplete folder. **Option B:** Allow for disabling the "keep incomplete torrents in" option per torrent. ### Use case When a torrent is partially complete (not all files are selected to be downloaded), it moves the entire contents from the incomplete folder to the completed folder. The example I have is when downloading large multi-season TV episodes. I might not select to download all files/seasons/episodes all at once (because I have bandwidth allotment). For example, I might just download the first season from the torrent, and next month download the next season from the torrent. When the first season is complete, QBT will move the torrent objects to the "completed" folder/drive. But when I download the next season, it moves all the object from "completed" back to "incomplete". I have my incomplete torrents on a SSD drive, and my completed torrents on a parity drive. Moving back and forth is not ideal. ### Extra info/examples/attachments qBittorrent v4.4.3.1 Web UI

deekerman added the

Feature request

WebUI

Temp folder

labels

2026-02-22 00:13:44 -05:00

deekerman commented

2026-02-22 00:13:51 -05:00

Author

Owner

@thalieht commented on GitHub (Aug 3, 2022):

Option B:
Allow for disabling the "keep incomplete torrents in" option per torrent.

Already possible.

@thalieht commented on GitHub (Aug 3, 2022): >Option B: Allow for disabling the "keep incomplete torrents in" option per torrent. Already possible.

deekerman commented

2026-02-22 00:13:54 -05:00

Author

Owner

@Snake883 commented on GitHub (Aug 3, 2022):

Option B:
Allow for disabling the "keep incomplete torrents in" option per torrent.

Already possible.

I need to mention that I'm using the WebUI.

@Snake883 commented on GitHub (Aug 3, 2022): > Option B: > Allow for disabling the "keep incomplete torrents in" option per torrent. > > > Already possible. I need to mention that I'm using the WebUI.

deekerman commented

2026-02-22 00:13:54 -05:00

Author

Owner

@ghost commented on GitHub (Aug 4, 2022):

I guess temp folder feature is not so intelligent like people expect it to be hence so many issues related to it.

@ghost commented on GitHub (Aug 4, 2022): I guess temp folder feature is not so intelligent like people expect it to be hence so many issues related to it.

deekerman commented

2026-02-22 00:13:54 -05:00

Author

Owner

@Snake883 commented on GitHub (Aug 4, 2022):

Workaround:
Don't use the "incomplete" feature. Instead use "categories" with the storage location, one category for incomplete. Manually switch category for the storage location.

@Snake883 commented on GitHub (Aug 4, 2022): Workaround: Don't use the "incomplete" feature. Instead use "categories" with the storage location, one category for incomplete. Manually switch category for the storage location.

deekerman commented

2026-02-22 00:13:55 -05:00

Author

Owner

@Torbins commented on GitHub (Oct 23, 2023):

I also have this problem. I have slow HDD for torrents and a very fast SSD for temp files. Also I have fast internet and often choose 4K quality for a new series, such as Ashoka. In my case managing files on HDD often takes even more time, than download itself. Especially when new episodes arrive every week, and you have to download updated torrent file each time. After torrent file update all existing files are moved to temp folder, new episode is downloaded, and then everything is moving back to HDD. It's a huge time waste.

@Torbins commented on GitHub (Oct 23, 2023): I also have this problem. I have slow HDD for torrents and a very fast SSD for temp files. Also I have fast internet and often choose 4K quality for a new series, such as Ashoka. In my case managing files on HDD often takes even more time, than download itself. Especially when new episodes arrive every week, and you have to download updated torrent file each time. After torrent file update all existing files are moved to temp folder, new episode is downloaded, and then everything is moving back to HDD. It's a huge time waste.

deekerman commented

2026-02-22 00:13:55 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 24, 2025):

ANNOUNCEMENT!

For anybody coming across this "Feature Request" & would like/love to see a potential implementation in the future!
Here are some options available to you:

Please select/click the 👍 &/or ❤ reactions in the original/opening post of this ticket.
Please feel free (If you have the "skillset") to create a "Pull Request" implementing what's being requested in this ticket.
(new/existing contributors/developers are always welcome)

DO:

Provide constructive feedback.
Display how other projects implemented same/similar etc.

DO NOT:

Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s).
(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)

@xavier2k6 commented on GitHub (May 24, 2025): ## ANNOUNCEMENT! For anybody coming across this **_"Feature Request"_** & would like/love to see a potential implementation in the future! **Here are some options available to you:** 1. Please select/click the 👍 **&/or** ❤ `reactions` in the original/opening post of this ticket. 2. Please feel free _(If you have the "skillset")_ to create a **_"Pull Request"_** implementing what's being requested in this ticket. **_(new/existing contributors/developers are always welcome)_** ____ **DO:** * Provide constructive feedback. * Display how other projects implemented same/similar etc. **DO NOT:** * Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s). **(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)**