Jellysweep

Jellysweep is a cleanup tool for self-hosted Jellyfin servers that removes old, unwatched movies and TV shows by analyzing viewing stats, configured criteria,…

  • Downloaders
  • Media Applications
  • Media Servers
  • Tools & Utilities
Jellysweep is a cleanup tool for self-hosted Jellyfin servers that removes old, unwatched movies and TV shows by analyzing viewing stats, configured criteria, and user keep requests.

Platform availability

Available on 2 of 10 platforms

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

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.

73/100 Good

Maintained
95last commit 8 days ago
Popular
48261 GitHub stars
Easy to install
452 install platforms, install notes, Docker image
Light to run
No data
Security check
88no serious findings, 2 minor, CI, tests

Based on 4 of 5 factors.

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

GitHub stars
261
Open issues
37
Last commit
2026-11-13
Latest release
v0.16.2
License
GPL-3.0
Activity
rising

Checked 7 days ago - source: GitHub (jon4hz/jellysweep)

Resources & Compatibility

Minimum requirements: 100 MB disk.

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

First-install notes

  • Fill in the YAML config before starting Jellysweep reads its main setup from a YAML (plain-text settings) config file, and library settings must be defined in that file instead of environment variables (settings set outside the file). If you skip the Jellyfin URL, API key, or library list, it will not know what to connect to or what to sweep. source
  • Open port 3002 for the web UI The example config uses port 3002 for the web interface, so open that port if you’ll access it from another device. If a firewall or Docker port mapping blocks it, your browser can’t reach the app to log in or manage cleanups. source
  • Enable login or keep access private Jellysweep can run with no authentication if you don’t configure an auth section, which makes the web UI open to anyone who can reach the port. Enable Jellyfin or OIDC (OpenID Connect, a common login protocol) login, or keep the port off the public internet, to avoid unauthorized access. source
  • Test with dry-run mode first Run a dry-run first and review the dashboard or logs to confirm what Jellysweep would mark for deletion. source

Fetched 47 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Where do I define the Jellyfin connection and library settings?

Put the main setup in the YAML config file before starting. Jellyfin URL, API key, and library list must be defined there instead of environment variables.

Which port should I open for the web UI?

Open port 3002 for the web interface if you need to reach it from another device. Make sure Docker port mapping and firewalls do not block it.

Is it safe to run without an authentication section?

It can run with no authentication, but then the web UI is open to anyone who can reach the port. Configure Jellyfin or OIDC login, or keep the port off the public internet.

Answers sourced from github.com

Community

Collected 49 days ago - public community threads