Back to Updates

QR Codes: Common Errors and Fixes

A
Admin
2026-11-15
Last updated 2026-11-15

Quick answer

A code that will not scan is almost always one of five things: too small for its density, too low in contrast, missing its quiet zone, damaged or covered, or inverted. A code that scans on one phone and not another is usually at the edge of legibility rather than broken. A code that opens the wrong page has the wrong payload, and no amount of reprinting the same symbol will fix it.

What this article covers

The symptoms in the order they appear, the cause behind each, and the fix — plus the cases where the correct answer is to regenerate rather than reprint. For a first run, read the beginner's guide.

What it actually does

The symbol is a grid of modules with error correction and a required margin. Every failure maps onto one of those three properties.

  • Density comes from the payload length and the error correction level. More characters or a higher level means more modules, and more modules need more printed width.
  • Contrast comes from the colours. Scanners need the modules to be darker than the background by a clear margin.
  • Margin is the quiet zone. Below four modules the encoder refuses, but artwork can still cover it afterwards.

The payload itself is fixed at generation time, which is why a wrong URL is a regeneration problem rather than a printing problem.

Step by step

  1. Scan the original SVG from the screen first. If that fails, the symbol or the payload is wrong.
  2. Scan the printed proof. If the screen works and the proof does not, the problem is size, contrast or material.
  3. Read the decoded text in the scanner app to check the payload.
  4. Change one property and re-proof.
  5. If the payload is wrong, regenerate rather than reprint the same file.

What to check after download

  • Decoded text, not just that a scanner reacted.
  • Module count, by eye: a dense symbol needs more width.
  • Contrast, from a distance.
  • Quiet zone, in the final artwork.
  • Placement, on the real object.
  • Lighting, in the place the code will be used.
  • A second phone, to confirm the symbol is not marginal.

Fixes by symptom

It will not scan at all. Scan the SVG on screen. If that fails, the payload contains characters the scanner app does not expect, or the symbol was damaged in layout. Fix: regenerate and re-place.

It scans on one phone but not another. The symbol is marginal: low contrast, small modules or a tight quiet zone. Fix: increase the printed size, restore the margin, or raise the contrast.

It will not scan in print but scans on screen. Paper is dimmer and the print may be smaller than it looked. Fix: print larger, use a matte material, and keep the code away from a fold.

It opens the wrong page. The payload is wrong. Fix: regenerate with the correct URL. Reprinting the same symbol changes nothing.

It stopped working after a while. The page behind the URL moved or expired. Fix: repoint the URL on your own domain if you control it; otherwise regenerate the code with the new address.

It will not scan with a logo over the middle. Error correction was too low for that much damage, or the logo covers the finder patterns in the corners. Fix: raise the level to H and keep the corners clear.

It scans as a blank or garbled string. The caption or surrounding artwork was read as part of the code, or the modules were inverted. Fix: restore the quiet zone, and use dark modules on a light background.

It looks blurry in print. A raster was used instead of the SVG, or the SVG was scaled badly in the layout. Fix: use the SVG at the final size.

It scans only when the phone is very close. The modules are small for the camera's field of view. Fix: print larger, or shorten the payload so the symbol needs fewer modules for the same width. A denser code is not a better code when the medium is small, and a larger code is not always possible on a label.

Common beginner mistakes

Debugging the print when the payload is wrong. Read the decoded text first; it tells you which problem you have.

Increasing error correction to fix a scan failure. A denser symbol at the same printed size can scan worse, not better.

Testing a code on a monitor and calling it verified. A monitor is the brightest, flattest surface the code will ever sit on.

Reprinting the same file after changing the URL in a spreadsheet. The file still contains the old payload; the code has to be generated again from the new address.

Assuming a screen scan proves the print. It proves the payload, not the print.

Cropping the quiet zone to make the layout tidy. The margin is part of the code.

When this tool is the right choice

When the failure is a legitimately static code that needs a better size, contrast or material. If the requirement is a changeable destination or scan analytics, no setting here will provide it and the right move is a different architecture.

Related tools

Resize an Image fixes artwork sizes around the code. Merge PDF Files assembles a corrected sheet with its instructions, and PDF Converter renders a PDF proof to check at pixel level.

Use this tool

Regenerate with a shorter payload and a clearer margin on QR Code Generator, then proof again at the real size.

Next step

If the code is going to print at scale, read best settings by medium and make the proof step part of the print procedure.

Tags