Reconsidering 4K/UHD Classification Logic

[theguymadmax]

Current Implementation

Jellyfin currently identifies 4K/UHD content using only a horizontal width threshold of 3800px. This single-dimension approach may be missing legitimate high-resolution content.

Real-World Examples

I analyzed my media library and found several high-resolution files that are not classified as 4K/UHD with the current logic. Here are actual examples:

2592x2160
2872x2156
2876x2160
2880x2160 (multiple files)
2960x2160 (multiple files)
2972x2160
3232x2152
3556x2156
3564x2156
3576x2156
3582x2160 (multiple files)
3584x2160

All these files have vertical resolutions at or very near 2160p, which is the vertical resolution standard for 4K/UHD content. However, they fall below the 3800px width threshold and thus aren't classified as 4K/UHD content.

Proposed Change

PR #13332 adds height-based detection (≥2100px) as an alternative criterion for 4K/UHD classification. This would properly categorize these high-resolution files while maintaining the existing width-based detection.

Concerns

• Commercial cinema and TV standards define 4K specifically by horizontal resolution (~4000 pixels)
• Different standards have specific definitions:
  • DCI 4K: 4096×2160, 3996×2160, or 4096×1716
  • SMPTE/ITU-R UHD: 3840×2160
• Streaming platforms use more flexible definitions (e.g., YouTube's "4K UHD" includes 2160p content)
• This change would shift us from an industry-standard horizontal definition to a more vertical-based approach

Questions for Discussion

Should Jellyfin strictly follow commercial standards, or adapt its classification to better match real-world content variations?

[Shadowghost]

IMHO we should use a more versatile approach. I'm all for using standards but in this case we miss any content where stuff like black bars were removed before (re)encoding because they take away from the height. From a user perspective that's still a 4k/UHD (or to be more correct 2160p) media.

[mikesulsenti]

An example of that resolution type is a 4K movie I re-encoded and clipped the black bars:
3840 × 1608

And similarly, 1080p movie files would have their own clipped black bars, often:
1920 × 804

Some other outliers may be more less

[MrPeteypoo]

The terminology in the video space for resolutions can be very confusing at times. It might be helpful to stop using the term "4K" and use the more general "Ultra HD" or "UHD" term. Although UHD is very often synonymous with 4K I think it more accurately includes cases where a 3840x2160 movie is cropped to 21:9 by removing the black bars (becoming 3840x1608) or where you have a 4:3 movie with a resolution of 2880x2160. 2160p Isn't a good alternate because again with most movies being in 21:9 it isn't very accurate. I would classify UHD as being anything above FHD (either 1920 pixels wide or 1080 pixels tall) unless there is a desire to introduce QHD (either 2560 pixels wide or 1440 pixels tall).

[theguymadmax]

I compared Jellyfin with two other major media servers, and found they both consistently classify content with resolutions like 2880x2160, 3582x2160, and 3584x2160 as 4K, while Jellyfin currently identifies these as HD due to our width-only threshold of 3800px.

Regarding resolution names, while not the main focus of the discussion, it’s still relevant, and it’s helpful to hear opinions in case the web team decides to make a change. Current resolution labels across platforms:

Jellyfin	E	P
SD	SD	SD
HD	720p	480p
4K	1080p	720p
	4K	1080p
		4K

Adding height-based detection (≥2100px) alongside our existing width threshold would:

1. Better match how other media servers classify content
2. More accurately reflect real-world content variations
3. Improve user experience when migrating between platforms

Additionally, we might want to consider splitting HD into 720p and 1080p.

[MrPeteypoo]

I can't really speak to how necessary 720p vs 1080p is because my media is all DVD/Blu-ray/UHD rips so my content is either SD, FHD or UHD.

One thing that is pretty commonplace in the media streaming space is to use classifications like 720p, 1080p and 2160p even when it's not true. My example would be watching a cropped 21:9 movie where the resolution is 1920x822~. If you were to buy a movie or TV show with that resolution you'd be buying a "1080p" version even though it's technically 822p. Jellyfin's language is much closer to the truth than the competitors. 4K is the odd one out because it doesn't account for 4:3 content, as I mentioned above the term UHD better encompasses that. Some streaming services such as Amazon use SD/HD/UHD classifications instead of being height specifications.

If you want to split up 720p and 1080p I'd suggest using HD and FHD.

[Maxr1998]

Another outlier that should be taken into account: vertical video. I have a few vertical 4K videos in my collection, so 2160x3840, which are currently (incorrectly) classified as 8K content by Jellyfin. It should still be detected as 4K, preferably even with a "Vertical" prefix.