This guide explains how to troubleshoot common issues that can prevent images from displaying correctly in Q-Play.
Resolution limitations (not just "file size too large").
SoC players may accept 4K input but render internally at 1080p or lower due to CPU/GPU limitations.
Very large images (e.g. 6000×4000+) can cause:
Memory (RAM) limitations.
Images are decompressed into memory before being displayed. Large images can exceed available RAM, which can cause:
This is especially common on lower-end Samsung Tizen / LG webOS models.
CPU / GPU processing limitations.
SoC devices use low-power embedded processors, not full PCs. Heavy images (very high resolution, transparency, or complex rendering) can lead to:
Practical conclusion.
For most SoC signage setups, stability is best when:
Try the following checks:
This depends heavily on the player, as there's a significant difference between a Windows player and a SoC player.
Generally, all "standard" formats are supported, such as .JPG (.JPEG) and .PNG.
What we've tested and confirmed works on SoC players:
LG WebOS 4 & 6:
LG WebOS 9:
Samsung Tizen 6.5:
Sony Bravia:
Windows:
This is usually due to differences in Chromium versions. Q-Play is built on the Chromium engine and uses whatever version the player has available locally. SoC players typically run an older Chromium version, where not all formats are supported.
| LG WebOS version | Chromium version | Notes |
|---|---|---|
| WebOS 4.0 / 4.1 | Chromium 53 | Older signage generation |
| WebOS 6.0 | Chromium 79 | Common in modern SoC signage |
| webOS 8/9 | Chromium ~124 | LG webOS doesn't expose or lock Chromium to a single consistent version across all devices and firmware builds |
| Samsung Tizen version | Chromium version | Notes |
|---|---|---|
| Tizen 6.5 | Chromium 85–86 | Very common in signage installations |
| Tizen 7.0 | Chromium 94 | Newer models / firmware-dependent |
| Sony BRAVIA (Android TV / BRAVIA Signage) | Chromium version | Notes |
|---|---|---|
| Android TV 7–9 | Chromium ~60–70 range | Older WebView |
| Android TV 10–11 | Chromium ~80–90 range | Modern WebView |
| Android TV 12+ | Chromium ~90–110+ | Depends on updates |
If the image shows as a broken icon or blank space, start by checking that the image format is supported by Q-Play.
If you're using a format that should be supported, try reloading the content on your player.
Try re-saving the image and uploading it to Q-Play again.
Make sure the player has a stable internet connection. A slow or unstable connection can result in the image failing to load.
Rename the file if it contains:
If nothing helps, contact NordicScreen support for further assistance.
There's no fixed maximum file size for images. As long as the image is reasonably optimized, and the player has enough available storage, it should display without issues. Keep in mind that the device needs free space for more than just a single image, so storage should always be managed with total system usage in mind.
To clear the cache or reload content on a specific player, do the following:
Note that not all players can clear their cache; for those, reloading the content is sufficient.
When you upload images to the Media Library, Q-Play Editor processes the file to generate a preview and read its metadata to determine the image format. This process typically only takes a few seconds.
However, larger image files may require additional processing time before displaying correctly.
Note that the Media Library doesn't always update automatically. If the image doesn't appear right away, refresh the Media Library or switch to another tab and back to trigger an update.
Yes, this can be a cause of images not displaying. We strongly recommend keeping your player software as up to date as possible — both Q-Play and the player's firmware.
For further support, you're always welcome to contact NordicScreen's support team: