Why Your QR Code Won’t Scan
A code that scans perfectly on a monitor can fail on paper. The pattern was readable on a bright screen at close range, but the printed copy is smaller, flatter and further from the camera. A failed scan is usually a physical problem before it is a software one.
The URL QR Generator can produce a fresh code, but replacing it is rarely the first fix. Work through the conditions around the code before you assume the image is wrong.
Quick answer
Check the size at the distance people will actually scan from, then the contrast, the clear margin around the pattern, and the surface. A dense code with a long URL needs more room than a short one. If the print is clean and still fails, try another scanner app or another phone before regenerating.
Start with size and distance
A code has to occupy enough of the camera frame to be resolved. As a rough guide, the scanning distance should be no more than about ten times the width of the code. A code read from two metres therefore needs to be around twenty centimetres wide, not two.
Test the printed proof at the final size, not by holding a phone close to a large monitor. A code that fills a business card may be comfortable at twenty centimetres and hopeless across a room. If the code is on a menu or a poster, place the proof where the real sign will hang and scan it from where a customer will stand.
Contrast, margin and finish
Dark modules on a light background are the reliable arrangement. Inverted codes, light modules on a dark field, fail on many cameras even when they look striking. Avoid printing a code over a photograph or a gradient: the scanner needs a clean difference between the two tones, not a pretty one.
Leave a clear quiet zone around the pattern, roughly four modules wide. A code cropped tight to its edge, or placed beside text and borders, can be hard for the camera to isolate. Glossy laminate and curved surfaces add reflections; matte paper and a flat position are easier. If the code is on a bottle or a folded leaflet, test it on the real object.
Density, damage and substitutions
A long URL produces a denser pattern than a short one. More modules in the same space means finer detail, so a dense code needs a larger print or a shorter address. Error correction helps with minor damage, but it cannot rescue a code that is scratched through the corner markers or partly covered by a sticker.
Check for the obvious physical problems too: a crease through the middle, a label peeling at one edge, direct sunlight washing out the print, or a code stuck over an older one. A code that has been replaced on a sign is worth treating with suspicion, not just patience.
When the code is probably fine
Camera focus, a dirty lens, low screen brightness and an app that only recognises web links can all look like a broken code. Try a second phone and a second scanner. If the code decodes there, the problem is the first device or app, not the print.
Generate the replacement with the URL QR Generator, keeping the address as short as practical. For the full production checklist, read How to Make a QR Code for a Link That Lasts. If you are choosing between a fixed and an editable code, see Static vs Dynamic QR Codes: Which Do You Need?.
Common questions
Why does my QR code scan on screen but fail on paper?
The printed code is probably smaller, less contrasty or more reflective than the screen version. Print a proof at the final size, keep a clear margin around the pattern, and scan it from the distance a real user will stand. A dense code may also need a larger print.
Can error correction rescue a QR code that will not scan?
Only if the damage is within the chosen level and the three corner markers are still readable. Error correction repairs a limited number of codewords, not a missing corner or a pattern covered by a sticker. If the code is badly damaged, generate a new one.
Should I invert a QR code to print light modules on a dark background?
Avoid it unless you can test on the exact phones your audience uses. Many cameras and scanner apps expect dark modules on a light background and fail on an inverted code, even when the pattern is otherwise correct. A conventional dark-on-light print is the safer choice.