QR Code Quiet Zone: The Empty Margin That Decides Whether a Code Is Found

What is a quiet zone on a QR code?

The quiet zone is the empty margin around a QR code that lets a scanner detect where the symbol begins and ends, and the standard specifies four modules on every side. It belongs to the code rather than to the page: a QR code is the dark modules plus the clear border around them, and any measurement or placement that covers only the dark part is describing something smaller than the code.

The mechanism is worth knowing, because it explains which fixes work. A decoder first reduces the camera image to black and white, then hunts for the three finder patterns by the 1:1:3:1:1 ratio of dark and light runs that crosses each of them, and from those three points works out the symbol's boundary, its rotation and the grid its modules sit on. A finder pattern is one of the three concentric squares in a QR code's corners that a scanner uses to locate the symbol and work out its rotation.

Every step of that runs before decoding starts. When artwork touches the outermost modules, a dark module on the edge of the symbol merges with whatever is next to it, the run measurement at that edge changes, and the boundary the decoder estimates moves with it. The data inside is untouched and irrelevant - nothing has decided yet that there is a symbol there to decode.

This is also why the failure is so confusing in practice. A QR code with no quiet zone is not a degraded code that reads badly. It is usually a code the scanner never reports at all, which reads to the person holding the phone as though nothing is there.

How big does the quiet zone have to be?

Four modules on all four sides, for every QR code, at every symbol version. ISO/IEC 18004 states the requirement in modules rather than in millimetres, so the physical width of the margin changes with the printed size of the code and with how much data it carries, while the count never does.

Two modules is a Micro QR allowance, not a shortcut for a normal code. Micro QR is a different symbol with a different structure, a single finder pattern and a much smaller capacity, and its relaxed margin does not transfer to the model 2 code that a phone camera reads off a menu.

Many decoders manage on two modules in good conditions, which is exactly why a short margin so rarely shows up during design and so often shows up after the print run. The four-module figure is not the point at which codes start working; it is the point at which they stop depending on the conditions being good.

What four modules works out to in millimetres

Quiet zone in millimetres = 4 x the module size, and the module size is the printed width divided by the number of modules across the whole footprint. Since the footprint is the symbol plus four modules on each side, the arithmetic is: quiet zone = 4 x printed width / (modules per side + 8).

The module count per side comes from the symbol version: a version V code is 4V + 17 modules across. Version 1 is 21, version 4 is 33, version 10 is 57. A version 4 symbol therefore occupies 41 modules including its quiet zone, and at a 20 mm printed width each of those is 0.49 mm, so the margin is about 2 mm per side.

Read down a column and the useful shape appears: at a fixed printed size, the denser the code, the narrower its quiet zone. A long URL raises the symbol version, which shrinks every module, which shrinks the margin - so the code that most needs help detecting its edge is the one that gets the least of it.

There is a practical floor underneath all of this. Printed modules should be 0.4 mm or larger on coated stock and 0.5 mm or larger on uncoated, which puts the smallest quiet zone on a properly sized printed code at 1.6 mm and 2 mm respectively. If a layout leaves less clear space than that around a code, the code is either too small or too tight, and both are worth checking before the file goes out. The minimum size for print guide takes the sizing half of that question end to end.

Why a percentage margin in a template gets it wrong

A quiet zone specified as a percentage of the code drifts as soon as the payload changes, because four modules is a different share of every symbol version. On a version 4 code the four-module margin is about 12% of the symbol's width; on a version 10 code it is 7%. A template that reserves 10% around the code is generous for one and short for the other.

The same effect is larger in area terms than most people expect. A version 4 code with its quiet zone covers 41 × 41 module cells, of which the symbol itself is 33 × 33 - so the margin is about 35% of the printed footprint. On a version 10 code it is 23%. That is the answer to why a code always looks bigger in a layout than the designer planned for.

Specify the clear space in modules or in millimetres, not in percent. If a brand guideline has to carry one number, make it millimetres at a stated printed size, and restate it whenever the size changes.

Does the quiet zone have to be white?

It has to match the light modules of the code, which on an ordinary black-on-white QR code means white, and on a coloured code means the code's own light colour. The standard describes the requirement in terms of reflectance rather than colour: the margin has to read as light to a scanner in the same way the light modules do, and the boundary between the two must be invisible to the decoder.

What that rules out in practice:

• A margin in a different colour from the code's background. A white code background on a cream card leaves a visible rectangle, and its edge is a contour the decoder has to discard before it finds the real one.
• A photograph or a pattern behind the code. Detail in the margin produces dark runs at the symbol's edge that look like modules. This is the single most common cause of a code that scans in the mock-up and not on the printed poster.
• A gradient running under the code. A gradient that is light at the top of the margin and mid-tone at the bottom gives the binarisation step two different thresholds to reconcile across one symbol.
• A transparent PNG dropped on a dark surface. Transparency is not white. A transparent export placed on a dark background has a dark quiet zone, which is no quiet zone at all - see SVG vs PNG for what each export format carries.
• An inverted code with a light margin. Light modules on a dark background need a dark quiet zone to match them, and several native cameras do not reliably read inverted codes in the first place.

A tinted quiet zone is allowed, and it is often the better design answer. A code with a pale background colour and a margin in that same pale colour, running to the edge of the panel, keeps the brand and keeps the margin. What breaks is any boundary inside the four modules, whatever colour it is.

Why error correction cannot replace the quiet zone

Error correction repairs damaged modules inside the data area after the symbol has been located, so it has no bearing on a symbol that is never located. Raising a code from level M to level H adds recovery capacity that a detection failure never gets to spend, and it makes the situation slightly worse: the higher level pushes the code up a symbol version, the modules get smaller, and the four-module margin gets narrower with them.

The order the two things happen in is the whole explanation. Detection comes first and uses the quiet zone; decoding comes second and uses error correction. There is no path by which the second compensates for the first.

This is the same reason the finder patterns, the timing patterns and the quiet zone are all outside the reach of Reed-Solomon recovery: they are the scaffolding the decoder needs before it has anything to recover. Error correction levels L, M, Q and H covers what recovery does protect, and how much of it a logo consumes.

Where layouts quietly eat the quiet zone

Almost every missing quiet zone is a placement decision rather than an export setting. The code left the generator with its margin intact and then met a layout that needed the space, and because the symbol itself is untouched the file still looks correct at every stage of approval.

The recurring cases, in rough order of how often they reach print:

• The code placed hard against a rule, a box or a panel edge. A keyline drawn to tidy up a corner sits inside the margin and gives the decoder a contour of its own.
• A 'Scan me' label tucked under the code. Type set close enough to read as one unit with the symbol is type inside the quiet zone. Move it four modules clear and it still reads as a caption.
• A code cropped to its symbol in the export, then placed. Some tools trim the margin on export. Once trimmed, the layout has to supply it, and nobody told the layout that.
• The trim edge of a printed piece. A code near a cut line loses margin to cutting tolerance, and a stack cut a millimetre out takes it from the same side on every copy.
• A fold or a spine crossing the margin. The crease shadows the code and the two halves stop being coplanar. Keep the whole footprint clear of the fold by at least 5 mm.
• A background image bleeding under the code. Common on menus and event posters, where the code is placed last onto a photographic panel.
• A sticker or label die-cut close to the symbol. The cut edge, the substrate underneath and the shadow at the edge all land in the margin.
• A code on the edge of a screen or a slide. The bezel or the dark slide background becomes the margin, which on a projected slide is usually fatal.

The check that catches all of them takes one sentence: measure the clear space in the placed layout, not in the exported file. A file's margin only survives if the page around it leaves the margin alone.

Frames, circles and custom shapes around a QR code

A frame around a QR code is fine as long as it starts outside the quiet zone, which means the frame's inner edge sits at least four modules clear of the symbol on every side. The mistake is not the frame; it is a frame drawn to the symbol and the margin then measured from the frame.

Shape-specific points worth checking:

• A circular frame around a square symbol. The corners are the tight spots. Measure the clear space diagonally from the corner modules, not horizontally from the sides, or the four corners will each be short.
• A frame with a tab or a banner. A 'Scan for the menu' strip attached to the frame is outside the margin only if the frame itself was outside it.
• Decorative module shapes. Rounded and circular modules put less ink in each cell than square ones, so the symbol's outer edge is already softer than a plain code's and the margin is doing more work, not less.
• A code inside a product shape or a logo lockup. Treat the four modules as part of the code's bounding box in the lockup, and give the lockup its own clear space on top of that.
• Cut lines on round stickers. A die-cut circle around a round layout leaves the least room exactly where the finder patterns are.

KoloQR, a free QR code generator with circular and custom-shaped QR codes, includes the four-module quiet zone in its plain and round exports, so the margin is in the file before it reaches a layout. Styling never improves scan performance - a decorated code needs the margin at least as much as a plain one, and usually a little more. Whatever generator produced the file, measure the margin on a framed or shaped export rather than assuming it, and see round QR codes and QR code shapes for what that looks like in a real layout.

How to check the quiet zone on a QR code file

Measure the margin in modules rather than judging it by eye, because the eye compares the margin to the code and the decoder compares it to one module. The procedure below takes about ten minutes and works on a file you were sent with no source and no notes.

1. Open the file at high zoom. Large enough that a single module is comfortably visible. On an SVG, zoom in the design tool rather than exporting a preview.
2. Count the modules along the top edge of the symbol. Count the dark and light cells across one full side, excluding the margin. The number will be 21, 25, 29, 33 and so on - it is always 4V + 17 for version V.
3. Measure the margin on its worst side, in modules. Compare the clear space to the width of one module at the same zoom. Check all four sides and take the smallest; a code trimmed on one side only is a common export result.
4. Convert to millimetres at the placed size. Divide the placed width by the module count including the margin, then multiply by four. Under 1.6 mm on coated stock or 2 mm on uncoated, the code is too small, too tight, or both.
5. Check the layout, not just the artwork. Look at what sits within four modules of the symbol in the actual page: rules, type, image edges, panel boundaries, the trim line.
6. Run the file through a validator. The QR code validator measures the margin the file carries outward from each edge and reports the worst side, along with contrast and module size.
7. Proof it on the real stock and scan it. One sheet at final size, on the material the job runs on, scanned with an iOS and an Android phone under the lighting the code will actually be read in.

If the margin is short and the artwork cannot be changed, regenerate the code rather than pasting white space around the existing file. Padding an exported raster leaves the symbol's own soft edge where it was, and a regenerated code costs nothing.

Quiet zones on screen, in PDFs and in design files

A screen forgives a short quiet zone and print does not, which is why the fault survives every review that happens on a monitor. A display gives the decoder even illumination, a high contrast ratio and hard pixel edges, so detection succeeds on margins that paper, ink spread and shop lighting would defeat.

Screen: keep the four modules anyway. A code shown on a phone for someone else to scan is being read off a glossy, angled, reflective surface, and the margin is the cheapest defence there is. Avoid placing the code at the edge of a slide or a web section where the surrounding background becomes the margin.

PDF: the margin travels with the artwork, but the placement does not travel with the approval. Codes in PDFs are routinely repositioned during production, and the margin is the first thing a reflow takes. State the clear space in the artwork spec in millimetres, in the same place the bleed is stated.

Design files: place the code as a vector with its margin included and lock the group. In Figma, a frame drawn to the symbol rather than to the footprint is the usual way the margin disappears between the design file and the export - the copy a QR code into Figma guide covers the placement side of that.

Export: keep the code vector wherever the destination accepts it, and where it has to be raster, export at a size that leaves whole pixels per module. A margin that is 3.5 pixels wide is a margin with an anti-aliased fringe on its inner edge, which is a soft boundary exactly where the decoder wants a hard one. Resolution and DPI has the arithmetic. The quiet zone is the fifth of nine checks; the print checklist has the sequence they run in.

How to tell a quiet zone fault from the other scan failures

A quiet zone fault fails completely rather than intermittently: the scanner shows nothing at all, on every attempt, from every distance. Contrast and size faults behave differently - they read sometimes, closer, in better light, on one phone but not another - and that difference is usually enough to identify the fault before measuring anything.

The first row is the one worth internalising. Total, repeatable silence points at detection, and detection points at the margin and the corners - not at the error correction level, the resolution, or the generator that made the file.

Common mistakes with the quiet zone

The most common quiet zone mistake is treating the margin as whitespace in the design rather than as part of the code. Once it is whitespace, every later decision - tightening a panel, adding a keyline, nudging the code away from a fold - is allowed to take some of it, and none of those decisions look like they touch the QR code at all.