Can I mix cabinet sizes to hit an exact resolution?

Some product families offer half-height cabinets that help the physical size, but the pixel grid stays cabinet-quantised. Chasing an exact pixel count is rarely worth it outside broadcast — scaling is excellent.

Does higher resolution need a bigger controller?

Yes — controllers are sized in total pixels and pixels per port. Fine-pitch walls need more ports for the same physical size; check the data-wiring math before locking the processor model.

What aspect ratio should the wall be?

Whatever the content and architecture want — but 16:9 keeps standard content unletterboxed, which is why 600 × 337.5 mm fixed-install cabinets exist: they tile to 16:9 exactly.

LED wall resolution: how to calculate it and how much you need

From wall size and pixel pitch to real resolution — whole-cabinet grids, 4K math, pixel density and when more pixels are wasted money.

By wikiLED team · Updated 19 August 2026

Resolution is geometry, not a product spec

An LED wall has no inherent resolution. It has a pixel pitch, and the resolution is whatever wall size you build divided by that pitch: pixels wide = width ÷ pitch. A 4 m wall at 2.5 mm is 1,600 px wide; the same wall at 1.25 mm is 3,200 px.

Because walls are assembled from whole cabinets, real resolutions come in cabinet-sized steps. A 500 mm cabinet at 2.5 mm pitch is exactly 200 px wide, so wall widths jump 200 px at a time. Any target resolution gets resolved to the nearest buildable grid — the difference is usually invisible, but it should be known, not discovered.

pixels = wall dimension ÷ pitch (same units) · real resolution = cabinet grid × cabinet pixels

The 4K question

'Is it 4K?' usually means 'will my 3840-pixel-wide content map 1:1?'. Divide 3840 by the cabinet's horizontal pixels to see how many cabinets wide that takes: nineteen-plus 200 px cabinets, i.e. a 9.6 m wall at 2.5 mm pitch. Most walls are smaller and simply scale the content down — processors do this cleanly and viewers cannot tell at proper distances.

Native mapping matters in two places: broadcast/virtual-production walls where cameras see the pixels, and data-dense control-room content with 1 px lines. There, the wall is designed from the required pixel canvas backwards.

Pixel density: the honest comparison

Density — (1000 ÷ pitch)² pixels per m² — compares products independent of wall size. It also exposes the cost curve: halving the pitch quadruples the pixels (and much of the price). That is why the right question is never 'how much resolution can I afford' but 'how much can my viewers actually resolve' — which is the viewing-distance question.

density = (1000 ÷ pitch mm)² px/m²

Worked example

Target: a 4 × 2 m lobby wall, viewers no closer than 3 m. Viewing distance permits up to ~3 mm pitch; choose 2.5 mm. Resolution: 1600 × 800 px from 8 × 4 cabinets of 500 mm / 200 px. Full-HD content downscales from 1920 × 1080 — imperceptible at 3 m. Stepping to 1.9 mm would cost ~73% more pixels for sharpness nobody in the lobby can see.

Run these numbers on your own wall — free, no account.

Resolution calculator Full wall calculator

Frequently asked

Can I mix cabinet sizes to hit an exact resolution?: Some product families offer half-height cabinets that help the physical size, but the pixel grid stays cabinet-quantised. Chasing an exact pixel count is rarely worth it outside broadcast — scaling is excellent.
Does higher resolution need a bigger controller?: Yes — controllers are sized in total pixels and pixels per port. Fine-pitch walls need more ports for the same physical size; check the data-wiring math before locking the processor model.
What aspect ratio should the wall be?: Whatever the content and architecture want — but 16:9 keeps standard content unletterboxed, which is why 600 × 337.5 mm fixed-install cabinets exist: they tile to 16:9 exactly.