Skip to main content
QR Code Design

QR Code Design: Colors, Logos and Contrast That Scan

6 min read Last updated 2026-11-17

A QR code is forgiving by design, but not infinitely so. Every aesthetic decision - color, inversion, logo, background texture - either consumes part of the code's error correction budget or interferes with how the scanner separates dark modules from light ones.

This guide explains the rules that keep stylized codes reliable, which decorations are safe, and where the real limits lie, so you can produce codes that look like part of your brand without becoming unscannable in the field.

Contrast and color: what actually matters

Scanners do not see hue; they see brightness. A colored code scans perfectly well as long as the dark modules stay significantly darker than the light modules - a common working rule is to keep at least 40% contrast between the two. Navy on cream, deep green on white and burgundy on beige all work; pale gray on white does not.

The risky exception is inversion. Light modules on a dark background still decode in principle, but a meaningful share of scanner pipelines - and many printed-context photos - handle inverted codes poorly, so it is unwise for public materials. Keep the light modules genuinely light (white or near-white) and the dark modules genuinely dark, and you remove the most common design failure before it happens.

  • Dark modules on light backgrounds: navy, black, dark green and dark red all work
  • Keep luminance contrast high - hue is free, brightness is not
  • Avoid inverted codes (light modules on dark) for print and public signage
  • Keep the quiet zone light: a dark frame or busy photo background can swallow the margin
  • Avoid gradients that blur the boundary between dark and light modules

Adding a logo without breaking the code

A logo can sit in the middle of a QR code because Reed-Solomon error correction spreads redundancy across the whole grid rather than concentrating it in one place. To spend that budget deliberately, generate the code at error correction level H, which tolerates roughly 30% codeword loss, and keep the logo modest - well under a quarter of the code's area. Never place a logo over the three finder patterns; scanners lock onto those corners first, and covering them disables the code entirely.

Leave clear module space around the logo so it does not straddle the timing pattern or alignment marks, and flatten the logo's background where it overlaps the data region. The non-negotiable final step is testing: scan the finished design on several different phones, at realistic angles and distances, before anything goes to print. A design that scans on one flagship phone but not on an older Android in dim lighting will generate complaints you cannot fix after the print run.

Sizing and the quiet zone in practice

The quiet zone is the blank margin around the code, and the specification recommends a width of about four modules. For a sticker scanned at close range that usually means five to ten millimeters of clear space; larger codes need proportionally more. What matters is not the exact number but the principle: nothing dark, textured or busy may touch the code, because the scanner needs a clean boundary to segment the grid from its surroundings.

Physical size should follow scanning distance. A dependable rule of thumb is that the code's width should be roughly one tenth of the distance it will be scanned from: a code two centimeters wide scans comfortably from about twenty centimeters, a four-centimeter table code from half a meter, and a thirty-centimeter poster code from three meters. Below roughly two centimeters, module sizes get so small that ordinary printing tolerances start to matter.

Shapes, frames and calls to action

Rounded modules, dots and custom frames are safe when they preserve the module grid and the contrast rule. Softening a square into a circle changes how the code looks far more than how it scans, because segmentation works on the pattern of dark and light cells, not on razor-sharp edges. Error correction quietly absorbs the rest.

The most effective design addition is usually textual: a frame around the code that carries a call to action such as 'Scan the menu' or 'Scan for setup'. A bare code makes people guess what it does, and many will not bother. Just keep two constraints: the frame must not touch or replace the quiet zone, and it must not visually connect the three finder patterns in a way that confuses segmentation on weaker scanners.

Testing and exporting for print

Test like your users, not like your design tool. Scan on both major phone platforms, at the real scanning distance, under the real lighting - including dim restaurant light and bright window glare. Then print a proof at final size on the final stock before committing a full run, because paper texture and ink behavior change what the camera sees.

For print, export vector formats such as SVG or PDF so modules stay crisp at any size. If you must use a raster file, keep it at least 300 DPI at the final printed dimensions; a small PNG stretched up produces fuzzy module edges that defeat even good error correction. For laminated or packaged surfaces, choose matte finishes over gloss, since specular highlights over the modules are a leading cause of scan failure.

Key takeaways

  • Contrast is about brightness, not hue: dark modules on light backgrounds with a large luminance difference
  • Logos need error correction level H, a modest size and clearance from the finder patterns
  • Keep roughly four modules of blank quiet zone around the code, light in color
  • Size for scanning distance: a workable rule is code width about one tenth of the distance
  • Export vector files or 300 DPI raster, proof on real stock, and prefer matte over glossy finishes

Put it into practice

Frequently asked questions