Jellyseerr: Media Request Manager for Jellyfin and Plex
Last updated on

Jellyseerr: Media Request Manager for Jellyfin and Plex

Merged into Seerr: in February 2026 Jellyseerr and Overseerr merged into a single project, Seerr, with one shared codebase supporting Plex, Jellyfin, and Emby. New installs should use Seerr, and existing users can follow the migration guide at docs.seerr.dev.

Jellyseerr gives the people using your media server a way to request content without touching the automation stack behind it.

The problem it solves

Once you share a media server, requests arrive by text message and get forgotten. Handing everyone access to Sonarr and Radarr is not the answer, since those interfaces expose quality profiles, indexers, and file management that nobody else should be near.

Jellyseerr is the front door: users browse a clean catalogue, request a title, and, once approved, it is passed to Radarr or Sonarr and appears in the library automatically. Users can see the status of their own requests, which stops the follow-up questions.

Fork context

Jellyseerr is a fork of Overseerr that adds Jellyfin and Emby support alongside Plex. If you run Plex only, either works; for Jellyfin, this is the one.

Features worth configuring

Per-user request limits and auto-approval rules, so trusted household members bypass the queue while others do not. Notifications through Discord, email, or ntfy. Users authenticate against your media server accounts, so there is no separate user list to maintain.

Deployment

A Docker container that needs network access to your media server and *arr instances, plus API keys for each. It is the one component of a media stack that is reasonable to expose to the internet, since household members need it from outside; put it behind a reverse proxy with HTTPS.

License

Jellyseerr is released under the MIT License.