mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
When I delete a torrent and files from the Transfers panel, also delete the .torrent file #14502
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#14502
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Programmer96 on GitHub (Apr 8, 2023).
Suggestion
This is the default behavior of uTorrent, I'd like to have it here
Use case
It's very useful because generally when I want to get rid of the torrent and files, often I want the .torrent deleted too, as I don't want to have that torrent at all, as I save all the .torrent files of all the torrents I want to keep.
Extra info/examples/attachments
No response
@glassez commented on GitHub (Apr 8, 2023):
This has been discussed many times! qBittorrent isn't uTorrent. It behaves differently. It does not associate the torrent with any source .torrent files at all after the torrent is added, and stores all the necessary data separately.
The only thing you can do with source .torrent files is enable the option to delete such files after torrents are added.
@Programmer96 commented on GitHub (Apr 8, 2023):
So what? is a good idea and I want it in
@stalkerok commented on GitHub (Apr 8, 2023):
@Programmer96, you do not understand how it works, .torrent is removed from the service folder by default along with .fastresume. You can also remove the original .torrent file when adding by checking the option.
@glassez commented on GitHub (Apr 8, 2023):
@stalkerok
It seems @Programmer96 just thinks that all BitTorrent clients should behave like uTorrent.
@stalkerok commented on GitHub (Apr 8, 2023):
@glassez, it looks like it is. It's probably better to close such issues right away.
@Programmer96 commented on GitHub (Apr 8, 2023):
No, the .torrent is kept in a location I configured to be stored, and that won't be deleted.
So you're closed minded to good ideas just because it's on another software, that's dumb, but now understand why so many forks exist and compilations with names
@stalkerok commented on GitHub (Apr 8, 2023):
@Programmer96, this function is only needed to copy the original .torrent and nothing else. After copying qbt has nothing to do with it.
@Programmer96 commented on GitHub (Apr 8, 2023):
And I never said it should do more, you misunderstood. Are you playing the fool, so I call you out on it and mods close this and ban me?
@Sentox6 commented on GitHub (Apr 8, 2023):
@Programmer96 You are choosing to be very contentious towards people here.
qBittorrent's current behaviour is much more robust than maintaining dependency upon the original .torrent file.
@Programmer96 commented on GitHub (Apr 8, 2023):
Wong, is the other way around, is all the people replying here and you continuing the trolling trend of absurd and irrelevant remarks; this is how dumb people try to get higher moral ground, to oppose with self-victimization, what they can't reach with a better idea or can't find anything false in true statement/idea.
What you just wrote translates to: the car is more important than a tyre, so we must not change the tyre for a better one; it's this inability to accept progress, what brings detriment to everything, this absurd conservatism.
This is the reason why, the first and maybe the second posts, are never answered in a forum, and I shouldn't have, since this is the normal procedure: get the OP angry so the thread justifies a cut off: not only coward but intellectually poor
@Programmer96 commented on GitHub (Apr 8, 2023):
It's not about purpose but useful function that I'm requesting.
There's no relation with the .torrent file? clearly there is, as I don't use even a webbrowser to get the .torrent files, but the internal search plugins, and that file is used, so you have the file and all their details; it's just put in a folder as qBittorrent configuration allows it; this file could external now to the app, but clearly within the easy reach of the app, and shouldn't be difficult to add a procedure to delete it; but you're just making pretexts to not do it.
Edit: This is for torrents I Configure to save in a Directory/Folder, so qB knows where they are
@Programmer96 commented on GitHub (Apr 16, 2024):
Why this hasn't been implemented? It's been more than a year, I need this function!
@vertigo220 commented on GitHub (Oct 5, 2024):
While I understand the logic in not needing it because qbittorrent is designed to not rely on it, it has the option to copy it, so that logic makes absolutely no sense if you're going to provide that option, which goes against it, then not provide the requested option (which, btw, has been requested numerous times in several issues) due to that logic. It seems there should either be both options or neither. And the current design, with an option to delete it and an option to copy it, has led many, myself included, to mistake its behavior as moving the file vs copying it, due to not piecing the two options and their actions together.
Secondly, while qbittorrent doesn't need them, I personally prefer to keep the files until a torrent is done, in case I need to recreate them in a different software and/or on a new OS install. I realize you can create a magnet link or .torrent file from qbittorrent for this purpose, but AFAICT you can't create .torrent files for more than one torrent at a time, and both are reliant on doing this first in qbittorrent, which may not be available at the time (e.g. if I were to decide to reinstall my OS and use a different client, I'd have to install qbittorrent, import the data to rebuild the ongoing torrents, manually export the .torrent files one at a time or batch copy the magnet links, then use those to get up and running on the other client. By simply keeping the .torrent files, I already have them to use for this, but then once they're done, I currently have to go through and manually remove them because qbittorrent won't, even though it's the one that moved (copied) them in the first place.
So I get your reasoning, but I also don't understand why, when so many people across so many issues have been requesting this for so many years, it can't just be added to give users what they want and make things easier for them, even if it's not 100% in line with qbittorrent's functional design, just because it's not "needed" in the same sense it is with other software. Clearly, with so many users requesting it, it's still "needed."
@stalkerok commented on GitHub (Oct 5, 2024):
Nobody seems to know that qBittorrent has a function to export torrent files directly from the client.

@stalkerok commented on GitHub (Oct 5, 2024):
IMO, should just close such issues. Or remove the copy feature.
@vertigo220 commented on GitHub (Oct 5, 2024):
And apparently some can't read
@xavier2k6 commented on GitHub (May 25, 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 ❤
reactionsin 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:
DO NOT:
(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)
@Programmer96 commented on GitHub (Jun 6, 2025):
Why this hasn't been implemented? It's been more than 2 years, I need this function! I need the file.torrent deleted, that's what software do, help automate or save a lot of work, by doing work for me, and I need this so I can purge unnecessary files, the moment they become unnecessary. I save all the files.torrent I find useful in a directory/folder, 3,263 and counting: so that's the problem, if I don't remember the name or not exactly, or I need to check is a time consuming event; while at the moment, I know and qBT also know exactly what file.torrent needs to be removed. That's why is necessary, that's why I need it, and probably many other people. Why the F is so hard to put add a checkbox option to delete the file.torrent, when you know exactly where it is and what it's name is:
It's just 1 more file to delete, what is the F'ing problem? I'd do it myself, if I could understand your Nested Spaghetti Code, I'm not that good at programming yet. You made Categories, to make new folders and redirect torrents accordingly, and you can't delete a file you gave the option to save? In 2 years? F'ing buttholes
And no, I don't need to export anything, I need to delete, permanently; as this wasn't clear enough already, I have to repeat it for the 3rd time
@Programmer96 commented on GitHub (Jun 6, 2025):
Why don't you shut up and let people discuss? Don't wanna discuss? leave
@xavier2k6 commented on GitHub (Jun 6, 2025):
@Programmer96 read/re-read https://github.com/qbittorrent/qBittorrent/issues/18818#issuecomment-2907734508