Display HASH column on Search tab. #11009

New issue

Open

opened 2026-02-21 21:05:47 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-21 21:05:47 -05:00

Owner

Originally created by @Snake883 on GitHub (Oct 18, 2020).

On the Search tab, display a Hash column.

Currently there are columns for: Name, Size, Seeders, Leechers, Search Engine.

Want a column for Hash so I can quickly and easily identify unique torrents.

qBittorrent version and Operating System

v4.2.5

Originally created by @Snake883 on GitHub (Oct 18, 2020). On the Search tab, display a Hash column. Currently there are columns for: Name, Size, Seeders, Leechers, Search Engine. ![image](https://user-images.githubusercontent.com/8312560/96378769-266b9d80-1143-11eb-8e75-8f5f5317e65e.png) Want a column for Hash so I can quickly and easily identify unique torrents. ### qBittorrent version and Operating System v4.2.5

deekerman added the

Feature request

Search engine

GUI

labels

2026-02-21 21:05:47 -05:00

deekerman commented

2026-02-21 21:05:49 -05:00

Author

Owner

@thalieht commented on GitHub (Oct 18, 2020):

This is a better idea IMO: #2511

Want a column for Hash so I can quickly and easily identify unique torrents.

Are you a machine? Can't imagine how someone can do that "quickly AND easily" with a column of hashes, and before you say it, yes even when sorting that column.

@thalieht commented on GitHub (Oct 18, 2020): This is a better idea IMO: #2511 >Want a column for Hash so I can quickly and easily identify unique torrents. Are you a machine? Can't imagine how someone can do that "quickly AND easily" with a column of hashes, and before you say it, yes even when sorting that column.

deekerman commented

2026-02-21 21:05:50 -05:00

Author

Owner

@tristanleboss commented on GitHub (Aug 23, 2022):

Great idea.

@tristanleboss commented on GitHub (Aug 23, 2022): Great idea.

deekerman commented

2026-02-21 21:05:50 -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.)**