What is the quiet zone on a QR code?

The quiet zone is the blank margin around the outside of a QR code, the same colour as the code's light modules, usually white. It is part of the code, not decoration: the decoder finds the code by looking for the three large corner squares, and it recognises them by the ratio of dark and light bands across them, including the light band on their outer edge. That outer light band is the quiet zone. Take it away and the corner squares blend into whatever surrounds them, and the phone cannot find the code to read it.

How big does the quiet zone need to be?

Four modules wide on every side, where a module is one of the small squares that make up the code. It scales with the code: if the modules are 1 mm across, the quiet zone is 4 mm; if they are 0.5 mm, it is 2 mm. It is not a fixed number of millimetres and it is not a percentage. Most phone cameras will read a code with a narrower margin under good conditions, but the four-module figure is the specification, and it is the margin that survives ink spread, laminate glare and a slightly blurred lens with nothing to spare.

Can I put a frame or a 'scan me' label around my QR code?

Yes, outside the quiet zone. The frame, the arrow and the words all need to sit beyond the four-module margin, with blank space between them and the code. A frame that touches the code's edge is, to the decoder, part of the code, and it breaks the corner squares' outer edge exactly as a cropped margin does. Generators that offer framed codes handle this by drawing the frame outside the margin; a frame you add yourself in a design tool usually does not.

Does a QR code on a dark background need a quiet zone?

Yes, and the quiet zone must match the code's light modules, not the page. If you have inverted the code so the modules are light on dark, the quiet zone has to be dark. If the code is normal, dark on light, and sits on a dark page, it needs its own light margin around it, four modules wide, before the dark background starts. A dark-on-light code dropped straight onto a dark page with no light border has no quiet zone at all, which is the most common way a code that scanned in the preview fails in the layout.

Guides2026-08-29

QR code quiet zone: what it is and how big it needs to be

Every guide about printing a QR code says to keep the quiet zone, and almost none of them say what it is, so people keep it the way they keep a superstition: vaguely, and only until a designer needs the space. The quiet zone is part of the code. Here is what it does, how big it has to be, and the four places it quietly disappears.

The five-minute version

The quiet zone is the blank border around the code, in the same colour as the light modules. It is part of the code, not padding.
It is four modules wide on every side. A module is one small square of the pattern, so the margin scales with the code; it is not a fixed millimetre figure.
Anything that touches the code — a frame, a border line, a background shape, a fold, a crop — must stay outside the margin.
On a dark page the margin is still light. A dark-on-light code needs its own white border before the dark background begins.
Export with the margin inside the file, on a solid background, so it cannot be cropped later without someone noticing.

What the quiet zone is for

A phone does not read a QR code the way you read a page, from the top left. It first has to find the code inside a camera frame full of other things, and it does that by looking for the three large squares in the corners, the finder patterns. Each one is a dark square inside a light ring inside a dark ring, and the decoder recognises it by the proportions of the bands it crosses along any line through the centre: dark, light, dark, light, dark, in the ratio 1:1:3:1:1. That ratio is only measurable if the band on the outside is light, and the band on the outside is the quiet zone. Put a dark line against the code’s edge and the outermost dark ring of the finder pattern merges with it; the proportions are wrong, the finder is not found, and the phone sees a busy patch of nothing.

So the margin is not there for legibility or taste. It is the light band that makes the corner squares recognisable as corner squares. That is why the specification counts it as part of the symbol and gives it a width in modules, the same unit as the rest of the code, and why a design tool that crops “the empty white bit” has not tidied the code but removed a piece of it.

How big: four modules, whatever the module is

The standard width is four modules on each of the four sides. A module is the smallest square in the pattern, and its physical size depends on how big you print the code and how much data is in it. A 25-module-wide code printed at 25 mm across has 1 mm modules and needs a 4 mm margin all round, so the whole object is 33 mm. The same code printed at 50 mm needs 8 mm. A denser code with 41 modules across, printed at the same 25 mm, has modules of roughly 0.6 mm and needs a margin of about 2.5 mm. The margin shrinks with the module, not with the code, which is why it is wrong to specify it as “5 mm” or “10% of the width” in a brand guideline: both are right for exactly one size of one code.

Two honest qualifications. Modern phone decoders are more tolerant than the specification, and most will read a code with a one- or two-module margin in a good light, held steady, on a clean print. That tolerance is the reserve you spend on everything else that goes wrong: ink that spreads a fraction of a module, a laminate reflecting a ceiling light across one corner, a lens that is not quite focused. Four modules is the width at which none of those has to be perfect. And a wider margin never hurts; there is no upper limit, and a code sitting in a generous field of white is the easiest thing a camera will find all day.

Quiet zone and print size are separate budgets. The size guide sets the smallest module the printer and the reading distance can support; the quiet zone is four of those modules on top, outside the code. If a label has room for a 20 mm code, plan for a 20 mm code plus the margin, not a 20 mm object with the margin squeezed inside it. Squeezing the margin means shrinking the modules, and the modules are the part with the floor.

Where the quiet zone disappears

The generator gives you the margin. It rarely survives to the print unless someone is guarding it, because every stage after the generator has a good reason to take it away.

The crop. The exported image has a white border, a designer trims to the visible edge of the pattern so the code “sits properly” on the grid, and the margin is gone before anything else has happened. This is the single most common cause, and it is invisible in the layout because the artboard behind the code is also white. It only shows when the background is not.
The frame. A “scan me” box, a rounded border, a rule under a caption. Drawn snug to the code because that looks deliberate, and to the decoder a rule against the edge is just one more dark module in the wrong place. Frames belong outside the margin, with the four blank modules between them and the code.
The background. A dark panel, a photo, a brand colour block. The code is placed on it with its white margin cropped away, so the light modules meet the dark background directly and the finder patterns lose their outer edge. The fix is a white plate behind the code, four modules larger than the code on every side, and the plate is the quiet zone. The design guide has the rest of the list of features that look like styling and act like damage.
The transparent export. A PNG with a transparent background contains no white at all; the page supplies it. That works until the page is dark, or a mail client renders in dark mode, or the label stock is kraft brown, and then the margin is whatever colour the world happens to be. The screen guide covers the dark-mode case; the principle is the same everywhere. Export on a solid background so the margin travels inside the file.
The edge. A code placed hard against the trim line of a card, the fold of a leaflet, the seam of a sleeve, or the die-cut of a label. Trim wanders by a millimetre, folds shadow, seams curve, and the margin on that one side is the first thing to go. Keep the code at least a quiet zone’s width, and preferably more, inside any physical edge.

Dark codes, light codes, and which colour the margin is

The rule is that the quiet zone matches the light modules, which is a more useful way to say it than “white”. For a normal code, dark pattern on a light ground, the margin is light, and if the surrounding page is dark the code needs its own light field around it before the page begins. For an inverted code, light pattern on a dark ground, the margin is dark, and a white border around an inverted code is the thing that breaks it. Inverted codes are already a risk — the not-scanning guide lists them among the six causes, because older decoders do not read them at all — so if you must invert, at least give the margin the colour the decoder expects, which is the ground the pattern sits on.

Keeping it: three habits

Export with the margin baked in, on a solid background, as SVG for print or PNG for anything else. Then the file’s edge is the margin’s edge, and cropping to the file is safe.
Write the margin into the brief in modules, not millimetres: “keep four modules of clear space on all sides; the white in the file is that space, do not trim it.” A printer or designer who has never heard the phrase quiet zone will understand that sentence.
Check it last, on the proof, against a dark or busy background if the final piece has one. The testing guide puts the scan of the proof at stage three for exactly this reason: the margin is intact in the export, and what you are testing is whether it survived everything after.