Design priorities
Scanners need separable modules and recognizable finders. Everything else is optional branding on top of that requirement.
| Priority | Goal | QRburst lever |
|---|---|---|
| 1 | Dark modules on a light field | Fill + background colors; Lab contrast heuristic |
| 2 | Intact quiet zone in modules | Compact / Standard / Generous presets |
| 3 | Clear finder patterns | Finder styles/colors; avoid covering corners |
| 4 | Recovery headroom | ECC (default H) |
| 5 | Brand marks | Logo size 10–35% UI range—test upward sizes carefully |
| 6 | Ornament | Module styles and gradients |
Styles and gradients
Rounded, dotted, or classy module styles can match a brand system, but they reduce the crisp square edges many decoders like. Prefer subtler styles when print size is small or payloads are dense.
Gradients should keep the lightest module regions clearly darker than the background. If Lab contrast warnings appear, darken the gradient stops before you ship.
- Square modules remain a reliable baseline
- Extreme styling + large logo + tiny print is a common failure combo
- Presets in QRburst are starting looks—still verify for your payload and size
Frames and CTA text
People scan more when they know why the code exists. Place a clear call-to-action in the surrounding layout—“Scan for the menu,” “Scan to connect Wi-Fi”—without invading the quiet zone.
Product clarity for 2026: QRburst does not claim a composed frame/CTA export where decorative frames are merged into the downloaded QR artwork. Keep CTA copy as nearby design elements outside the symbol. Purpose toolkits may suggest wording for print placement; those strings are not encoded into the modules.
Test after customization
Every logo swap, gradient experiment, or ECC change deserves a fresh pass through configuration analysis and simulated decode stress tests. Browser evidence reduces risk; physical proof closes it for print.
Do not ship because a single phone scanned once in ideal light. Aim for layered evidence: Lab heuristics, P4 stress categories, multi-device checks, and a final material scan when the code will be printed.
- Re-test after export size changes
- Re-test after print vendor color conversion
- Keep a known-good Classic-style backup if a campaign is time-critical