Free scan · £29 Register · £79/mo Watch
United Kingdom · CAP Code · landing pages
Pixel density and PPI claims on UK display landing pages — CAP literacy
Display marketers cite PPI, pixel density and sharpness on product detail pages alongside resolution heroes. Under CAP Code 3.7, measurable density claims need consistent size and pixel bases on the URL you submit. This guide supports register inventory — not ASA clearance and not legal advice.
Pixel density heroes on display landing pages
Phone, laptop and monitor pages cite PPI, pixel density and sharpness beside resolution and panel technology badges.
Buyers may assume marketed sharpness applies across all presets and scaling settings without reading OS scaling footnotes.
Start with glare reduction display claims, energy efficiency rating claims, and repairability score claims when spec modules stack.Common PPI and pixel density wording patterns
| Hero phrase | What to inventory | CAP note |
|---|---|---|
| PPI / pixels per inch | Numeric density | Hold size basis |
| Retina / HiDPI | Brand term vs number | Check if numeric PPI also shown |
| 4K / UHD density | Resolution + size | Calculate consistency |
| Ultra-sharp pixel clarity | Puffery risk | Pair with measurable PPI if used |
| Per-eye VR density | Basis note | Split binocular claims |
Separate PPI numbers from generic sharpness claims
Crystal-clear picture lines without PPI or resolution numbers may be puffery — log whether heroes cite measurable density or tone alone.
Comparison tables that mix different diagonal sizes on one PPI row create register contradictions — split rows when templates reuse one line across SKUs.
See claim register agency template when handoffs lack a display substantiation column.Retina and HiDPI marketing terms may appear without numeric PPI — classify puffery versus measured pixel density before register entry.
Laptop panels quote diagonal PPI while phone pages cite linear pixel density — inventory measurement basis strings beside PPI heroes.
Subpixel layout may affect perceived sharpness without changing PPI — log RGB versus Pentile descriptions when footnotes exist.
Scaling defaults on operating systems may affect sharpness claims — register OS scaling footnotes separately from hardware PPI.
VR headset PPI may cite per-eye values — split binocular claims when heroes do not specify single-eye basis.
Monitor size rounding affects calculated PPI — note whether marketing uses 27-inch class versus exact diagonal in substantiation.
Ultrawide monitors may cite horizontal pixel density only — inventory axis basis when comparison tables mix aspect ratios.
Retailer spec imports may miscalculate PPI from resolution and size — verify arithmetic when feeds disagree with manufacturer pages.
Touch layer stack may be omitted from PPI footnotes — log touch versus non-touch SKUs separately on register rows.
Anti-glare coatings do not change PPI but may affect clarity claims — read glare reduction guide when clarity heroes stack with PPI.
4K on 27-inch versus 32-inch yields different PPI — split size classes when one hero template spans multiple SKUs.
CiteBefore does not measure panels — substantiation remains your lab or supplier specification folder.
Comparison against Apple Retina thresholds may be comparative — read comparative claims guide when rivals are named beside PPI.
Projector pixel density may cite screen size assumptions — inventory throw distance footnotes when PPI depends on setup.
E-ink PPI claims may cite different rendering modes — register refresh mode when heroes assume static text rendering.
Kiosk displays may quote viewing distance assumptions — log distance footnotes when PPI heroes mention optimal viewing range.
Factory calibration does not alter PPI numerics — keep calibration claims on separate register rows from pixel density.
Outlet pages may show wrong size class in feed metadata — rescan when PPI heroes follow automated spec tables.
Dual-screen laptop marketing may cite combined pixel counts — split inner and outer panel PPI on two register rows.
Magnifier accessibility modes may upscale content without changing native PPI — note software magnification footnotes when present.
Retina and HiDPI marketing terms may appear without numeric PPI — classify puffery versus measured pixel density before register entry.
Laptop panels quote diagonal PPI while phone pages cite linear pixel density — inventory measurement basis strings beside PPI heroes.
Subpixel layout may affect perceived sharpness without changing PPI — log RGB versus Pentile descriptions when footnotes exist.
Scaling defaults on operating systems may affect sharpness claims — register OS scaling footnotes separately from hardware PPI.
VR headset PPI may cite per-eye values — split binocular claims when heroes do not specify single-eye basis.
Questions
Are PPI pixel density claims objective under CAP Code 3.7?
Numeric PPI, pixels per inch and resolution-plus-size claims are measurable when diagonal and pixel counts are held — inventory exact spec strings.
Must PPI claims match the size class sold?
Register rows should tie each screen size and panel SKU to substantiation — mixed size classes on one hero create contradiction risk.
Does CiteBefore measure panel PPI?
No. CiteBefore inventories visible advertising copy on submitted URLs. Supplier specs remain your product folder.
Can 4K resolution heroes substantiate PPI alone?
Resolution without diagonal size does not define PPI — log both rows when spec modules stack.
Do retailer feeds miscalculate PPI?
Automated feeds sometimes miscompute density — log merchant strings separately from manufacturer pages.
Inventory PPI heroes before retailer feeds refresh
Free scan and Watch flag contradictions when size classes or feeds drift from your register.
All guides: /guides/.