QR brand palette 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 brand palette, 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 brand palette
A brand palette is the set of colors a business uses across its packaging, posters, and screens. Applying that palette to a QR code can make the code feel like part of the brand, but only when the palette offers a dark color for the code and a light color for its background. Not every brand palette does, and the code must come first.
Pick the darkest brand color for the code and the lightest brand color for the background, and check the pair as a pair. Two brand colors that look good side by side in a logo can still fail as a code pair if their brightness is too close. The code pair must pass a contrast check, not just a brand check.
How brand palette affects scanning
Reserve the rest of the palette for the frame, the call to action, and the surrounding design. The code itself needs one dark and one light; the surrounding design can carry the accent colors, the secondary shades, and the brand personality. This keeps the code readable and the design branded.
Write the approved code pair down as a rule, with the exact color values, so every designer and printer uses the same pair. A rule that says use the dark brand color is not enough, because the palette may hold three dark colors. Name the pair, name the background, and name the fallback for dark surfaces.
Setting up brand palette before you print
Test the brand pair on the real materials it will be printed on. A pair that works on white card can fail on kraft, on a colored pack, or under a laminate. The palette rule must name the background panel that travels with the code, not just the two colors.
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 brand palette 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 color pair tester](/qr-color-pair-tester) 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.
