starred/qBittorrent

Fork 0

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

WebUI: Show free space of temp folder in status bar #13832

New issue

Open

opened 2026-02-22 00:23:20 -05:00 by deekerman · 12 comments

deekerman commented

2026-02-22 00:23:20 -05:00

Owner

Originally created by @dsm1212 on GitHub (Sep 16, 2022).

Suggestion

In status bar today it shows:
Free space: xxTB
I'd like it to show:
Work space: xxGB Free Space: xxTB

Use case

Subject says it all. On my nas I use an SSD for incompleted torrents because it's so much faster, but completed files are moved to raid magnetic storage. The status bar seems to show the final destination folder. That's great, but it's the busy/temp folder I'd like to monitor because it's not so massive.

Extra info/examples/attachments

No response

Originally created by @dsm1212 on GitHub (Sep 16, 2022). ### Suggestion In status bar today it shows: Free space: xxTB I'd like it to show: Work space: xxGB Free Space: xxTB ### Use case Subject says it all. On my nas I use an SSD for incompleted torrents because it's so much faster, but completed files are moved to raid magnetic storage. The status bar seems to show the final destination folder. That's great, but it's the busy/temp folder I'd like to monitor because it's not so massive. ### Extra info/examples/attachments _No response_

deekerman added the

labels

2026-02-22 00:23:20 -05:00

deekerman commented

2026-02-22 00:23:26 -05:00

Author

Owner

@luzpaz commented on GitHub (Aug 14, 2024):

What's the function qbit uses to probe to find out the temp folder capacity?

@luzpaz commented on GitHub (Aug 14, 2024): * What's the function qbit uses to probe to find out the temp folder capacity?

deekerman commented

2026-02-22 00:23:29 -05:00

Author

Owner

@thalieht commented on GitHub (Aug 14, 2024):

What's the function qbit uses to probe to find out the temp folder capacity?

This is used for the default save path's free space. freeDiskSpaceOnPath can also be used for the temp path (or any path). github.com/qbittorrent/qBittorrent@c5b7c82344/src/webui/freediskspacechecker.cpp (L42)

@thalieht commented on GitHub (Aug 14, 2024): >What's the function qbit uses to probe to find out the temp folder capacity? This is used for the default save path's free space. `freeDiskSpaceOnPath` can also be used for the temp path (or any path). https://github.com/qbittorrent/qBittorrent/blob/c5b7c82344eaf2f795d65c2158fef03932d6db64/src/webui/freediskspacechecker.cpp#L42

deekerman commented

2026-02-22 00:23:29 -05:00

Author

Owner

@luzpaz commented on GitHub (Mar 9, 2025):

Related #22407

@luzpaz commented on GitHub (Mar 9, 2025): Related #22407

deekerman commented

2026-02-22 00:23:29 -05:00

Author

Owner

@glassez commented on GitHub (Mar 11, 2025):

@qbittorrent/bug-handlers, @Pentaphon
What format would you like to see it in?
The suggestion from OP Work space: xxGB Free Space: xxTB looks confusing to me.

@glassez commented on GitHub (Mar 11, 2025): @qbittorrent/bug-handlers, @Pentaphon What format would you like to see it in? The suggestion from OP `Work space: xxGB Free Space: xxTB` looks confusing to me.

deekerman commented

2026-02-22 00:23:29 -05:00

Author

Owner

@luzpaz commented on GitHub (Mar 11, 2025):

How do other apps approach this ? Anyone know?

@luzpaz commented on GitHub (Mar 11, 2025): How do other apps approach this ? Anyone know?

deekerman commented

2026-02-22 00:23:29 -05:00

Author

Owner

@Pentaphon commented on GitHub (Mar 11, 2025):

@qbittorrent/bug-handlers, @Pentaphon What format would you like to see it in? The suggestion from OP Work space: xxGB Free Space: xxTB looks confusing to me.

The format really doesn't matter to me as long as the free space is actually shown so whatever makes the most sense to you is fine by me in this case. "Temp space" seems the most consistent, no? Perhaps an option whether to show temp space or not for people who don't want to display it? Opt-in of course.

@Pentaphon commented on GitHub (Mar 11, 2025): > @qbittorrent/bug-handlers, [@Pentaphon](https://github.com/Pentaphon) What format would you like to see it in? The suggestion from OP `Work space: xxGB Free Space: xxTB` looks confusing to me. The format really doesn't matter to me as long as the free space is actually shown so whatever makes the most sense to you is fine by me in this case. "Temp space" seems the most consistent, no? Perhaps an option whether to show temp space or not for people who don't want to display it? Opt-in of course.

deekerman commented

2026-02-22 00:23:29 -05:00

Author

Owner

@glassez commented on GitHub (Mar 11, 2025):

"Temp space" seems the most consistent, no?

When I see "Free space" and some other "space" at the same time, it looks like an opposition (i.e., as if other space is not free, unlike "Free space"). That's what looks confusing to me. They both are free space.

@glassez commented on GitHub (Mar 11, 2025): > "Temp space" seems the most consistent, no? When I see "Free space" and some other "space" at the same time, it looks like an opposition (i.e., as if other space is not free, unlike "Free space"). That's what looks confusing to me. They both are free space.

deekerman commented

2026-02-22 00:23:29 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Mar 11, 2025):

"Temp space" seems the most consistent, no?

When I see "Free space" and some other "space" at the same time, it looks like an opposition (i.e., as if other space is not free, unlike "Free space"). That's what looks confusing to me. They both are free space.

Well, on windows we have "Used space" & "Free space" when talking about drives.

So, why not Total Size or Total Capacity/Drive Capacity & then we can also use Free space?

@xavier2k6 commented on GitHub (Mar 11, 2025): > > "Temp space" seems the most consistent, no? > > When I see "Free space" and some other "space" at the same time, it looks like an opposition (i.e., as if other space is not free, unlike "Free space"). That's what looks confusing to me. They both are free space. Well, on windows we have "Used space" & "Free space" when talking about drives. ![Image](https://github.com/user-attachments/assets/f541a21e-0def-4784-bb25-02dc2fca0516) So, why not `Total Size` or `Total Capacity/Drive Capacity` & then we can also use `Free space`?

deekerman commented

2026-02-22 00:23:29 -05:00

Author

Owner

@glassez commented on GitHub (Mar 11, 2025):

So, why not Total Size or Total Capacity& then we can also use Free space?

Do we talk about total size, etc.?
Don't we talk about free space at temp save path in addition to free space at main save path?

@glassez commented on GitHub (Mar 11, 2025): > So, why not `Total Size` or `Total Capacity`& then we can also use `Free space`? Do we talk about total size, etc.? Don't we talk about free space at temp save path in addition to free space at main save path?

deekerman commented

2026-02-22 00:23:29 -05:00

Author

Owner

@xavier2k6 commented on GitHub (Mar 11, 2025):

Do we talk about total size, etc.?

I might've misinterpreted the request - I though the OP was asking for capacity/free space of temp drive in addition to free space for destination drive.

Don't we talk about free space at temp save path in addition to free space at main save path?

If they are on the same drive....then "free space" for both will be equal, won't they?

How about for naming?!

(Incomplete Path) Free space: X.XX GiB / (Save Path) Free space: X.XX GiB

@xavier2k6 commented on GitHub (Mar 11, 2025): >Do we talk about total size, etc.? I might've misinterpreted the request - I though the OP was asking for capacity/free space of temp drive in addition to free space for destination drive. >Don't we talk about free space at temp save path in addition to free space at main save path? If they are on the same drive....then "free space" for both will be equal, won't they? ____ How about for naming?! (Incomplete Path) Free space: X.XX GiB / (Save Path) Free space: X.XX GiB

deekerman commented

2026-02-22 00:23:29 -05:00

Author

Owner

@dsm1212 commented on GitHub (Mar 11, 2025):

Yes I was asking for temp space. My temp space is more limited than my final storage because I use an SSD for temp and bunch of large magnetic drives for completed downloads. I still find sometimes stalled downloads have piled up a lot of temp.

@dsm1212 commented on GitHub (Mar 11, 2025): Yes I was asking for temp space. My temp space is more limited than my final storage because I use an SSD for temp and bunch of large magnetic drives for completed downloads. I still find sometimes stalled downloads have piled up a lot of temp.

deekerman commented

2026-02-22 00:23:29 -05:00

Author

Owner

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