1. The player, not the panel
A 4K panel fed by a 1080p Android box shows 1080p. Text gets soft, price edges get halos, and everyone blames the display.Ask what the player outputs at 60 Hz, not 30. Ask whether it downscales content above its output resolution without saying so. The datasheet usually does not mention it.
2. The content's real resolution
A file can be 3840 x 2160 and still contain a menu rendered at 1080p and upscaled by the design tool.Request one sample at native size and zoom to 100 percent on a computer before it goes near a screen.
3. Cable and input version
HDMI 1.4 will not carry 4K at 60 Hz, and neither will a long passive cable that worked at 1080p.Confirm the input version and use an active cable beyond five metres. Cheapest failure to prevent, most annoying to diagnose from a photograph.
4. How many devices are scaling
Panel, player, content management system, and sometimes a matrix switcher: four devices that can each scale independently.Set every one to passthrough or native, and let exactly one device do the work. We ask for a screenshot of each settings page. Ten minutes, twelve store visits saved.
5. Play the real file on the real player
Before the order, one sample file on the actual player and panel in the showroom.It catches the mismatch that otherwise surfaces three weeks after rollout, when the agency has already been paid.
And if the content is animated, multi-zone or schedule-driven, keep an external player and buy a good one. A built-in player is simpler only for static menus that change weekly.