Jellyfin: The Free Software Media System

Original Article ↗ Hacker News Discussion ↗

Emby/Plex/Kodi Comparison & Licensing

  • Jellyfin is a fork of Emby from before Emby went closed‑source; it keeps all core features free (including hardware transcoding) with no paid tiers or ads.
  • Compared to Plex, Jellyfin is praised for avoiding “enshittification” (no injected streaming content, no cloud login requirement) but widely viewed as less polished in UX and client support.
  • Several users say Jellyfin now matches or surpasses Plex for their needs; others feel it’s where Plex was ~5 years ago and still not worth switching if you already have Plex Pass.
  • Kodi is seen as great for purely local playback; Jellyfin complements it by adding multi-user, remote access, transcoding, and watch history.

Clients, UI & UX Quality

  • Big spread of experiences: some find the web UI and Android/TV apps fast and smooth; others report laggy scrolling, visible placeholder tiles, and general “web page” feel even on fast LANs.
  • Apple TV / iOS: native Jellyfin clients (notably Swiftfin) are criticized as unstable or janky; many people solve this by using Infuse or other third‑party players against Jellyfin.
  • Console and TV platforms: lack of official PS5 app and patchy support for Tizen/Samsung, LG, etc., are recurring pain points. Some rely on DLNA or browser workarounds.

Performance, Transcoding & Codec Support

  • Jellyfin uses ffmpeg (with optional hardware accel) and supports AV1 “if the device does,” with server‑side transcoding as needed.
  • Some users get rock‑solid 4K HDR/Dolby Vision + Atmos/DTS passthrough on Shield or similar; others report stutter, audio desync, or fallback to stereo where Plex works fine.
  • There is debate over auto HDR→SDR tone mapping: some value it highly for mixed-display setups; others argue SDR masters are usually preferable.

Library Management & Features

  • Strengths: on‑the‑fly bitrate downgrades for poor networks, multi-user logins, SyncPlay/watch‑together, rich metadata plugins, trailers (if enabled), trick‑play thumbnails, live TV via plugins (Ersatztv/Tunarr, HDHomeRun etc.).
  • Weaknesses:
    • Strict expectations for folder/filename layouts, especially for TV, music, and disc structures; some users give up after failed attempts and find Plex more forgiving.
    • Movies/TV separation annoys people who want unified franchises (e.g., Star Trek across shows + films).
    • No strong Netflix‑style recommendation engine; some don’t miss it, others do.
    • Blu‑ray folder (BDMV) support via concatenation/transcode is seen as fragile and frequently broken.

Scale, Reliability & Large Libraries

  • One commenter claims Jellyfin “simply does not work” beyond ~1000 items; multiple others contradict this, reporting smooth operation with multi‑TB, tens‑of‑thousands‑files libraries given decent hardware and SSD-backed DB.
  • Music libraries: workable but weaker than dedicated music servers; issues include slow rescans, poor CUE support, and simplistic queue UI.

Remote Access, Networking & Security

  • Common patterns: Jellyfin behind nginx/Caddy/Traefik/SWAG, with local DNS for pretty hostnames and HTTPS; or fully private via Tailscale/WireGuard/ZeroTier.
  • There’s concern about exposing Jellyfin directly to the internet; many recommend VPN-based access or at least reverse proxies with tight rules.
  • Cloudflare Tunnel is used by some, though ToS and “no streaming” concerns are raised; others prefer Tailscale for app compatibility.

Ecosystem & Use Cases

  • Heavily used with Radarr/Sonarr/*arr, Filebot, MakeMKV, HandBrake, yt‑dlp, etc.
  • Use cases include ripped DVDs/BDs, home videos, OTA live TV+DVR, curated YouTube for kids, and sharing with friends over VPN.
  • Some users prefer the simplicity of SMB/NFS + VLC, but others emphasize Jellyfin’s advantage for guests, watch tracking, transcoding, and multi-device convenience.

Community, FOSS Expectations & Criticism

  • Strong appreciation for a volunteer‑run, ad‑free, fully FOSS media server; several people donate.
  • Debate over “don’t complain, send PRs”: some argue criticism and UX pain reports are valuable even if users can’t contribute code; others stress maintainers’ need to avoid hacks and platform-specific one-offs for long-term sustainability.