Tags

Organize and link related configuration with simple text labels. Tags are the mechanism Luminarr uses to scope indexers, download clients, and notifications to specific movies.

Overview

What are Tags?

A tag is a short text label — like 4k, anime, or usenet — that can be attached to movies and configuration objects. When a movie and a configuration object share at least one tag, they are considered linked. Luminarr uses these links to restrict which indexers are searched, which download client is used, and which notifications are sent for a given movie.

Tags are purely additive: adding a tag to a movie never removes access to untagged configuration. If a movie has no tags, it uses all untagged configuration objects. If a movie has tags, it uses those tagged objects plus all untagged objects.

Untagged = global. A configuration object with no tags applies to every movie. Only add tags when you need to restrict or direct behaviour for a subset of movies.

Supported Objects

What Can Be Tagged

Movies

Tag movies to direct them to specific indexers, download clients, or notification channels. A movie with a 4k tag will only use indexers and clients tagged 4k (plus any untagged ones).

Indexers

Tag an indexer to restrict it to movies with a matching tag. Useful for niche indexers that only carry specific content types, such as a foreign-language indexer tagged foreign.

Download Clients

Route specific movies to a specific download client. For example, tag a client usenet and only Usenet-sourced movies will be sent to it.

Notifications

Scope notification channels to specific movies. Send Discord notifications only for movies tagged watch-party, or Slack alerts only for movies in your work collection.

Import Lists

Tag an import list to automatically apply that tag to every movie added by the list. Movies from a "Trakt 4K Watchlist" list tagged 4k will inherit the tag on creation.

Libraries

Tag a library so that movies imported into it automatically inherit the library's tags. Keeps tag assignment consistent without manual per-movie work.

Logic

How Tag Matching Works

When Luminarr searches for releases, sends a download, or fires a notification, it checks whether the movie and the target object (indexer, client, notifier) are compatible:

  1. 1

    Does the configuration object have any tags?

    If no tags — the object is untagged — it applies to all movies unconditionally. No further check needed.

  2. 2

    Does the movie have any tags?

    If the movie has no tags, tagged configuration objects are skipped — a tagged indexer is not searched for an untagged movie.

  3. 3

    Do any tags overlap?

    Luminarr checks if the movie's tag set and the object's tag set share at least one tag. If yes, they are linked and the object is used.

A tagged movie with no matching objects. If a movie has tags but none of your indexers share those tags, Luminarr will only search untagged indexers for that movie. If all indexers are tagged and none match, no search is performed. Check your tag assignments if a tagged movie is not getting grabbed.

Example

Example Workflow

A common setup uses tags to separate a 4K library from an HD library, each with dedicated indexers and download clients:

Tag: 4k 
# Objects tagged "4k"
Indexer:         TorznabArr (4K-capable tracker)
Download client: qBittorrent-4K (seeding directory on NAS)
Library:         /data/movies-4k

# Movies added to the 4k library inherit the "4k" tag
# Those movies are only searched on TorznabArr
# Completed downloads go to qBittorrent-4K
# All other indexers and clients remain untagged (apply globally to HD movies)

With this setup, adding a movie to your 4K library automatically routes all of its automation through the 4K-specific stack. No per-movie manual configuration is required.

Tag via import list. If you maintain a "4K Watchlist" on Trakt, create an import list for it and tag the list 4k. Every movie auto-added from that list arrives pre-tagged and routes correctly without any manual intervention.