Anatomy of a QR code

Anatomy of a QR code is the map a camera uses: three corner finders, timing lanes, a payload region that starts at 21×21 modules, and a quiet zone of at least four empty modules. Cover a finder and decode never starts. A logo is not a fourth finder; it is damage that error correction must pay for.

Anatomy of a QR code the camera actually uses

The three corner finders are nested squares. They locate the symbol and its rotation. The fourth corner holds alignment-related structure as versions grow; leave it uncropped. Timing pattern lanes are the alternating strips that help the camera count modules as perspective distorts the grid. The payload region version is everything else: the bytes, the error-correction blocks, the mask. Version 1 is 21×21. Each version adds four modules per side.

How QR codes work is the sequence. This page is the parts list. Error correction is why a scuff in the payload region can still decode, and why a missing finder cannot. How to make a QR code is the making path once the map is clear.

iOS Camera and Android Camera read this anatomy from the viewfinder on current versions. A separate app is not a requirement for a well-formed symbol. A guest who cannot scan may have an Android skin that hides the reader behind a mode toggle. That is not missing anatomy.

What the nested squares are for

Location. Without three intact finders the camera does not know where the grid begins. Stickers, round business-card corners, Picture Format crop on a 16:9 slide, and Fill Frame in InDesign are how people remove one. Anatomy of a QR code, in a layout meeting, is a request to stop treating finders as decoration you can cover with a crest.

Dark finders on a light ground is the default. A true invert can work when the reader renormalises. A dark ground with dark modules and no invert does not.

Why the empty margin around the grid

Quiet zone four modules is spec-minimum. It is not a design suggestion. Wrap text in Word, captions in Canva, and foil on a Publisher card eat it. Keep a light gutter. Bleed to trim is how packaging fails. Classroom prints fail the same way when a header reprints on top of the top finder. Anatomy of a QR code, in a print meeting, is a request for that gutter in millimetres, not in a vague bit of white. Measure it. Four modules at your version is a physical width. Guessing by eye is how captions win and scans lose. Anatomy of a QR code is a measuring job after it is a naming job. Bring a ruler to the proof.

Does a logo sit in a special anatomy slot

No. A logo on a hosted file sits in the payload region. Error correction restores that region up to L, M, Q, or H. There is no logo mode. If the artwork covers a finder, you left the map. Hosted versus static does not change anatomy. Canva's static widget uses the same finders. Use that widget when the job is a one-off that will never be counted. Use hosted when the payload bytes should mean a URL you can retarget. The squares on the paper look like the same species either way.

What does not belong on the map

Colour, frames, and gradients are product styling. They are not extra finders. If contrast dies, decode dies, regardless of anatomy trivia. Dark modules on a light ground is the default. Anatomy of a QR code does not include a white-on-white brand move.

Version growth adds modules to the payload region. Finders stay in the corners. That is why a version-20 card still has three nested squares and still needs quiet zone. People crop the "busy middle" and leave finders, which can work, or crop a finder to fit a crest, which cannot. How to make a QR code is the making path. This page is why the corners are sacred. A Canva one-off uses the same map. Use Canva when the job will never be counted. Use hosted when the payload bytes should mean a URL you can retarget. Either way, do not cover a finder.