How to check an event QR code before printing
Check the encoded URL, the live booking page and the printed code separately.
Detailkite field notes · Reviewed 28 October 2026
Three separate QR checks
A code can scan successfully and still lead to the wrong event.
| Check | What to confirm |
|---|---|
| Encoded URL | Does the value inside the code match the approved URL? |
| Live page | Does it open the right event, date, venue and ticket offer? |
| Printed code | Can a phone read the proof at its final size and likely viewing distance? |
- Decode the code in the final export.
- Compare the full URL, including its path.
- Open the destination on a phone.
- Review any redirects and the booking page.
- Test a physical proof; keep a readable fallback URL.
Begin with the approved URL
Write down the booking URL before generating or reviewing the code. If you use a short link, record the expected final destination too. Different URLs are not automatically equivalent. In our fictional sample, the visible URL is /studio but the code contains /old-studio.
Compare the code in the exported file
Use the final PNG, JPG or PDF page. Detailkite compares one detectable QR destination per page with the URL you supply. If it cannot read the code, or there are more codes on the page, check those manually. It does not visit the destination or certify that it is safe.
Test what the audience will use
Open the destination on a phone and check the event name, date, venue and offer. Look for expired pages, broken redirects and unexpected sign-in prompts. For print, test a proof at its final size. Follow the printer’s guidance on spacing, contrast and finishing; a digital decode does not approve the physical result.
Compare a sample export
The fictional workshop PDFs contain a date, price and QR example you can inspect in the checker.
Open the sample