How jellyfin/jellyfin works
Jellyfin is a self-hosted media server for organizing a media library and streaming it to client devices. A typical user requests library content or playback through the API; the server resolves and queries media, returns item data, or prepares a stream. The map also includes metadata providers, user/session services, and database persistence as important supporting capabilities. Some edges reflect explicit README statements or source-index references; links to unsampled subsystems are omitted rather than inferred.
Main entry points: LibraryManager.cs Library manager · ItemsController.cs HTTP API · DynamicHlsController.cs HLS endpoints · ProviderManager.cs Metadata providers
Components 22
API and access
- HTTP API
Jellyfin.Api/Controllers/ItemsController.cs - HLS endpoints
Jellyfin.Api/Controllers/DynamicHlsController.cs - Authentication
Emby.Server.Implementations/HttpServer/Security/AuthService.cs - Item responses
Emby.Server.Implementations/Dto/DtoService.cs
Library and metadata
- Library manager
Emby.Server.Implementations/Library/LibraryManager.cs - Media item model
MediaBrowser.Controller/Entities/BaseItem.cs - Video model
MediaBrowser.Controller/Entities/Video.cs - Library contract
MediaBrowser.Controller/Library/ILibraryManager.cs - Name resolution
Emby.Naming/Video/VideoResolver.cs - Metadata providers
MediaBrowser.Providers/Manager/ProviderManager.cs - Photo provider
Emby.Photos/PhotoProvider.cs - Library search
Emby.Server.Implementations/Library/Search/SearchManager.cs
Playback and sessions
- Transcode manager
MediaBrowser.MediaEncoding/Transcoding/TranscodeManager.cs - Encoding helper
MediaBrowser.Controller/MediaEncoding/EncodingHelper.cs - Session manager
Emby.Server.Implementations/Session/SessionManager.cs - Synchronized playback
Emby.Server.Implementations/SyncPlay/SyncPlayManager.cs
Persistence and users
- Item query
Jellyfin.Server.Implementations/Item/BaseItemRepository.Querying.cs - Query translation
Jellyfin.Server.Implementations/Item/BaseItemRepository.QueryBuilding.cs - Database context
src/Jellyfin.Database/Jellyfin.Database.Implementations/JellyfinDbContext.cs - User records
src/Jellyfin.Database/Jellyfin.Database.Implementations/Entities/User.cs - User management
Jellyfin.Server.Implementations/Users/UserManager.cs
Other components
- Client device
Connections 20
- Client device → HTTP API: requests content
README.md - Client device → HLS endpoints: requests playback
README.md - HTTP API → Authentication: authenticates
- Library manager → Video model: resolves items
Emby.Server.Implementations/Library/LibraryManager.cs - Library manager → Name resolution: uses naming
Emby.Server.Implementations/Library/LibraryManager.cs - Library contract → Library manager: implemented by
Emby.Server.Implementations/Library/LibraryManager.cs - Metadata providers → Library manager: uses library
MediaBrowser.Providers/Manager/ProviderManager.cs - Metadata providers → Photo provider: loads providers
- HTTP API → Library manager: queries items
- HTTP API → Item responses: returns item data
- HTTP API → Library search: searches library
- HLS endpoints → Transcode manager: requests transcoding
Jellyfin.Api/Controllers/DynamicHlsController.cs - HLS endpoints → Encoding helper: uses encoding
Jellyfin.Api/Controllers/DynamicHlsController.cs - HLS endpoints → Library manager: looks up media
Jellyfin.Api/Controllers/DynamicHlsController.cs - HLS endpoints → Session manager: checks user state
- Synchronized playback → Session manager: coordinates sessions
- Item query → Query translation: builds queries
- Item query → Database context: queries database
Jellyfin.Server.Implementations/Item/BaseItemRepository.Querying.cs - Query translation → Database context: translates queries
Jellyfin.Server.Implementations/Item/BaseItemRepository.QueryBuilding.cs - User management → User records: manages users
Jellyfin.Server.Implementations/Users/UserManager.cs