Jellyfin 12.2 Is Current Stable: What Home Server Users Should Do Before Upgrading

Quick answer

Jellyfin 12.2 was released on 5 October 2026 and is the current stable point release. The server release contains 51 fixes, while Jellyfin Web 12.2 contains 17 web-client changes.

The web release also includes a security fix for improper escaping of track titles and external URLs. For the focused 12.2 update procedure and troubleshooting, see Jellyfin 12.2 Update Guide: Fix Scanning, Crashes and Docker Problems.

For a home server, the major migration rules are unchanged: back up first, remove incompatible third-party plugins, let database migrations finish, allow the required first full library scan to complete and keep the old data until the new server has proved stable.

If you are still on 12.0, take a fresh backup and review the 12.1 release notes before troubleshooting a problem that may already have been fixed in the point release.

Before changing a working 10.10.7 or 10.11.x server:

1. take a tested backup and keep the pre-upgrade data
2. check for usernames that differ only by capitalisation
3. remove incompatible third-party plugins
4. record Docker image/package details and hardware-acceleration settings
5. upgrade only Jellyfin
6. allow database migrations to finish
7. allow the required first full library scan to complete
8. hard refresh the browser if the web interface looks wrong
9. verify playback, plugins, clients and remote access
10. keep the old version reference and backup until the new server has proved stable

If you have already upgraded and something looks broadly wrong, use Jellyfin 12 Upgrade Problems: What to Check After Updating.

If the problem is specifically high CPU, memory growth, scanning forever, migration loops or unexpected transcoding, use Jellyfin 12 High CPU, Memory and Scan Problems: What to Check.

What changed between 12.0 and 12.1

Jellyfin 12.0 introduced the major database and library changes. Jellyfin 12.1 is a point release that follows quickly with bug fixes rather than another major migration design.

The 12.1 server release contains 47 fixes, including work across library handling, metadata, performance, scanning and playback-related behaviour.

That means a server already on 12.0 should not treat 12.0 as the preferred long-term target merely because the initial migration completed there. After taking a fresh backup, review the 12.1 changelog and move to the current point release when your maintenance window allows.

Do not interpret 12.1 as proof that every reported 12.0 problem is fixed. There are still configuration-specific issue reports around migrations and library behaviour, so logs and evidence remain important.

Check your current version first

In Jellyfin:

Dashboard → General

For Docker:

docker exec jellyfin jellyfin --version
docker inspect jellyfin --format '{{.Config.Image}}'
docker inspect jellyfin --format '{{.Image}}'

For native Ubuntu:

jellyfin --version
apt-cache policy jellyfin jellyfin-server jellyfin-web

Interpret the result:

10.10.7 or 10.11.x
→ prepare for the major Jellyfin 12 migration

12.0
→ take a fresh backup and review the 12.1 and 12.2 release notes

12.1
→ take a fresh backup, then move to the current 12.2 point release

12.2
→ current stable point release

Back up before upgrading

Jellyfin 12 rewrites database data during the major migration from 10.x.

A proper rollback needs:

previous Jellyfin version
+
matching pre-upgrade data/configuration

Use How to Back Up and Restore Jellyfin Before an Upgrade before changing the server.

If you are already on 12.0, take another fresh backup before applying 12.1. Point releases are smaller than the original major migration, but a working server still deserves a recovery path.

Docker users: make the update intentional

If your Compose file uses a floating stable tag such as:

image: jellyfin/jellyfin:latest

then a normal pull may move you to the current stable point release.

Before pulling:

docker inspect jellyfin --format '{{.Config.Image}}'
docker inspect jellyfin --format '{{.Image}}'
docker compose config --images

Record the current image and keep the backup.

Then update only Jellyfin and verify the server before changing Sonarr, Radarr, Docker Engine or Ubuntu.

Expect the first major-version library scan to be heavy

If you are moving from 10.11 to Jellyfin 12 for the first time, the required first library scan is not a normal routine scan.

It can involve:

• significantly longer scan time
• higher CPU and disk activity
• temporary library ordering changes
• alternate versions appearing different while the scan is still working

A long scan is not automatically a failed scan.

However, if CPU or memory continues climbing, the same items repeat indefinitely, or a migration appears stuck, use the dedicated Jellyfin 12 High CPU, Memory and Scan Problems workflow.

Verify hardware acceleration after the upgrade

After the server itself is stable, verify one known transcode.

Open:

Dashboard → Playback → Transcoding

Confirm the intended hardware acceleration method is still enabled.

For Docker, also confirm the GPU device remains mapped:

docker inspect jellyfin --format '{{json .HostConfig.Devices}}'
docker exec jellyfin ls -la /dev/dri 2>/dev/null

For native Ubuntu:

ls -la /dev/dri 2>/dev/null
getent group render video

Use How to Check Why Jellyfin Is Transcoding before changing FFmpeg, codecs or GPU drivers.

After upgrading

Use this order:

migrations
→ first full library scan
→ users and libraries
→ browser UI
→ plugins
→ one Direct Play file
→ one required transcode
→ hardware acceleration
→ remote access
→ controlled restart/reboot

If anything looks wrong, collect the exact logs before repeatedly restarting or deleting cache/database files.

What SmallGrid readers should do

For most home servers:

Use Jellyfin 12.2 as the current stable target, but keep the same backup-first discipline required by the 12.0 migration.

If you are still on 10.10.7 or 10.11.x, use the full Jellyfin 12 Upgrade Preparation guide.

If you are on 12.0 or 12.1, take a fresh backup and review the 12.2 changelog before updating.

If you are already on 12.2 and the server has high CPU, high memory, a scan that appears stuck or unexpected software transcoding, use the dedicated performance/scanning guide rather than assuming every 12.2 installation has the same bug.

Official sources

• Jellyfin Server 12.2 release
• Jellyfin Server 12.1 release
• Jellyfin 12.0 release notes

Related SmallGrid guides

• Jellyfin 12.2 Update Guide: Fix Scanning, Crashes and Docker Problems
• Jellyfin 12 Upgrade Guide: 10 Things to Check Before You Update
• Jellyfin 12 Upgrade Problems: What to Check After Updating
• Jellyfin 12 High CPU, Memory and Scan Problems: What to Check
• How to Back Up and Restore Jellyfin Before an Upgrade
• Jellyfin Troubleshooting
• Jellyfin Library Not Showing Files
• Jellyfin Not Scanning New Files
• Jellyfin Hardware Transcoding on Ubuntu
• How to Check Why Jellyfin Is Transcoding

Recap

Jellyfin 12.2 is the current stable point release. It contains 51 server fixes, while Jellyfin Web 12.2 contains 17 web-client changes including the track-title and external-URL escaping security fix.

The major migration precautions still matter: preserve a tested backup, keep compatible starting data, remove incompatible plugins, allow migrations and the required first scan to finish, then verify playback and hardware acceleration before calling the update complete.

If you are on 12.0 or 12.1, take a fresh backup and move toward 12.2 rather than treating an earlier 12.x build as the preferred permanent target.

Keep the permanent fix nearby

Affected SmallGrid guides