Cleanarr

Get your storage back without losing what you love.
Rule-based library cleanup for Sonarr and Radarr, driven by what your household actually watches and requests.

Quick start · How it works · Safety · Rules · Reference

Your library is full. Deciding what goes is the hard part.

Nobody wants to scroll four thousand titles asking did anyone ever watch this? And nobody wants an automation that guesses.

Cleanarr asks the questions you would, across your whole library, and shows its working:

Added over a year ago. Nobody has watched it in six months. The person who requested it already has. It isn't tagged "keep".

Match those, and it queues the title for removal with a countdown. Miss any one, and it leaves it alone.

Why Cleanarr

How it works

flowchart LR
    A["<b>Rules</b><br/>what you'd remove,<br/>what you'd keep"] --> B["<b>Preview</b><br/>every match,<br/>with the reasons"]
    B --> C["<b>Queue</b><br/>a countdown you<br/>can cancel"]
    C --> D["<b>Re-check</b><br/>live data, right<br/>before the write"]
    D --> E["<b>Reclaim</b><br/>delete, unmonitor,<br/>or free the files"]
    E --> F["<b>Audit trail</b><br/>what, why, when"]

1. Connect Sonarr and Radarr, then add Plex and Seerr if you want rules that use watch history and requests.
2. Describe what should go with a template or the condition builder, and what should always stay with protect rules.
3. Preview everything that would match, with the reasons, while nothing is changed.
4. Go live when the preview looks right. Matches queue, count down, are re-validated, and are removed. You can step in at any point.

A schedule is optional. Run it daily, weekly or monthly, or press Reclaim now when you want space back.

Built to never surprise you

Safety is the product. Cleanarr is deliberately cautious, and each layer assumes the one before it might be wrong.

What you can ask it

Rules are plain conditions combined with and, or and not, evaluated in priority order.

What it can do to a match:

• Delete: remove from Sonarr or Radarr and delete the files
• Unmonitor: keep everything, stop downloading
• Delete files: keep the entry, free the space
• Delete season: Sonarr only, one season at a time

Different actions for movies, continuing shows and ended shows are a single rule away.

Start from a template: Added and not watched for 60 days, Last watched over a year ago, Requester watched it, no one since, Ended series with no monitored seasons, Protect kids content, Protect anything watched recently, Protect new additions, Protect fresh requests, Protect the "keep" tag, Protect shows still airing. Rules can be imported and exported as JSON.

Your day-to-day

Quick start

Docker

docker compose up -d --build        # then open http://localhost:8080

Node 22+

npm install
npm run build
CLEANARR_API_KEY=change-me npm start

Unraid: add the template manually from https://raw.githubusercontent.com/Daneng66/Cleanarr/main/unraid/cleanarr.xml. The image is ghcr.io/daneng66/cleanarr.

Then:

1. Instances: add Sonarr and Radarr, plus Plex and Seerr if you use them. Use the Plex server owner's token so every user's history is visible.
2. Rules: pick a template or two.
3. Dashboard: read the preview and press Why? on a few titles.
4. Settings: when you trust it, turn off dry run.

Set CLEANARR_API_KEY if the port is reachable by anyone else on your network.

Reference

{ "op": "and", "of": [
  { "type": "age", "params": { "operator": "older_than", "days": 365 } },
  { "type": "last_watched", "params": { "operator": "not_watched_in_days", "days": 180 } },
  { "op": "not", "of": { "type": "tag_match", "params": { "operator": "includes_any", "tags": ["keep"] } } }
] }

npm run dev:api     # API with tsx watch, on :8080
npm run dev:web     # Vite dev server for the React UI
npm run typecheck   # server and web
npm test            # vitest: rules, engine safety paths, Plex/Seerr providers, API
npm run build       # tsc → dist/, vite → dist/web