starred/qBittorrent

Fork 0

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

"Move when completed" option #12349

New issue

Closed

opened 2026-02-21 22:37:52 -05:00 by deekerman · 11 comments

deekerman commented

2026-02-21 22:37:52 -05:00

Owner

Originally created by @BenMcLean on GitHub (Aug 19, 2021).

Feature request

Checklist

I have read the feature request section in the contributing guidelines, so I know how to submit a good feature request with the required information
I have verified that the feature I am requesting is not available in the latest version
(optional but recommended) I have verified that the feature I am requesting is not available in the latest CI build
I have checked the frequent/common issues list and searched the issue tracker for similar feature requests (including closed ones) to avoid posting a duplicate
This request is not a support request or question, both of which are better suited for either the discussions section, forum, or subreddit. The wiki did not contain a suitable solution either

Description

Suggestion

In addition to the existing "Set location..." option, it would be nice to have a "Move when completed" option for each torrent.

Use case

Helps keep completed torrents separate from those still in progress.

Extra info/examples/attachments

The idea is that this feature would be the same as if you clicked "Set location..." on the torrent right at the moment it was completed, only you're able to set it up ahead of time and for each individual torrent separately or after having selected multiple torrents just like how "Set location..." works.

Originally created by @BenMcLean on GitHub (Aug 19, 2021). # Feature request  ## Checklist  - [x] I have read the **feature request section** in the [contributing guidelines](https://github.com/qbittorrent/qBittorrent/blob/master/CONTRIBUTING.md), so I know how to submit a good feature request with the required information - [x] I have verified that the **feature** I am requesting is **not available** in the **[latest version](https://www.qbittorrent.org/download.php)** - [ ] (optional but recommended) I have verified that the **feature** I am requesting is **not available** in the **[latest CI build](https://github.com/qbittorrent/qBittorrent/actions/workflows/ci.yaml?query=branch%3Amaster+event%3Apush)** - [x] I have **checked the [frequent/common issues list](https://github.com/qbittorrent/qBittorrent/projects/2)** and **searched** the issue tracker for similar feature requests (including closed ones) **to avoid posting a duplicate** - [x] This request is **not a support request or question**, both of which are better suited for either the [discussions section](https://github.com/qbittorrent/qBittorrent/discussions), [forum](https://qbforums.shiki.hu/), or [subreddit](https://www.reddit.com/r/qBittorrent/). The [wiki](https://github.com/qbittorrent/qBittorrent/wiki) did not contain a suitable solution either ## Description  ### Suggestion In addition to the existing "Set location..." option, it would be nice to have a "Move when completed" option for each torrent. ### Use case Helps keep completed torrents separate from those still in progress. ### Extra info/examples/attachments The idea is that this feature would be the same as if you clicked "Set location..." on the torrent right at the moment it was completed, only you're able to set it up ahead of time and for each individual torrent separately or after having selected multiple torrents just like how "Set location..." works.

deekerman

2026-02-21 22:37:52 -05:00

closed this issue
added the
Feature request
label

deekerman commented

2026-02-21 22:38:09 -05:00

Author

Owner

@thalieht commented on GitHub (Aug 19, 2021):

It already exists and it's called "Keep incomplete torrents in:"

@thalieht commented on GitHub (Aug 19, 2021): It already exists and it's called "Keep incomplete torrents in:"

deekerman commented

2026-02-21 22:38:09 -05:00

Author

Owner

@BenMcLean commented on GitHub (Aug 19, 2021):

It already exists and it's called "Keep incomplete torrents in:"

As I understand it, that feature is only one setting for all torrents. This feature request is to make it so it's configurable for each individual torrent.

I may not be explaining this very well.

@BenMcLean commented on GitHub (Aug 19, 2021): > It already exists and it's called "Keep incomplete torrents in:" As I understand it, that feature is only one setting for all torrents. This feature request is to make it so it's configurable for each individual torrent. I may not be explaining this very well.

deekerman commented

2026-02-21 22:38:10 -05:00

Author

Owner

@shama84 commented on GitHub (Aug 20, 2021):

maybe another view: "set location" vs "completed". Drop my comment if not relevant regarding your request
This feature is useful to have 2 locations: an incomplete and completed one. This is not always necessary: certainly good with a high bandwidth connection and SSD as primary storage and regular data disk as final destination. But if your data disk can handle the download it may be more interesting to not move completed (copy is resource intensive) but well simply relocate on the same drive (cost no performance at all)

An example: a computer with C (OS) and D (torrent data). Consider D as good enough to handle the connection speed is more interesting to have D:\download as default location an use the "set location" right-click option to put the torrent in its final folder. If the "download" folder and the final folder reside on the same drive, no copy or performance cost meaning you can set the location directly when adding the torrent or during/after the download with no performance hit.

@shama84 commented on GitHub (Aug 20, 2021): _maybe another view: "set location" vs "completed". Drop my comment if not relevant regarding your request_ This feature is useful to have 2 locations: an incomplete and completed one. This is not always necessary: certainly good with a high bandwidth connection and SSD as primary storage and regular data disk as final destination. But if your data disk can handle the download it may be more interesting to not move completed (copy is resource intensive) but well simply relocate on the same drive (cost no performance at all) An example: a computer with C (OS) and D (torrent data). Consider D as good enough to handle the connection speed is more interesting to have D:\download as default location an use the "set location" right-click option to put the torrent in its final folder. If the "download" folder and the final folder reside on the same drive, no copy or performance cost meaning you can set the location directly when adding the torrent or during/after the download with no performance hit.

deekerman commented

2026-02-21 22:38:10 -05:00

Author

Owner

@BenMcLean commented on GitHub (Aug 20, 2021):

But if your data disk can handle the download it may be more interesting to not move completed (copy is resource intensive) but well simply relocate on the same drive (cost no performance at all)

That's actually what I'm trying to do. Move from an incomplete folder on my SSD to a completed folder on the same drive. I have noticed that sometimes qbittorrent is doing a full copy when relocating on the same drive and uhh ... when on the same drive, it should just be moving, not copying. Gonna wear out people's drives doing that

@BenMcLean commented on GitHub (Aug 20, 2021): > But if your data disk can handle the download it may be more interesting to not move completed (copy is resource intensive) but well simply relocate on the same drive (cost no performance at all) That's actually what I'm trying to do. Move from an incomplete folder on my SSD to a completed folder on the same drive. I have noticed that sometimes qbittorrent is doing a full copy when relocating on the same drive and uhh ... when on the same drive, it should just be moving, not copying. Gonna wear out people's drives doing that

deekerman commented

2026-02-21 22:38:10 -05:00

Author

Owner

@shama84 commented on GitHub (Aug 20, 2021):

As you are on SSD, double check the option "Pre-allocate disk space for all files" is not checked.
Then simply define "Default Save Path" on the SSD and use the "set location" option to move torrent on the same drive.
I reserve the SSD for caching/OS and the regular HDD for torrent target. Up to now the move are instant, so no full copy made.
It should only occur if the drive is different indeed

@shama84 commented on GitHub (Aug 20, 2021): As you are on SSD, double check the option "Pre-allocate disk space for all files" is not checked. Then simply define "Default Save Path" on the SSD and use the "set location" option to move torrent on the same drive. I reserve the SSD for caching/OS and the regular HDD for torrent target. Up to now the move are instant, so no full copy made. It should only occur if the drive is different indeed

deekerman commented

2026-02-21 22:38:10 -05:00

Author

Owner

@BenMcLean commented on GitHub (Aug 20, 2021):

As you are on SSD, double check the option "Pre-allocate disk space for all files" is not checked.
Then simply define "Default Save Path" on the SSD and use the "set location" option to move torrent on the same drive.
I reserve the SSD for caching/OS and the regular HDD for torrent target. Up to now the move are instant, so no full copy made.
It should only occur if the drive is different indeed

But I'm wanting it to only move when completed.

@BenMcLean commented on GitHub (Aug 20, 2021): > As you are on SSD, double check the option "Pre-allocate disk space for all files" is not checked. > Then simply define "Default Save Path" on the SSD and use the "set location" option to move torrent on the same drive. > I reserve the SSD for caching/OS and the regular HDD for torrent target. Up to now the move are instant, so no full copy made. > It should only occur if the drive is different indeed But I'm wanting it to only move when completed.

deekerman commented

2026-02-21 22:38:10 -05:00

Author

Owner

@shama84 commented on GitHub (Aug 21, 2021):

But I'm wanting it to only move when completed.

Well not existing so far I know in this form, you will have to download it fully then "set location" afterward.
What's the reason to wait? Maybe something can be done on this side

@shama84 commented on GitHub (Aug 21, 2021): > But I'm wanting it to only move when completed. Well not existing so far I know in this form, you will have to download it fully then "set location" afterward. What's the reason to wait? Maybe something can be done on this side

deekerman commented

2026-02-21 22:38:10 -05:00

Author

Owner

@thalieht commented on GitHub (Aug 21, 2021):

You can use Categories in Automatic Management Mode in conjunction with Keep incomplete torrents in: option. When they finish downloading they will be moved from the temp folder to whatever is set as "Save path" in their assigned category.
FYI and In case you ask, different temp folder per torrent is currently not possible.

@thalieht commented on GitHub (Aug 21, 2021): You can use Categories in `Automatic Management Mode` in conjunction with `Keep incomplete torrents in:` option. When they finish downloading they will be moved from the temp folder to whatever is set as "Save path" in their assigned category. FYI and In case you ask, different temp folder per torrent is currently not possible.

deekerman commented

2026-02-21 22:38:10 -05:00

Author

Owner

@BenMcLean commented on GitHub (Aug 21, 2021):

"Different temp folder per torrent" is a better way to describe this feature request.

@BenMcLean commented on GitHub (Aug 21, 2021): "Different temp folder per torrent" is a better way to describe this feature request.

deekerman commented

2026-02-21 22:38:10 -05:00

Author

Owner

@thalieht commented on GitHub (Aug 21, 2021):

"Different temp folder per torrent" is a better way to describe this feature request.

Duplicate of #1812 but its closed and locked. Two other issues discussing the redesign of the "Temp folder" which include this topic: #13065 and #7164 (and more specifically about this topic https://github.com/qbittorrent/qBittorrent/issues/7164#issuecomment-320873953 onward).

@thalieht commented on GitHub (Aug 21, 2021): >"Different temp folder per torrent" is a better way to describe this feature request. Duplicate of #1812 but its closed and locked. Two other issues discussing the redesign of the "Temp folder" which include this topic: #13065 and #7164 (and more specifically about this topic https://github.com/qbittorrent/qBittorrent/issues/7164#issuecomment-320873953 onward).

deekerman commented

2026-02-21 22:38:10 -05:00

Author

Owner

@BenMcLean commented on GitHub (Aug 23, 2021):

Thanks. #13065 definitely covers it and expresses the idea better than I could.

@BenMcLean commented on GitHub (Aug 23, 2021): Thanks. #13065 definitely covers it and expresses the idea better than I could.