- Definition: Physical pixel count of the finished wall
- Set by: Wall size and pixel pitch, not a broadcast standard
- Source: Processor scales the source to the native grid
- Demand: Higher count needs more processing and data runs
- Verify: Show a test pattern across the full wall at handover
- Later use: Records guide content, repair and expansion
Why is LED resolution different from a television?
A television arrives with a fixed grid such as 1920 by 1080. An LED wall is assembled from cabinets, so its resolution follows the physical build: the cabinet pixel count multiplied by the number of cabinets in each direction. Two walls of the same physical size can carry different pixel counts, and two walls with the same pixel count can be very different sizes.
This is why 'is it 4K' is rarely a useful question for an LED project. There is no standard grid for the wall to match. What matters is the native pixel count, how close that sits to the content you intend to show, and how well the processor handles the difference between the two.
How do wall size and pitch set the pixel count?
Pitch sets how many pixels sit in a metre, and the wall dimensions set how many metres there are. Halve the pitch on the same wall area and the pixel count rises substantially; enlarge the wall at the same pitch and it rises in step. Every decision about sharpness is therefore a decision about these two numbers together.
Cabinet dimensions matter as well. Cabinets come in fixed sizes, so the finished wall is built in those increments. Where the target dimensions are not a clean multiple, the design needs a plan for the remainder, either by adjusting the drawing slightly or by filling the edge deliberately. Ask how the proposed cabinet count lands on your dimensions before the order is placed.
What happens when the source does not match the wall?
The processor scales the incoming signal to the wall's physical grid. When a source arrives below the native count, the image is enlarged and softness appears; when it arrives above, detail is discarded. Neither is a fault of the panels. A wall showing content prepared at its own native resolution looks noticeably cleaner than one fed a mismatched signal.
This makes content preparation part of the resolution decision. Confirm the native pixel count early, give it to whoever produces the content, and ask for a test clip to be shown on the actual wall during commissioning. Screens that look disappointing are often carrying content built for a different grid.
Does higher resolution demand more from the control system?
Yes. Every pixel has to be driven, so a higher native count needs more processing capacity, more data groups running to the cabinets, and a processor able to accept the sources and windowing the project requires. A wall mixing live camera feeds, several windows and stored presets places a heavier load than one showing a single full-screen source.
Ask what processor ships with the job, how many pixels it is rated to drive, how many inputs and live windows it supports, and whether future expansion needs additional sending capacity. Confirming this at specification stage avoids discovering the limit during commissioning, when the alternatives are all expensive.
How does resolution behave on curved or shaped walls?
Curved, corner and non-standard layouts change how content maps onto the surface. A continuous image wrapped around a corner needs the content produced for the full pixel width and mapped correctly across the bend, and a cylinder or cube needs each face treated as part of one canvas instead of as separate screens.
Shaped walls also affect cabinet selection and spare strategy, because faces may use different cabinet types. Confirm the mapping approach with the supplier before content production starts, and ask for a visual proof on the actual layout instead of a flat mock-up.
What should be written into the specification?
Write the native pixel count, the wall dimensions it is derived from, the cabinet model and count, the processor model with its rated pixel capacity, the input list, and the spare module and card quantity. Ask for the pixel count to be stated for the finished wall instead of for a single cabinet, so the figure cannot be misread.
Then ask how the count is verified at handover. A commissioning step that displays a test pattern across the full wall confirms every cabinet is receiving data and that the mapped resolution matches the specification. Put that step in the acceptance criteria.
How does resolution affect running the screen later?
Resolution sets the baseline for everything downstream: content produced later has to match the same grid, replacements have to be the same module type, and expansion has to respect the same pixel structure. Recording the native count and module type in the handover documentation saves a great deal of guesswork years later.
Ask what documentation arrives with the job: cabinet and module references, the pixel map, processor configuration, and calibration data. A wall whose configuration is documented can be extended or repaired without a survey; one without it usually cannot.
| Factor | Effect on resolution |
|---|---|
| Wall size | More metres means more pixels at a fixed pitch |
| Pixel pitch | Smaller pitch packs more pixels per m2 |
| Cabinet size | Finished wall built in fixed increments |
| Processor | Must drive the native count and inputs |
| Content scale | Must be prepared at the native grid |
A wall that could not show 4K
A wide lobby wall was specified without checking the processor's output. The source was 4K but the wall showed it scaled, and the detail the client wanted was lost until the processing was upgraded.
A match that needed no scaling
A control room wall was sized so the operator windows divided cleanly into the native resolution. Maps and tables stayed sharp at the desks where they were read.
How to set a usable resolution
- Match resolution to content, not to the catalogue Decide the smallest detail the content carries, then size the wall so that detail renders at enough pixels. The screen should fit the message, not the other way around.
- Watch native versus scaled A canvas that does not divide into the source resolution forces scaling. Native resolution keeps edges sharp; scaling a live feed is where softness appears.
- Count pixels across the whole wall Total resolution is width times height across all cabinets. Confirm the processor can drive that count before the order is built.
Beliefs worth rechecking on resolution
“More pixels is always sharper” — Only if content, processing and viewing distance use them. Unused resolution is cost with no visible return.
“Resolution equals pitch” — Resolution is total pixel count; pitch is spacing. Both matter, and the processor decides whether the count is actually driven.
“Any 4K source looks 4K” — It looks 4K only when the wall, content scale and signal path all match. Mismatches quietly soften the image.
Points to verify on resolution
- State the native pixel count of the finished wall
- Give the native count to the content team early
- Confirm processor rated pixel capacity and inputs
- Plan content for curved or shaped walls
- Verify with a full-wall test pattern at commissioning
- Record pixel map and config in the handover pack