Size a video wall by total pixels, not by screen count. One HDMI 2.0 output carries one 4K panel, and a 2 x 2 wall of 4K panels is a 33.2 million pixel canvas, the working ceiling for one small-form-factor PC. A 3 x 3 wall is 74.6 million pixels, so split it across synced players or run one 4K source through a wall processor.
A video wall is sized in pixels, not in screens. One 4K panel carries 8,294,400 pixels, so the question of how many 4K screens one player can drive is really two questions: how many 4K outputs the device physically has, and how many pixels it draws every second. A small-form-factor PC clears both checks up to a 2 x 2 of 4K panels. A 3 x 3 clears neither through one box, and the fix is a split: one source into a video wall processor, or one player per panel kept in step. This page gives the two checks, the four build options and the numbers behind each decision.
Two checks decide it
Count outputs first. A 4K panel at 60 Hz with 8-bit color takes about 14.4 Gbps of the 18 Gbps one HDMI 2.0 output carries, the 14.4 accounting for the encoding overhead, so every panel at that rate needs a whole output to itself. In the small-form-factor class that means the motherboard's outputs plus one add-in card, which typically adds four outputs, two DisplayPort and two HDMI. Four screens is the practical direct-drive ceiling for one box.
Then count canvas pixels: wall width times wall height. A 2 x 2 of 4K panels is a 7680 x 4320 canvas, and 7680 x 4320 = 33,177,600 pixels. At that refresh the machine draws 33,177,600 x 60 = 1,990,656,000 pixels per second, about 2.0 billion. That canvas runs well from one small-form-factor PC when the content is looped video, slides and lightly animated dashboards.
A 3 x 3 canvas is 11520 x 6480 = 74,649,600 pixels, about 4.5 billion pixels per second at the same refresh. No box in the class draws that with room to spare.
Content moves the ceiling more than screen count does. Full-screen video is decoded by fixed-function hardware and is the lightest case. Dashboards with many animated layers are composited on the graphics processor every frame, and that load scales with canvas pixels, which is why generative and interactive content shrinks it. Dropping motion to 30 fps halves the pixel rate: a 33,177,600 pixel canvas at 30 fps is 995,328,000 pixels per second, about 1.0 billion.
So the working threshold for the class: up to about 33 million pixels of animated canvas from one box, one output per screen. Above it, split the wall.
Four ways to build the wall
| Setup | Screens | Canvas the player renders | Best for | Watch for |
|---|---|---|---|---|
| One small-form-factor PC, one output per screen | up to 4 (a 2 x 2) | 33.2 million pixels, native | interactive walls, touch over USB from each panel | nothing above four screens; keep content light |
| One 4K source into a video wall processor | 9 and more | 8.3 million pixels (one 3840 x 2160 canvas) | video walls fed from one library | each 4K panel shows a 1280 x 720 slice, upscaled 3x, so small text softens; no touch path back |
| Screens with a built-in tile matrix | small arrays | 8.3 million pixels | no extra box, one cable into the first screen | the largest tile array is a screen specification; check it before planning a 3 x 3 |
| One player per panel, kept in sync | 9 and more | 8.3 million pixels per panel, native | dashboards and text at full sharpness | sync drift, per-panel playlists, a player per panel |
The processor question at four panels has its own page on when a 2 x 2 video wall processor earns its place, and the player-side canvas cap behind the sliced options is the subject of the 3840 x 2160 cap and the 4K canvas fix.
Touch changes the choice more than anything else in the table. Panels plugged straight into the PC send their touch data back over USB, and the canvas maps each panel's touches to its place on the wall. A processor takes video in only and has no channel back to the source, so an interactive 3 x 3 runs as per-panel players, each handling its own ninth of the canvas. No small-form-factor machine has nine direct outputs, so per-panel players is the interactive path at that size.
Example: a 3 x 3 wall of 3840 x 2160 panels
Inputs: nine panels, each 3840 x 2160 from the panel specification sheet, arranged three wide and three high, so the canvas is 11520 x 6480; refresh 60 Hz from the content plan, which calls for motion video; 8-bit color, the ordinary signage case.
The rule in words: canvas pixels equal panel pixels times panel count; pixel rate equals canvas pixels times refresh rate; and direct drive needs one output per panel, because one HDMI 2.0 output's 18 Gbps carries exactly one 4K stream at that refresh, about 14.4 Gbps after encoding overhead.
The arithmetic:
- One panel: 3840 x 2160 = 8,294,400 pixels.
- The wall: 8,294,400 x 9 = 74,649,600 pixels, about 74.6 million.
- The rate: 74,649,600 x 60 = 4,478,976,000 pixels per second, about 4.5 billion.
- The outputs: nine panels need nine outputs, and the class tops out at four.
The result: one box fails both checks. It offers four outputs where the wall needs nine, and 74.6 million pixels of animated canvas sits well past the 33.2 million pixel working ceiling of the class.
The decision: above about 33 million pixels of animated canvas, split the wall. For this 3 x 3, put one 4K source through a video wall processor when the wall plays video, accepting a 1280 x 720 ninth per panel; use nine synced players when dashboards and text must stay pixel-sharp. Motion at 30 fps cuts the rate to 74,649,600 x 30 = 2,239,488,000 pixels per second, but the output count stays at nine against four, so the split decision stands.
When to pick something else
A wall of 1080p panels. Nine 1920 x 1080 panels total 18,662,400 pixels, a quarter of the 4K wall, and a 2 x 2 of them equals one 4K panel exactly: 4 x 2,073,600 = 8,294,400 pixels. 1080p is the resolution across most of our panel-mount display sizes, and it keeps this much canvas inside the class's range.
Two screens. The question there is whether the second screen mirrors or slices, and the HDMI splitter or video wall processor decision for two screens works through it.
Four screens. The build question is one player or one per screen, and one signage player or one per screen for four TVs covers the trade-offs this page assumes.
LED walls. An LED wall raises its own scaling questions, and driving an LED video wall from an Android signage player is the closer read.
What to ask for
From the panel specification: the native resolution, whether the HDMI input carries 3840 x 2160 at that refresh rate, and the largest tile array the screens hold if tile mode is in play.
From the PC or player quote: how many outputs, of what type, and whether each carries 3840 x 2160 at the same refresh. Send the signage app vendor the finished canvas size and content plan and ask for their minimum specification for that canvas; a 33 million pixel canvas and a 74.6 million pixel canvas get different answers.
From the content plan: motion or still, frames per second, touch or not.
From the room: cable runs. At the full 18 Gbps of a 4K stream a passive HDMI cable holds about 3 m; past that, run an active cable or an extender over Cat 6.
From the sync plan, when the wall goes per-panel: how the players stay in step is its own architecture, covered in video wall sync architecture: how players stay in step, and the symptom to watch for is sync group screens playing video out of sync.
For the player basics this page assumes, start with how to choose a digital signage player.
Recommendation: Drive one small-form-factor PC up to a 2 x 2 of 4K panels with one output per screen and content that stays looped video, slides or lightly animated dashboards; if the build feels tight, drop motion to 30 fps and halve the pixel rate. At a 3 x 3, split the wall: one 4K source through a video wall processor when the wall plays video, nine synced players when dashboards and text must stay pixel-sharp.
Questions
Can I drive nine 4K panels from one PC if I add two graphics cards?
You can reach the output count, but not the render budget. Nine panels at 3840 x 2160 need 4,478,976,000 pixels drawn per second at that refresh, and animated dashboards redraw every one of them every frame. Hardware that renders comfortably at that rate lives in workstation towers, with the size, noise and cost that follow, while a processor or synced players reach the same wall with small parts. For a plain video wall the processor path is the cheaper, quieter build.
Does a wall processor make dashboard text blurry?
On a 3 x 3 wall it can. The processor cuts one 3840 x 2160 canvas into nine 1280 x 720 pieces and upscales each piece 3 times to fill a 4K panel. Video tolerates that; small text and thin lines go soft. Feed the processor the largest canvas its input accepts, or drive each panel from its own player when the text has to stay pixel-sharp.
Can I just use a splitter to feed all nine panels?
No. A splitter copies one picture to every screen, so all nine panels would show the same 3840 x 2160 frame. A wall needs the picture cut into slices, which is what a processor does, or what a screen's tile mode does when the screens include it. The tile route needs the daisy chain and crop settings the screen manual documents, so check the panel specification before counting on it.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.