The resolution shown in the System tab of a player doesn't always reflect the native resolution of the display panel. Instead, it typically reports the Document Object Model (DOM) resolution, which is the resolution of the browser rendering environment—essentially, the size of the browser window where your content is displayed. This is a crucial distinction, especially for displays with high native resolutions like 4K. 🧐
Why Is the Reported Resolution Different?
The reported resolution is different because most devices use separate processing pipelines for graphics and video. For example, a 4K display might be able to play 4K video content, but the graphical layer, which includes our media player's interface and the DOM, is often limited to a lower resolution, such as Full HD (1920x1080). This is a deliberate design choice by device manufacturers to optimize performance.
Which Players Are Affected?
The reported resolution on the System tab is the DOM resolution for all standard API players.
Player Type | Reported Resolution | Notes |
Samsung Tizen and LG webOS | FHD (1920x1080) | These players, despite often having 4K displays, report FHD because their graphics layers are limited. They can still play 4K video content. |
Brightsign, Electron, and ChromeOS | Varies | These are currently the only player types that can render both graphical and video elements at resolutions above FHD. The reported resolution is more likely to match the native display resolution. |
This information is generally not applicable to SMIL players or legacy PC players.
What Does This Mean for You?
Don't be alarmed if the resolution reported on the System tab is lower than your display's native resolution. It doesn't mean your 4K content won't play in 4K. It simply means the player's graphical user interface operates at a lower resolution. The device is still capable of playing high-resolution video content, ensuring your visuals remain crisp and clear. ✅