A QR code is one of the very few brand surfaces that ships with a built-in tolerance for damage. Almost nobody spends it.
The default QR code is a generated square of black noise. It works, it is free, and it looks exactly like everyone else's, which is a strange thing to accept for an object you hand to someone at the moment you introduce yourself.
It does not have to be that. There is real room inside the specification, and it is worth knowing precisely where that room is, because the difference between a beautiful code and a beautiful code that fails in a dim restaurant is a few technical decisions.
The error correction is the opportunity
QR codes carry Reed-Solomon error correction at one of four levels, chosen when the code is generated:
- L, roughly 7% of the code recoverable
- M, roughly 15%
- Q, roughly 25%
- H, roughly 30%
That redundancy exists so a code still reads when it is scratched, smudged, folded or badly lit. The decoder does not know or care why some modules are unreadable. Which means the same budget that covers a coffee stain will just as happily cover a deliberate piece of artwork.
Generate at H and you have roughly thirty percent of the field to spend on design. That is the whole trick. Everything else is knowing what you are not allowed to touch.
What has to survive, without exception
- The three finder patterns. The large concentric squares in the corners. They are how a scanner locates the code and works out its orientation and perspective. Restyle them at your peril, and never remove one.
- The timing patterns. The alternating line of modules running between the finders. They tell the decoder the grid size. They look like decoration. They are not.
- The alignment patterns. The smaller squares that let a decoder correct for a curved or angled surface.
- The quiet zone. A clear margin of four modules on every side. This is the single most common real-world failure, because it looks like wasted space and gets cropped, or something gets set too close to the edge.
- Contrast, in the right direction. The dark modules must be genuinely darker than the light ones. Inverted codes, light on dark, are decoded by some readers and not others, which is a coin flip you do not want in print.
Where the freedom actually is
Everything else in the field is negotiable, and there is more of it than people expect.
The module shapes
The data modules do not have to be squares. They can be rounded, merged into continuous forms, given weight, or drawn as something else entirely, as long as a module that should read dark reads dark across its whole cell.
Colour
Any two colours work if the contrast holds. This is where a code stops looking like a utility and starts looking like it belongs to you. Test the printed result rather than the screen version: ink on uncoated stock has a habit of losing the contrast you approved on a monitor.
The centre
A logo knocked out of the middle is the well-known move, and it works precisely because of the error correction budget described above. It is the least interesting thing you can do with that budget.
The URL itself
A shorter destination means fewer modules, which means larger modules at the same physical size, which means more tolerance for everything else. Shortening the link is a design decision before it is a technical one.
Our own cards
Ours draw a skyline. San Diego, Dubai and Toronto, built from the modules of a working code, so that the thing carrying the link is also the picture. It was designed the way anything with a constraint gets designed: establish exactly what cannot move, then treat everything left over as the canvas.
You can see them in the studio artifact section on our home page.
The test people skip
A decorated QR code is not finished when it looks good. It is finished when it scans off a printed proof, at the real size, on an old phone, in bad light, at an angle, using the built-in camera app rather than a dedicated reader.
Those decoders are not equivalent, and the built-in one is what a stranger will actually use. If it takes a second attempt, it failed.
Why bother at all
Because of where it gets used. A business card is handed over in person, in the first thirty seconds of knowing someone. A menu code is looked at by every single customer. A packaging code is on the shelf next to the competition.
These are unusually high-attention moments to fill with a generated square that could belong to anyone. The generic version is free. The distinctive version costs a day of design and the discipline to test it properly, and it is one of the clearest cases of the distinctiveness argument in what a brand actually is: being recognisable beats being tasteful, and a code drawn as your own skyline is not something a competitor can put on their website tomorrow.
It is also, straightforwardly, a system problem rather than an artwork problem, which is the subject of digital branding as a system.