Jellyfin 12: upgrading without the tears
Jellyfin 12 (September 2026; 12.4 is current) is the project's biggest release in years — a new database engine, .NET 10 underneath, FFmpeg 8 for transcoding. It is also a one-way door: once 12 migrates your database, returning to 10.11 requires restoring a full backup. That single fact turns this from an update into a procedure. Here is the procedure.
Published Nov 18, 2026
What 12 changes (and why the door is one-way)
Version 12 replaces Jellyfin's library database with a new engine for speed and scale — the migration runs automatically on first start and is not reversible in place. Around it: the runtime moved to .NET 10 (which is why plugins built for 10.11 will not load until their authors rebuild them), transcoding rides FFmpeg 8.1 with faster CUDA/OpenCL paths and an HLG tone-mapping change that alters how some HDR content renders, and the interface got its new default look. None of this is a reason to wait — 12.4 has had two months of fixes — but all of it is a reason to prepare.
Pre-flight checklist
- Back up the whole Jellyfin config volume — stop the container and copy the entire /config directory (database, users, watch state, everything) somewhere off the NAS. A backup made while Jellyfin runs can catch the database mid-write; stopped is clean.
- Audit your plugins: list every installed plugin and check its repository for a 12-compatible build. The core experience needs none of them; the ones you love (intro skipping, extra metadata sources) are the ones to verify. An incompatible plugin does not block the upgrade — it just silently will not be there after.
- Note your transcoding settings (screenshot the Playback settings page). FFmpeg 8 occasionally resets or renames options; a screenshot turns a mystery into a two-minute restore.
- Check free space: the database migration wants working room on the config volume — a nearly-full SSD is the classic mid-migration failure.
The upgrade itself
- Pull the new image (your tag strategy decides how: Watchtower users will get it automatically — consider pinning Jellyfin to manual updates after this, see below) and recreate the container with the same volumes and ports.
- First start will sit at 'migrating database' longer than feels comfortable on a big library. Let it. The log (Dozzle or docker logs) shows progress; interrupting a database migration is how databases die.
- Sign in and sanity-check in this order: users present, libraries present, watch state present, a stream plays, a transcode engages hardware (next section).
Pin the version after this. An irreversible-update tool should never update itself unattended again. Exclude Jellyfin from Watchtower (label or list) and make its upgrades a deliberate, backed-up, five-minute ritual — the Watchtower guide shows the exclusion pattern.
Verify transcoding on FFmpeg 8
Play something that forces a transcode (a 4K HEVC file to a 1080p client is the classic) and confirm the dashboard's playback info reports hardware acceleration, then check the numbers with the same method as our Quick Sync guide (intel_gpu_top or the ffmpeg log line). FFmpeg 8 changed defaults under the hood; if tone mapping looks washed or crushed on HDR-to-SDR plays, the HLG change is the suspect and the playback settings' tone-mapping options are the fix. CPU transcoding where you used to have QSV almost always means the render-group permission got lost in the container recreation — a thirty-second fix once you know to look.
If it goes wrong
Your rollback is the backup, and only the backup: stop the container, put the 10.11 image tag back, restore the entire /config copy, start. Everything returns, including watch state as of backup time. This is why the pre-flight's first step is the whole game — Jellyfin told everyone, in the release notes, in bold, that there is no other way back. Believe release notes when they bold things.
Official documentation and references
- Jellyfin blog — the official 12.0 release announcement
- Jellyfin on GitHub — release notes for every version
- Jellyfin documentation — server configuration and where it lives
- Jellyfin documentation — the quick start for a fresh install
Frequently asked questions
Can I downgrade from Jellyfin 12 to 10.11?
Only by restoring a full backup of your /config taken before the upgrade, with the 10.11 image. The 12 database cannot be converted back — that is the central fact of this release.
My plugins disappeared after upgrading. Are they gone forever?
They are incompatible, not deleted: plugins built for 10.11 cannot load on the .NET 10 runtime. Check each plugin's repository for a 12 build; most actively-maintained ones have shipped theirs by now.
Should fresh installs use 12 or 10.11?
12, without hesitation — new installs have nothing to migrate and get the new database from day one. This guide's caution applies to upgrades of existing libraries. Migrating from Plex? You land on 12 directly via our migration guide.

