Reaper

Reaper finds media that nobody watches, explains why it thinks each item is expendable, and removes it safely through Sonarr and Radarr.

  • Media Applications
  • Media Servers
  • Tools & Utilities
Reaper finds media that nobody watches, explains why it thinks each item is expendable, and removes it safely through Sonarr and Radarr. It reads watch history from Tautulli and pending requests from Seerr, then refreshes Plex when it is done. Deletion is off by default, so a fresh install can only scan, score and explain; you can run it for weeks and just read the results before switching it on. It never touches your files directly — every removal goes through Sonarr and Radarr, so the container needs no access to your media shares. Built for Plex users running Sonarr and Radarr who want to reclaim space from unwatched shows and movies.

Platform availability

Available on 4 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac
  • Windows
  • Linux
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

62/100 Good

Maintained
100last commit 7 days ago
Popular
187 GitHub stars
Easy to install
654 install platforms, install notes, Docker image
Light to run
304 GB minimum RAM

Availability: platform listings confirmed today, links checked 18 days ago

GitHub stars
7
Open issues
1
Last commit
2026-11-14
Latest release
v2026.11.1
License
AGPL-3.0
Activity
steady

Checked 6 days ago - source: GitHub (scythe-labs/reaper)

Resources & Compatibility

Minimum requirements: 4 GB RAM, 6 CPU core(s), 1 GB disk.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • First install On install you choose a channel: Releases is the stable option, while the dev channel follows daily development and changes often. Data-folder ownership is handled automatically on start (PUID/PGID; default 99:100 / nobody:users on Unraid), so no manual chown is needed. Then open the WebUI to begin. Deletion stays off until you enable it — until then Reaper only scans, scores and explains. source

Fetched 48 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does Reaper need read or write access to my media shares?

No. Reaper does not touch files directly; it removes media through Sonarr and Radarr. It only needs its own small data folder.

How can I preview policy changes before they affect my library?

Use the simulator to re-decide the last scan under a draft policy without calling your services. It shows how changing a rule would change the outcome.

How do I turn deletion on after installing Reaper?

A new install is read-only and can only scan, score, and explain. Arm deletion with a password, or set deletion on at first boot.

Which update channel should I run?

Releases is the stable option. The dev channel follows daily development and changes often.

Do I need to manually fix permissions for Reaper’s data folder?

No. Data-folder ownership is handled automatically on start using PUID/PGID, with a default of 99:100 or nobody:users on Unraid.

Can I protect specific media from being reaped?

Yes. You can protect items with Sonarr or Radarr keep tags, a curated Plex collection, or curated lists such as the IMDb Top 250.

Answers sourced from docs.scythelabs.dev, docs.scythelabs.dev, github.com

Community

Collected 49 days ago - public community threads