Supported Backends
SeerrClient works with all three backends in the Seerr ecosystem. This page explains the differences between them and how SeerrClient adapts its UI based on which backend you are running.
Backend comparison
Section titled “Backend comparison”| Feature | Jellyseerr | Overseerr | Seerr |
|---|---|---|---|
| Project status | Active | Maintained | Active |
| Primary media server | Jellyfin / Emby | Plex | Jellyfin + Plex |
| Watchlist sync | Jellyfin watchlist | Plex watchlist | Jellyfin + Plex |
| Auth: Local login | Yes | Yes | Yes |
| Auth: Plex OAuth | Yes | Yes | Yes |
| Auth: Jellyfin/Emby | Yes | No | Yes |
| API compatibility | Full | Full | Full (superset) |
| Recommended for | Jellyfin/Emby users | Plex users | Both |
| SeerrClient support | Full | Full | Full |
Jellyseerr
Section titled “Jellyseerr”Jellyseerr is an active fork of Overseerr designed for Jellyfin and Emby users. It adds Jellyfin/Emby authentication, Jellyfin watchlist sync, and multi-media-server support.
SeerrClient has full Jellyseerr support including:
- All three auth methods (Local, Plex OAuth, Jellyfin/Emby)
- Watchlist tab (Jellyfin watchlist sync)
- Self-signed certificate support for local Jellyfin installs
Jellyseerr is the recommended backend if your media library runs on Jellyfin.
Overseerr
Section titled “Overseerr”Overseerr is the original media request manager, built for Plex. It is well-maintained and widely deployed.
SeerrClient has full Overseerr support. The Watchlist tab is not shown on Overseerr (Plex watchlists use a different mechanism that Overseerr handles server-side). Auth methods shown are Local and Plex OAuth.
Overseerr is the recommended backend if your media library runs on Plex.
Seerr is an active fork that extends both Jellyseerr and Overseerr. It supports Jellyfin, Plex, and Emby simultaneously, adds additional features, and maintains API compatibility with both upstream projects.
SeerrClient has full Seerr support. Because Seerr’s API is a superset of Jellyseerr and Overseerr, all features work. The features shown in SeerrClient (including the Watchlist tab) adapt based on your Seerr server’s configuration.
How SeerrClient detects your backend
Section titled “How SeerrClient detects your backend”When you connect a server, SeerrClient calls GET /status on your server. The response identifies the backend type and version. SeerrClient uses this to:
- Show only the auth methods your server has enabled
- Show or hide the Watchlist tab
- Adapt any backend-specific behaviour in requests and settings
You do not need to specify which backend you are running — the detection is automatic.