RigPlan.app

How many LED panels per data port

Updated 2026-09-04

This guide works out how many panels one gigabit port from an LED processor can drive, and how that one number decides the way a wall is broken into data runs.

The pixel budget per port

A 1G port carries roughly 650,000 pixels at 60 Hz and 8-bit processing. That is the figure NovaStar rates its gigabit ports at on its own spec sheets; Brompton rates 525,000 for its protocol. It is a ceiling, not a target.

Divide it by the pixels in one cabinet to get panels per port. A 176 × 176 pixel cabinet holds 30,976 pixels, so a port theoretically carries 21 of them. A coarser 104 × 208 cabinet holds 21,632 pixels, so a port carries 30.

Refresh rate and bit depth

The published pixel figure assumes 60 Hz at 8-bit. Both assumptions cost capacity when you change them, because the constraint is bandwidth.

At 120 Hz, which is common for broadcast and anything shot on camera, the per-port pixel budget roughly halves. Moving to 10-bit processing for smoother gradients costs capacity again in proportion to the extra bits. A wall that fits on eight ports at 60 Hz 8-bit can need sixteen at 120 Hz, which is an expensive thing to discover on site.

Port headroom at 80%

Most crews do not fill ports to the theoretical maximum. Loading to around 80% of the pixel budget leaves room for a panel swap, a slightly larger wall than planned, or a late change from 8-bit to 10-bit, without re-patching the whole rig.

At 80% of 650,000 pixels, that 176 × 176 cabinet gives 16 panels per port rather than 20. On a six-row wall that means two whole columns per run instead of three, which changes the cable count and the processor choice.

Runs along columns

Data runs normally follow whole columns, snaking up and down, because that matches how panels connect when hung and keeps the patch legible when something fails at 2 am. Fit as many whole columns onto a run as the pixel budget allows; on a tall wall where a single column exceeds the budget, split that column across two runs.

Then check the plan against the processor twice: once for port count, and once for total pixel capacity, since a processor can run out of pixels while it still has spare ports.

Redundancy on installs and on rental

Looped A/B redundancy runs a second data path so that a failed cable does not black the wall. It doubles the run count and the cable order, and it is standard on critical fixed installations.

It is not the norm on rental shows. Most rental rigs run single-path data and carry spare cable instead, which is why redundancy should be an explicit choice rather than a default assumption in any calculation.

RigPlan does this arithmetic for you. Enter the wall once and it derives panels and spares, rigging from your own stock, circuits, the data wiring plan and the full pack list, free with no sign-up.

Open the planner

Common questions

How many pixels can one gigabit port drive?

NovaStar rates a gigabit port at 650,000 pixels at 60 Hz with 8-bit processing; Brompton rates 525,000. Higher refresh rates and deeper bit depths reduce that figure proportionally. NovaStar’s own sheets halve it at 10-bit and 12-bit.

Does 120 Hz halve the number of panels per port?

Approximately, yes. Doubling the refresh rate roughly doubles the bandwidth per pixel, so the number of panels a single port can carry drops by about half.

Should I load ports to 100% of their pixel capacity?

Loading to around 80% is the safer convention. It leaves headroom for wall size changes, a switch to 10-bit, or a panel swap without repatching the entire wall.

Reference pages

More guides