What a pixel defect is
A pixel defect is a single LED or sub-pixel that fails to light, lights wrong, or shifts in colour or brightness compared with its neighbours. On a wall of millions of pixels, isolated defects appear over time.
The defect is judged against the rest of the wall, because a single off pixel is far more visible on a plain dark field than in busy content.
Why it matters to the buyer
Defects are the most visible sign of quality and age, and they are what a client points at during acceptance. The agreed level decides whether a wall passes or is reworked.
They also signal the underlying build quality, because a wall that ships with many defects usually has weak drivers, poor soldering or mishandled modules.
How defects are counted
The level is stated as a count or a rate per area, often with a distinction between a fully dead pixel and a dim or colour-shifted one, because the latter is less visible.
The count is taken at a defined viewing distance and content, because a dark test field shows defects that bright content hides, so the condition is part of the agreed number.
Acceptance and the contract
The acceptance level is agreed before delivery as a maximum number or rate, so handover is a check against that line, not an opinion on the day.
A clear line also sets the service response: above the line the supplier reworks; below it the wall is accepted and monitored as it ages.
How it relates to service
Most defects are fixed by swapping the affected module or the pixel's part, which is why front or rear service access is part of the same conversation.
A wall designed for fast module swap keeps the defect count down in use, because a failed module is replaced before it spreads or annoys the client.
Common mistakes
The frequent error is leaving the defect level unstated, so handover becomes an argument about what looks acceptable instead of a check against a number.
Another is judging only at handover and ignoring the rate of new defects, which is what actually tells you about long-term build quality.
A further error is judging defects only by eye at handover and skipping the documented count. Two walls can look similar yet carry very different defect rates, and the rate of new defects after start-up is what signals build quality. The number, not the impression, is the contract.
What to write into the specification
State the maximum defect count or rate at acceptance, the viewing distance and content used to count, and the service response above the line.
Tie the level to the wall's use, because a broadcast or close-view wall needs a tighter line than a roadside board.
Checking defects on a quote
Ask for the acceptance number as a written limit with the measurement condition, instead of a promise of 'no dead pixels' that no large wall can honestly meet.
Confirm the service turnaround for defects above the line, so the contract covers the wall as it ages, not only as it ships.
A dispute settled by the contract
A buyer flagged a few failed pixels at handover. Because the contract stated the allowed count at a set distance, both sides agreed the wall passed without a fight.
No level, endless argument
An order shipped without an agreed defect level. At acceptance each side held a different standard, and the handover stalled until a retroactive number was negotiated.
How to apply this
- Agree the acceptance level before delivery Set a maximum defect count or rate at a defined viewing distance in the contract. The line between normal and unacceptable is a number you agree up front, not after.
- Define how defects are counted State the method and the distance used to count, and whether clustered defects count differently. A clear method stops arguments at acceptance.
- Tie defects to service Write which defects are covered during the warranty and how a borderline wall is handled. This connects the acceptance level to the repair path.
- Ask for the level on the quote Request the proposed acceptance level and counting method on the quotation, so suppliers are compared on the same basis.
Common misconceptions
“Zero defects is realistic.” — On a wall of millions of pixels, a few failures over time are expected. The practical control is the agreed acceptance level, not a zero target that no production line meets.
“Defects are only a warranty problem.” — The acceptance level decides whether the wall is accepted at all. Settling it before delivery prevents handover disputes and links directly to the service path.
Key takeaway
A pixel defect is a single LED or sub-pixel that fails or shifts against its neighbours, and on a wall of millions some appear over time. The practical control is the agreed acceptance level, a maximum count or rate at a defined viewing distance and content, set before delivery so handover is a check against a number. Most defects are fixed by swapping the module, so service access and turnaround are part of the same specification.