Step 1 — Decide what the code should do
A QR code is a container, not a destination. The first decision is which payload format to use, and that determines what the phone will offer to do when it reads the code.
| Goal | Format | What the phone does |
|---|---|---|
| Send someone to a page | https:// | Opens the browser |
| Join a network | WIFI: | Prompts to connect |
| Save a contact | vCard | Offers to add to contacts |
| Start a text | sms: | Opens messaging with body filled |
| Place a call | tel: | Opens the dialler |
| Show information | Plain text | Displays the string |
Choosing the wrong format is the single most common reason a code "does nothing" on a phone. A URL wrapped inside a text payload, for example, will display as a string instead of opening — the scanner has no way to know it should be a link.
Step 2 — Keep the payload as short as possible
QR codes use Reed–Solomon error correction, which means they can survive damage and logos — but the density cost is real. Every extra character adds modules, and smaller modules are the first thing to disappear when a code is printed badly or scanned from too far away.
Three habits keep payloads short:
- Shorten long URLs before encoding. A 180-character URL with tracking parameters produces a visibly denser code than a 25-character short link.
- Drop the optional fields. A vCard with a note field can be twice the length of one without.
- Do not encode what the user can infer. A Wi-Fi code does not need the network's location or a welcome message.
As a rough guide: under 100 characters scans comfortably at 2 cm, 100–300 needs about 3 cm, and anything past 500 characters should be printed at 4 cm or more, or replaced with a link.
Step 3 — Generate and check the pattern
Generate the code at the largest export size available — a 1024 px PNG or an SVG. Before worrying about design, look at the pattern itself:
- Is there a clear quiet zone (blank margin) on all four sides? At least four modules wide is the standard.
- Are the three corner squares intact and unobstructed? These are the finder patterns the camera locks onto first.
- Does the pattern look like an even grid, or are there suspicious blank patches? A blank region usually means the encoder failed or the logo is covering too much.
Step 4 — Test on real hardware, not just the preview
This is the step people skip, and it is the only one that catches actual problems. Test on at least one iPhone and one Android device, using the built-in camera app rather than a third-party scanner — that is what most people use.
Test three states:
- On screen, at the size it will appear in print. Zoom out until it matches.
- Printed on paper, at the real size, under indoor lighting.
- At the real viewing distance — hold the phone where a user would actually hold it. A poster read from two metres needs a much bigger code than one read from twenty centimetres.
If it fails at step 3 but worked at step 1, the problem is print quality or size, not the payload. If it fails everywhere, check the payload format.
Step 5 — Export the right file for the job
| Use case | Format | Why |
|---|---|---|
| Professional printing, signage, merch | SVG | Vector — infinitely sharp at any size |
| Documents, slides, social posts | PNG 1024 px+ | Lossless, universally supported |
| Quick internal preview | JPG | Small file, but compression blurs edges |
Never enlarge a small PNG in an image editor. Interpolation softens the module edges and the result scans worse than the original. Regenerate at a larger size instead — it takes seconds.
The five mistakes that cause most failures
1. Low contrast
Light grey on white, or a coloured code on a mid-tone background. The scanner needs a clear luminance difference. Dark foreground on a light background is the safe default; invert it only if you test thoroughly.
2. A logo that covers too much
Error correction can recover roughly 7% (level L), 15% (M), 25% (Q) or 30% (H) of the pattern. A logo at 30% of the width already removes about 9% of the area — plus the margin around it. Keep logos under 25–30% and always use level H when a logo is present.
3. Printing too small
A code that scans perfectly on a bright monitor can fail on matte paper at 15 mm. Paper absorbs ink, dot gain blurs adjacent modules, and the effective contrast drops.
4. Placing it on a curved or reflective surface
Wrapping a code around a bottle distorts the grid. Glossy laminate creates a specular highlight that whites out a corner under direct light. Use matte stock, or place the code on a flat label.
5. Never testing the final artwork
The file you send to the printer is not the file you tested — the printer may resize, re-colour or re-compress it. Ask for a physical proof of the actual code, not just a PDF preview, and scan that.
Frequently asked questions
Do I need to register or pay for a QR code?
No. QR codes are an open standard. Static codes cost nothing to create and nothing to scan. You only pay if you choose a service that hosts a redirect behind the code, which adds editability but creates a dependency.
How many scans can one code handle?
Unlimited. A static code is just a pattern — there is no counter and no server, so scanning it does not consume anything. The only limit is the physical durability of the printed surface.
Can I put two links in one code?
Not directly. One pattern holds one string. To offer a choice, use a landing page with two buttons, and encode the link to that page.
Why does my code scan on Android but not iPhone?
Usually a payload format issue rather than a hardware one. iOS Camera is stricter about unknown schemes — for example, it may not act on a geo: URI, while most Android scanners will. Switch to an https:// link that both platforms handle.
Ready to build one? Start with the QR code generator, or go straight to the type you need from the tools menu.