A plain black-and-white code works, but it looks like an afterthought. A well-branded code signals that the experience behind it was designed with care. The challenge is that every design choice nibbles at scannability — so the goal is maximum brand expression within the limits the technology imposes.
Contrast is non-negotiable
Scanners read luminance, not hue. Before any color decision, make sure your dark modules are genuinely dark and your background genuinely light. A deep brand navy on white scans beautifully; a mid-tone teal on a pale grey does not. If you only remember one rule, remember that brand color lives in the dark modules, and they must stay dark.
A quick test: convert your color pair to greyscale in your head. If the two would be hard to tell apart in black and white, a scanner will struggle too.
Where to apply color safely
The safest place for brand color is the data modules and the finder patterns (the three corner squares), kept dark against a light background. You can also color the background lightly — a faint tint rarely hurts. Gradients can work if they stay within the dark range and never approach the background's brightness.
Avoid coloring individual modules differently or using multiple competing colors inside the grid; it looks busy and confuses scanners. Restraint reads as premium.
Adding a logo correctly
A center logo is the highest-impact branding move. Keep it under roughly 20% of the code's area, give it a small clear margin, and crucially raise error correction to Q or H so the covered modules can be reconstructed. Done right, the logo looks intentional and the code still scans instantly.
Module and eye shapes
Rounded modules, dot patterns and custom corner “eyes” are popular and can look excellent. They also reduce the crispness scanners rely on, so treat them as a budget: pick one or two stylistic moves, bank extra error correction, and test hard. Subtle rounding is low-risk; heavy artistic dot patterns need real testing across devices.
Make it part of a system
If you produce many codes, define a small house style — the same dark color, the same logo treatment, the same frame and call to action — so every code looks like part of one brand. Consistency across business cards, posters and packaging is what makes branded codes feel professional rather than novel.
Document the recipe (colors, error-correction level, logo size) so anyone on the team can produce an on-brand, scannable code without guessing.
Test the branded version, not the plain one
A common trap is designing and approving a plain black code, then adding the logo and color at the last minute without re-testing. Every branding choice changes the code, so always test the final, fully-branded version on real phones — the version that will actually be printed.
If a heavily branded code proves marginal, the fix is usually to dial back one element: shrink the logo a little, increase contrast, or raise error correction. Small adjustments recover reliability without losing the look.
A branding checklist that stays scannable
To brand confidently without gambling on scannability, work through a short checklist each time. Confirm the dark modules are genuinely dark against a clearly lighter background — mentally convert to greyscale and check the gap survives. Keep brand color in the modules and finder patterns rather than splashed across the whole grid. If there is a logo, hold it under a fifth of the area and lift error correction to Q or H.
Then count your stylistic flourishes. Rounded modules, custom eyes, gradients and a center logo each spend a little of your scannability budget, so pick the one or two that matter most for the brand and resist piling on the rest. Restraint nearly always reads as more premium than maximalism anyway, and it keeps the code reliable.
Crucially, test the final branded version — the exact file that will print — on several real phones, not the plain black draft you approved earlier. If it proves marginal, recover reliability by dialing back one element rather than abandoning the look entirely. A documented house recipe of color, logo size and error-correction level lets anyone on the team produce an on-brand, dependable code without rediscovering these limits each time.
- Contrast beats color: dark modules, light background, always.
- Put brand color in the dark modules and finder patterns.
- Logo under 20% + error correction Q/H.
- Treat shapes and gradients as a scannability budget — spend sparingly.
- Define a house style so every code looks like one brand.
Ready to put this into practice?
Create a free, branded QR code in seconds — no sign-up, no watermark.
Open the generator Try Animated QR