QR gradients 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 gradients, 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 gradients
A gradient blends one color into another across a QR code, giving the symbol a sense of depth and brand color. Gradients can look striking, but they also change the darkness of modules from one side of the code to the other, which is exactly what a scanner does not want.
Keep the gradient within a narrow brightness range, with both ends clearly dark against a light background. A gradient that drifts from dark to light will leave one side of the code too pale to read. The safest gradients move between two dark shades of similar brightness.
How gradients affects scanning
Run the gradient in one direction only, and keep it smooth. A diagonal or top-to-bottom blend is easier for the eye to follow than a radial burst that makes the centre pale and the edges dark, or the reverse. Avoid gradients that pass through a mid-tone or a pale band in the middle of the symbol.
Keep the finder patterns in a single solid dark color rather than letting the gradient run through them. The corner squares need to read as consistent landmarks, and a gradient that lightens one corner makes detection harder. Apply the gradient to the data modules and keep the finders solid.
Setting up gradients before you print
Test the gradient at the real size, in the real light, on the real material. A gradient that looks even on screen can band or wash out in print, especially on textured stock. A printed proof is the only honest test.
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 gradients 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 gradient maker](/qr-gradient-maker) to check your choices before you commit to a design.
- Use the [QR contrast checker](/qr-contrast-checker) 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.
