Jellyfin Is Dropping Version 10: The 12.0 Debate Explained
In January 2026, the Jellyfin team dropped a quiet but significant announcement in their "State of the Fin" blog post:
"We are considering 'dropping' the major version 10, which would make the next release 12.0."
For a project that has been on version 10.x since 2019, this is a meaningful shift. The announcement sparked immediate discussion on Hacker News, Lemmy, and the Jellyfin forum - with opinions ranging from enthusiastic support to confusion about why version 11 was being skipped entirely.
This article explains what happened, why the team is considering this change, and what it means for the future of Jellyfin.
Why Version 10 Has Lasted So Long
Jellyfin launched in December 2018 as a fork of Emby. The first stable release was version 10.0.0 - inheriting Emby's versioning at the point of the fork. Every release since has been 10.x.y.
This created an unusual situation: Jellyfin has shipped releases as significant as any "major version" in other software projects - complete UI rewrites, database overhauls, new codec support - all under the "10.x" label that implies incremental updates.
The 10.11 release made this problem impossible to ignore.
The 10.11 Versioning Problem
When Jellyfin 10.11.0 shipped in October 2025, many users treated it as a routine minor update. The version bump from 10.10 to 10.11 looked small. The actual change - a complete database migration from raw SQLite to EF Core - was anything but small.
Users who upgraded without backing up their configuration lost watch history. Libraries with unusual structures broke. Performance regressions hit large installations hard.
The community feedback was consistent: the versioning did not communicate the risk level of the upgrade. A change this significant should have been labeled 11.0 at minimum - or even a new major version.
From the State of the Fin:
"We received a substantial amount of feedback regarding our versioning scheme following the 10.11 release, particularly concerning the stability of what are perceived as 'minor' version updates."
Why 12.0 and Not 11.0?
This is the question that generated the most discussion on Hacker News and the Jellyfin forum.
The answer is practical: Emby is currently on version 4.x. Plex has its own versioning. Jumping to 11.0 would still look like a minor increment to users familiar with other software. Jumping to 12.0 creates a clear break - it signals "this is a new era, not just the next point release."
There is also a precedent in the open-source world. When projects make fundamental architectural changes, a major version bump communicates that clearly. Jellyfin 12.0 would be the first release where the version number itself tells users: back up before upgrading, something significant changed.
Some community members on Hacker News pointed out that skipping 11 is unusual and could confuse users. The counter-argument: Jellyfin has been "version 10" for seven years. The number itself has lost meaning. A clean break to 12.0 is more honest than pretending 11.0 is a natural progression.
What Is Planned for 12.0
Based on the State of the Fin and active development branches, the next major release is expected to include:
New Web UI as Default
The "Experimental" layout introduced in 10.11 - with a redesigned navigation, updated UI components, and CSS variable-based theming - will become the default for all non-TV devices. The legacy "Classic" layout will remain available but is no longer the primary interface.
This is the most visible change for end users. The new UI is cleaner, faster to load, and significantly easier to theme.
Theming Overhaul
The CSS variable system introduced in the new web UI makes custom themes dramatically easier to create and maintain. Theme authors will have a stable API to target instead of overriding internal class names that change between releases.
For server admins who use themes like Ultrachromic or JellyFlix, this means themes will be more reliable across updates.
Performance Fixes for Large Libraries
The client-side enumeration issues introduced in 10.11 - where large libraries caused 30+ second load times - are a priority fix for 12.0. The team is investigating ways to push filtering back to the database layer rather than loading entire datasets into memory.
PostgreSQL Support (Roadmap)
The EF Core migration in 10.11 was the prerequisite for external database support. PostgreSQL is on the roadmap for 12.0 or a subsequent release. This would allow Jellyfin to scale to much larger libraries and enable multi-instance setups with a shared database.
Plugin API Updates
Several plugin APIs are being updated to align with the new EF Core database architecture. Plugin authors will need to update their plugins for 12.0 compatibility - similar to the breaking changes that accompanied 10.11.
The Community Reaction
On Hacker News
The State of the Fin post reached the Hacker News front page in January 2026. The discussion was largely positive, with several threads noting that Jellyfin's growth trajectory - from a niche Emby fork to the dominant self-hosted media server - mirrors other successful open-source projects that eventually outgrew their original versioning.
One commenter noted that the 10.11 experience had pushed them to finally build a homelab, which then expanded into a full NAS and self-hosted cloud storage setup. The Jellyfin community's transparency about what went wrong - and what they were doing to fix it - was cited as a reason for trust rather than abandonment.
On the Jellyfin Forum
The versioning discussion on the forum was more mixed. Some users wanted 11.0 for continuity. Others supported 12.0 as a clean break. A vocal minority argued that version numbers do not matter - what matters is clear release notes and mandatory backup warnings.
The team's response was measured: nothing is finalized, but the feedback from 10.11 made it clear that the current versioning scheme was not serving users well.
What This Means for Jellyfin Admins
Short term (now through 10.11.x)
- Stay on the latest 10.11.x point release (10.11.7 as of April 2026)
- Ensure your backup strategy is solid before any future upgrade
- Monitor the GitHub releases page for 12.0 RC announcements
When 12.0 arrives
- Treat it as a major upgrade regardless of how smooth the migration looks
- Back up your entire
/configfolder before upgrading - Wait for the first point release (12.0.1) before upgrading production servers
- Check plugin compatibility - the API changes will break some plugins
The bigger picture
Jellyfin 12.0 represents the project's maturation from a scrappy Emby fork into a serious, architecturally sound media server platform. The EF Core foundation, the new web UI, and the potential PostgreSQL support are not incremental improvements - they are the infrastructure for the next decade of Jellyfin development.
The versioning change is not just cosmetic. It is the project acknowledging that it has grown into something that deserves a number that reflects its ambition.
Jellyfin Turns 7
December 2025 marked Jellyfin's 7th anniversary. From the State of the Fin:
"A lot has changed in 7 years, but we remain steadfast in our commitment to Open Source and to being the best personal media server out there."
Seven years from a fork born out of frustration with Emby's closed-source pivot, Jellyfin now holds 51% of the self-hosted media server market among homelab users. The next seven years - starting with 12.0 - look even more interesting.
Stay ahead of every Jellyfin update - monitor your server from your phone. Download JellyWatch on Google Play - real-time session monitoring, server health, and push notifications for Jellyfin admins on Android.
Comments
No comments yet. Be the first to share your thoughts.
Leave a comment