# Short answer: the three squares are where scanning starts
# Why is scanning hard in the first place?
One-dimensional; read by a laser from one direction; about 13 digits in the retail standard (EAN-13); essentially zero damage tolerance — one scratch, game over
Two-dimensional; read by a camera from any angle and distance; up to 7,089 digits in the largest version; 7% to 30% damage tolerance through error correction
# The story: a Toyota factory and a Go board
# The full map: everything in its place
| Piece | Where it lives | What it does |
|---|---|---|
| Quiet zone | White margin around the whole code | Separates the code from its background — 4 empty modules on every side |
| Finder patterns ×3 | Three corners | Finding, orientation, scale — the subject of this article |
| Separators | White ring around each square | Keep the squares from blending into the data |
| Timing pattern | Row and column 6, dashed | An alternating dash line; marks the module grid step by step |
| Alignment pattern | Near the empty corner (large versions only) | Compensates for lens distortion and curved surfaces |
| Format strip | Beside the squares | Declares the error-correction level and the chosen mask |
| Data + error correction | Everything else | What we call "the content" |
# Why three, not four?
# Why this exact shape? The 1:1:3:1:1 signature
# When half of it is under a coffee cup: error correction
| Level | Recovery capacity | Where it is used |
|---|---|---|
| L | 7% | Billboards and open spaces — maximum data capacity |
| M | 15% | The default for most codes |
| Q | 25% | Tickets and receipts — paper that gets folded and rubbed |
| H | 30% | Business cards — where a logo is printed over the code |



