Jellyfin
A fully open-source, subscription-free self-hosted media server application. Forked from the Emby project in 2018, it supports deployment on NAS devices, home computers, and servers. Jellyfin collects no telemetry data and is entirely community-driven, with over twenty thousand GitHub stars, making it one of the de facto standards for self-hosted media management.
Core Facts
Jellyfin is completely open-source and free media management software, and is especially popular among privacy-conscious users.
Jellyfin is a fully open-source, subscription-free media server software that evolved independently as a community fork of the Emby project
Jellyfin is a fully open-source and free media streaming service whose codebase originated from an early open-source fork of Emby; Plex's core features are free, but some advanced features require a Plex Pass subscription.
Timeline (last 90 days)
Jellyfin already covers the vast majority of Plex's core capabilities, including transcoding, multi-client sync, and metadata fetching.
Jellyfin is maintained by community volunteers, contains no tracking code, requires no account registration, has no paywalls, and all features are fully available to all users.
Jellyfin's Syncplay feature enables synchronized watching by multiple people.
Home server users commonly deploy applications such as Nextcloud, Jellyfin, and Home Assistant via Docker.
Some users have used Sonnet 5.5 to complete complex tasks such as a JS rewrite of a custom Jellyfin plugin.
The self-hosting ecosystem includes well-known open-source projects such as Jellyfin, Nextcloud, and Home Assistant.
DYSC supports three self-hosted media libraries simultaneously: Jellyfin, Navidrome, and Plex.
A Reddit user, with the help of AI tools, built a complete self-hosted system including Immich, Jellyfin, and Pi-hole in two afternoons and one evening.
Reverse proxy front-end authentication solutions typically cannot deeply integrate with Jellyfin's native user system, and have compatibility limitations on mobile apps or certain clients.
Users can implement front-end authentication by using a reverse proxy combined with an identity gateway (such as Authelia or Authentik) to intercept authentication requests before they reach Jellyfin.
40 more timeline events
All Facts (20)
Jellyfin is completely open-source and free media management software, and is especially popular among privacy-conscious users.
75%VerifiedJellyfin is a fully open-source, subscription-free media server software that evolved independently as a community fork of the Emby project
75%VerifiedJellyfin is a fully open-source and free media streaming service whose codebase originated from an early open-source fork of Emby; Plex's core features are free, but some advanced features require a Plex Pass subscription.
75%VerifiedJellybox is a cross-platform native music client designed specifically for Jellyfin and Emby media servers, covering both desktop and mobile.
65%VerifiedJellyfin was founded in 2018, originating as an open-source fork of the Emby media server.
65%UnverifiedJellyfin supports GPU hardware-accelerated transcoding, such as Intel QSV and NVIDIA NVENC, and offers hardware transcoding as a standard feature free of charge.
60%UnverifiedJellyfin is maintained by community volunteers, contains no tracking code, requires no account registration, has no paywalls, and all features are fully available to all users.
50%UnverifiedJellyfin's Syncplay feature enables synchronized watching by multiple people.
50%UnverifiedJellyfin already covers the vast majority of Plex's core capabilities, including transcoding, multi-client sync, and metadata fetching.
50%UnverifiedHome server users commonly deploy applications such as Nextcloud, Jellyfin, and Home Assistant via Docker.
50%UnverifiedThe self-hosting ecosystem includes well-known open-source projects such as Jellyfin, Nextcloud, and Home Assistant.
50%UnverifiedDYSC supports three self-hosted media libraries simultaneously: Jellyfin, Navidrome, and Plex.
50%UnverifiedThird-party clients such as Infuse and Swiftfin face compatibility issues similar to those of the official mobile app under reverse proxy front-end authentication solutions.
50%UnverifiedJellyfin mobile clients typically establish connections directly with the server, bypassing the browser's cookie-based authentication mechanism, causing reverse proxy front-end authentication to fail.
50%UnverifiedThird-party plugin-based SSO implementations for Jellyfin have long existed in the community, but they are not part of the official mainline, and users must assess their stability and security on their own.
50%UnverifiedReverse proxy front-end authentication solutions typically cannot deeply integrate with Jellyfin's native user system, and have compatibility limitations on mobile apps or certain clients.
50%UnverifiedForcibly layering OIDC on top of an authentication system that has not yet been properly organized may cause new and old logic to intertwine, increasing the risk of security vulnerabilities, and may create technical debt when future refactoring overturns already-merged code.
50%UnverifiedFor production environments or multi-user shared scenarios, caution is advised when using unofficial SSO solutions.
50%UnverifiedJellyfin's lack of native OIDC support makes it an authentication island within self-hosted environments.
50%UnverifiedUsers can implement front-end authentication by using a reverse proxy combined with an identity gateway (such as Authelia or Authentik) to intercept authentication requests before they reach Jellyfin.
50%