QR Code Design Best Practices
A QR code that looks great and doesn't scan is worse than no QR code at all. Most scan failures trace back to a small number of physical, print-related issues — not the platform that generated it. Here's what actually matters, in rough order of how often it's the real culprit.
Contrast matters more than color choice
A phone camera reads a QR code by distinguishing dark modules from light ones — what actually matters is contrast between the two, not which specific colors you pick. Dark foreground on a light background (or vice versa) reads reliably; two mid-tone colors close to each other in brightness, even if they look distinct to a human eye, can fail to scan at all. If you're using a custom color scheme — this platform supports solid colors, gradients, and a transparent background — check the contrast, not just whether the colors match your brand.
Leave the quiet zone alone
The blank margin around a QR code (the "quiet zone") isn't wasted space — it's how a camera's scanning algorithm finds the edges of the code in the first place. Cropping it tightly to fit a design, or placing other graphics right up against the edge, is one of the most common causes of a code that scans fine on a phone held close but fails from any distance or angle.
Size for the actual scanning distance
A code meant to be scanned from a few inches away (a table-tent menu, a business card) can be small. A code on a billboard, a storefront window, or a poster meant to be scanned from several feet away needs to be proportionally larger — as a rough rule of thumb, the code should be roughly a tenth of the expected scanning distance (a code meant to be read from 10 feet away should be at least about a foot across). Print a physical test copy at the intended size and distance before committing to a full run.
Adding a logo without breaking the scan
QR codes have redundancy built into the standard itself, which is why a logo placed in the center of a code can still scan correctly — the format is designed to tolerate a certain amount of the pattern being obscured or damaged. That tolerance has limits, though: a logo that's too large relative to the code, or that overlaps the corner marker squares (the three larger squares in three corners, which the scanner uses to orient itself), can push a code past what it can recover from. Keep a logo modest in size and clear of the corner markers, and test the result the same way you'd test any other design change — a real scan on a real phone, not just a visual check that it looks fine.
Corner markers and pattern style
Custom corner-marker shapes and dot-pattern styles are available here, and can make a code look more distinctly "yours" than the default square-grid look. The same rule applies as with color: a stylistic change is fine as long as it doesn't reduce contrast or make the corner markers themselves ambiguous to a scanner — stick with the defaults if scan reliability matters more to you than visual branding for a given use case, and test a physical print either way before a full run.
The pre-print checklist
- High contrast between foreground and background — check it, don't assume it.
- Quiet zone (margin) left intact, nothing crowding the edges.
- Sized appropriately for the actual scanning distance.
- If a logo is added, it's modest in size and clear of the corner markers.
- A physical test print, scanned on at least one real phone, at the intended size — not just a screen preview.