Seerr: the request front door your media stack was missing

In June 2026, Overseerr and Jellyseerr — the twin request apps for Plex and Jellyfin — merged into a single project: Seerr. The old apps are deprecated; new installs should go straight to Seerr. If your *arr stack has no request layer, your household is texting you titles. This guide installs Seerr, wires it to Radarr and Sonarr, and gets the filesystem layout right so downloads hardlink into your library instantly instead of copying gigabytes.

Published Nov 18, 2026

Why the merger matters (and what to do with old installs)

Two codebases doing the same job for two media servers was always going to end this way. Seerr v3.3.0 unified them: one app, sign-in with either Jellyfin or Plex, and an automatic database migration for existing Overseerr/Jellyseerr installs. Running an old install? Migrate in place (back up its config first, as always). Starting fresh? Skip the ancestors entirely — any guide still telling you to newly install Jellyseerr in late 2026 is out of date, including, until now, parts of the wider *arr literature. Our own *arr stack guide now points here for the request layer.

One /data mount→Deploy Seerr→Connect Radarr + Sonarr→Connect Jellyfin→Test a request end-to-end

The filesystem: hardlinks are the whole game

The number-one *arr failure is invisible: downloads 'import' slowly and your disk fills twice as fast as it should. The cause is layout. Hardlinks — two filenames, one file on disk, zero copying — only work when the download folder and the library folder live on the same filesystem under one mount in every container. The TRaSH Guides layout is the canonical answer:

# One top-level share, mounted identically in qBittorrent, Radarr, Sonarr AND Seerr's stack:
/data
├── torrents/          # downloads land here (movies/ and tv/ subfolders)
└── media/
    ├── movies/
    └── tv/

# In each container's Compose, the same single line:
volumes:
  - /volume1/data:/data

Deploy and connect

services:
  seerr:
    image: ghcr.io/seerr-team/seerr:latest
    container_name: seerr
    environment:
      - TZ=America/New_York
    volumes:
      - ./seerr/config:/app/config
    ports:
      - "5055:5055"
    restart: unless-stopped
  1. First run: sign in with your Jellyfin (or Plex) account — that account becomes the admin. Seerr pulls your libraries from the media server automatically.
  2. Settings → Services: add Radarr and Sonarr with their API keys, test each connection, and set the default quality profile and root folder (/data/media/movies and /data/media/tv) to match the layout above.
  3. Add your download client's categories so requests land in torrents/movies and torrents/tv — the subfolder discipline is what lets the *arrs find and hardlink cleanly.
  4. Create accounts for the household (or let them sign in with their Jellyfin accounts) and set request quotas if your disk has opinions.

The end-to-end test

Request something you do not own, as a non-admin user, from a phone. You should watch it flow: Seerr marks it requested → Radarr grabs it → the download completes → import is near-instant (hardlink) → Jellyfin shows it, and Seerr flips it to Available and notifies the requester. If import takes minutes proportional to file size, the layout is wrong — go back to the /data section, because that slowness is the sound of copying. If Jellyfin does not show it, check that Seerr's Jellyfin sync ran and that the library paths match Radarr's root folder exactly. Once this loop closes, the stack is done: the Compose generator's Media preset plus this guide is the complete, current 2026 media stack.

Gear for this build

Prices are editorial and change often; buttons show live prices. Some links may earn a commission at no cost to you — see the disclosure page.

Will your imports hardlink — or silently copy? Run your volume layout through the hardlink checker: it resolves your mounts the way Sonarr and Radarr see them and hands back the corrected single-/data layout if yours would copy.

Official documentation and references

Frequently asked questions

I already run Jellyseerr. Do I have to start over?

No — Seerr migrates existing Overseerr and Jellyseerr databases automatically on first run against the old config. Back up the config folder first, then swap the image; users, requests and settings carry over.

Why do my imports copy instead of hardlinking?

Your downloads and library are on different mounts from the containers' point of view. Hardlinks need one shared filesystem: mount a single /data (containing both torrents/ and media/) into every container in the chain, exactly as this guide lays out.

Does Seerr work with both Jellyfin and Plex?

Yes — the merger unified the two apps. You sign in with your media server account and Seerr syncs libraries and users from it, whichever server you run.

Related guides