Jellyfin
Jellyfin turns a drive full of films and series into your own streaming service. Copy your films onto the drive from any computer, plug it into your server, and Jellyfin finds them, fetches the posters and descriptions, and plays them in a browser, on a phone, or on the TV through the Jellyfin apps. Nobody tracks what you watch, nothing is removed because a licence ran out, and there is no subscription to cancel.
Install it from Suite Manager → Apps — once running it lives atjellyfin.<your-domain> and on your Home dashboard.
What you can do
- Your drive becomes a streaming service — MOS makes a Movies and a Series folder on the drive you pick. Fill them from any computer, plug the drive back in, and the films are there with posters and descriptions, ready to play.
- Every screen in the house — Watch in any browser, or install the Jellyfin app on your phone, tablet, smart TV or streaming stick and sign in to your own server.
- Picks up where you left off — Jellyfin remembers how far you got in every film and episode, on every device, and shows what comes next in a series.
- Nothing watches you watching — No viewing history leaves your server, no recommendations are sold, and no title disappears because someone else's licence ended.
A self-hosted Netflix alternative
Jellyfin does the job people use Netflix, Plex, Emby, Disney+, Apple TV, HBO Max, Kodi, XBMC, and Amazon Prime Video for, on a server you own: the same everyday task, without a subscription and without an account at a company that also keeps your data. If you arrived comparing one of these, this is the app My Own Suite installs in its place — its privacy posture below says exactly what it does and does not send anywhere.
- Netflix alternative
- Plex alternative
- Emby alternative
- Disney+ alternative
- Apple TV alternative
- HBO Max alternative
- Kodi alternative
- XBMC alternative
- Amazon Prime Video alternative
Good to know
Jellyfin
External dependencyPrivacy grade C (A is best, D is worst)Something leaves your server in normal use and there is no in-app setting that stops it. MOS reviewed that and accepted it as the price of the feature. The full assessment says exactly what leaves, who receives it, and why.
Contacts 6 hosts outside your server in normal use, before you turn anything on.
api.themoviedb.orgFrom the appimage.tmdb.orgFrom the appwww.omdbapi.comFrom the apprepo.jellyfin.orgFrom the app*.mirror.jellyfin.orgFrom the appwww.gstatic.comFrom your browser
- Resource needs: High resources — Quiet while nobody watches, but converting a film for a device that cannot play it directly keeps several cores busy. MOS gives Jellyfin no graphics card, so that conversion runs on the processor.
- Package-provided privacy notes (not independently verified by MOS): Your films and what you watch stay on your server. Jellyfin looks up posters and descriptions on public film databases, which learn the titles it asks about, and its pages load Google's Cast library for Chromecast.
- Your films stay on your own drive and are only ever read: Jellyfin cannot change or delete them, and no subtitles or artwork are written beside them.
- To show posters, cast lists and descriptions, Jellyfin asks TheMovieDb and OMDb about each title it finds. Those services see your server's address and the titles it looks up, never your viewing history. Each library's settings in Jellyfin can turn them off.
- Jellyfin's pages load Google's Cast library in Chrome and similar browsers so you can send a film to a Chromecast. Google sees your browser's address when a Jellyfin page opens; MOS cannot turn this off without removing casting.
- Jellyfin checks its plugin catalogue for updates. Playing a film never contacts anything outside your server.
Privacy assessment
This is the assessment behind Jellyfin's posture grade, exactly as it ships inside the package. It describes Jellyfin 12.3 as MOS packages it and nothing else — install a different version and its own assessment travels with it. Reviewed 25 October 2026, due for reassessment by 17 January 2027.
What was reviewed
- Package — content digest
42ea4510af48…at commitc51f02165fcb - Jellyfin — version 12.3 from
docker.io/jellyfin/jellyfinpinned at2038fe038ab3…
Deliberately outside this assessment:
- Jellyfin mobile, TV and desktop client apps
- Third-party Jellyfin clients
- Plugins the owner installs from the plugin catalogue
What it connects to
Every host Jellyfin contacts in normal use as MOS ships it, before you turn anything on. The MOS test suite fails this package if it contacts a host this list does not name.
api.themoviedb.orgFrom the appLooks up the title, year, cast and description of each film and series found on the drive. It sees the server's address and the titles asked about.
Received by TheMovieDb
image.tmdb.orgFrom the appDownloads posters and backdrops for the films and series it identified.
Received by TheMovieDb
www.omdbapi.comFrom the appLooks up ratings and descriptions for the films and series found on the drive, through the bundled OMDb plugin. It sees the server's address and the titles asked about.
Received by OMDb API
repo.jellyfin.orgFrom the appReads the plugin catalogue to offer plugins and their updates. It sees the server's address.
Received by Jellyfin project
*.mirror.jellyfin.orgFrom the appThe mirrors the plugin catalogue is served from.
Received by Jellyfin project
www.gstatic.comFrom your browserLoads Google's Cast library in Chrome and other Chromium browsers so a film can be sent to a Chromecast. Google sees the browser's address when a Jellyfin page opens.
Received by Google
Evidence
ObservedWatched on the wire, in a running instance of this package.
A local run of the packaged image (Jellyfin 12.2) on 2026-10-17 created the administrator and a Movies library through the API, found a test film in the read-only folder, and the stored library options showed SaveSubtitlesWithMedia false and EnableRealtimeMonitor true.
Source: Package image built from apps/jellyfin and run under Docker Desktop · checked 2026-10-17
The server's startup log shows the Update Plugins scheduled task running on first start, which reads the configured plugin repository. The task can be disabled under Scheduled Tasks in the dashboard.
Source: Jellyfin 12.2 container log, local run · checked 2026-10-17
The MOS E2E network capture recorded this package on the Hyper-V lab on 2026-10-17, through install with a storage drive, the package's journey (signing in, copying a film onto the drive, plugging it back in, Jellyfin listing the film and playing it in the browser) and a control lookup and connection from each app container. The server looked up and connected to repo.jellyfin.org and ams1.mirror.jellyfin.org (the plugin catalogue and its mirror), api.themoviedb.org and www.omdbapi.com (metadata for the film it found). The browser, on Jellyfin's own pages, loaded https://www.gstatic.com/cv/js/sender/v1/cast_sender.js, Google's Cast sender library, which the web client loads to offer casting to a Chromecast. The test film matched no title, so no artwork was downloaded in this run.
Source: MOS E2E `npm run e2e -- owner app:jellyfin network`, run 20261017-001359-owner-app-jellyfin-network (network/report.md) · checked 2026-10-17
The image bundles the OMDb metadata plugin next to TheMovieDb (the container log shows "Loaded plugin: OMDb 12.2.0.0"), and the web client references the Cast sender library by that URL in its scripts. Jellyfin offers no setting that stops its pages loading it.
Source: Jellyfin 12.2 container on the MOS lab: its log and /jellyfin/jellyfin-web/*.js · checked 2026-10-17
Jellyfin 12.3 server and web are bug-fix releases with no new integration, account or telemetry. Its image has the same entrypoint, user, ports, volumes and environment as 12.2 and still bundles the same metadata plugins, including OMDb. Its web client and plugins name the same external URLs as 12.2's, including the Cast sender library.
Source: Jellyfin v12.3 server and web release notes; package image built from apps/jellyfin and compared with the 12.2 package image under Docker · checked 2026-10-25
ConfiguredRead from the configuration MOS actually ships.
The package mounts the owner's Movies and Series folders read-only and creates every library with SaveLocalMetadata, SaveSubtitlesWithMedia, SaveLyricsWithMedia and SaveTrickplayWithMedia off, so nothing is written beside the owner's files.
Source: apps/jellyfin/entrypoint.sh
DocumentedTaken from upstream documentation, policies or source.
Jellyfin fetches metadata and artwork for library items from external providers enabled per library, TheMovieDb by default for films and series. The providers can be switched off in each library's settings.
Source: Jellyfin documentation, Metadata · checked 2026-10-17
Jellyfin has no account with the Jellyfin project and no telemetry; administrators and users exist only on the server.
Source: Jellyfin project site · checked 2026-10-17
Security
Jellyfin's 2026 advisories include a critical path traversal that could delete or move directories before first-run setup was finished (GHSA-6828-c7cx-hvqm) and an FFmpeg argument injection through subtitle file names (GHSA-wwwm-px48-fpvq). Each is fixed in 10.11.10 or 12.0; this package runs 12.2. Only the newest stable release receives security fixes, so the package follows Jellyfin's releases.
Documented Source: Jellyfin security advisories and security policy · checked 2026-10-17
The film folders are mounted read-only from a drive mounted without executables, device files or setuid, so a flaw like the directory-deletion one reaches only Jellyfin's own settings and cache, which MOS backs up. Jellyfin runs without extra privileges, the Docker socket or a graphics device, on a network of its own apart from the other apps.
Configured Source: apps/jellyfin/manifest.json, system-agents/apps/storage.cjs, system-agents/apps/system-adapter.cjs
Jellyfin trusts MOS's reverse proxy for the visitor's address, so a user whose remote access is switched off can sign in only from the home network. A lab check refused such a user from a public address and let them in from a home address, after a restart and on a new network too.
Observed Source: apps/jellyfin/entrypoint.sh; Jellyfin 12.2 package image on the MOS Hyper-V lab · checked 2026-10-17
What this review does not settle
Published rather than smoothed over. Each of these is a limit of the method, not a finding against the app.
- Jellyfin's pages load Google's Cast library whether or not the owner has a Chromecast. Patching it out of the web client, as the Stirling PDF package does for its pages, would remove casting; it was not attempted in this package version.
- Bundled metadata plugins beyond TheMovieDb and OMDb may contact their own services for other content types, such as music.
Policies read
How this review was produced
- Method — AI-assisted review, human-reviewed by Rasmus Puls at version 12.2 in October 2026
- Model — claude-opus-5-5 (Anthropic)
- Workflow —assess-app-privacy at
008fe9bd8810 - Repository commit —
c51f02165fcb
Technical reference
Maintained alongside the package at apps/jellyfin/README.md and rendered here as-is.
Jellyfin MOS Package
Environment Variables
JELLYFIN_PUBLISHEDSERVERURL: Projected from the app public URL, so clients that discover the server are told its HTTPS address. .NET reads Jellyfin’s settings case-insensitively, which is why the upper-case name the manifest requires still applies.MOS_ADMIN_NAME,MOS_ADMIN_PASSWORD: The administrator the package creates on first start, from the two setup fields.MOS_LIBRARIES: The libraries the package creates, asName|collection type|container pathentries separated by;. Each must match a folder understoragein the manifest.
Volumes And Persistence
config:/config: Server configuration, the library database, users and watch history. Backed up with the suite.cache:/cache: Transcodes and image cache. Rebuilt on demand.
Disable preserves these volumes. Uninstall removes them; the films on the drive are never touched.
Folders On The Owner’s Drive
The manifest declares two folders under storage, required, so MOS refuses the install until the server has a drive formatted as exFAT, NTFS or FAT32. On install MOS creates MOS-files/apps/jellyfin/Movies and MOS-files/apps/jellyfin/Series on the drive the owner picks and mounts them read-only at /media/movies and /media/series. They are not app volumes: the suite backup does not include them and uninstall leaves them on the drive.
Because the mounts are read-only, every library is created with SaveLocalMetadata, SaveSubtitlesWithMedia, SaveLyricsWithMedia and SaveTrickplayWithMedia off, so Jellyfin never tries to write beside the media.
First Start
Jellyfin creates its administrator and libraries only through its API, so entrypoint.sh starts the server and runs a background job against http://localhost:8096:
- Waits for
/System/Info/Public, which answers only once the API is up (/healthanswers earlier). - If
StartupWizardCompletedis false, finishes the wizard withMOS_ADMIN_NAMEandMOS_ADMIN_PASSWORD. - Signs in and creates an API key named
MOS, kept in/config/mos-api-key(mode 0600), so later starts still work after the owner changes the password. - Adds a library for each
MOS_LIBRARIESentry whose path is mounted and not yet a library, with realtime monitoring on. - Calls
POST /Library/Refreshon every start. MOS restarts the container when the drive is plugged back in, so files copied onto it elsewhere are found then; while the drive is attached, Jellyfin’s file watcher picks up changes itself.
A failed step is logged with a MOS: prefix and retried at the next start; it never holds the server back.
Before the server starts, the wrapper also sets KnownProxies in /config/config/network.xml to the container’s gateway, where Caddy’s requests arrive, so Jellyfin takes the visitor’s address from X-Forwarded-For and a user’s “Allow remote connections” setting works. It rewrites that entry on every start because the gateway changes with the network. On first start it also sets LocalNetworkSubnets to the private ranges; the owner can change them afterwards in the dashboard. Jellyfin reads this file only at start.
Health Check
http://jellyfin:8096/health
Transcoding
MOS grants containers no device access, so there is no hardware acceleration: transcoding runs on the CPU with the bundled jellyfin-ffmpeg. Clients that play the file directly use no CPU for it.