Trackers

upbrr's tracker catalog is built from registered tracker implementations. The Web UI renders each tracker's supported settings and capabilities from that catalog.

See Supported trackers to find a tracker by its public name.

Configure a tracker

1. Open Settings.
2. Open the tracker section.
3. Enter only the requested credentials and options.
4. Save settings.
5. Export and import browser cookies, sign in, or test authentication when those actions are available.
6. Add the tracker to default selection only after it reports ready.

Auth requirements vary. A tracker can require an API key, passkey, cookie session, username/password login, 2FA, or a supported combination. upbrr stores managed tracker cookies encrypted in SQLite.

Never paste tracker credentials, cookies, announce URLs, OTP secrets, or raw auth failures into issues or chat.

Defaults and per-run selection

• Default trackers seed the initial tracker set.
• Preferred tracker influences workflows that need one preferred source of tracker data.
• CLI --trackers selects a comma-separated set for one run.
• CLI --trackers-remove removes trackers from that run.
• The Web UI lets you select trackers from the Input page.

CLI workflows that require post-duplicate approval use the exact tracker subset you approve. The Web UI uses its per-stage tracker selections. Later stages do not add disabled, blocked, or unselected trackers.

Duplicate checks and rules

Tracker adapters normalize duplicate results into a common review surface. A tracker can return:

• a completed search with zero or more matches;
• a not-run result with a reason, such as missing auth or metadata;
• an attempted search failure.

Warnings that permit an override can block a live upload while allowing debug preparation. Strict constructibility failures block every mode. Debug retains the actual blocked or failed assessment and can continue diagnostic payload preparation when its inputs are available; it never grants submission authority. Subjective or incomplete tracker rules remain visible for review.

Tracker settings can restrict duplicate competition by incoming release group. When a tag matches that tracker's Same-group duplicate-check groups or Internal release groups, confirmed candidates from other groups coexist and are omitted from slot-capacity decisions. Exact duplicates, same-group candidates, conflicting evidence, and unknown groups keep their normal duplicate result. See tracker group policy lists.

A completed search with no matches can still require duplicate-policy review when ordinary-slot eligibility, source availability, or staff-owned decisions are unresolved. Review these reasons alongside potential duplicates. Acknowledgement records your decision for the current evidence; it does not establish tracker staff approval or missing source evidence. Changing the reviewed name, relevant facts, or review reasons requires a new decision.

Duplicate checks use structured 3D labels when available. Release-name fallback recognizes explicit stereoscopic markers in release metadata, while ambiguous title text remains unknown. Missing 3D information does not prove that an existing release is 2D.

--skip-dupe-check and similar bypasses remove safeguards. Use them only when you have manually completed the equivalent tracker checks.

Approve tracker warnings

Some tracker warnings permit an explicit override. On Dupe Check, read the warnings on the affected tracker's card. Turn on Acknowledge tracker warnings only after deciding that the release is appropriate for that tracker. The warning details remain visible while acknowledged.

Approval applies only to that tracker and its current warning set. After the initial duplicate check, changing its warning toggle rechecks only that tracker when eligible. Other trackers keep their fresh, unchanged duplicate evidence and decisions. Turning the toggle off withdraws approval and skips that tracker's search until it is eligible again. Changed inputs, configuration, or expired evidence still require fresh checks. Changed warnings or a new prepared generation require renewed approval. Strict failures cannot be waived for a live upload. Debug can continue diagnostic preparation while preserving the real assessment; it never authorizes tracker submission.

The interactive CLI and --unattended_confirm prompt for approval. Strict --unattended declines without prompting and skips that tracker; other eligible trackers can continue. Debug can continue diagnostic preparation after an approval is declined when required inputs are available; unresolved construction requirements still block the affected preparation.

Blocking reasons and warnings

Review the assessment displayed for each selected tracker:

• Prohibited: a rule prevents the release from proceeding in a normal upload.
• Staff approval required: the release needs permission from the tracker's staff; answering a question or acknowledging a warning does not grant that permission.
• Trumpable release: a compliant replacement may supersede the upload. Proceed only when the displayed finding permits an explicit acknowledgement.
• Unresolved: required evidence is missing or conflicting. Correct the facts or answer the requested questions before continuing.
• Guidance: non-blocking advice in a panel that starts collapsed on Dupe Check. Expand it to read the warnings. It requires no answer or acknowledgement and does not establish that unknown source details are correct.

Check the tracker's current rules to understand what each finding means for your release. upbrr's assessment is not a substitute for those rules.

Account maintenance advice can also appear in Guidance or the upload log after a tracker responds to an upload. Expiry advice uses that credential's latest upload response; read-only checks do not refresh it, and no missing-expiry reminder appears before the first upload response. Remembered advice is cleared when the application restarts. Follow the displayed renewal instructions and update the configured credential as needed. This advice does not require acknowledgement or block unattended uploads; authentication failures still follow the normal recovery process.

Package checks use the files intended for the torrent, following its inclusion policy. A complete inventory can still contain prohibited files or a missing episode in a sequence. Inventory completeness is separate from the technical and language coverage of inspected media. ISO inputs retain their image-file identity during package validation. Older prepared generations require preparation again to collect this evidence.

Track order and the default flag are separate facts. An original-language track can be present without being first or default. Ordering recommendations appear as non-blocking Guidance, including for personal releases, and require no answer or acknowledgement. Independent requirements for original audio, default flags, permitted dubs, subtitles and compatibility tracks still apply.

Ordinary audio tracks contribute their inspected languages without needing an "Original" title or flag. Identified commentary, descriptive audio and other secondary tracks do not establish original programme audio or count as programme dubs. Missing or conflicting language evidence still needs review. Prepare the release again after updating so retained track facts are rebuilt before tracker checks.

Correct language and other factual evidence on Input. Naming overrides and warning acknowledgements do not change media facts. An acknowledgement applies only to its tracker and current prepared generation; it cannot clear an independent strict finding. Changed evidence requires renewed review.

When source contents fail a destination's rules, review those rules before selecting or preparing a corrected source. upbrr does not remove or remux media tracks automatically.

Media analysis

The release-level audio name describes a selected track. A destination may also flag features found on other inspected non-commentary tracks; changing the audio name does not establish those features. After updating, prepare saved releases again to rebuild inspected audio evidence. Missing required container evidence can block a destination; follow its displayed finding and current rules, then prepare corrected source evidence again.

Partial-season sources retain explicit part labels or source episode ranges in generated names. Known episode membership comes from included filenames; unidentified or conflicting members remain unverified. A part number never implies an episode range, and identifying every included episode does not prove a complete season. Duplicate checks distinguish verified disjoint membership from overlapping coverage. Tracker restrictions and explicit overrides still apply.

Omitting season and episode text also hides episode ranges in generated names while preserving coverage for duplicate checks. Explicit part labels remain visible. Conflicting ranges stay available for review and are omitted from generated names.

Non-disc pack preparation uses the selected primary video’s MediaInfo report. Programme-language and permitted-dub checks use that inspected file; other uninspected pack files do not by themselves block those checks. Inspected tracks still reports incomplete coverage. A pack-consistency reminder is passive Guidance: it does not scan every episode, establish pack-wide consistency, or require an answer or acknowledgement. Missing or conflicting evidence in the inspected file and independent tracker requirements still need review. Check the pack against the tracker’s current rules. Cancellation is checked between input-file reads; an operating-system read already in progress may delay stopping. Inspected languages, track titles, default/forced flags and container order inform the assessment. Source-history and hypothetical subtitle concerns remain warnings rather than requests to guess missing facts.

Tracker questions

On Dupe Checking, open Tracker questions for a selected tracker, review any required fields, and choose Apply tracker answers. Loading the questions uses existing prepared facts without contacting the tracker. Applying answers refreshes the assessment; it does not upload or start another duplicate search. Unanswered required fields block only their tracker, and unapplied edits must be applied before dry runs or uploads. See the questionnaire workflow for retained duplicate evidence and questions discovered during preparation.

Questions remain for genuine upload inputs, naming choices and ambiguous track associations that available metadata cannot supply. Available provider genres can supply genre tags automatically; unsupported or missing defaults may use a supported fallback provider. Explicit tag answers and genre corrections, including clears, take precedence. An optional tag field may remain empty when the destination can obtain genres from its metadata provider. Required fields with supplied values are identified separately from missing answers; optional controls do not require a response. Correct missing canonical facts on Input. An answer cannot waive an independent prohibited or staff-only finding. Debug can preserve an eligibility failure while continuing diagnostic preparation; evidence needed to construct names, payloads or required descriptions remains necessary.

Where supported, an opt-in class-based replacement setting exposes an explicit intended-replacement choice and optional reason in tracker questions. The setting alone does not approve a replacement: review the current release and duplicate evidence, then confirm upload as usual. Changing the source generation requires a fresh intention. Exact duplicates and files already present in the client keep their existing protections. Staff-managed authorization remains site-side and requires no token value in these controls. Unattended operation does not supply missing confirmations.

Names and payloads

Automatic downscale markers require explicit evidence in the source name; output resolution alone does not establish a downscaled source. A destination may omit or position an evidenced marker differently. Review the projected name, and use a complete name override when a source does not provide enough evidence.

upbrr resolves upload and search names before duplicate checking. Review the projected name for every selected tracker. The eventual payload uses that reviewed name rather than deriving a new name at submission time. Manual naming controls are presentation choices and do not grant upload eligibility or replace required factual evidence.

Correct PROPER, REPACK, PROPER2, PROPER3, REPACK2, REPACK3, or RERIP with the independent Release version control on Input, then refresh metadata and review the projected names again. Clearing Edition does not clear the release version; see Input corrections for None, Auto, and the legacy No edition behavior.

Automatic title and year sources can differ by destination. A required title must come from matching metadata for the current release; missing or outdated evidence blocks that name instead of silently substituting another provider. Refresh metadata and prepare the release again when requested. Explicit manual titles and complete name overrides remain authoritative, while an automatic duplicate-search name can still require its own provider evidence. These naming choices do not change the shared release facts or another destination's name. TV series-year disambiguation can use a different provider from the primary title. Established evidence may add or omit an automatic series year; manual title choices remain authoritative.

When a destination uses TVDB year disambiguation, an explicit naming year in the selected TVDB title or an eligible alias remains valid even if a name search finds no collision. A premiere year alone does not establish a naming year. Available TVDB naming data controls the TV year, including a decision that no year qualifier belongs in the name. Manual year and Omit year cannot override it. When usable TVDB data is missing, those controls are available for correction; newly available TVDB data supersedes the fallback. Destination-specific year rules still apply. A destination may include the current matching prepared provider year independently of TVDB disambiguation, without changing episode identification or other destinations’ names. Optional year policies preserve manual components and complete-name overrides; unavailable provider years do not invent a replacement. Movie year controls are unchanged. Prepare the release again after updating so retained naming decisions are recomputed.

Generated DVDRip release names include the known resolution, such as 480p or 576p, after the movie year or TV season/episode segment. Missing or unknown resolution stays absent, and complete manual names remain unchanged.

An Encode with DVD, PAL DVD, or NTSC DVD source normally displays DVDRip in its generated name while keeping the selected type, source, and TV episode details. Destination naming rules may use PAL DVD, NTSC DVD, or a system-qualified DVDRip instead. If a destination requires PAL or NTSC, select that source explicitly or provide a known DVD resolution (480i/480p for NTSC, 576i/576p for PAL), then refresh metadata and review the name. An unknown DVD system is not guessed.

Missing audio tracks and unidentified audio languages are separate facts. A tracker-specific no-audio label uses inspected evidence that audio is absent. Non-linguistic audio retains its codec and channels; an unknown language does not imply that audio is absent or non-linguistic.

Categories, source/type mappings, descriptions, media selection, questionnaires and authentication requirements can vary. Review the displayed requirements and consult the tracker's current rules. A successful local preparation does not prove that a remote upload will be accepted.

Editions and commentary

A solitary Theatrical cut or edition is ignored. Compound editions retain their constituent cuts and multi-edition marker. Presentation and technical-feature annotations do not establish another edition. Actual additional editions and multi-cut sets remain intact. Fully recognized manual compounds such as Director's Cut / Hybrid separate their meanings; unknown/custom wording stays intact. Use the independent Presentation and Release features controls for corrections without changing Edition.

Review detected labels and inspected tracks before approval. Missing track languages cannot be borrowed from another report without a reliable identity match; correct missing languages explicitly when needed. A separate compatibility stream can match a single suitable mix automatically when its known languages agree and it is not identified as commentary or a distinct mix. Ambiguous associations and current manual choices remain editable. Automatic association does not change inspected track roles or waive independent codec, core, or track-count requirements. Consult the tracker's current rules when interpreting any eligibility finding.

To override commentary detection, set Commentary to Yes or No and refresh metadata, or use --commentary=true / --commentary=false (--mc is an alias). Explicit No survives re-preparation and removes With Commentary. No extra commentary prompt is introduced, including in unattended mode. Older prepared generations must be refreshed to use the new evidence and classification.

Disc region and distributor IDs

Region and distributor fields accept supported suggestions or explicit numeric IDs where applicable. Disc playback zones such as A/B/C are not country codes. If a required value cannot be resolved, correct it on Input and refresh metadata before retrying. Check the destination's current requirements rather than guessing an ID.

Diagnostics

For a tracker defect, follow troubleshooting guidance and collect only the relevant sanitized excerpt. upbrr is intended to redact credentials automatically, but inspect every log and remove any remaining credentials, cookies, tokens, private URLs and unrelated personal information before sharing.

Image hosts and clients

Trackers can restrict usable image hosts or select tracker-specific image/client overrides. Configure a compatible host before media preparation. Confirm the final hosted links and client injection settings per tracker.

Add or update tracker support

Tracker implementation work requires registry, auth, naming, duplicate-search, validation, payload, and test contracts. Read ADDING_TRACKERS.md before changing code.

For a tracker defect, report the smallest sanitized reproduction. Omit private rules, credentials, response bodies, and private URLs unless tracker staff have authorized publication.