One 3840 × 2160 canvas split across six screens leaves 1280 × 1080 pixels per screen, about one-sixth of a 4K panel's native grid, so every panel upscales a sub-HD slice. Six native portrait feeds need a 6480 × 7680 canvas that no single HDMI output carries. The fix is one native portrait file per screen, with seam offsets held under about 8 ms.
A six-screen wall built from consumer TVs has one job: put moving content on six large portrait panels and keep it readable. When every screen looks soft and the seams twitch where they meet, the cause is usually arithmetic, not broken hardware. One 4K canvas cannot feed six 4K panels at their native grids. The network hop between player and panels compresses what the split leaves. Panels that are not phase-locked show the difference at the seams. This page gives the arithmetic, the sync limit, and the decision for each way out.
Why does a six-screen wall fed by one 4K player drop to HD per screen?
Because the split happens before the panel. A 3840 × 2160 canvas holds 8,294,400 pixels, six screens divide that, and 8,294,400 ÷ 6 = 1,382,400 pixels per screen, the pixel count of a 1280 × 1080 slice. A full-HD frame is 1920 × 1080, or 2,073,600 pixels, so each screen receives two-thirds of one full-HD picture and nowhere near what its own 4K panel can light.
The chain works like this. The media player renders one landscape 4K frame, the transmitter pushes it onto the network, and each receiver draws one tile of that same frame. The tile is one-sixth of the source no matter how sharp the panels are. Each panel then stretches its slice to fill its native grid. The ceiling itself sits in the player's canvas, not in the wall: the cap and how to build content around it are covered on the video wall resolution limit and the 4K canvas fix.
How many pixels would the panels need for native portrait playback?
Six 4K panels turned portrait each carry a 2160 × 3840 grid. A canvas that fed all six at native resolution would measure 6480 × 7680, or 49,766,400 pixels, six times what any single HDMI output delivers.
The width comes from three columns of 2160 (3 × 2160 = 6480) and the height from two rows of 3840 (2 × 3840 = 7680). HDMI 2.0 tops out at 18 Gbit/s, which carries 3840 × 2160 at 60 Hz. Pixel count scales the rate roughly in proportion, so 49,766,400 pixels at 60 Hz needs about 108 Gbit/s, six times the fastest HDMI 2.0 link. No media player, cable or transmitter gets near that, which is why six native portrait feeds take six sources. Rotating 4K content for portrait screens has its own traps too, covered on why a 4K portrait signage player shows a quarter of the layout.
What does the gigabit hop between player and screens change?
It forces compression. A gigabit Ethernet port carries 1 Gbit/s under IEEE 802.3ab, while an uncompressed 3840 × 2160 picture at 60 Hz fills an 18 Gbit/s HDMI 2.0 link, so an HDMI-over-IP hop has to discard data before it ever reaches the wire.
Every HDMI-over-IP extender compresses, and the resolution its compressed stream carries is a datasheet number for that specific model; the datasheet is where that figure is stated. In a wall like this one, though, the split already caps each screen at one-sixth of the canvas, and better network gear adds no pixels to a tile cut at the source. So the order of work is fixed: raise pixels per screen first, audit the extenders second.
Why do the seams show a tear or a lag?
Because tearing appears when the video feed is not synchronized with the display's refresh rate. Motion crossing a seam turns any offset between two panels into a visible kink; hold screen-to-screen offset under about 8 ms.
At 60 Hz a panel refreshes every 1000 ms ÷ 60 = 16.7 ms, so half a refresh is about 8 ms. An offset of one full frame draws one panel an entire picture ahead of its neighbor. The artifact is ordinary screen tearing, not a fault in the panels. Screens that start on their own clocks then drift: two devices whose clocks differ by 50 parts per million move apart 86,400 s × 0.00005 = 4.3 s over a day unless something corrects the offset as it grows. Sync that holds a wall together is phase correction that runs all the time between players, or one source whose six crops are locked together by design. You will never get there by pressing play on six remote controls at once.
Worked example: how many pixels reach each screen of a 3 x 2 portrait wall?
Each screen receives 1,382,400 pixels and lights a panel of 8,294,400, so every slice pixel is drawn over six native pixels, and text designed on the slice needs capitals of about 40 pixels to read from 20 m.
The arithmetic, step by step:
- Canvas: 3840 × 2160 = 8,294,400 px. Six screens share it, so 8,294,400 ÷ 6 = 1,382,400 px per screen, a 1280 × 1080 slice.
- Panel: a 70-inch 4K TV in portrait lights 2160 × 3840 = 8,294,400 px.
- Softness: 8,294,400 ÷ 1,382,400 = 6, so each slice pixel covers six native pixels and thin lines blur accordingly.
- Native canvas: (3 × 2160) × (2 × 3840) = 6480 × 7680 = 49,766,400 px, which no single output carries.
- Text: a 70-inch 16:9 panel stands about 1550 mm tall. 1080 slice pixels over 1550 mm gives 1550 ÷ 1080 = 1.43 mm per slice pixel, so a 40 px capital measures 40 × 1.43 = 57 mm, or 2.26 in. The FHWA planning figure of 30 ft of viewing distance per inch of capital height reads 2.26 in from 2.26 × 30 ≈ 68 ft, about 21 m.
Result: the wall plays one canvas at one-sixth of each panel's usable detail, and text sized at 40 slice pixels stays legible to about 21 m. Filling the panels natively takes six files at 2160 × 3840, one per screen.
Can six TVs each play their own file from a USB stick and stay in sync?
For six independent compositions, yes: each screen shows its own finished picture and an offset of even a few seconds between screens is invisible. For one picture crossing all six seams, no, because a TV's USB player has no way to phase-lock with its neighbors.
The export is the job: build each screen as a finished portrait composition at that panel's native grid, 2160 × 3840 on a 4K panel, and save it as its own file. How to plan files that turn or stay upright is covered on planning portrait and landscape signage content. If nothing crosses the seams, align the starts by hand and the 4.3 s-a-day drift described above shows up only as a late start, which nobody sees. If motion crosses the seams, the 8 ms budget rules USB playback out, and you need players built for walls that correct one another over the network.
When is a sub-HD slice per screen good enough?
When the content is bold and self-contained: few elements per screen, capitals of at least 40 slice pixels, line spacing at 1.7 × capital height, and no motion crossing the seams, for viewers standing closer than about 21 m.
An exhibition stand or a lobby where visitors gather 5 to 15 m from the screens sits well inside the 21 m limit, so the 40 px capitals carry with margin to spare. Keep the single-canvas chain in that case and redesign the content at slice scale: fewer words, heavier shapes, one idea per screen. The 1.7 × line spacing is the standard signage planning ratio between line spacing and capital height, and it keeps three or four lines readable where six cramped lines would not survive the upscale. Watch one boundary: the moment the content needs small print, fine diagrams or motion across the seams, the slice stops being good enough and the per-screen fix takes over.
Which fix fits your wall?
Recommendation: Play one file per screen at native portrait resolution, 2160 × 3840 on a 4K panel, from one player per screen whenever motion crosses the seams; keep the single 3840 × 2160 canvas chain only for bold content whose motion never crosses the seams, read from 20 m or closer.
The decision for each case:
- One picture across all six screens, motion crossing the seams: per-screen players built for walls, holding offsets under about 8 ms. The one-player-versus-many choice, worked through for a four-screen case, is on one signage player or one per screen for four TVs.
- Six independent compositions: six files at native portrait grids, any player per screen, starts aligned by hand, and the extenders and switch leave the signal path.
- Bold content, viewers within about 21 m: keep the chain you have and design at slice scale, 40 px capitals and 1.7 × line spacing.
The working shape in the first two cases is one screen, one file, one player. That is how our panel-mount signage displays play too, each unit running its own files from its own storage; the larger wall formats in the current range are quoted per project, with configuration, power and orientation confirmed in the quote.
Questions
Does a 2 x 2 wall from one 4K canvas have the same problem?
No. A 3840 × 2160 canvas divided across four screens leaves 1920 × 1080 per screen, which is exactly a full-HD frame, so each panel shows its tile at native resolution with no upscaling. The deficit appears once the tiles outnumber what the canvas carries: six tiles give 1280 × 1080 per screen, and a 3 x 3 wall of nine tiles gives 1280 × 720. Count tiles before buying anything: canvas width ÷ columns and canvas height ÷ rows is the pixels each screen receives.
What resolution should I export each file to when playing one file per screen?
Match the panel's native portrait grid: 2160 × 3840 for a 4K panel, 1080 × 1920 for a full-HD panel. Build each screen as a finished portrait composition and export it as its own file, so the player never rotates or crops during playback. Keep the six exports on one timeline if you plan to align starts by hand, and name each file for its screen position so the right file reaches the right panel.
Do screens with a built-in video wall mode fix the softness?
A built-in wall mode crops a single input into tiles, so pixels per screen still equal canvas ÷ screens: one 4K input across six tiles is still 1280 × 1080 per screen. What wall mode changes is the seams: every tile comes from the same input and stays locked to its neighbors' refresh, which stops the tearing. It fixes the lag while leaving each screen's pixel count exactly where it was, so softness needs the per-screen fix.
Planning information, not legal or engineering advice. Rules differ by place: check codes and permits with your local authority and your licensed trades.