Why Won't My QR Code Scan? Troubleshooting Common Scanning Errors

How a Phone Reads a QR Code

When you point a camera at a QR code, the decoder first looks for the three large squares in the corners, called finder patterns. They tell the software where the code is, how big it is and how it is rotated. Smaller alignment patterns and the timing lines between the finders then help it map every module onto a grid.

Next, the decoder decides whether each module is dark or light, reads the format information that describes the error-correction level and mask, and finally reconstructs the data. Reed-Solomon error correction can repair a portion of damaged or unreadable modules, but only up to the level chosen when the code was created: about 7% for level L, 15% for M, 25% for Q and 30% for H.

Understanding these steps explains most failures: if the finder patterns are hidden, the grid cannot be mapped, or too many modules are misread, the code cannot be decoded.

The Most Common Scan Failures

In our experience supporting HAYAQR users, the same problems appear again and again. Most can be spotted in seconds once you know what to look for.

• Insufficient contrast: dark grey on light grey, or brand colours that are too similar in brightness, fail under dim lighting
• Inverted colours: light modules on a dark background confuse some older or budget phone decoders
• Missing quiet zone: text, borders or graphics placed inside the empty margin of four modules around the code
• Oversized logo: a centre image covering more data than the error-correction level can repair
• Low print resolution: blurry or pixelated printing where small modules bleed together
• Too much data: a long URL creates a dense code with tiny modules that is hard to read at small sizes
• Wrong size for the distance: a small code on a poster that people view from several metres away

Contrast and Colour Problems

Decoders convert the image to black and white before reading it, so what matters is the difference in brightness, not the colours themselves. A dark navy code on a white background works well; a red code on a green background may look striking but can turn into nearly identical shades of grey.

A simple test is to convert your design to greyscale in any image editor. If the code is still clearly dark on light, it will scan. Aim for the foreground to be much darker than the background, and avoid gradients that fade the code into its surroundings.

Size, Data Density and Scanning Distance

Every extra character you encode adds modules. A short address produces a simple code that can be printed small, while a long tracking URL with many parameters creates a dense pattern whose modules may be smaller than a millimetre.

Keep encoded URLs short, remove unnecessary parameters and pick a print size that matches how far away people will stand. A common rule is that the code should be at least one tenth of the scanning distance: about 2 cm for a business card held in the hand, 10 cm for a poster read from one metre and 30 cm or more for a banner across a room.

Printing and Surface Issues

Glossy laminate reflects light and can create a bright glare spot exactly where the camera needs to see detail. Curved surfaces such as bottles distort the grid, and textured papers or fabrics can blur module edges.

Export codes as vector files (SVG or PDF) or high-resolution PNG at 300 DPI or more, and ask your printer not to resample or compress the image. On curved or reflective packaging, increase the size and test a physical proof before the full run.

Step-by-Step Diagnosis

When a code will not scan, work through these checks in order. Most problems are found within the first three steps.

• Scan the original digital file on screen. If it fails here, the problem is in the design or content, not the print
• Check the destination: does the encoded URL open correctly when typed into a browser?
• Look at the quiet zone and make sure nothing touches the code's edges
• Remove or shrink the logo and raise the error-correction level to Q or H
• Shorten the encoded data to reduce density
• Increase contrast and make the background plain
• Print a test at the final size and scan it with at least one iPhone and two different Android phones, in normal and dim light

Environment and Device Factors

Sometimes the code is fine and the conditions are not. Dirty camera lenses, cracked screens over displayed codes, low light, strong backlighting and holding the phone too close for the camera to focus all cause failures. Ask users to move back slightly, wipe the lens and avoid shadows falling on the code.

Codes displayed on screens should be shown at full brightness and without moiré from photographing a monitor. For codes on digital signage, leave them on screen long enough for people to raise their phones.