Superseded by Seerr: in February 2026 the Overseerr and Jellyseerr teams merged into a single project, Seerr, which supports Plex, Jellyfin, and Emby. Overseerr will no longer receive new features or major updates. New installs should use Seerr, and existing users can follow the migration guide at docs.seerr.dev.

Overseerr is the request layer for a Plex server: users browse, request titles, and approved requests flow into Sonarr and Radarr automatically.

Why it exists

Sharing a Plex server generates requests, and without a system they arrive as messages you forget. Overseerr turns that into a queue with status visible to the requester, which removes both the forgetting and the chasing.

Discovery is a real feature here

Overseerr’s interface is built around browsing: trending titles, recommendations based on what is already in your library, and search that clearly marks what you already have. Users often find things rather than arriving with a specific title, which is closer to how commercial streaming apps behave.

Integration and permissions

It authenticates against Plex accounts, so anyone you have shared with can log in without a new account. Granular permissions control who can request what, whether requests need approval, and how many are allowed per week. Requests route to the correct Radarr or Sonarr instance, including separate 4K instances if you run them.

Overseerr or Jellyseerr

Jellyseerr is a fork adding Jellyfin and Emby support. If your server is Plex, Overseerr is the original and is well maintained. If you run or might run Jellyfin, Jellyseerr covers both.

Deployment

Docker, with API keys for Plex and each *arr instance. Like Jellyseerr, it is the piece of the stack that legitimately faces the internet so household members can reach it; put it behind HTTPS.

License

Overseerr is released under the MIT License.

Links

• Website
• Repository