Move completed files of a torrent to the final destination #5806

New issue

Open

opened 2026-02-21 18:03:30 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-21 18:03:30 -05:00

Owner

Originally created by @Gelunox on GitHub (Jul 21, 2017).

qBittorrent version and Operating System: v3.3.13 (64-bit), Windows 10

I'd like to have files in a torrent that have finished downloading moved to the completed path rather than having to wait until the entire torrent has finished downloading.

One of the reasons being that this way I can keep my cache-drive from running out of space, which it will if I download a torrent larger than the drive: when that happens qBT starts giving nothing but error messages. The other being that it gives me a view of all the files that have finished.

Originally created by @Gelunox on GitHub (Jul 21, 2017). ### qBittorrent version and Operating System: v3.3.13 (64-bit), Windows 10 I'd like to have files in a torrent that have finished downloading moved to the completed path rather than having to wait until the entire torrent has finished downloading. One of the reasons being that this way I can keep my cache-drive from running out of space, which it will if I download a torrent larger than the drive: when that happens qBT starts giving nothing but error messages. The other being that it gives me a view of all the files that have finished.

deekerman added the

Feature request

Temp folder

labels

2026-02-21 18:03:30 -05:00

deekerman commented

2026-02-21 18:03:34 -05:00

Author

Owner

@glassez commented on GitHub (Jul 25, 2017):

See #7164.

@glassez commented on GitHub (Jul 25, 2017): See #7164.

deekerman commented

2026-02-21 18:03:34 -05:00

Author

Owner

@luzpaz commented on GitHub (Oct 31, 2023):

Added 'Temp folder' label

@luzpaz commented on GitHub (Oct 31, 2023): Added 'Temp folder' label

deekerman commented

2026-02-21 18:03:34 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 23, 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 23, 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.)**