QR print versus screen 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 print versus screen, 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 print versus screen
Print and screen are different homes for a QR code, and a code designed for one does not automatically work in the other. Print is fixed, matte, and affected by ink and paper; screen is backlit, variable in brightness, and affected by glare and resolution. Each needs its own file and its own proof.
Make a separate file for print and a separate file for screen, with the right resolution and background for each. A screen file exported at low resolution will look soft in print, and a print file with a transparent background can fail on a colored screen. Keep the two files clearly named and never swap them.
How print versus screen affects scanning
Test the print version as a printed proof on the real stock, and test the screen version on real phones at real brightness settings. A screen proof on your own bright monitor tells you nothing about a dim phone in daylight, and a print preview on screen tells you nothing about ink spread.
For print, use a high-resolution file, a solid background, and a matte finish where possible. For screen, use a clean file with a solid background that survives brightness changes, and check it at low brightness as well as high. A code that only works at full brightness will fail for many users.
Setting up print versus screen before you print
Remember that print is permanent and screen is changeable. A printed code with a wrong link, a weak color, or a missing quiet zone needs a reprint; a screen code can be fixed in minutes. Spend the extra proof time on print, because the cost of a mistake is higher.
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 print versus screen 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 DPI calculator](/qr-dpi-calculator) 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.
