Why modules, not pixels
A module is one cell of the QR matrix. Version sets how many modules sit on each side of the data grid. Quiet zone must be expressed in those same units. A fixed pixel margin is misleading in two common ways: as export size grows, the same pixel pad covers fewer modules; and as payload density (version) changes, a margin that “looked fine” on another code no longer means the same thing.
- Version 1 → 21×21 data modules; Version 10 → 61×61
- Fixed 24px at 256px export can look “generous”; the same 24px at 1024px may be under one module
- Longer payloads and higher ECC can increase version—re-check quiet zone whenever density jumps if you are outside QRburst’s module-based presets
matrix size (modules per side) = 21 + 4 × (version − 1)
quiet zone (per side) ≈ margin pixels ÷ module pixel size
module pixel size ≈ (size − 2 × margin) ÷ matrix modules
| Export size | Module px (approx.) | Quiet zone in modules | Takeaway |
|---|---|---|---|
| 256 px | ~5.6 px | ~4.3 modules | Looks fine by accident |
| 512 px | ~12.5 px | ~1.9 modules | Same 24px, fewer modules |
| 1024 px | ~26.4 px | ~0.9 modules | Pixel habit collapses the collar |
Conventional guidance
Industry practice commonly targets about four modules of quiet zone per side as a safer conventional presentation. That is planning guidance for reliability—not a promise that every decoder rejects anything thinner.
QRburst Lab heuristics treat roughly ≥3 modules as a healthier band, with thinner margins classified toward borderline or below-recommendation. Those thresholds are product heuristics to steer creators; they are not a substitute for device and print testing.
- ~4 modules per side: conventional safer target (QRburst Generous)
- 2 modules: workable in some clean digital layouts; verify harder for print
- 1 module: minimal; expect more failures near busy backgrounds or after trim
- 0 / invaded: common root cause in “won’t scan” reports
QRburst presets
Design Studio exposes three semantic presets. Pixel margin is computed so the chosen module target stays stable across export sizes—the opposite of the old fixed-pixel failure mode.
marginPx ≈ round(size × quietModules / (moduleCount + 2 × quietModules))
| Preset | Modules per side | Typical use |
|---|---|---|
| Compact | 1 | Space-constrained digital UI; Minimal preset; not preferred for small print without testing |
| Standard | 2 | Middle ground when Generous will not fit |
| Generous | 4 | Default for most QRburst presets; conventional safer target |
Print and layout pitfalls
Print workflows destroy quiet zones in mundane ways: aggressive cropping, tight die-cuts, table-tent folds, sticker kiss-cuts, and “helpful” background patterns under the code. Measure the empty collar on the physical proof, not only in the generator preview.
When space is scarce, it is usually better to shrink surrounding decoration—or enlarge the whole QR—than to steal modules from the quiet zone. Pair Generous margins with adequate physical size; a four-module collar on a microscopic sticker still yields tiny modules.
- Keep CTA text and icons outside the quiet zone (nearby is fine; overlapping is not)
- Give transparent or dark layouts a light pad behind the entire symbol including margin
- After vendor imposition, confirm no security trim ate the collar
- If Compact is required, run Lab checks, stress tests, and a strict physical proof before a large run