QR shadows decides whether a QR code feels like part of your design or like an afterthought stuck onto it, and it also decides whether the code scans. This guide sets out the working rules for shadows, explains why each rule matters, and shows how to apply it on real materials. The rules are practical rather than theoretical: each one can be checked on a proof with your eyes and a phone, before you spend money on a print run. If you follow them, your code will look intentional and still read quickly in the place where it will actually be used.
The core rules for shadows
A shadow is the soft dark edge that a design tool adds behind a QR code to lift it off the page. Shadows can make a code look like a card floating over a background, but they also darken the quiet zone and the background the scanner relies on. Most codes scan better with no shadow at all.
Avoid shadows that fall inside the quiet zone or across the code background. A shadow that darkens part of the margin or the light modules breaks the even background the scanner needs. If you want depth, put the shadow outside the code panel, not under the code itself.
How shadows affects scanning
If a shadow is essential to the design, keep it light, short, and even, and keep the code on a solid panel that the shadow does not touch. A soft, distant shadow behind a white panel can suggest depth without darkening the code. A hard, close shadow behind the code itself will not.
Check shadows in print, not only on screen. A shadow that looks subtle on a backlit screen can print darker and wider than expected, especially on absorbent stock. A printed proof shows the true shadow before the run.
Setting up shadows before you print
Remember that shadows move with the light. A code that relies on a printed shadow can look different under shop lighting, daylight, and phone flash. A design that needs perfect lighting to scan is a design that will fail in real use.
Start with the plainest version that meets the brief, then add branding step by step, testing after each addition. If a step makes scanning slower, that step is the one to simplify. This gradual approach keeps the design honest: you can see exactly which choice helped and which choice hurt. Keep a copy of the last version that scanned instantly, so you can always fall back to a known-good design if a later variation fails.
Putting this into practice
Pick one live design that uses shadows and run it through this guide today. Print a proof at the final size, check the rules against it, and fix the first problem you find. Then scan the corrected proof with two phones in the real light. Keep the passing proof as a reference, and use it as the starting point for the next design so you are not solving the same problems twice.
Common mistakes to avoid
Even when the main rules are followed, small slips still creep in. The most common ones are letting decoration drift into the quiet zone, choosing colors that look distinct but share a brightness, and approving a design from a screen preview instead of a printed proof. Another frequent slip is changing one part of a working design, such as the link or the paper, without retesting the whole thing. Treat every change as a reason to run a fresh proof, and treat any hesitation in a test scan as a signal to simplify rather than to hope the next phone will cope better.
Quick checklist
- Keep dark modules on a light, even background with strong contrast.
- Leave a clear quiet zone on all four sides of the symbol.
- Keep the finder patterns solid, undisturbed, and easy to find.
- Check the code at the real size, on the real material, in the real light.
- Confirm the call to action names the payoff and the typed alternative works.
- Recheck the code after any change to the link, design, size, or placement.
Related tools and guides
- Try the [QR contrast checker](/qr-contrast-checker) to check your choices before you commit to a design.
- Use the [QR print proof checklist](/qr-print-proof-checklist) to confirm the numbers and guardrails for this element.
- Check the [QR size calculator](/qr-size-calculator) for a practical way to verify the finished code.
- Check the [QR scanner](/qr-scanner) for a practical way to verify the finished code.
- Check the [QR safety checker](/qr-safety-checker) for a practical way to verify the finished code.
- Check the [printed QR tester](/printed-qr-tester) for a practical way to verify the finished code.
- Browse the [blog](/blog) for more guides on sizing, printing, and design for QR codes.
