What you are seeing
The printed code shows light modules on a dark background, the reverse of the design. Inverted codes look striking, but many scanners expect dark modules on a light background and fail on an inverted symbol, even when the contrast is strong. The inversion can come from a design choice, a print setting, or a material that reverses the image. The fix is to restore the standard polarity and to test any inverted design thoroughly before you commit to it.
Likely causes
1.
Design uses inverted colours — A design that deliberately puts light modules on a dark background inverts the code. Test: compare the proof with the standard dark-on-light version.
2.
Print setting inverts the image — A negative, invert, or reverse setting in the printer or layout can flip the polarity. Test: check the print and layout settings for an invert option.
3.
Material reverses the appearance — A dark stock with a light ink, or an engraving that removes the dark surface, can produce an inverted appearance. Test: compare the finished print with the design file.
4.
Background panel darkened in print — A background that prints darker than designed can swallow the distinction between modules and background. Test: compare the printed background with the design.
5.
Proof never scanned — An inverted code can look fine to the eye, so a visual proof check misses the polarity fault. Test: scan the proof.
Step-by-step fix
1. Compare the proof with the design file and confirm the polarity is inverted.
2. Scan the proof to confirm whether it fails.
3. Check the design, the layout, and the print settings for an invert option.
4. Restore dark modules on a light background in the file or the settings.
5. Print one corrected proof and scan it on two phones.
6. Approve an inverted design only if it passes a scan test on two phones.
Putting this into practice
In practice, dark on light is the safe polarity, and inverted codes are a gamble. Some scanners handle them and some do not, so an inverted code that passes on your phone can fail on a visitor's. Use the standard polarity unless you have a strong reason and a passing scan test on two phones. Keep a short note of what you tested, what failed, and what you changed, so the next person starts from evidence rather than guesswork. A fix that is written down survives staff changes and reprints; a fix that lives only in memory gets repeated.
Common mistakes to avoid
- Shipping an inverted code because it looked stylish, without ever scanning the proof.
- Reprinting the full run before a single proof passes, which turns one failure into many.
- Testing on one phone in ideal conditions instead of two phones in the real conditions where a code that prints inverted will be used.
- Changing the artwork and the placement at the same time, so you cannot tell which change fixed a code that prints inverted.- Skipping the proof test because the change looked small, when small changes cause most repeat failures.
Quick checklist
- The modules are dark on a light background
- No invert setting is active in the layout or printer
- The proof scans on two phones
- The corrected proof passes on two phones in the real conditions
- The fix is recorded in the job file so the next reprint starts from a proven setup
- Every printed copy is checked against the approved proof
- The proof is retested after any later change to the link, design, or placement
Related tools and guides
- [QR minimum size checker](/qr-minimum-size-checker)
- [QR contrast checker](/qr-contrast-checker)
- [QR print proof checklist](/qr-print-proof-checklist)
- [QR DPI calculator](/qr-dpi-calculator)
- [QR quiet zone calculator](/qr-quiet-zone-calculator)
- [printed QR tester](/printed-qr-tester)
- [QR size calculator](/qr-size-calculator)
