A simpler torrent review workflow
Torrent Inspector 2.3.0 keeps the checks, tracker setup and matching releases in one drawer beside the torrent page. Read the page checks, then connect trackers when you want searches.
Setup is saved. You do not need to open another settings panel for each torrent.
Read the verdict line; click it to unfold every problem. Tick the Manual checks you have done and open Automatic checks for the page evidence. No API key is needed for the loaded-page checks.
Set up trackers shows Prowlarr import and a manual tracker-key form together. Use either path and save/test a connection. Check this torrent searches connected trackers; your setup is remembered.
Use the copy buttons on a result for its report or original BBCode. Details opens its comparison and report. Use Retry beside a failed tracker. Finish the manual checks, then use Mark reviewed to save your progress.
One verdict line, three folded groups and the same evidence when you expand them.
Check this torrent in the header starts API search and opens Cross-checks. Results keep setup, comparisons and copying together. Search options holds filters, Search more broadly and Search all trackers. More in the bottom action row holds website search tabs separately from the API action.
Set up trackers in the header opens saved tracker controls when needed. Page checks and returned results stay in the same panel. Tick Manual checks as you confirm them, open Automatic checks for the page findings and Cross-checks for search results. As scans arrive, your reading position, open details and focus are kept. Each result shows its title and any reported filename. Equivalent identities share a card, including eligible Candidates to review. Grouped candidates still need review against this torrent; they do not become matches. Each tracker keeps its own date, original report and BBCode, copy buttons and Open torrent. Similar names alone or conflicting identity evidence do not group results; Other editions stay separate. Details opens its comparison and report; copying works without opening it.
Copy recommended name in the bottom action row copies a name reassessed against the active guide. Expand a group and check row for evidence or manual confirmations. A Suggested title card above the groups explains a correction when one is available; its Reply to uploader combines selected findings into BBCode. Page checks passed means the checked items and manual checks are clear; Review needed means something still needs review. Listing badges say Title to show that only the displayed name was checked. Failed tracker searches show a failure count and a retry action. The Personal Release check row shows Yes, No or Unknown from an explicit tracker badge or API flag, separately from Internal. Missing evidence stays Unknown; it does not identify who made the release or add requests. Open a row for its full evidence or title preview. Suggested title explains supported formatting fixes and gives you a copy button. Reply to uploader lets you choose findings, read a BBCode preview and copy one message. Missing release information is never guessed. Nothing is renamed or posted automatically.
InfinityHD naming follows its movie, TV and music guide, including DV HDR and bracketed music with an optional group tag. Metadata and official retail box-set status still need manual confirmation. Music requirements §10 add FLAC 16/24-bit report/file checks; missing evidence stays for review. Completeness, tags, provenance, untouched WEB files, analog lineage, unmodified logs and bundled-video origin remain manual. Secure CD ripping, logs, cue sheets and a 100% score are recommendations. Original Scene/P2P names are kept.
Automatic checks contains screenshot count/size details and season-pack checks, with optional expected episode numbers. Cross-checks contains the local .torrent helper. Other editions starts collapsed. Details and copy actions stay available in the same panel.
Hide › slides the drawer away to an edge tab; Alt+I brings it back. Drag its left edge to make it wider or narrower. The ▾ beside the title folds it to the verdict line. In page places it below the release name, and As drawer returns it. Below 600px it stays in the page with larger controls. The colours follow the Nocturne blue-grey palette.



On requests, Search trackers opens a compact box and starts the saved API search in one click, including the current tracker. Request lists use matching Search trackers and Web links buttons. One compact request-page toolbar holds search and header Set up trackers, with folded Website searches. Request results use at most two columns on wide screens and one on phones. Matches request details means an ID and listed requirements agree; title-only or incomplete results stay under Check these releases, and conflicts under Other editions. Open a result or copy its returned report and original BBCode directly. These are request-detail comparisons, not MediaInfo, hash or same-file matches. Searching never fills, claims or approves a request.
For a queue, choose Review loaded titles on a listing, then open a torrent. Mark reviewed & next continues when another queued item is available. In the review tools, Next unchecked follows the captured queue. Listing settings remain under Settings & tools.
A release name is a starting point. The returned evidence tells you what can be compared.
Details compares MediaInfo IDs, filenames, exact file bytes and available torrent hashes. Full Blu-ray BDInfo can show Matching disc report when the disc label, disc bytes, playlist and tracks agree. Check a local .torrent file compares chosen v1/v2/hybrid metadata locally. Matching names and sizes alone do not confirm identical media. Missing or shortened reports stay for review; these checks do not verify actual media.
Uploads are ordered oldest first within each comparison group, with missing dates last. This ranks returned results; it does not prove where a release originated.
A listed home gives a recommended tracker search. Scene-listed and unlisted groups can use Search srrDB by title and group. It opens only when clicked and does not automatically confirm a scene record.
A matching report for one episode does not prove that an entire season pack is identical. Local Season-pack checks run when the file list appears, before the main check, with a visible Missing episode numbers warning for interior gaps. Expand the section for filenames, sizes and comparisons. Expected episodes (optional) accepts your count or list for this torrent and visit; it takes precedence for partial packs and can check leading or trailing absences. Incomplete or ambiguous lists stay unconfirmed. No official season length is guessed, no extra API call is made and the tracker’s title is not changed. The review tools keep the original Season check tab. Last saved check on another page is older stored evidence, shown separately.
Enter the base server address (including its application prefix, without a settings-page path) and API key, then press Connect once. If your seedbox asks for a separate login, fill Server login (optional) first, using an HTTPS address. Supported direct keys are imported. Configured trackers such as TorrentLeech and FileList use search fallback automatically, without a second checklist.
In Manual · One tracker key, select the tracker, paste its API key and press Save & test. PeerGarden supports direct searches, MediaInfo, original BBCode and available torrent hashes.
Test all connections checks saved supported direct keys and Prowlarr discovery without changing selections. Updates retain settings and keys already saved in Tampermonkey; older page-only credentials need one-time re-entry. Blank key fields are intentional. Keys stay private and excluded from backups.
Use Copy MediaInfo or Copy BDInfo for the original report, and Copy description for its original BBCode. Fallback results may have no report or original description to copy. The script does not invent missing reports.
Expand a check or open the detailed review tools for reports, comparisons and private notes.



Detailed tools also include private notes, naming templates, captured-release comparisons and rules profiles. The Rules builder helps you create a profile for your tracker.
The script is handed out privately to moderators and staff of supported trackers. Ask DKOKTO on your tracker for the installation address. This public website carries the screenshots and Rules builder; it does not offer the userscript for download.
Settings and keys already saved in Tampermonkey are retained. Older page-only credentials need one-time re-entry.