Processed locally
Your input stays in this browser.
Classify the failure before changing anything
A QR scan has two stages: the camera locates the square pattern, then a decoder interprets the recovered payload. A code with a cropped quiet zone may never be located; a well-read symbol can instead contain an expired address or malformed contact record. Treating both symptoms as one problem leads to random redesigns that erase the evidence.
Use a three-file diagnosis
Keep the original export, a plain black-on-white control with the same payload, and a photograph of the failing print. If the export and control decode but the photograph does not, reproduction is the suspect: inspect glare, ink spread, curvature, folds, and missing quiet space. If the export itself fails, the issue is already in the matrix, contrast, distortion, or encoded data; printing another copy cannot cure it.
Read geometry before error correction
A camera needs the full square, three finder patterns, a clean pale border, and modules that remain square enough to sample. Stretching a 300 by 300 image to 300 by 240 changes every module into a rectangle. Cropping four white modules from one edge removes part of the locator margin. Neither change is ordinary data damage, so recovery level H is not a remedy for either one.
Separate capture from symbol evidence
A glossy flyer can fail only under a ceiling lamp because the reflection covers a finder square in the camera image. A small label can fail while autofocus is still hunting. Try even light, a clean lens, a parallel camera angle, and enough distance for the whole code to enter the frame. A successful scan after moving the light identifies a capture condition; it does not prove the printed design is robust in its normal location.
Make one reversible change
Suppose a 25 mm code fails on paper. Do not simultaneously enlarge it to 40 mm, replace the colours, add a logo halo, and shorten the URL. First test a plain control at 25 mm; then change just the size, or just the surface, and keep each result. The comparison tells you whether module pitch, contrast, or artwork caused the change, and it leaves a reproducible correction for the next print run.
A decoded payload can still be the fault
When the reader returns text, inspect the exact result. `https://example.com/order` and `https://example.com/orders` are different destinations; a WiFi record with an old password can decode perfectly and still fail to connect. Test the payload in an appropriate application after confirming that the symbol reads. Static images cannot be edited in place, so a bad stored value requires a newly generated file and a replacement print.
The boundary is evidence, not a universal fix list
This sequence diagnoses common physical and payload failures, but it cannot certify an unfamiliar scanner app, a broken camera, or a destination controlled by someone else. Preserve the three diagnostic files and note the device, surface, light, and distance that produced the result. That record is more useful than repeatedly trying visual changes until one phone happens to scan.
Capture evidence before changing the file
Keep the failing print, the original QR export, the full-page PDF and a photo of the code in its installed location. Name the reader and phone used. Without those four items, a team often regenerates the code and cannot tell whether the change fixed the link, printer scaling, lighting or a damaged original. Decode the original export locally first. Its result divides the investigation into a data or rendering problem versus a physical reproduction or capture problem.
Look for an asymmetric failure
If the source PNG scans but one side of the printed card does not, inspect that side's trim, fold and coating. If one phone succeeds only in dim light, look for reflected glare rather than rewriting the payload. If every device reads the image but the target app refuses an event or Wi-Fi action, the symbol may be healthy while the receiving app lacks that payload behavior. State exactly which object failed and which reader was used; 'the QR code does not work' combines too many different faults.
Check the quiet zone as a physical object
The clear border is not decorative whitespace. A dark frame, photograph, crop mark, table edge or stain close to the matrix can prevent the camera from locating it. QR Code requires four modules of quiet zone on every side; at a 0.8 mm module pitch that is 3.2 mm of clear margin. Measure it after trimming, not only in the design file. A proof that removed 2 mm from one edge has changed the detection problem even if the dark square itself is undamaged.
Use a controlled repair sequence
Make a black-on-white export with no logo and the same payload. If it scans, add back one choice in this order: intended size, background colour, logo panel, surrounding artwork and final print process. Test after each step. If the plain export does not scan, reduce the payload or inspect the encoder input; do not begin with a new colour palette. This order prevents four simultaneous changes from producing an apparent fix that cannot be repeated for the next print run.
Worked diagnosis: a glossy counter card
A 45 mm card contains a 37 by 37 matrix plus an eight-module border, so its pitch is 45/45 = 1 mm. The source file scans. The matte proof scans on three phones; the laminated proof fails when a ceiling light reflects across it. That pattern points to reflection, not insufficient error correction or an invalid URL. Move the code away from the brightest reflection path, choose a matte area, or increase its panel. Changing a link in that case would destroy evidence while leaving the optical cause untouched.
When a decode succeeds but the task fails
A scanner may display https://example.org/check-in correctly while the browser reports a missing page, a captive portal blocks the network, or an app refuses a calendar record. Those are destination or receiving-environment failures, not scan failures. Compare the decoded bytes with the approved payload, open the address through a known network, and check whether the service has moved. A static code cannot be edited; the correction is a newly generated asset and a controlled replacement of the printed one.
Escalate format-specific jobs
For retail, warehouse or regulated production symbols, a phone-camera pass does not prove scanner interoperability or print grade. GS1's verification guidance treats square-module geometry and quiet-zone measurements as measurable quality factors. Send the actual sample through the destination scanner and record its returned value. For a public web link, a readable physical proof and correct destination may be enough; for an operational identifier, the receiving system is part of the test fixture.