1. What the 15 Bits Contain
The format information has 5 data bits and 10 error-check bits. The 5 data bits are 2 bits for the error correction level and 3 bits for the mask pattern (0 to 7). The 10 check bits come from a BCH (15,5) code. This low-level structure is handled automatically by tools like our [URL QR code generator](/url-qr-code-generator) and [barcode generator](/barcode-generator), ensuring every symbol is spec-compliant.
2. Masking the Format String
The final 15-bit string is XORed with the fixed pattern 101010000010010. This prevents an all-zero format string and keeps the area from looking like a blank region. When you use our [QR scanner](/qr-scanner) or any standards-compliant reader, it automatically reverses this mask to extract the format data. Understanding these details helps when troubleshooting scanning issues with our [printed QR tester](/printed-qr-tester).
3. Redundancy
The format string is written twice: once around the top-left finder pattern, and once split between the other two finders. If one copy is damaged, the reader falls back to the other. Version information (Version 7 and above) is a separate 18-bit block also written twice. This redundancy is one reason why QR codes work reliably even when partially obscured—a critical consideration when using the [error correction simulator](/error-correction-simulator) to plan damage tolerance. For sizing and placement that preserves these critical areas, consult our [QR placement guide](/qr-placement-guide) and [QR size calculator](/qr-size-calculator).
Putting this into practice
Start with the smallest real test you can run. Generate the code, print it at the exact size you plan to use, and scan it with two different phones in the lighting where it will live. Check that the destination page loads quickly on a mobile connection and that the call to action next to the code tells people what they will get. If anything feels slow or unclear, fix it before you print a full batch, because reprints cost more than a short test. Keep a note of the size, material, and placement that worked so the next batch starts from a proven setup.
Common mistakes to avoid
The most common mistakes are easy to avoid once you know them. Long payloads make modules tiny, low contrast makes edges hard to read, and text placed too close to the border eats the quiet zone the scanner needs. Covering a corner finder pattern with a logo or a sticker breaks detection entirely, and a code placed behind glare or on a curved surface fails even when the print is perfect. Review each of these points on a proof copy, and treat any failure as a reason to adjust the design rather than a reason to blame the scanner.
Quick checklist
- Keep the payload as short as practical so modules stay large.
- Keep dark modules on a light background with strong contrast.
- Leave a clear quiet zone on all four sides of the symbol.
- Test the printed code at the real viewing distance and lighting.
- Confirm the destination page loads fast on a phone.
- Recheck the code after any change to the link, design, or placement.
