Physical size ÷ pixel pitch
This gives a theoretical estimate. It is useful for comparing candidate pitches and testing whether a target resolution is physically realistic.
Choose the Uniview LED website that best matches your market or language.
Published September 01, 2026· Updated September 01, 2026· Uniview LED Knowledge Center
LED Wall Resolution Engineering

Planning vs production
The first calculation is useful before a product is selected. The second is the calculation that should appear on the final cabinet map, processor plan and project approval drawing.
This gives a theoretical estimate. It is useful for comparing candidate pitches and testing whether a target resolution is physically realistic.
This is the commissioning value. The result follows released cabinet and module geometry rather than an independently rounded theoretical number.
Worked calculation
This example shows the difference between an early planning estimate and a production-ready cabinet calculation.

First-party product arithmetic
This is the clearest demonstration that physical screen dimensions alone do not determine native resolution. Pixel pitch and cabinet resolution do.
Uniview LED UHD uses a 960 × 540 mm 16:9 cabinet. The released product data shows different cabinet pixel matrices by pitch. On a 5 × 5 cabinet wall, the physical size remains 4.80 × 2.70 m, while the native pixel canvas changes with the selected model.
| Configuration | Pixel pitch | Cabinet resolution | Cabinet grid | Physical size | Native resolution |
|---|---|---|---|---|---|
| UHD2.5 | 2.5 mm | 384 × 216 px | 5 × 5 | 4.80 × 2.70 m | 1920 × 1080 |
| UHD1.2 | 1.25 mm | 768 × 432 px | 5 × 5 | 4.80 × 2.70 m | 3840 × 2160 |
The GHC 600 × 337.5 mm 16:9 cabinet uses different pixel matrices at 0.9375, 1.25 and 1.5625 mm. Each can reach a 3840 × 2160 native canvas with a different cabinet grid and therefore a different physical wall size.
| Reference pitch | Pixels per cabinet | 4K cabinet matrix | Native canvas | Approx. physical size |
|---|---|---|---|---|
| 0.9375 mm | 640 × 360 | 6 × 6 | 3840 × 2160 | 3.60 × 2.025 m |
| 1.25 mm | 480 × 270 | 8 × 8 | 3840 × 2160 | 4.80 × 2.70 m |
| 1.5625 mm | 384 × 216 | 10 × 10 | 3840 × 2160 | 6.00 × 3.375 m |
Target resolution first
Reverse calculation is useful when the content canvas is already defined and the available wall width is known.
For Full HD use 1920 × 1080. In this guide, 4K means 4K UHD at 3840 × 2160.
Approximate pitch = active wall width in mm ÷ target horizontal pixels.
Select the closest released pitch and verify that the cabinet grid produces an acceptable native canvas and physical size.
| Active wall width | 1080p target pitch | 4K UHD target pitch |
|---|---|---|
| 3 m | ≈ 1.56 mm | ≈ 0.78 mm |
| 4 m | ≈ 2.08 mm | ≈ 1.04 mm |
| 4.8 m | ≈ 2.50 mm | ≈ 1.25 mm |
| 6 m | ≈ 3.13 mm | ≈ 1.56 mm |
Validate the calculated wall
A mathematically correct native canvas can still be the wrong project choice if viewing distance, content, signal processing, installation or service access are ignored.
A finer pitch is justified when viewers are close enough to see pixel structure or must read small text. Use viewing need and real content—not a single universal pitch-to-distance rule.
Dashboards, maps, spreadsheets and broadcast graphics benefit from more native pixels than large logos or long-distance advertising. One-to-one mapping is valuable when practical, but a LED wall does not have to be an integer multiple of the source resolution.
Confirm the total pixel load, output-port topology, source resolution, scaling method, frame rate and receiving-card plan. Processing capacity should be checked against the actual native canvas rather than the theoretical size/pitch estimate.
Finished width and height follow complete cabinets or approved mixed-cabinet geometry. Service access, trim, cable routes and structural tolerances should be coordinated with the cabinet map.
The calculation does not change outdoors, but larger viewing distances, daylight brightness, weather protection and larger cabinet formats often shift the practical pitch and native resolution.
The real number must come from a buildable module and cabinet matrix. Do not independently round 1,231 pixels to 1,230, 1,232 or 1,280 without checking cabinet geometry.
“1000 × 1000 mm” describes physical size; “256 × 256 px” describes the pixel matrix. Mixing these units can create major layout errors.
Module count is calculated in both directions. For example, a 96 × 96 pixel cabinet built from 48 × 32 pixel modules contains 2 modules across and 3 high—6 modules total, not 4.
LED walls often use non-standard native canvases. The correct question is whether mapping, scaling or cropping can preserve the required content quality and workflow.
Viewing distance matters, but target native resolution, content detail, wall size, budget and cabinet options must be evaluated together.
Extra pixels add value only when viewers, content and the signal chain can use them. Overspecification increases cost without guaranteeing a visible benefit.

Before approval
Use millimeters for width and height so the physical-size calculation and pixel pitch use consistent units.
Identify whether the source is Full HD, 4K UHD, an ultrawide canvas or a custom pixel map.
Use it to test candidate pitches and estimate whether the target pixel density is realistic.
Do not finalize from theoretical pitch alone. Confirm released pitch, cabinet dimensions and pixels per cabinet.
Multiply cabinet columns and rows by the exact horizontal and vertical pixel count per cabinet.
Verify that the selected pitch supports the required text size, visual detail and viewer position.
Confirm whether content will be mapped 1:1, scaled, cropped or produced specifically for the native LED canvas.
Check total pixels, frame rate, output topology, source inputs and any redundancy requirements.
Coordinate active dimensions, supporting structure, cable paths, trim and service access before fabrication.
Keep the cabinet matrix, native resolution, selected pitch and approved product revision in the final project record.
Common questions
For early planning, horizontal pixels ≈ wall width in millimeters ÷ pixel pitch in millimeters, and vertical pixels ≈ wall height ÷ pixel pitch. The final buildable native resolution should then be calculated from the cabinet grid and the exact cabinet pixel matrix.
Do not round it independently. Treat the decimal value as a theoretical estimate, select an actual cabinet configuration, and use the cabinet pixel matrix to determine the achievable native resolution.
Multiply the number of cabinet columns by the horizontal pixels per cabinet, and multiply the number of cabinet rows by the vertical pixels per cabinet. For example, five 768 × 432 pixel cabinets across and five high produce 3840 × 2160 pixels.
It depends on the physical wall size. A 4.8 m wide wall needs an approximate horizontal pitch of 4800 ÷ 3840 = 1.25 mm for 4K UHD. A 6 m wide wall needs about 1.56 mm. Always move from this estimate to a real cabinet configuration before approval.
Yes. Custom LED walls commonly use non-standard native canvases because their dimensions follow room geometry and cabinet count. Modern processors can map and scale source content to the native canvas; 1:1 mapping is useful when practical but is not always required.
The pixel-count principle is the same, but use the active surface length represented by the approved curved cabinet layout rather than assuming a simple flat-wall chord. Curved projects should be calculated from the final cabinet map.
Yes. Resolution arithmetic is the same. The practical product choice differs because outdoor projects often use longer viewing distances, higher brightness, weather protection and different cabinet formats.
No. 4K UHD provides four times the total pixels of 1080p, but those pixels create value only when the viewing distance, content detail, physical screen size and budget justify the finer pitch and higher native resolution.
Continue learning
Final calculation rule
Before production, freeze the active dimensions, selected pixel pitch, cabinet grid, native pixel canvas, processor loading, viewing distance and content mapping as one coordinated system.