Choose where to save .torrent file and a couple of issues #1376

Closed
opened 2026-02-21 15:37:43 -05:00 by deekerman · 7 comments
Owner

Originally created by @Sephiroth43 on GitHub (Apr 24, 2014).

Hello,

I want to suggest to allow us the option to choose where to save the torrent files from the BT_backup folder. Currently it's in C:\Usersuser\AppData\Local\qBittorrent\BT_backup and I don't see a way to change that. However stupid it might sound I prefer to save them on my D drive, where I save all "TEMP" files.

Also I want to report a couple of errors I'm experiencing while using Chrome. If I set "always open files of this type" in Chrome and at the same time I enable "Automatically add torrents from:" in the "Tools\Options\Downloads" menu in qbt, then I'm getting the I/O Error "The torrent file does not exist".
Problem number two appearing in the case described above - the torrent however is successfully loaded in qbt, but I don't get the "Display torrent content and some options" despite it is being enabled in the options. Which is annoying because I might want to disable some files from being downloaded.

If I disable the "Automatically add torrents from:", then I get the popup window with the options, but the problem is that the .torrent file from Chrome is kept in my download directory which I don't want. However if the "Automatically add torrents from:" is enabled then qbt is deleting that file which is great.

Thank you!

Originally created by @Sephiroth43 on GitHub (Apr 24, 2014). Hello, I want to suggest to allow us the option to choose where to save the torrent files from the BT_backup folder. Currently it's in C:\Users*user*\AppData\Local\qBittorrent\BT_backup and I don't see a way to change that. However stupid it might sound I prefer to save them on my D drive, where I save all "TEMP" files. Also I want to report a couple of errors I'm experiencing while using Chrome. If I set "always open files of this type" in Chrome and at the same time I enable "Automatically add torrents from:" in the "Tools\Options\Downloads" menu in qbt, then I'm getting the I/O Error "The torrent file does not exist". Problem number two appearing in the case described above - the torrent however is successfully loaded in qbt, but I don't get the "Display torrent content and some options" despite it is being enabled in the options. Which is annoying because I might want to disable some files from being downloaded. If I disable the "Automatically add torrents from:", then I get the popup window with the options, but the problem is that the .torrent file from Chrome is kept in my download directory which I don't want. However if the "Automatically add torrents from:" is enabled then qbt is deleting that file which is great. Thank you!
deekerman 2026-02-21 15:37:43 -05:00
Author
Owner

@pixy-misa commented on GitHub (Apr 24, 2014):

FYI. The options "Copy .torrent files to:" and "Copy .torrent files for finished downloads to:" works for me. It creates a copy of the .torrent file in the folders I specified.

@pixy-misa commented on GitHub (Apr 24, 2014): FYI. The options "Copy .torrent files to:" and "Copy .torrent files for finished downloads to:" works for me. It creates a copy of the .torrent file in the folders I specified.
Author
Owner

@Sephiroth43 commented on GitHub (Apr 25, 2014):

Yes, but those options copies the files, and I don't want to make copies. I just want to store the backup that qbt is creating in a different folder/storage.

@Sephiroth43 commented on GitHub (Apr 25, 2014): Yes, but those options copies the files, and I don't want to make copies. I just want to store the backup that qbt is creating in a different folder/storage.
Author
Owner

@Soukyuu commented on GitHub (Apr 27, 2014):

As a workaround, you could just symlink that directory so that qBit thinks it's writing to C: but the folder is actually where you specified. Most simple way to do that is moving your current BT_backup folder somewhere else then running the command line prompt in admin mode and typing in

mklink /J %localappdata%\qBittorrent\BT_backup D:\Temp\Torrents

The result will look like a simple folder shortcut, but it's actually a hardlink.

@Soukyuu commented on GitHub (Apr 27, 2014): As a workaround, you could just symlink that directory so that qBit thinks it's writing to C: but the folder is actually where you specified. Most simple way to do that is moving your current BT_backup folder somewhere else then running the command line prompt in admin mode and typing in ``` mklink /J %localappdata%\qBittorrent\BT_backup D:\Temp\Torrents ``` The result will look like a simple folder shortcut, but it's actually a hardlink.
Author
Owner

@sledgehammer999 commented on GitHub (Apr 27, 2014):

Just so you know those .torrent are for internal use for qbt. If a .torrent goes missing from there, your torrent will disappear from the transfer list too upon qbt launch.

@sledgehammer999 commented on GitHub (Apr 27, 2014): Just so you know those .torrent are for internal use for qbt. If a .torrent goes missing from there, your torrent will disappear from the transfer list too upon qbt launch.
Author
Owner

@pixy-misa commented on GitHub (Apr 28, 2014):

I dislike forcing a user application preference on the internal design of the application. I think the "Copy" is the safest option. I know µTorrent will allow you to keep one physical set of .torrent files in the folder you designate but its way has an issue. I think qbittorrent's way is safer.

In µTorrent, should the .torrent files be moved from outside the tool you will have invalid entries in your torrent display. This can easily happen when the folder for the .torrent is on an external drive.

Then should you remove one of the invalid entries from the torrent display before restoring the .torrent files back to former location, you will end up with a situation where you can not add the removed torrent back to the torrent display because the tool thinks the .torrent is already loaded when it sees the a torrent with a matching hashinfo in restored folder referenced by resume.dat.

In µTorrent case, the only way I have found to correct the issue requires working outside the tool. The reference to the .torrent files needs to be physically removed from the resume.dat file with a bencode editor.

By maintaining the .torrent files in its internal area and making a copy of then in the user specified folders, qbittorrent avoids the issue that can occur with µTorrent.

By the way, the resume.dat file is how µTorrent prevents the torrent entries from disappearing from the list when the physical .torrent file is missing. It simply display a text message to let you know the .torrent is missing.

@pixy-misa commented on GitHub (Apr 28, 2014): I dislike forcing a user application preference on the internal design of the application. I think the "Copy" is the safest option. I know µTorrent will allow you to keep one physical set of .torrent files in the folder you designate but its way has an issue. I think qbittorrent's way is safer. In µTorrent, should the .torrent files be moved from outside the tool you will have invalid entries in your torrent display. This can easily happen when the folder for the .torrent is on an external drive. Then should you remove one of the invalid entries from the torrent display before restoring the .torrent files back to former location, you will end up with a situation where you can not add the removed torrent back to the torrent display because the tool thinks the .torrent is already loaded when it sees the a torrent with a matching hashinfo in restored folder referenced by resume.dat. In µTorrent case, the only way I have found to correct the issue requires working outside the tool. The reference to the .torrent files needs to be physically removed from the resume.dat file with a bencode editor. By maintaining the .torrent files in its internal area and making a copy of then in the user specified folders, qbittorrent avoids the issue that can occur with µTorrent. By the way, the resume.dat file is how µTorrent prevents the torrent entries from disappearing from the list when the physical .torrent file is missing. It simply display a text message to let you know the .torrent is missing.
Author
Owner

@Owyn commented on GitHub (Nov 19, 2021):

copy .torrent files in

can't we just name it "store .torrents files in:" instead and get red of copying? also there would be no need in storing .torrent files in BT_Backup folder then if user has enabled the option to store em somewhere else? (I think that's exactly what uTorrent does)

also, if an user has few thousands torrents your bt_backup folder would store twice as much files in there which is really not performance-friendly

@Owyn commented on GitHub (Nov 19, 2021): > copy .torrent files in can't we just name it "store .torrents files in:" instead and get red of copying? also there would be no need in storing .torrent files in BT_Backup folder then if user has enabled the option to store em somewhere else? (I think that's exactly what uTorrent does) also, if an user has few thousands torrents your bt_backup folder would store **twice** as much files in there which is really not performance-friendly
Author
Owner

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

I want to suggest to allow us the option to choose where to save the torrent files from the BT_backup folder. Currently it's in C:\Usersuser\AppData\Local\qBittorrent\BT_backup and I don't see a way to change that.

Use portable mode https://github.com/qbittorrent/qBittorrent/wiki/How-to-use-portable-mode

@thalieht commented on GitHub (Aug 5, 2022): >I want to suggest to allow us the option to choose where to save the torrent files from the BT_backup folder. Currently it's in C:\Usersuser\AppData\Local\qBittorrent\BT_backup and I don't see a way to change that. Use portable mode https://github.com/qbittorrent/qBittorrent/wiki/How-to-use-portable-mode
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/qBittorrent#1376
No description provided.