Skip to content
UseQR
ESC

↑↓ MOVE↵ OPEN48 PLACES

Troubleshooting

QR code scans on one phone but not others

One phone scanning is a warning, not a success — the code is at the margin of decodability and one decoder squeaks through. Usual causes are modules too small for other cameras to sample, fixed or long minimum focus distance on budget phones, and damage or logo coverage eating the error-correction budget. Fix by raising every margin at once.

View as MarkdownPaste this page into any AI assistant — it is plain, portable Markdown.

One phone working is a warning sign

A healthy QR code decodes on effectively everything. When only one phone reads it, that phone is not special — the code is marginal, and one camera-decoder combination happens to squeak over the line. Treat it as a failure that has not finished happening, because it will also fail for most of your audience.

Cause 1 — modules too small for the camera to sample

A decoder needs roughly 3–4 camera pixels per module to threshold reliably. How many pixels a module actually receives depends on the camera's resolution, its field of view and the scanning distance — which is why the 10:1 distance rule exists. A flagship with a high-resolution sensor and sharp optics samples a marginal code adequately; a budget phone's basic camera does not. Full mechanics: module size vs camera resolution.

Fix: larger print, or a shorter payload — both make each module bigger.

Cause 2 — focus distance

Small codes invite people to move the phone close, and every lens has a minimum focus distance — typically around 8–10 cm on phones without a macro mode. Inside that distance the image gets bigger and blurrier at the same time. Phones that auto-switch to a macro lens cope; fixed-focus budget phones fail hardest.

Fix: print the code large enough to scan comfortably from 15 cm or more, so nobody needs to lean in.

Cause 3 — the error-correction budget is already spent

Error correction tolerates a fixed share of damaged codewords — up to 30% at level H. A logo takes a slice, ink spread takes a slice, a scuff or glare takes a slice. When the budget is nearly exhausted, decoding turns probabilistic: the phone with the best optics and the most persistent decoder recovers the pattern, everything else gives up.

Fix: shrink or remove the logo, reprint cleanly, raise the contrast.

Cause 4 — decoder differences

Decoding software differs in how many binarisation passes it runs, whether it retries with inverted polarity, and how much perspective distortion it tolerates. Those differences only matter for marginal codes — which is the diagnostic point. If the split runs along platform lines, see scans on Android but not iPhone.

The fix is margins, plural

Do not hunt for a single culprit. Raise every margin at once and the symptom disappears:

Margin Action
Module size Print larger, or shorten the payload to drop the version
Contrast Dark on light, ≥ 40% luminance difference
Quiet zone 4 modules minimum on every side
Error correction Keep a reserve — no logo over ~20% coverage
Focus Size the code for scanning at 15 cm or more

Run the artwork through our validator, which decodes the rendered output and reports contrast and quiet-zone problems, and sanity-check the size against distance with the size calculator.

FAQ

Why does a QR code scan on my phone but not other people's?

Your phone's camera and decoder are slightly more capable, and the code is marginal — too small, too low-contrast, too dense or too damaged. The fix is improving the code, not upgrading everyone else's phones.

Are some phone cameras better at reading QR codes?

Yes. Higher resolution, better optics, closer minimum focus and more persistent decoding software all widen tolerance. That is exactly why testing only on a flagship is misleading — it reads codes your audience's phones cannot.

Does raising error correction make a QR code scan on more phones?

Only when the budget is genuinely being spent on damage or a logo. On a clean code, raising it adds modules and makes each one smaller at the same printed size, which can make marginal scanning worse, not better.

How small is too small for a QR code module?

In print, keep modules at 0.4 mm or larger and the whole code at least a tenth of the scanning distance wide. Below that, budget cameras cannot give the decoder the 3–4 pixels per module it needs.

Try it — free, no signup

  • QR code not scanning: the checklistWork through these in order, because they are ranked by how often they are the actual cause: quiet zone, contrast, size for distance, glare, blur from…
  • QR code scans on Android but not iPhoneUsually a decoder difference, not a broken code — Android-only URI schemes, Micro QR, very dense codes or an old iPhone. Causes ranked, with fixes.
  • QR code too small to scan — the fix ladderCameras need 3–4 pixels per module. Minimum sizes by scan distance, why shortening the payload beats enlarging the code, and the 2 × 2 cm print floor.
  • Module size vs camera resolutionA decoder needs roughly three or more image pixels per module. The arithmetic from sensor to module, and why tiny codes fail on older cameras.