Troubleshooting

Why Is My QR Code Not Scanning? 11 Causes and How to Fix Each

A QR code fails to scan when the camera cannot separate dark modules from light ones, or cannot find the three corner squares that tell it where the symbol is. Almost every failure comes down to contrast, size, the blank margin around the code, damage, or a code that was dynamic and has expired. Work through the causes below in order: they start with the phone, move to the print, and end with the code itself.

1. Start with the phone, not the code

Before changing anything on the print, rule out the scanner. Every iPhone since iOS 11 and every Android phone since Android 9 reads QR codes with the built-in camera app, but some phones ship with the feature switched off: on Android look for "Scan QR codes" in the camera settings, on Samsung phones in the camera's More menu, and on iPhone under Settings, Camera, Scan QR Codes. Older phones and phones with the feature disabled need a scanner app or Google Lens.

Then check the basics. Wipe the lens, hold the phone still at roughly arm's length, and let it focus; moving closer than about ten centimetres puts most phone cameras out of focus. Avoid pointing a flash straight at glossy paper. If the phone shows the decoded address as a banner and you simply have not tapped it, the code is working.

2. Contrast is too low

A scanner decides whether each module is dark or light by comparing it with its neighbours. Dark grey on light grey, gold on cream, or a dark blue on a dark green background leaves the decision ambiguous and the read fails. The safe rule is a contrast ratio of at least 4.5 to 1 between the module colour and the background, measured the same way as for text; black on white is 21 to 1 and leaves the most margin for poor lighting.

Fix: darken the modules or lighten the background until the ratio clears 4.5, and print a sample. The generator on this site warns you below the preview when the two colours you picked fall under that threshold.

3. The colours are inverted

ISO/IEC 18004 defines a QR symbol as dark modules on a light background. Many scanners, including the default camera apps on some phones, will not read a light code on a dark background at all, and others read it inconsistently. Designers invert codes to match dark branding, and it is the single most common reason a code that "looks fine" refuses to scan.

Fix: keep the modules darker than the background. If the surrounding design is dark, print the code on a light panel with its own quiet zone, which also solves the next problem.

4. The quiet zone is missing

The quiet zone is the blank margin around the symbol, and the standard asks for four modules of it on every side. It is how the scanner tells where the code ends and the artwork begins. Borders, frames placed too tightly, text run right up to the edge, or a code placed against a dark photo all eat the quiet zone, and the finder patterns in the corners stop being recognisable.

Fix: leave a margin at least four modules wide, in the background colour, on all four sides. On a code with 29 modules across, printed at 30 millimetres, that is a little over four millimetres of clear space. The generator's frames are drawn outside the quiet zone for this reason; if you add your own frame in a layout tool, keep it outside too.

5. It is printed too small for the distance

The working rule is that a code should be at least one tenth of the distance it will be scanned from. A business card scanned from 20 centimetres needs a 2 centimetre code; a poster read from 3 metres needs a 30 centimetre one; a code on a window meant to be scanned from the pavement needs to be larger than most people expect. Dense codes with many modules need to be bigger still, because each individual module must be large enough for the camera to resolve it.

Fix: measure the realistic scanning distance, divide by ten, and use the size calculator to turn that into millimetres and pixels for your symbol's version. Shorten the payload if the code is too dense: a shorter address means fewer modules and a bigger module at the same print size.

6. The logo covers too much

A logo in the middle of a code works only because Reed-Solomon error correction can rebuild the modules it hides. Level L recovers about 7 percent of the symbol, M 15, Q 25 and H 30. A logo that covers a fifth of the area on a level-M code has already used the whole budget, and any dirt, glare or print defect on top of it pushes the code past what the scanner can reconstruct.

Fix: use level Q or H when a logo is present, keep the logo and its margin to well under a fifth of the symbol area, and never let it touch the three corner finder patterns. The error correction guide explains the budget in detail, and the logo tool raises the level for you automatically.

7. Gradients, patterns and rounded modules went too far

Rounded modules, dots and gradients scan fine when the modules stay clearly separated and every part of the gradient keeps enough contrast with the background. They fail when dots shrink so far that the code looks like a halftone, when a gradient runs to a colour close to the background, or when a pattern is placed behind the code.

Fix: check the lightest end of any gradient against the 4.5 to 1 rule, keep modules at their full size, and never place a texture or photograph behind the symbol. When in doubt, switch back to square modules for the print run; the scan is worth more than the styling.

8. The export is blurry or upscaled

A 300 pixel PNG enlarged to fill a poster becomes a soft grey blur with no sharp module edges, and the scanner's threshold between dark and light lands in the middle of every fuzzy edge. The same happens when a raster code is placed in a layout at a much larger size, saved as a JPEG at low quality, or screenshotted from a screen.

Fix: export an SVG for anything printed and let the layout software scale the vector; the vector QR code maker defaults to that. If you must use a raster, export at the final print size at 300 dots per inch, and never save a QR code as a low-quality JPEG.

9. The surface is curved, glossy or damaged

A code wrapped around a bottle or a cup distorts the square grid into a curve that the scanner may not be able to straighten, especially when the wrap covers more than a fifth of the circumference. Glossy laminate and glass reflect the room's lights as bright patches that read as light modules. Scratches, creases and fading take modules away outright.

Fix: print a smaller code on curved objects so the curvature across the symbol stays small, prefer matte finishes, and raise the error correction level to H on anything that will live outdoors or be handled. Error correction absorbs damage; it does not absorb geometry.

10. The payload is too long

A QR symbol grows with its content, up to version 40 with 177 modules on a side. A long tracking URL, a vCard with every field filled, or a paragraph of text produces a dense grid whose individual modules are tiny at any sensible print size, and dense codes are also more sensitive to every other problem on this list.

Fix: shorten the data. Use a short path on your own domain instead of a long tracked link, drop optional vCard fields, and keep text under a few hundred characters. The version and module count shown under the preview on this site tell you immediately whether a change helped.

11. The code was dynamic and has expired

If the phone reads the code without complaint but the page that opens is an error, an upgrade prompt or an unrelated site, the code is fine and the destination is the problem. Most often the code was dynamic: it contained a short redirect link owned by a QR service, and the redirect was switched off when a free trial or subscription ended. Static codes, which store the real address in the pattern, cannot fail this way.

Fix: there is no fix for the printed code; print a new one. Encode the final destination directly this time, so the replacement never depends on anyone's subscription. The article Do QR codes expire? explains how to tell the two kinds apart before you print.

12. The destination itself is broken

The remaining cases are not scanning failures at all. The web page moved, the WiFi password changed, the phone number was retired, or the address had a typo from the day it was made. A WiFi code also fails when the security type is wrong, for example WEP selected for a WPA2 network, or when the network name has a trailing space.

Fix: scan the code, read the decoded text on the phone before tapping it, and compare it character by character with what you intended. Fix the data, regenerate, and reprint.

13. A sixty-second test before you print

  • Print one copy at the final size on the final material.
  • Scan it with two different phones using the built-in camera app, from the real distance, in the real lighting.
  • Read the decoded address on the screen and confirm it is yours, not a short link on someone else's domain.
  • Cover a corner of the code with a thumb and scan again; if it fails immediately, raise the error correction level.
  • Only then send the file to press.

Sources & further reading

Make a Code That Scans First Time

Static, high-contrast, with a proper quiet zone and vector export. The read-out under the preview shows the version and error-correction level you are printing.

Open Free Generator