Sonarr / Radarr instances

One card per instance. Multiple Sonarr and Radarr instances are supported.

**Some of these settings are Kustos's and some are the arr's own.* The difference matters more than anything else on this page, so it is worth stating plainly before the tables start:

• New media defaults are Kustos's. They decide how Kustos adds a title.
• Media Management, Indexer options, Completed download handling, Quality definitions, Root folders and Naming are the *arr's own settings, shown here so you do not have to leave Kustos. They write straight through. Changing one here is exactly the same as changing it in Sonarr or Radarr, and it affects everything that instance does, including work Kustos had nothing to do with.

New media defaults

What an add looks like when Kustos adds something — from the Add form, from an approved request, and from a watchlist set to add automatically. All three, not just the form.

Quality profile and root folder are the two worth setting first. They decide what gets downloaded and where it lands, and before they existed here every add fell through to the instance's first profile and first writable root regardless of what you intended.

Media Management

The instance's own file handling. **These write straight through to the arr.*

Set the recycle bin before you run a single cleanup rule. It is the one setting on this page that turns a mistaken deletion into a recoverable one, and it costs nothing until something goes wrong. Pair it with a non-zero cleanup period so the bin does not grow forever.

Indexer options

Applies to every indexer on the instance. The indexers themselves are on the Indexers tab.

Completed download handling

Quality definitions and TRaSH recommended sizes

The size window — minimum, preferred and maximum megabytes per minute — that the instance will accept for each quality.

You can set each resolution to one of three modes:

How Block actually works, because the table looks broken otherwise. It writes a 1 / 1 / 1 megabyte-per-minute window, which no real release fits, so the *arr rejects everything at that quality. That is why blocked rows show 1/1/1 in the size table rather than an error or a flag.

Qualities with no resolution in the name — Unknown, Raw-HD, disc rips — are grouped separately, since there is no resolution to decide them by. The preview also names TRaSH qualities this instance does not have, so a mismatch between the guide and your *arr is visible rather than silent.

Root folders

The instance's roots. Removing one here stops the *arr offering that location. Nothing on disk is deleted.

Anime profiles

Which quality profiles on this instance mean "anime".

Shows on these profiles get MediUX title-card sets numbered in absolute order (E1…E75) remapped onto their real season and episode — but only when the literal season and episode are not found, so sets that already line up are left untouched.

Kustos also checks these shows are set to Series Type: Anime in Sonarr, which is what makes Sonarr use anime naming and absolute-numbered searches. Setting the profile here without setting the series type there will not do what you want.

Instance tier

Show a 4K marker, set to Mark as 4K, flags a second instance. Kustos guesses this from the port it found the instance on, and that guess is often wrong — a second instance is just as often for kids, anime, or another disk.

Adding a second Sonarr or Radarr

Three settings start interacting the moment a second instance exists, and none of them matter with one. Do them in this order.

1. Connect it in Connections, the same way as the first. See getting your keys if you need the key.
2. Fix the tier straight away. Kustos guesses Mark as 4K from the port and is often wrong. Correct it now, while you remember which instance is which — it is a label and changes nothing about what Kustos sends, but a wrong one is confusing on every screen afterwards.
3. Set the Plex library mapping. This is the question you were never asked with one instance, because there was only one possible answer. Now it decides which Plex libraries this instance feeds, and artwork and collection scoping both read it. An instance mapped to the wrong library sends artwork to the wrong place.
4. Set its New media defaults. Quality profile and root folder especially. A second instance usually exists precisely because its defaults should differ from the first, and leaving them unset falls through to whatever that instance lists first.
5. Point the Seerr routing at the right one. Under Applications → Seerr, Movies go to and Shows go to now have a real choice to make. Before you set them, an approved request lands on whichever instance resolved first, which is nobody's decision.
6. Check anything that names an instance. Arr rules and cleanup rules are scoped per instance, so a rule written when you had one instance still applies to that one only.

It is a label only. It does not change what Kustos sends anywhere. Turning it off removes the marker from every screen at once.

Plex library mapping

Which Plex libraries this instance feeds. Asked only when a second instance of the same type exists — with one Sonarr and one Radarr there is exactly one possible answer, and asking would be pure setup friction.

Artwork and collection scoping read this mapping, so an instance mapped to the wrong library sends artwork to the wrong place.

Naming

The *arr's own naming format, editable here so you do not have to leave Kustos.

Quality profiles

Read from the instance, with per-profile format scores. A drift badge appears when a profile no longer matches what Kustos last saw, so a change made in the *arr's own UI does not silently diverge.

Opening one gives you the full editor:

Grouping qualities, and why you would

Ticking several qualities and grouping them makes them rank equally, so the quality ladder stops deciding between them and custom-format scores break the tie instead.

That is the whole point of it. Without a group, a profile prefers WEB-DL 1080p over Bluray 1080p purely because one sits above the other in the list, whatever the release actually is. Grouped, both are simply "1080p" and the thing that decides is whatever your custom formats say — release group, audio, HDR.

Use the TRaSH grouping replaces the list with the arrangement the guide recommends for that template, rather than you building it by hand.

The ⊘ beside each field is the TRaSH sync pin, and it defaults to excluded here. Red means your value is kept and the guide will not touch it; muted means you have opted that field in and TRaSH keeps it current. Profile fields do not sync unless you say so, and neither do scores: a score changes only when you have marked it keep recommended.

Custom formats (with TRaSH sync)

What TRaSH Guides is, since the wiki leans on the name throughout. TRaSH Guides is a community project that publishes tuned settings for Sonarr and Radarr: which release groups are worth having, what a good file size is at each resolution, and how to score all of it. It is the reference most people end up using, and working it out yourself is weeks of fiddling.

Kustos does not merely point you at it. It fetches their definitions at runtime from the Guides repository, caches them for twelve hours, shows their recommended score beside each of your formats, and writes their formats onto your instances. Matching is by the format's regex specification rather than its name, so renaming a format on your side does not break the link.

Their work is MIT licensed and credited under Settings → Maintenance → Credits, with the licence text in the third-party notices.

Import and score TRaSH Guides custom formats.

• The panel lists formats not on this instance, so you can see what is missing rather than only what is present.
• Excluded formats are ones you have decided never to add; they stop being offered. Excluding does not delete anything — it is a Kustos preference meaning "never add or re-add this one".
• Scores are per profile.

Set up the TRaSH sync

The sync does nothing until a profile is labelled with a TRaSH template, and that is the step people miss. Without it the sync reports no labelled profiles and stops.

1. Browse the templates. TRaSH profile templates on the instance card lists the guide's recommended quality profiles, so you can see what the guide suggests before committing to it.
2. Label a profile with its template. Each profile card has a dropdown for this. The label is what tells the sync which guide rules apply to that profile. A profile with no label is left alone entirely.
3. Add the formats you want. The panel lists what is missing rather than what is present, so the list is the work remaining. Add them from there.
4. Exclude the ones you never want. Search the missing list and exclude them. They stop being offered and stop being re-added by later syncs. This is the step that stops the sync fighting you every night.
5. Set your scores per profile. Only scores you have marked keep recommended are ever set by the sync. Every other score you set by hand is never touched, which is what makes the sync safe to run on a profile you have tuned.
6. **Press Sync from TRaSH.** It previews first. You get a confirmation naming how many formats would be added, how many definitions refreshed, how many scores set, and how many were skipped as excluded, across how many labelled profiles. Nothing is written until you accept.
7. **Turn on Auto nightly if you want it kept current. Note the label: it is all instances**, not this one. It is a single nightly schedule that fans out over every instance with labelled profiles, so turning it on here is not a local change.

Indexers and download clients

The instance's own indexers and clients, editable in place. The specification editor injects real pickers for id-typed fields (quality profile, root folder, tags) rather than asking you to type a numeric id — a wrong number there is a rule that quietly matches the wrong thing.

Each indexer carries four settings of its own, above whatever fields that particular indexer defines:

A toggle the indexer cannot honour is not shown at all, rather than shown greyed. An indexer that does not support searching simply has no search toggles, so you are never left believing you enabled something it will never do.

Download clients carry two:

The remaining fields on both belong to the provider, not to Kustos. They are rendered from the *arr's own schema, so the form is whatever that indexer or client defines, and it stays correct when they change it.

Import lists

The instance's import lists — the feeds that add titles on their own.

These are per list, not per instance, which is the point of them. A list you trust can add and search immediately while a noisier one adds nothing until you look at it.

A list that adds titles is also the thing that undoes a cleanup rule. If a rule deletes something a list still contains, the list puts it back. Prevent re-adding on the cleanup rule is the fix — see what happens when a rule matches.

Auto tagging

Rules that apply tags to titles matching conditions.

• Apply these tags — what to add.
• Conditions — what must match.
• Take the tags back off when a title stops matching — makes the rule maintaining rather than one-shot. Leave it off if something else also owns that tag, or the two will fight: Kustos's arr rules append and collection rules strip the same tag, and a maintaining rule with a co-owner never converges.

Each condition carries two toggles, and they are the same two in the custom format editor:

Start from a preset… fills a new condition from a known-good shape rather than a blank form, which is the quicker way in when you are not sure what the field names mean yet.

Delayed release

How long to wait before grabbing, so a better release has a chance to appear first.