When planning a COB LED wall, two of the most common questions are: How large should the LED wall be? and Can it achieve native 4K resolution?
These questions are closely related, but they are not the same.
A larger LED wall does not automatically have a higher resolution, while a smaller LED wall can sometimes achieve the same pixel resolution with a finer Pixel Pitch. The relationship depends on three key factors: Pixel Pitch, cabinet pixel matrix, and cabinet configuration.
This article explains how these factors determine the relationship between COB LED wall size and resolution, with practical examples of how different Pixel Pitches can achieve native 4K.
Pixel Pitch is the distance between the centers of two adjacent LED pixels, measured in millimeters.
In a basic calculation:
Horizontal Pixels = Effective Width ÷ Pixel Pitch
Vertical Pixels = Effective Height ÷ Pixel Pitch
For example, if an LED wall is 4,800 mm wide and uses a 1.25 mm Pixel Pitch:
4,800 ÷ 1.25 = 3,840 pixels
The same principle applies to the vertical direction.
This means Pixel Pitch determines how many pixels can fit into a specific physical area.
A smaller Pixel Pitch provides a higher pixel density, allowing more pixels to fit within the same physical space. A larger Pixel Pitch requires more physical space to accommodate the same number of pixels.
However, this calculation is only the starting point for LED wall planning.
A COB LED wall is normally assembled from standard cabinets or modules rather than built to an arbitrary pixel dimension.
For this reason, engineering calculations should not rely only on dividing the physical cabinet dimensions by Pixel Pitch and rounding the result.
A more reliable approach is to use the actual cabinet pixel matrix specified for the applicable product.
For example, if a cabinet measures: 600 × 337.5 mm
and its specified pixel matrix is: 480 × 270 pixels
then the total LED wall resolution can be calculated directly from the cabinet matrix.
This approach avoids rounding errors and makes it easier to determine how many cabinets are required to achieve a target resolution.
For an actual project, the manufacturer's technical specification should always take priority over a theoretical calculation.
Once the cabinet pixel matrix is known, the next step is to determine how many cabinets are required horizontally and vertically.
The basic calculation is:
Horizontal Cabinet Count = Target Horizontal Pixels ÷ Cabinet Horizontal Pixels
Vertical Cabinet Count = Target Vertical Pixels ÷ Cabinet Vertical Pixels
For a native 4K target of:
3,840 × 2,160 pixels
the cabinet matrix needs to be compatible with this target.
For example, a cabinet with a 480 × 270 pixel matrix can be used as follows:
3,840 ÷ 480 = 8
2,160 ÷ 270 = 8
This produces an: 8 × 8 cabinet configuration
The final physical dimensions then depend on the physical dimensions of each cabinet.
This is why specifying an LED wall simply as “4K” is not enough. The cabinet dimensions and pixel matrix must also be considered.
The term “4K” can refer to different aspects of an LED display system.
A controller may accept a 4K input signal, but that does not necessarily mean the LED wall itself has a native 3840 × 2160 pixel matrix.
It is useful to distinguish between three concepts:
4K Input
The controller or display system can receive a 4K video signal.
Scaled 4K Display
A 4K signal is processed and scaled to fit a display with a different physical pixel matrix.
Native 4K Display
The LED wall itself has a physical pixel matrix of approximately:
3840 × 2160 pixels
For projects that require true native 4K output, the physical pixel matrix of the LED wall is therefore more important than simply confirming 4K signal compatibility.
This leads to the next engineering question:
How does Pixel Pitch affect the physical size required to achieve native 4K?
The answer is straightforward.
A finer Pixel Pitch places more pixels within the same physical area. Therefore, the same 3840 × 2160 pixel matrix can be achieved with a smaller physical LED wall when the Pixel Pitch is finer.
However, cabinet dimensions and cabinet pixel matrices must also be considered.
The following examples use a 600 × 337.5 mm cabinet as a mathematical example to demonstrate this relationship. They are intended to explain the engineering principle and should not be treated as specifications for a particular product SKU. Actual cabinet dimensions and pixel matrices should always be verified against the applicable product documentation.
For a fixed native resolution, pixel pitch determines the active display dimensions: multiply the horizontal and vertical pixel counts by the pitch. The following examples use the same 600 × 337.5 mm cabinet format to show how 1.25 mm and 0.9375 mm pitches produce different wall sizes and cabinet counts for native 4K.
Assume a 600 × 337.5 mm cabinet using a theoretical 1.25 mm Pixel Pitch.
Horizontal pixels: 600 ÷ 1.25 = 480 pixels
Vertical pixels: 337.5 ÷ 1.25 = 270 pixels
Therefore, one cabinet represents: 480 × 270 pixels
To achieve native 4K:
3,840 ÷ 480 = 8 cabinets horizontally
2,160 ÷ 270 = 8 cabinets vertically
The required configuration is therefore: 8 × 8 cabinets
The physical dimensions are:
8 × 600 mm = 4,800 mm
8 × 337.5 mm = 2,700 mm
The resulting LED wall is: 4.8 × 2.7 m
with a theoretical native resolution of: 3,840 × 2,160 pixels
Under these assumptions, a 1.25 mm Pixel Pitch requires approximately a 4.8 × 2.7 m LED wall to achieve native 4K.
Now consider the same 600 × 337.5 mm cabinet with a finer 0.9375 mm Pixel Pitch.
Horizontal pixels:
600 ÷ 0.9375 = 640 pixels
Vertical pixels:
337.5 ÷ 0.9375 = 360 pixels
One cabinet therefore represents:
640 × 360 pixels
For native 4K:
3,840 ÷ 640 = 6 cabinets horizontally
2,160 ÷ 360 = 6 cabinets vertically
The required configuration becomes: 6 × 6 cabinets
The physical dimensions are:
6 × 600 mm = 3,600 mm
6 × 337.5 mm = 2,025 mm
The resulting LED wall is: 3.6 × 2.025 m
while still providing: 3,840 × 2,160 pixels
This demonstrates how a finer Pixel Pitch can achieve the same native 4K resolution within a smaller physical LED wall.
The two examples show how Pixel Pitch affects the physical size of a COB LED wall while maintaining the same native 4K resolution.
|
Pixel Pitch |
Cabinet Pixel Matrix |
Cabinet Configuration |
Approx. LED Wall Size |
Native Resolution |
|
1.25 mm |
480 × 270 |
8 × 8 |
4.8 × 2.7 m |
3840 × 2160 |
|
0.9375 mm |
640 × 360 |
6 × 6 |
3.6 × 2.025 m |
3840 × 2160 |
Both configurations reach the same native 4K pixel matrix, but their physical dimensions are different.
The reason is Pixel Pitch.
A finer Pixel Pitch increases pixel density, allowing the required 3840 × 2160 pixels to occupy a smaller physical area. A larger Pixel Pitch requires more physical space to accommodate the same number of pixels.
This is why COB LED wall size and resolution cannot be evaluated separately from Pixel Pitch.
At the same time, the smallest available Pixel Pitch is not necessarily the best choice for every project.
The appropriate Pixel Pitch should also be evaluated against:
The goal is not simply to select the smallest Pixel Pitch. The goal is to find the right balance between pixel density, physical size, viewing conditions, system requirements, and cost.
Choosing a COB LED wall should start with the project requirements rather than the product name or a “4K” label.
First, define the required LED wall size, viewing distance, and content type. Then determine whether the project requires native 4K resolution or simply 4K input compatibility.
The proposed configuration should clearly specify:
Physical LED Wall Size
Overall width, height, and aspect ratio.
Cabinet Configuration
The number of cabinets horizontally and vertically.
Total Pixel Matrix
The actual native pixel resolution of the complete LED wall.
Pixel Pitch
The pixel spacing and resulting pixel density.
Processing Requirements
Controller and processing capacity required for the final pixel matrix and signal workflow.
Content Adaptation
How 16:9, 4K, and other content formats will be displayed.
The key relationship is:
Before procurement, these parameters should be checked against the installation space, viewing requirements, content, processing capacity, and project budget.
Q1: Does a larger COB LED wall always have a higher resolution?
A1: No. Resolution depends on the number of physical pixels, not simply the physical size of the LED wall. A larger wall with a larger Pixel Pitch can have fewer pixels than a smaller wall with a finer Pixel Pitch.
Q2: Does a 4K input mean the COB LED wall is native 4K?
A2: No. A display can accept a 4K input signal while having a lower physical pixel matrix. Native 4K requires the physical LED wall itself to provide approximately 3840 × 2160 pixels.
Q3: Does a smaller Pixel Pitch always mean a better COB LED wall?
A3: Not necessarily. A smaller Pixel Pitch provides higher pixel density and can reduce the physical size required for a given resolution, but the best choice also depends on viewing distance, screen size, content, installation conditions, processing requirements, and budget.
Q4: What specifications should be checked before purchasing a COB LED wall?
A4: At minimum, check the Pixel Pitch, cabinet dimensions, cabinet pixel matrix, cabinet configuration, total LED wall dimensions, native resolution, and controller requirements.
Designing a COB LED wall is more than choosing a Pixel Pitch and calling it “4K”. A reliable design connects Pixel Pitch, cabinet pixel matrix, cabinet configuration, physical wall size, and native resolution.
In simple terms, 4K defines the required pixel count, Pixel Pitch determines pixel density and physical size, and cabinet configuration determines how those pixels are assembled into the final LED wall.
For a project-specific solution, provide your LED wall dimensions, viewing distance, content type, target resolution, and technical requirements. These parameters can then be matched with the appropriate cabinet configuration and verified before procurement.
Need help designing the right COB LED wall?
→ Contact Premteco team for a project-specific recommendation.
By continuing to use the site you agree to our privacy policy Terms and Conditions.