Media Servers
Automatically refresh your media server library when movies are imported, and compare your Luminarr library against what your server already has using the Library Sync page.
Supported Media Servers
Multiple connections are supported — for example, a Plex server and a Jellyfin server simultaneously. Each configured server receives a refresh notification after every successful import.
Plex
Section-specific library refresh via the Plex Media Server API. Supports local and remote Plex instances.
Jellyfin
Full library refresh via the Jellyfin REST API using an API key. Free and open source.
Emby
Full library refresh via the Emby REST API. Configuration is identical to Jellyfin.
Connection Settings
These fields are common to all three server types. The authentication field name differs between servers.
| Field | Description | Notes |
|---|---|---|
| Name | Display name for this connection | Used in logs and the Library Sync page |
| URL | Base URL of the media server | Include protocol and port. Example: http://192.168.1.10:32400 |
| Token / API Key | Authentication credential | See per-server instructions below |
| Skip TLS Verify | Disable TLS certificate validation | Only enable for self-signed certificates |
| Enabled | Whether this server receives refresh calls | Disabled servers are skipped during imports |
Plex Configuration
| Field | Description | Notes |
|---|---|---|
| URL | Plex Media Server address | http://localhost:32400 |
| Token | Plex authentication token (X-Plex-Token) |
Find it in your Plex account settings or from browser network traffic while logged in to the Plex web UI |
Finding your Plex token: Sign in to app.plex.tv, open any library item, click the three-dot menu, choose "Get Info", then "View XML". The token appears in the URL as X-Plex-Token=....
How Plex refresh works
After a successful import, Luminarr identifies the Plex library section whose path overlaps with the imported file's destination, then requests a targeted section refresh for that path only. This is faster than a full library scan and avoids unnecessary metadata re-fetches for unrelated content.
Jellyfin Configuration
| Field | Description | Notes |
|---|---|---|
| URL | Jellyfin server address | http://localhost:8096 |
| API Key | Jellyfin API key | Create at Dashboard → Advanced → API Keys |
How Jellyfin refresh works
Jellyfin and Emby do not expose a path-scoped refresh endpoint, so Luminarr triggers a full library scan. Jellyfin's built-in change detection ensures only newly added files are processed; existing content metadata is not re-fetched unless it is missing.
Emby Configuration
| Field | Description | Notes |
|---|---|---|
| URL | Emby server address | http://localhost:8096 |
| API Key | Emby API key | Create at Dashboard → Advanced → API Keys |
Emby and Jellyfin share the same API shape. If you have both running, configure them as separate connections — Luminarr will refresh both after every import.
Library Comparison
The Library Sync page compares what Luminarr knows about vs. what your media server has indexed. This helps you find movies in your media server that Luminarr isn't managing, or movies Luminarr is managing that your media server hasn't picked up.
Server-only movies
In your media server but not in Luminarr. You can bulk-add these to start managing them.
Luminarr-only movies
In Luminarr but not in your media server. Usually means the file hasn't been imported yet or the server hasn't scanned the folder.
Matching is TMDB ID only. Movies in your media server without a TMDB GUID are excluded from the comparison. For Plex, ensure your library is using the TMDB agent or has TMDB metadata matched.