Jellyfin 12.2 Released With Dolby Vision, Transcoding and Security Fixes

Jellyfin 12.2 is now available as a stable maintenance release focused heavily on playback reliability, transcoding behavior, Dolby Vision compatibility, subtitles, database stability, and Jellyfin Web security.

Rather than introducing another major interface redesign, this update concentrates on fixing the problems users are most likely to notice while actually watching media.

One of the most important changes affects Dolby Vision Profile 8, where Jellyfin now uses the hvc1 codec tag in the relevant playback path. The release also improves video quality when reducing bit depth at low bitrates, prevents the transcode segment cleaner from removing MKV-remux segments too early, improves graphical subtitle delivery, and corrects several audio-transcoding behaviors.

Jellyfin Web receives its own significant update. A security issue involving improperly escaped track titles and external URLs has been addressed, while the “Are you still watching?” prompt is now disabled by default. Multiple web interfaces, subtitle, live TV, Samsung, and navigation fixes are included as well.

For users running Jellyfin as the center of a large home-media system, 12.2 is therefore less about adding something flashy and more about making existing playback paths behave correctly.

Jellyfin 12.2 at a Glance

Dolby Vision Profile 8 Gets an Important Compatibility Fix

Dolby Vision continues to be one of the most complicated areas of modern personal-media playback.

A file may technically contain Dolby Vision while also carrying an HDR10-compatible base layer. Different Dolby Vision profiles package the information differently, and different televisions or streaming boxes advertise different levels of support.

Jellyfin 12.2 changes the codec tag used for the relevant Dolby Vision Profile 8 playback path to hvc1.

That small-looking metadata change can have a major effect.

Clients do not decide whether they can play video purely by examining the visible resolution and codec name. Container metadata and codec tags can influence how the media pipeline interprets the stream.

If the server presents the stream using a tag a device or application does not expect, the client may refuse Direct Play even when the underlying hardware can actually decode the video.

The server may then remux or transcode unnecessarily.

Using the correct HVC1 behavior improves the chances that compatible Dolby Vision media reaches the intended decoder through the correct path. Jellyfin’s earlier Profile 8 compatibility issues had already demonstrated how server-side classification can affect whether capable Android TV and webOS devices Direct Play, remux, or fall back to conversion. 

Why Avoiding Unnecessary Dolby Vision Transcoding Matters

Dolby Vision files are often large 4K HEVC sources.

If a server can directly play one of those files, the server primarily needs to read the media and deliver it over the network.

If Jellyfin instead decides the video must be transcoded, the server may suddenly need substantial GPU or CPU resources.

That can create multiple disadvantages.

Picture quality can be reduced. HDR metadata may need to be converted or discarded. Power consumption increases. Lower-powered NAS systems may simply be unable to transcode the file fast enough.

Correct media identification is therefore critical.

The best playback fix is often not making transcoding faster—it is avoiding transcoding when the client already supports the original file.

Low-Bitrate Transcoding Quality Has Been Improved

Not every Jellyfin client has enough bandwidth for Direct Play.

Remote users may intentionally request a lower streaming quality. Mobile connections can fluctuate. Some server owners also impose bitrate limits to prevent one remote playback session from using too much upstream bandwidth.

Jellyfin 12.2 addresses video-quality problems at low bitrates when reducing bit depth.

Bit-depth conversion can be necessary when the source format contains more color information than the target playback profile supports.

The problem becomes especially visible when that conversion is combined with aggressive bitrate reduction.

Poor transcoding decisions can produce banding, damaged gradients, blockiness, and loss of detail.

The new correction is therefore particularly useful for remote playback rather than only local 4K viewing.

A user watching from outside the home may not receive the original video, but the transcoded result should now better preserve quality within the selected constraints

MKV Remuxing Gets a Critical Playback Reliability Fix

Another important server fix involves the segment cleaner used during MKV remuxing.

Streaming clients often do not receive one giant media file from beginning to end.

Jellyfin may package content into smaller streaming segments that the client requests progressively.

The server also needs to clean old segments so temporary storage does not grow indefinitely.

The difficulty is determining which segments are truly safe to delete.

In the affected scenario, the cleaner could remove segments that were still ahead of the current playback position.

That creates an obvious problem: the client eventually requests a segment that no longer exists.

The viewer may experience buffering, playback stopping, or unexplained stream failures.

Jellyfin 12.2 corrects this behavior.

For users who experienced strange failures partway through remuxed MKV playback, this may be one of the most practically important fixes in the release.

Graphical Subtitles Are Now Served Differently

Subtitles receive another significant backend improvement.

Jellyfin 12.2 can serve graphical subtitles as raw files with HTTP range support.

Unlike SRT-style subtitles, graphical subtitle formats store subtitle content as images.

Blu-ray and DVD-derived libraries frequently contain these formats.

Serving them efficiently can be more complicated because clients may need access to specific portions of the subtitle stream while seeking or changing playback position.

Range support allows a client to request only the necessary portion of the file instead of repeatedly processing the whole resource.

This should improve subtitle delivery and make seeking behavior more reliable for compatible clients.

Embedded VobSub Rendering Is Fixed in Jellyfin Web

The web client also addresses a related subtitle issue.

Embedded VobSub subtitles could fail to render correctly.

VobSub is an image-based subtitle format commonly associated with DVD media.

For users who preserve older disc libraries inside MKV containers, VobSub remains relatively common.

The fix means the browser client should handle those embedded subtitle tracks more reliably instead of requiring users to find or convert an external text subtitle file.

This complements the server-side graphical-subtitle improvements and shows that subtitle handling remains an important focus across both sides of the Jellyfin stack.

Stereo Downmixing Becomes More Consistent

Jellyfin 12.2 also changes how the stereo downmix filter is applied during progressive audio transcoding.

A source may contain 5.1, 7.1, or another multichannel audio layout while the playback client requests stereo.

In that situation Jellyfin needs to combine multiple channels into a two-channel output.

If the appropriate filter is not applied consistently, playback behavior can differ depending on which transcode route is selected.

The update makes the downmix process more predictable.

For users, the expected result is simple: if the playback profile requests stereo, the server should reliably produce a proper stereo output rather than behaving differently between similar streaming paths.

Jellyfin Web Includes an Important Security Fix

The web client receives a security-focused correction involving track titles and external URLs that were not being escaped correctly.

Escaping is an important part of web application security.

When user-controlled or metadata-derived text is displayed inside a web interface, special characters need to be treated as content rather than executable markup or script.

The corrected behavior reduces the chance that specially crafted metadata or external-link content could be interpreted incorrectly by the browser.

Jellyfin identifies minor releases as important vehicles for both bug fixes and security corrections, so server administrators should avoid treating them as optional cosmetic updates. 

“Are You Still Watching?” Is Now Disabled by Default

Another user-visible Jellyfin Web change involves the “Are you still watching?” prompt.

The prompt is now disabled by default.

These interruptions are familiar from commercial streaming services, where playback stops after several episodes unless the viewer confirms they are still present.

That model can reduce unnecessary streaming bandwidth, but it is less attractive in a self-hosted environment.

A Jellyfin user may intentionally play a long television playlist, music videos, background content, or several episodes without wanting an interruption.

Disabling the prompt by default puts control back in the hands of the server owner and viewer.

Users who still want this kind of playback confirmation can configure their environment accordingly.

Search Gets More Flexible

Jellyfin Web also removes its previous 40-character search restriction.

This is useful for content with long names, detailed episode titles, or more complicated search queries.

The change may seem small, but search limitations become increasingly noticeable as personal libraries grow.

Jellyfin also improves internal search behavior around multiple writing systems, helping its server-side discovery features work better for international libraries.

For users maintaining anime, foreign-language cinema, or multilingual collections, those improvements can make content easier to find without manually navigating through folders.

Samsung Tizen Playback Gets an OPUS Compatibility Correction

Samsung users receive a specific format-profile change.

Jellyfin Web now drops OPUS from MP4, MPEG-TS and HLS-TS profiles on Tizen.

This is another example of why codec support cannot be evaluated in isolation.

A television may support a particular audio codec in one container while failing when the same codec is delivered through another container or streaming protocol.

If Jellyfin advertises an unsupported combination, the server may incorrectly choose Direct Play or remux when it should instead convert the audio.

Removing incompatible combinations from the Tizen profile allows Jellyfin to make better playback decisions for Samsung televisions.

Live TV and Navigation Receive Smaller Fixes

Jellyfin Web also corrects Live TV program badges that could disappear from detail pages.

Navigation with multiple gamepads has been fixed, Samsung browser detection has been improved and a backdrop-removal race condition has been addressed.

Playlist move options are now hidden from users who do not have the required editing access.

The metadata manager also receives theme corrections, while filter reset behavior and alphabet-based browsing have been improved.

Individually, none of these changes defines the release.

Together, they make Jellyfin Web more consistent across televisions, browsers and different input methods.

Jellyfin 12.2 Is Primarily a Stability Release

The best way to understand 12.2 is not as a feature release but as a polish release for the larger Jellyfin 12 platform.

The server includes dozens of fixes touching playback, metadata, database handling, search, user data and cleanup tasks.

One change corrects a transcoding-settings migration failure caused by a null EncoderPreset.

Other improvements address database context disposal, inherited tags, orphaned values and optimistic locking behavior.

These backend corrections may never appear as visible buttons, but they are important for servers with large libraries and long-running installations.

A media server is expected to run continuously for months.

Small database inefficiencies or cleanup bugs can therefore become significant over time.

Should Jellyfin Users Upgrade?

For most Jellyfin 12 users, 12.2 is a worthwhile update.

The combination of security hardening, Dolby Vision improvements, subtitle fixes and transcoding corrections gives the release value across a wide range of installations.

Users with 4K HDR libraries have an obvious reason to update.

So do users relying on Jellyfin Web, Samsung televisions, graphical subtitles or remote transcoding.

As with any server upgrade, maintaining a current backup before installation remains sensible.

Jellyfin itself continues to recommend having a backup available before upgrading.

Final Thoughts

Jellyfin 12.2 may not introduce a dramatic redesign, but it improves several areas that have a direct impact on everyday viewing.

The Dolby Vision Profile 8 change can reduce incorrect playback decisions on compatible hardware.

The low-bitrate transcoding fix should improve picture quality for constrained remote streams.

The MKV segment-cleaner correction addresses a problem capable of breaking playback entirely.

Graphical and VobSub subtitles are handled more reliably, audio downmixing is more consistent, and Samsung Tizen receives better codec-profile behavior.

The Jellyfin Web security fix is another strong reason not to ignore the update.

Taken together, these changes reinforce what a good maintenance release should do: make the media server quieter, more predictable and less likely to require troubleshooting.

For users with large self-hosted movie and television libraries, that kind of reliability can be more valuable than a long list of new interface features.

FAQs About Jellyfin 12.2

1) What is Jellyfin 12.2?

Jellyfin 12.2 is a stable maintenance release focused on bug fixes, playback improvements, transcoding corrections and Jellyfin Web security and usability updates.

2) Does Jellyfin 12.2 improve Dolby Vision?

Yes. The server now uses hvc1 for the relevant Dolby Vision Profile 8 playback path, improving compatibility with clients that depend on the correct HEVC codec tag.

3) Does it improve 4K transcoding?

The update improves video quality at low bitrates when reducing bit depth and contains additional fixes affecting remuxing and transcoding behavior.

4) What MKV problem was fixed?

Jellyfin corrected a segment-cleaner issue that could delete streaming segments ahead of the active playback position during MKV remuxing.

5) Are subtitles improved?

Yes. Graphical subtitles can be served as raw files with range support, while Jellyfin Web fixes embedded VobSub subtitle rendering.

6) Is there a security fix in Jellyfin Web?

Yes. Jellyfin Web fixes improper escaping of track titles and external URLs.

7) What happened to the “Are you still watching?” prompt?

It is now disabled by default.

8) Does Jellyfin 12.2 improve Samsung TV compatibility?

Yes. Among other changes, Jellyfin Web removes OPUS from MP4, TS and HLS-TS playback profiles on Tizen to avoid unsupported combinations.

Stay Updated with the Player SDK Guide Hub

Media-server updates can affect far more than library management. Dolby Vision metadata, codec tags, subtitles, HLS segments, audio conversion, hardware transcoding and client capability profiles all influence whether a video Direct Plays, remuxes or requires conversion.

The Player SDK Guide Hub tracks developments across Jellyfin, Plex, Emby, Android TV, Google TV, Fire TV, Roku, Apple TV, LG webOS, Samsung Tizen, Infuse, Kodi, VLC and other media-player platforms.

We cover server releases, video-player updates, playback regressions, SDK changes and streaming-device developments to explain what changed, why it matters and what users and developers should test next.

Explore the Player SDK Guide Hub for the latest Jellyfin, media-server and video-playback developments.