TL;DR
Jellyfin published a State of the Fin update covering its seventh anniversary, a major database refactor in version 10.11, and ongoing client work across web, desktop, Android TV, Xbox, Roku and Swiftfin. The team is addressing migration and performance issues from the EF Core refactor, iterating on web theming and layout, and rolling out client-specific improvements and fixes.
What happened
Jellyfin marked its seventh anniversary and published a development roundup outlining recent engineering and client updates. The project shipped version 10.11 after a major EF Core refactor that consolidated legacy library.db into a single jellyfin.db; that change followed six months of development plus six months of release-candidate testing. Post-release, the team has tracked issues in three categories—general, performance, and migration—and delivered four point releases with more than 100 changes to address many of them. Web vNext (10.12/12.0) enabled an Experimental layout by default on non-TV devices and overhauled theming to use CSS variables. Client work includes rebranding Jellyfin Media Player to Jellyfin Desktop and migrating to Qt 6, Android TV updates for music transcoding and codec support, Xbox improvements including gamepad navigation and 4K/HDR support, a Roku patch release, and Swiftfin 1.4 plus a public roadmap. The Tizen app failed review and needs further fixes.
Why it matters
- Large database refactors like the EF Core migration can affect library stability, metadata and user workflows, so ongoing fixes matter for reliability.
- Client-specific changes (desktop Qt migration, Android TV codec support, Xbox gamepad/4K) impact playback compatibility and user experience across devices.
- Web theming and layout changes aim to improve accessibility and customization for users and simplify theme development for contributors.
- Active tracking and multiple point releases show the project is prioritizing post-release issue resolution and community feedback.
Key facts
- Jellyfin celebrated its 7th anniversary in December.
- Version 10.11 consolidated legacy library.db into a unified jellyfin.db via a major EF Core refactor.
- Development for 10.11 included six months of development plus six months of release-candidate testing.
- Post-10.11, the project shipped four additional point releases with over 100 changes addressing mainly general and migration issues.
- Open GitHub issue categories for 10.11 include general bugs, performance bugs, and migration/database bugs.
- Web vNext (10.12 / 12.0) ships an Experimental layout default for non-TV devices and improved theming using CSS variables.
- Jellyfin Media Player has been rebranded to Jellyfin Desktop and migrated from Qt 5 to Qt 6; saved servers and settings will not migrate.
- Android TV releases v0.19.5 and v0.19.6 improved music transcoding (durations, seeking, lyrics) and added VC-1 and broader AV1 direct play support.
- Jellyfin for Xbox added default gamepad navigation (requires server 10.11+), fixes for 4K/HDR, logging uploads, and tighter web UI integration.
- Roku release 3.0.15 (2025-12-18) fixed an HDHomeRun tuner bug; the Tizen app failed review and requires additional fixes.
What to watch next
- Potential versioning scheme change under consideration — the team has discussed dropping major version 10 to make the next release 12.0.
- Upcoming bug-fix releases expected to address remaining music metadata display issues and watched-status preservation.
- Desktop: a future UI for switching servers is planned but its timeline is TBD.
- Swiftfin tvOS release schedule and additional platform support progress — not confirmed in the source.
Quick glossary
- EF Core: A Microsoft object-relational mapper for .NET used to manage database schema and data access in applications.
- Direct play: Playback method where media is sent to a client without server-side transcoding, relying on the client to support the codec and container.
- Transcoding: Converting media from one codec or container to another so it can be played on devices that lack native support.
- Release candidate (RC): A pre-release version of software that is potentially the final product unless significant bugs are discovered.
- Flathub: A software repository that distributes Linux desktop applications packaged as Flatpak, simplifying installation across distributions.
Reader FAQ
Will saved servers and settings migrate to the rebranded Jellyfin Desktop?
Saved servers and settings will not be migrated from Jellyfin Media Player to Jellyfin Desktop.
Are stable builds for Windows and macOS available for the new desktop client?
Stable builds for Windows and macOS are not currently available; releases are present on Flathub and the Arch AUR.
Has the project finalized a change to its versioning scheme?
No; the team is discussing revising the versioning scheme but has not finalized any change.
Does Jellyfin support Ubuntu 24.04 LTS with the new desktop build?
Not currently; Ubuntu 24.04 LTS remains on Qt 6.4 while the desktop depends on at least Qt 6.5.
What happened to the Tizen app?
The Tizen app failed review and requires additional work to reproduce and fix reported issues.
State of the Fin 2026-01-06 January 6, 2026 · 9 min read Bill Thornton Core Team, Web and iOS Lead Happy New Year and welcome to the State of the…
Sources
Related posts
- LEGO launches SMART Play System: interactive bricks, tags and minifigures
- Klipsch to Relaunch Hi‑Fi Headphones With New Atlas Series at CES 2026
- LG launches fastest, brightest OLED gaming monitor at $999.99