Add "Seeders/Leachers Ratio" column to search results grid #16609

New issue

Open

opened 2026-02-22 03:16:20 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-22 03:16:20 -05:00

Owner

Originally created by @drittich on GitHub (Feb 16, 2025).

Suggestion

I'm often looking for the highest seeders to leachers ratio in the search results grid, so the ability to sort by a "Seeders/Leachers Ratio" column would avoid having to mentally check this for each search result before choosing a candidate torrent to download.

Note: While this is similar to these other PRs, it is related to search, not the main UI:

Use case

No response

Extra info/examples/attachments

No response

Originally created by @drittich on GitHub (Feb 16, 2025). ### Suggestion I'm often looking for the highest seeders to leachers ratio in the search results grid, so the ability to sort by a "Seeders/Leachers Ratio" column would avoid having to mentally check this for each search result before choosing a candidate torrent to download. **Note:** While this is similar to these other PRs, it is related to search, not the main UI: - https://github.com/qbittorrent/qBittorrent/issues/5366 - https://github.com/qbittorrent/qBittorrent/issues/5031 - https://github.com/qbittorrent/qBittorrent/pull/2507 ### Use case _No response_ ### Extra info/examples/attachments _No response_

deekerman added the

Feature request

Search engine

labels

2026-02-22 03:16:20 -05:00

deekerman commented

2026-02-22 03:16:27 -05:00

Author

Owner

@thalieht commented on GitHub (Feb 16, 2025):

Why do leechers matter to you for a torrent you're going to download?
Also FYI, seeders who have chosen to not download even one tiny file are considered leechers.

@thalieht commented on GitHub (Feb 16, 2025): Why do leechers matter to you for a torrent you're going to download? Also FYI, seeders who have chosen to not download even one tiny file are considered leechers.

deekerman commented

2026-02-22 03:16:29 -05:00

Author

Owner

@drittich commented on GitHub (Feb 16, 2025):

Why do leechers matter to you for a torrent you're going to download? Also FYI, seeders who have chosen to not download even one tiny file are considered leechers.

A low seeder to leecher ratio like 1:10 usually means slower downloads than one like 10:1. Your second point is good to know, thanks.

@drittich commented on GitHub (Feb 16, 2025): > Why do leechers matter to you for a torrent you're going to download? Also FYI, seeders who have chosen to not download even one tiny file are considered leechers. A low seeder to leecher ratio like 1:10 usually means slower downloads than one like 10:1. Your second point is good to know, thanks.

deekerman commented

2026-02-22 03:16:29 -05:00

Author

Owner

@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 ❤ 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 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:** 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.)**