Use this sequence: validate the content, test the digital export, print at final size, test the real surface, then record approval. Each stage catches a different class of failure.
1. Confirm the encoded content
- Open the destination and confirm the final domain, page, and language.
- Remove accidental spaces from URLs, network names, email addresses, and phone numbers.
- Verify capitalization in Wi-Fi credentials and event time zones.
- Check that public vCards contain only details intended for public distribution.
- For campaigns, verify UTM parameters without exposing private identifiers.
Do this before discussing colors or placement. A perfectly printed code with the wrong destination is still a failed code. For bulk jobs, keep a proof sheet that pairs each human-readable label with its destination.
2. Test the exported file
Download the same format that will enter the layout. SVG is usually best for professional print because it remains sharp when resized. PNG is appropriate when the production system requires pixels, but it must have enough resolution for the final dimensions.
- Scan the downloaded file instead of relying only on the live preview.
- Place it on the intended background and confirm the quiet zone stays clear.
- Make sure no logo, crop, or design element covers the finder patterns.
- Check the code at 100% size, not only while zoomed in.
3. Print one proof at final size
A home or office proof does not perfectly reproduce a commercial press, but it reveals sizing, trimming, and basic contrast problems. Print at actual size with scaling disabled. Measure the code itself, including its quiet zone, and compare it with the approved layout.
| Test | What it reveals | Pass condition |
|---|---|---|
| Normal viewing distance | Code may be too small for placement | Scanner locks quickly without moving unusually close |
| Two different phones | Camera and software differences | Both reach the correct destination |
| Bright and dim light | Low contrast, glare, or shadows | Code remains detectable in realistic conditions |
| Final surface angle | Curves and reflections | Typical users can hold a workable scanning angle |
4. Test the installed context
Stand where the user will stand. A tabletop card may be scanned from a seated position; a storefront sign may be viewed through glass; a poster may be approached from several directions. Check whether furniture, frames, folds, hands, or reflections cover part of the code.
The text beside the code should explain the result: “View today’s menu,” “Join guest Wi-Fi,” or “Save this event.” A clear promise reduces hesitation and makes it easier to notice when a destination does not match.
5. Sample a batch intelligently
For a batch, test the first, middle, and last records plus any unusually long destination. Then randomly sample additional rows. Confirm that the visible label matches the encoded destination; this catches row shifts that a simple scan-quality check cannot.
Do not approve from a screen capture alone. Resampling, messaging compression, and PDF export can change edges or margins. Approve the file that the printer will actually use.
6. Keep a small proof record
Record the file name, destination, final size, material, date, phones used, and approver. This is especially useful when a design is reused months later or when different locations print the same campaign.
Prepare a proof
Generate the code, download the production format, and use the checklist before committing to a full run.
Create a test QR code