Most Android players on a 4K panel draw the app surface at 1920 x 1080 and scale it up 2x. Full-screen video still plays at 3840 x 2160, while text, PDF pages and charts take the scale and soften. Test with a one-pixel image before you buy.
A 4K screen on the wall and a player that says 4K on its spec sheet can still be showing you 1080p. The player sends a 3840 x 2160 signal to the panel, then draws its app on a 1920 x 1080 surface and scales that surface up two times. Video comes through the decode path at full panel resolution, so it looks right. Everything the app draws itself, the text, the PDF page, the chart, takes the downscale and the upscale, and goes soft. Here is what that scale does to your numbers, a five-minute test that exposes it, and the decision it forces.
Two resolutions inside one player
Every player has two resolutions that move independently. The output resolution is the signal on the cable: 3840 x 2160. The render resolution is the surface the app draws on, and the system sizes that surface, not your layout. This is documented platform behavior. On Android TV 11 and all earlier versions the system interface and every application render in 1080p, and only some video playback switches to the full panel resolution. Field reports from 4K signage projects match it: a 4K layout is scaled down to 1920 x 1080 inside the signage app, and the device stretches the finished frame back up to 4K. Only video stays native.
On an Android signage unit the HDMI port is an output, so the unit draws all of its own content and nothing you connect changes the size of that surface. The basics of why this happens are covered in why your 4K signage player only renders at 1080p. This page is about what the double scale costs your content and how to catch it before you pay.
Why video stays sharp and your text does not
Video is decoded frame by frame and presented to the display, so a 3840 x 2160 MP4 reaches a 4K panel as 3840 x 2160. The app surface is where the player composes everything else, and when that surface is 1920 x 1080, the app draws with a quarter of the panel's pixels no matter what your files contain.
| What is on screen | Path it takes | Result on a 4K panel |
|---|---|---|
| Full-screen MP4 | Decoder frames to the display | Native 3840 x 2160 |
| Text, PDF pages, charts | Drawn on the app surface | Drawn at 1920 x 1080, stretched up 2x |
| Images in the layout | Drawn on the app surface | Same 2x stretch |
| A 2x2 split layout | Composition on the app surface | 960 x 540 of real detail per region |
A split layout takes the worst of it. Four regions on a 1920 x 1080 surface hold 960 x 540 each, and on the players installers tested, four videos in four regions was already more than the device could sustain. If you are putting a live dashboard on a signage screen, the dashboard is drawn content, so it sits on the weak side of this table.
What the 2x stretch does to your numbers
One pixel of the surface becomes a 2 x 2 block on the panel. Count them: 1920 x 1080 is 2,073,600 pixels against 8,294,400 on the panel, one quarter.
Sizes survive the trip. A layout built for the full screen still fills the full screen, and a capital letter keeps its height in inches, because the small surface is stretched across the whole panel. Detail does not survive. An 8 px stroke in the layout is drawn as 4 px on the surface and stretched back to 8 panel pixels: the same size on screen, drawn with a quarter of the pixels it was designed for. A 2 px chart gridline becomes a 1 px line on the surface and comes back gray, and thin lines lose contrast at every viewing distance.
Example: an 80 px title on a 55-inch 4K panel
Take a 55-inch 16:9 panel. The diagonal is 55 in, the width is 55 x 16 / 18.36 = 47.9 in, and the panel packs 3840 / 47.9 = 80 pixels per inch.
Your dashboard title has 80 px capitals. Rendered native: 80 px / 80 px per inch = 1.0 in of capital height. The fast-reading figure is 20 ft of viewing distance per inch of capital height, so this title is built to be read from 20 ft.
Now the player renders its app surface at 1920 x 1080. The title is drawn at 40 px and stretched back to 80 panel pixels. On screen it is still 1.0 in tall and still serves 20 ft. Underneath, the 16 px chart labels were drawn at 8 px, and the 2 px gridline was drawn at 1 px and returned as gray.
Distance hides the rest. With 20/20 vision you resolve about one arcminute: 0.07 in of detail at 20 ft, 0.025 in at 7 ft, 0.01 in at 3 ft. One panel pixel here is 1/80 in = 0.0125 in, and the upscale step is two of those, 0.025 in. Past about 7 ft the stretch is smaller than what your eye resolves, so the title looks the same on both players. At 3 ft you resolve finer than one panel pixel, and the softness is plain.
The decision for this screen: read from 20 ft, a 1080p surface costs you the thin lines and little else. Read at arm's length, it costs you the 4K panel you paid for.
A five-minute test with a one-pixel image
Build the image before you buy, and run it on the exact build the vendor ships.
- Make a 3840 x 2160 PNG. Left half: vertical bars, 1 px black, 1 px white. Right half: the same bars at 2 px. Save as PNG. JPEG compression smears one-pixel bars on its own and would ruin the test.
- Show it full screen from a playlist with that one image and no resizing.
- Stand about 2 ft from the panel. Native 4K rendering shows crisp 1 px bars. A 1080p surface turns them into flat gray or a shimmering moire, because one layout pixel is half a surface pixel.
- Check the 2 px bars as the control. They land on whole surface pixels and stay a visible pattern on both players, just softer on the one that upscales.
- Play the same bars as a 3840 x 2160 MP4. Sharp bars in the video and gray bars in the image is the signature of this whole problem: the panel and the cable are fine, the app surface is small.
Running the real file on the real player before payment is the same discipline as the video bitrate test you run before deploy. And if your layout is portrait and only a quarter of it shows, that is a different failure, covered in why a 4K portrait signage player shows a quarter of the layout.
What to ask before you buy
Ask the vendor one question in writing: does the player render its application surface at 3840 x 2160, or at 1920 x 1080 scaled? Ask for the answer together with a run of the test image above. Platform releases change this behavior over time, so a yes from last year's build settles nothing; test the build you will receive.
A 4K line on a spec sheet is an output claim. It tells you what leaves the port, and the render resolution lives elsewhere in the build. What a signage spec sheet tells you walks the rest of the sheet the same way.
On the panel-mount displays sold through the cart, the panels are 1920 x 1080, with the 10.1 inch at 1280 x 800, so the app surface and the panel match and this problem does not arise. On a larger quoted wall model, have the render resolution confirmed with the quote, in writing, next to the panel's native resolution.
Recommendation: if the sign shows text, PDF pages, charts or a dashboard that people read from within about 7 ft, buy only a player that renders its app surface at 3840 x 2160, and prove it with the one-pixel image before payment. If the playlist is full-screen MP4 viewed from farther away, a player that upscales from 1920 x 1080 is an acceptable choice, because the video path plays at panel resolution either way.
Questions
Does a 4K output on the spec sheet mean the app renders in 4K?
No. The output figure describes the signal on the cable. A player can send 3840 x 2160 while drawing its app surface at 1920 x 1080 and scaling it up. Ask for the app surface resolution in writing, then confirm it with the one-pixel test image.
Why is video sharp but text soft on the same 4K screen?
Because the two take different paths. The decoder hands 3840 x 2160 frames straight to the panel, and only full-screen video gets that path. Text, PDF pages and charts are composed on the app surface, and on a 1080p surface a split layout is the worst case: four regions on 1920 x 1080 leave 960 x 540 of real detail per region, so each region's text takes the 2x stretch twice over.
Can a setting fix this?
Sometimes. On some platforms the render resolution is fixed by the system build; on others the vendor can change it. Ask for the exact setting name and a run of the test image after the change. An answer without a setting name is a no.
Does this matter on a 1920 x 1080 screen?
No. When the app surface and the panel are both 1920 x 1080, nothing is scaled and the problem cannot occur. It appears only when the panel has more pixels than the surface the app draws on, which in practice means 4K panels.
From how far away does the softness stop mattering?
With 20/20 vision you resolve about one arcminute, which is 0.025 in of detail at 7 ft. On a 55-inch 4K panel the upscale step after the 2x stretch is 1/40 in, or 0.025 in, so past about 7 ft the stretch falls below what your eye resolves. Thin one-pixel lines still gray out at any distance.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.