starred/qBittorrent

Fork 0

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

Option to delete unchecked content #8643

New issue

Closed

opened 2026-02-21 19:43:59 -05:00 by deekerman · 5 comments

deekerman commented

2026-02-21 19:43:59 -05:00

Owner

Originally created by @emanruse on GitHub (May 7, 2019).

Currently unchecking files and directories in Content section of UI does not delete them. Removing those requires manual intervention and in certain cases can be quite inconvenient. Having an option to have QBT delete the content would be very useful.

Originally created by @emanruse on GitHub (May 7, 2019). Currently unchecking files and directories in Content section of UI does not delete them. Removing those requires manual intervention and in certain cases can be quite inconvenient. Having an option to have QBT delete the content would be very useful.

deekerman

2026-02-21 19:43:59 -05:00

closed this issue
added the
Feature request

Duplicate
labels

deekerman commented

2026-02-21 19:44:05 -05:00

Author

Owner

@xnoreq commented on GitHub (Jun 2, 2019):

It's not that simple. Parts (the beginning or end) of unchecked files can be needed by qbittorrent since torrent content is just a stream of bytes chopped into chunks that don't need to align with file boundaries.

That's why after deleting unchecked files and doing a recheck you will see that qbittorrent won't report 100% finished but something like 99.x%.

@xnoreq commented on GitHub (Jun 2, 2019): It's not that simple. Parts (the beginning or end) of unchecked files can be needed by qbittorrent since torrent content is just a stream of bytes chopped into chunks that don't need to align with file boundaries. That's why after deleting unchecked files and doing a recheck you will see that qbittorrent won't report 100% finished but something like 99.x%.

deekerman commented

2026-02-21 19:44:05 -05:00

Author

Owner

@xnoreq commented on GitHub (Jun 2, 2019):

Besides, removing the torrent will remove unneeded files.

@xnoreq commented on GitHub (Jun 2, 2019): Besides, removing the torrent will remove unneeded files.

deekerman commented

2026-02-21 19:44:05 -05:00

Author

Owner

@emanruse commented on GitHub (Jun 4, 2019):

It's not that simple.

I have never commented about simplicity or complexity :)

Parts (the beginning or end) of unchecked files can be needed by qbittorrent since torrent content is just a stream of bytes chopped into chunks that don't need to align with file boundaries.

But QBT recognizes what a file is and can move files. So there should be no additional complexity in deleting one instead of moving it, no?

That's why after deleting unchecked files and doing a recheck you will see that qbittorrent won't report 100% finished but something like 99.x%.

That should depend on the logic. If the user wants only 2 of 5 files, then from user viewpoint it is 100% job done. Perhaps a setting or an additional column in the UI can indicate that.

Besides, removing the torrent will remove unneeded files.

Sure but that's not the topic here.

@emanruse commented on GitHub (Jun 4, 2019): > It's not that simple. I have never commented about simplicity or complexity :) > Parts (the beginning or end) of unchecked files can be needed by qbittorrent since torrent content is just a stream of bytes chopped into chunks that don't need to align with file boundaries. But QBT recognizes what a file is and can move files. So there should be no additional complexity in deleting one instead of moving it, no? > That's why after deleting unchecked files and doing a recheck you will see that qbittorrent won't report 100% finished but something like 99.x%. That should depend on the logic. If the user wants only 2 of 5 files, then from user viewpoint it is 100% job done. Perhaps a setting or an additional column in the UI can indicate that. > Besides, removing the torrent will remove unneeded files. Sure but that's not the topic here.

deekerman commented

2026-02-21 19:44:05 -05:00

Author

Owner

@Dobatymo commented on GitHub (Jun 5, 2019):

@xnoreq Because it's not that simple, this is a good feature request.

If the user could just manually delete the files on disk it would not be really necessary. But you cannot do this as parts of the files might still be required for other chunks like you said.

These bytes should be moved to a separate file like they would if they had been unchecked from the beginning.

@Dobatymo commented on GitHub (Jun 5, 2019): @xnoreq Because it's not that simple, this is a good feature request. If the user could just manually delete the files on disk it would not be really necessary. But you cannot do this as parts of the files might still be required for other chunks like you said. These bytes should be moved to a separate file like they would if they had been unchecked from the beginning.

deekerman commented

2026-02-21 19:44:05 -05:00

Author

Owner

@thalieht commented on GitHub (Sep 13, 2020):

Duplicate of #2391

@thalieht commented on GitHub (Sep 13, 2020): Duplicate of #2391