Why Your Custom-Logo QR Code Won't Scan (And How to Fix It Without Removing the Logo)لماذا لا يُمسح رمز QR بشعارك المخصّص (وكيف تصلحه دون إزالة الشعار)

A QR code with the brand's logo dropped into the centre is the visual that every marketing director wants. It looks polished, it looks intentional, it ties the QR to the brand identity instead of leaving a generic black-square dot pattern on the design. So the designer drops the logo in, exports the QR, the marketing director scans it on their iPhone, it works, the print run goes out — and then customer support starts getting complaints that 30% of recipients can't scan it. The logo isn't the problem. The way the logo was inserted is.

There are three rules that determine whether a logo-embedded QR works reliably. Almost every failure comes down to one of them being violated. Designers who learned QR generation through ad-hoc free tools have no way to know the rules — the tools don't enforce them, the failure mode is asymmetric (works on iPhone, breaks on a 2-year-old Android), and the bug surfaces after print. This piece walks through what's actually happening, the three rules, and how to fix custom-logo QRs without removing the logo.

What's actually happening when a logo breaks a QR

A QR code is a precisely-specified grid of black and white modules (the 'dots'). The camera scanning the QR uses three position-detection patterns in the corners to find the QR's orientation, then reads every module's black-or-white state to decode the data. The QR's built-in Reed-Solomon error correction lets some modules be unreadable — at level L it tolerates ~7% damage, at L it tolerates ~30% — but only up to that level. Beyond the tolerance, the scan fails.

A logo placed in the centre of the QR obscures the modules underneath it. From the camera's perspective, those modules are 'damaged' — the logo's colours don't match the black-or-white module state the QR's bitstream expects, so the decoder treats those modules as unreadable. The bigger the logo, the more modules obscured, the more 'damage' the error correction has to absorb. Past the threshold, the math fails and the scan returns no result.

There's a second, more subtle problem when there's no 'safe zone' between the logo and the QR modules: the modules at the boundary of the logo are not fully obscured but not fully visible either — half-covered. The camera's interpretation of these boundary modules becomes unreliable, sometimes reading them as black, sometimes as white, depending on the camera's angle, lighting, and processing pipeline. Different phone models interpret these ambiguous boundary modules differently. This is why a logo-embedded QR can scan reliably on iPhone (whose camera ML is more permissive) and fail on a budget Android (whose ML is stricter).

The three rules

Rule 1 — Logo size: ≤20% of QR width

The single most-violated rule. A logo larger than ~20-22% of the QR's width starts to obscure too many modules for even the highest error-correction level to fully recover. Designers who haven't seen this rule treat the centre of the QR as 'free design space' and push the logo to 35-40% of the width, because at that size the brand mark feels right. The QR then scans only on the most-permissive phones; the rest fail.

The 20% maximum is conservative but reliable. Some QRs survive up to 25% with very-high error-correction and clean module patterns, but the asymmetric phone-camera variability means 20% is the threshold below which scan reliability stays high across phone models. If your designer feels 20% is too small, the answer isn't to push beyond 20% — it's to make the QR itself physically bigger so the 20% logo is also bigger.

Rule 2 — Safe zone: clean white cutout around the logo

The QR modules underneath and immediately around the logo should be REMOVED, not just covered. Most QR generators do this by 'cutting out' a circular or rounded-square region in the QR pattern where the logo will sit, leaving clean white space behind the logo. The logo then sits in that clean area with a thin border between the logo edge and the surrounding modules. The boundary-ambiguity problem disappears — every module the camera reads is either clearly black or clearly white, never half-covered.

The safe zone should extend 2-4 modules beyond the logo's actual visible edge. Most QR generators handle this automatically; some don't. If your generator overlays the logo on top of an unchanged QR pattern (rather than cutting the pattern away first), the QR will exhibit the asymmetric-phone-failure behaviour even if the logo is within size limits. Switch generators.

Rule 3 — Error-correction level: H (30%)

QR codes support four error-correction levels: L (~7% redundancy), M (~15%), Q (~25%), and H (~30%). The default in most QR generators is M, which is fine for a plain QR with no logo but borderline-insufficient for a logo-embedded QR even with the size and safe-zone rules respected. For any logo-embedded QR, set the error-correction level to H during generation. This adds redundancy to the QR's encoded bitstream, so when the safe-zone cutout removes modules, there's enough redundant data elsewhere in the pattern that the decoder can still reconstruct the original payload.

The cost of error-correction H is that the QR itself becomes slightly larger (more modules needed to encode the same data with more redundancy). For a typical short URL, level H increases the QR from ~Version 3 (29×29 modules) to ~Version 4-5 (33×33 or 37×37 modules). At a printed size of 3-4 cm, the difference is barely visible. The reliability gain is large.

Three rules, one example

Concrete numbers. You're generating a QR that will be printed at 4 cm wide. The brand wants the logo in the centre.

• Maximum logo width: 20% of 4 cm = 0.8 cm. The logo's visible mark should fit inside a 0.8 cm square area (or a 0.9 cm circle for a circular logo).
• Safe-zone cutout: extends 2-4 modules beyond the logo edge. At a 4 cm QR with ~33 modules across (Version 4 at error-correction H), each module is ~1.2 mm. A 3-module safe-zone margin = ~3.6 mm. The total clean area in the QR centre is roughly 0.8 cm + 0.7 cm (extra 3.5 mm on each side) = ~1.5 cm.
• Error-correction level: H. Generate the QR explicitly at level H, do not accept the default.

Print the result at 4 cm. Test on three phones (one iPhone, one mid-range Samsung, one mid-range Xiaomi/Huawei/Oppo). If all three scan reliably from 25-30 cm away, the production run is cleared.

When the rules aren't enough — secondary fixes

If you've followed the three rules and a logo-embedded QR still has scan issues, the secondary suspects are:

Logo colour conflicts with QR module colour

If the QR modules are dark indigo (not pure black) and your logo is also dark indigo, the boundary modules — even with a safe zone — can blend visually under certain lighting. Increase the contrast: keep QR modules pure black and the logo a clearly different colour, OR keep the logo dark and the QR background clearly white (not off-white). The visual elegance of the brand palette can fight the QR's scan-reliability requirements; tune the colours so they're brand-on but scan-clean.

Logo has fine detail that visually competes with module pattern

A logo with intricate fine lines (calligraphic Arabic logotypes, detailed crests, fine-line illustrative marks) can visually 'connect' to the surrounding QR module pattern at small print sizes, confusing the camera even with proper safe-zone separation. Simplify the in-QR version of the logo — use a more iconographic or geometric simplification of the brand mark specifically for the QR-centre placement. Keep the full intricate logo for everywhere else on the design.

Print quality on the actual material

Even with perfect three-rules generation, a logo-embedded QR printed on absorbent material (uncoated cardstock, kraft paper) can develop ink bleed at the logo edge, contaminating the safe-zone. Test on the actual print material before committing. For absorbent or textured material, increase the QR size by 15-20% to compensate.

What designers should NEVER do

• Drop a logo into a QR in Photoshop without using a QR-aware tool that creates the safe-zone cutout. Photoshop will happily overlay the logo on top of intact QR modules — the file looks right; the scan fails.
• Resize the logo to fit a 'designer judgment' size larger than 20% because 'it looks better that way'. Designer judgment ≠ scan reliability. Both can be right; you need a tool that enforces both.
• Skip the multi-phone test before printing. The single-iPhone-on-the-designer's-desk test is the most common pre-failure pattern.
• Use a logo with detail that competes with QR module size — simplify the in-QR variant.
• Default to error-correction level M because the generator's UI hides the H option. Find the option; set it.

What's actually achievable with logo-embedded QR

Done right, a logo-embedded QR is essentially indistinguishable in scan reliability from a plain QR. Major MENA brands use them at scale on packaging, signage, business cards, and marketing collateral without scan problems. The reliability comes from the three rules, not from special technology. Any QR-generation tool that enforces the three rules automatically produces logo-QRs that work; any tool that doesn't requires the designer to enforce them manually — and most designers don't know the rules exist.

How QRA handles logo-embedded QR

QRA enforces all three rules by default. When you upload a logo into the QR generator, the platform automatically: sizes the logo to fit ≤20% of QR width (with a manual override for designers who want to push to 22% on specific high-contrast use cases); creates a safe-zone cutout with appropriate margin around the logo edge; sets error-correction to level H whenever a logo is present. The exported QR (PNG, SVG, EPS) embeds the logo as vector geometry, preserving sharpness at any print scale. Multi-phone scan testing is built into the preview — the platform suggests testing against a real device library before committing the design to print.

The short answer

Custom-logo QRs fail when the logo is too big, when there's no safe-zone cutout, or when error-correction was left at the default. Fix is three rules: logo ≤20% of QR width, clean white cutout around the logo extending 2-4 modules beyond its edge, error-correction level H. Use a QR generator that enforces these automatically (most don't). Test on at least three phones (especially mid-range Androids) before printing. The logo stays in the QR; the scan reliability comes back; the brand and the engineering both win.