Jellyfin Media Player
Jellyfin Media Player 1.12.0 is an open-source desktop client for a self-hosted Jellyfin server. It combines the web interface with mpv playback and supports hardware decoding, audio passthrough and direct playback for more formats.
What Jellyfin Media Player provides
Jellyfin Media Player 1.12.0 is a desktop client that connects to an existing Jellyfin server and uses a web interface with mpv playback. The client can improve direct-play coverage, hardware decoding and audio passthrough, but it does not include a media server, a library or any media content.
Direct play and transcoding
The server may direct-play, remux or transcode depending on the container, video, audio, subtitle and client capabilities. Burned-in subtitles can consume substantial server resources. Check playback information and server logs before blaming the network or changing several decoder settings at once.
Version and migration boundaries
Version 1.12.0 is the final stable Qt 5 release. The project later moved to Jellyfin Desktop, where a 2.x preview may not migrate old settings automatically. Record the server list, playback preferences and mpv options before upgrading. Review date: 2026-08-23.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave Jellyfin Media Player to this cloud drive
Baidu Netdisk
Save Jellyfin Media Player to this cloud drive
Jellyfin Media Player 1.12.0 installation and server-connection guide
Confirm an accessible Jellyfin server and authorized media first, install the client, test one ordinary video with direct play, and configure hardware decoding or subtitles only after the connection works.
Before you start
- Prepare a reachable Jellyfin server, valid account and any required verification step, and confirm the server version and network path.
- Choose the Windows, macOS or Linux package for the target architecture; verify the operating-system support before installation.
- Use media you own or are authorized to access, and record server transcoding capacity, network bandwidth and display capabilities.
Installation steps
- 01
Install the 1.12.0 build
Choose the matching Windows installer, macOS DMG or Linux package, then verify the version and the client log location after launch.
- 02
Add the server and sign in
Enter the complete server address, protocol, port and any reverse-proxy path, then sign in without saving long-lived credentials on an unknown device.
- 03
Test direct playback
Play a normal H.264 and AAC sample, inspect playback information for direct play, remux or transcode, and then test subtitles, audio tracks and fullscreen.
Quick start
- 01
Calibrate hardware decoding
Change hardware decoding only when CPU use, stutter or display artifacts justify it; change one option at a time and compare client and server logs.
- 02
Check subtitle impact
Compare no subtitles, text subtitles and image subtitles. If enabling subtitles starts transcoding, check client support and server capacity before raising quality settings.
- 03
Record migration details
Save the server list, playback preferences and mpv options, and expect to re-add the server and retest playback when moving to a newer Jellyfin Desktop major version.
Usage tips
- The client stores local configuration, cache, logs and session data; shared devices should sign out and remove sensitive records after use.
- Server permissions, library scope, reverse-proxy settings and transcoding hardware directly affect the client experience.
- Direct play is a compatibility result, not a permanent guarantee; a new subtitle, audio track or device can change the required server path.
Troubleshooting and uninstall
Why is the client blank or repeatedly asking for the server?
Check protocol, port, reverse-proxy path, certificate and server version, then confirm that the same address works in a browser without exposing an access token in logs.
Why is playback buffering while the server CPU is high?
Inspect playback information to confirm transcoding, test without subtitles and at a lower bitrate, then compare client decoding, server codecs, bandwidth and GPU configuration.
- Record server and custom settingsSave the server list and mpv preferences, sign out and confirm that a shared device no longer has a usable session or token in its logs.
- Uninstall and clean local dataExit the client and uninstall it through the operating system, then remove local configuration, cache and logs only when no longer needed; server media is not removed.
Frequently asked questions
Does Jellyfin Media Player include a server or movies?
No. It is a desktop client and must connect to a Jellyfin server that you operate or are authorized to use. The server provides users, libraries, storage and transcoding.
Why does the server still transcode?
Any incompatible container, video, audio or subtitle can trigger remuxing or transcoding. Check playback information first, with burned-in subtitles often requiring more server CPU.
How does 1.12.0 relate to Jellyfin Desktop 2.x?
1.12.0 is the final stable Qt 5 client, while the later project is called Jellyfin Desktop. A major upgrade may require a new server entry and manual preference checks.