Latest release

Find the media nobody watchesSee exactly why before it goes

Reaper is a free, open-source library cleaner for Plex. It reads your watch history, works out what has been sitting untouched for years, and shows you the reasoning behind every single verdict. Then it removes only what you approve, through Sonarr and Radarr.

Get Started View on GitHub

Read-only. Reaper can look but can't remove anything until you turn it on.

Reaper's review queue. Scored titles on the left, each showing how long it has gone unwatched, and a panel on the right breaking down why one of them scored 90.

Every soul gets a verdict, not just the condemned

Not just which rules matched. Reaper shows you every protection it checked and every one that did not fire, with the real numbers behind each. You are never asked to trust a score you cannot take apart.

Built to fail safe

Anything Reaper could not check counts in your favor, never against you. A rating it cannot reach or a user it cannot map can only ever protect a file. That is enforced by the type system, not by good intentions.

It never touches your disks

Reaper has no delete path of its own. It asks Sonarr and Radarr to remove things and refreshes Plex afterwards, so anything neither of them manages can be reported and never removed.

Policy

Tune it, and watch what changes before you save

Policy is intuitive. Flag a movie once it scores 70 out of 100, keep anything watched by three or more people, remove at most ten titles per run. No rule syntax to learn.

Move any number and the panel on the right re-decides your last scan on the spot, with no calls to your services. You can see how many titles change, and why the rest were spared, before you commit to anything.

Cautious, Balanced or Aggressive to start from, then adjust anything.
Movies and TV are tuned separately, because they do not age the same way.
Nothing applies until you save, and then only on the next scan.

Reaper's policy screen. Plain-language sliders on the left, and a panel on the right showing that this draft would remove 240 items and reclaim 1.2 TiB, with a histogram of every title's score against the threshold.

The reap plan

Read the plan before a single request goes out

Nothing is sent straight from a scan. Reaper writes a plan first, listing every request it intends to make, in order, and you can run the whole thing as a practice run that sends nothing at all.

The first item is always a test: the smallest one, on its own, verified before anything else is touched. If it does not go exactly as planned, the run stops there.

Every call is written down before it is made, and again after.
Your own spares and picks sit on top of the policy's verdict.
Executing needs a phrase you type, recomputed from the plan's contents.

Reaper's reap plan. A summary of what the reap removes, a breakdown of why the policy condemned them, and the list of individual API requests it will send, each marked waiting.

Scales

Who asked for what, and who watched it

Requests come in through Seerr and then nobody remembers who asked. Scales keeps the receipts: how much disk each person has been granted, and how much of it they actually watched. Not to shame anybody, but because a title somebody asked for and never played is the easiest thing in the library to let go of.

The top of Reaper's Scales screen: 392 requests across 28 people, nothing currently reclaimable, and one title no longer in the last scan.

Safety

No file is condemned on a maybe

Reaper removes data you cannot get back, from a server other people rely on. So four things are true before a single file is touched, and none of them are optional.

Off until you turn it on

A fresh install can scan, score and explain, and nothing else. The refusal sits in the network layer, so a request that would change something is stopped before it leaves, whatever the rest of the program thinks it is doing.
Nothing goes while it is playing

Reaper checks for an active stream in the moment before each removal, not once at the start of the run. Anything watched since you approved it drops out too.
The evidence is frozen before anything is scored

A scan takes all of its readings first and locks them, and only then works out the verdicts. A service that goes slow or drops out halfway through cannot tip a title one way or the other, because it was already judged on numbers taken before the scoring started.
Caps stop the run, they do not trim it

If a run would exceed the limits you set, Reaper aborts rather than quietly deleting the first N items and calling it done.

What else it does

Careless reapers make orphans

Take a season out from under someone halfway through a show and you have not saved disk, you have made a mess. Each of these exists because the obvious version of the feature would have done exactly that.

Season by season, never a whole show

It keeps the newest seasons, the first season, the specials, and whichever season each viewer is partway through, moving that hold forward the moment they finish one. Ask it to keep a few seasons ahead and someone on season 1 keeps what they are about to reach.

Lists that protect

Never reap anything in the IMDb Top 250. Add keep tags in Sonarr and Radarr, or curate a Plex collection from your phone and Reaper will respect it.

A countdown your users can see

Titles on the way out show up in a Leaving Soon collection in Plex. If somebody watches one, it stays. So does anything you spare by hand.

Limbo, for what it cannot judge

If Reaper cannot check enough of the evidence on a title, it does not guess. The title goes to Limbo and waits for you, instead of being condemned on a thin case.

Defaults that keep more than they remove

Every shipped default errs toward keeping, and the scoring and protections are pinned by tests that fail the moment a verdict changes.

How often things get rewatched

Every title gets years to be rewatched before it can be flagged at all, and anything enough people played recently is kept whatever it scored, however long it has sat.

Works with

Plex Sonarr Radarr Tautulli Seerr

See what is gathering dust

Point Reaper at your library and let it scan. The scythe doesn't swing until you say so.

Get Started Read the manual