A QR code can give an audience a route from a visual set to your portfolio, credits, or event page. The difficult part is making the code readable in the actual room without interrupting the visuals.
Disclosure: I represent PlainlyKit, which makes the optional QR generator linked below. This is a production checklist, not a claim that a specific projector or venue has been tested.
Start with a destination you control
Use a short HTTPS URL on your own domain when possible. Link to a mobile-friendly page containing your artist name, current work, credits, and an obvious next action. A direct URL encoded in a static QR code does not require a separate QR redirect provider, though the destination website still needs to stay available.
A static code cannot be edited after printing. If you control the destination URL, you can update the page served there. That is different from changing the encoded URL itself. Avoid temporary download links and URLs containing private tokens.
Separate the code from the live visuals
Keep the QR image still and place it on a plain, contrasting background. Preserve the blank border around the code. Do not crop that border, put animated textures behind it, or run the image through a distortion effect simply to match the set.
For a projected code, avoid a position where performers, stage equipment, or audience silhouettes repeatedly block it. A foyer display, printed card, or separate holding slide may work better than a moving show layer. Keep it visible long enough for someone to notice it, unlock a phone, aim, and open the link. There is no universal duration or pixel size: test the real setup.
Generate once, then test the exported file
One option is the free PlainlyKit static QR generator. Any generator that produces a standard, readable code can fit this workflow. Copy the complete destination URL, generate the code, and export it before adding it to your composition.
Test the exported image rather than relying only on the generator preview. Scan it with more than one phone if available. Confirm the exact hostname and final page, including redirects. A phone recognizing the pattern is only the first check; the page must also load and be useful on mobile.
Test through the whole signal chain
Bring the code through the same composition, output scaling, projector or display, and physical placement you will use at the event. Check it from the furthest intended audience position and from an off-center angle. Projector focus, keystone correction, compression, display brightness, and room light can all change the result.
If scanning fails, simplify before adding effects: shorten the URL, increase the code's displayed size, remove background detail, restore the border, or move it to a less distorted part of the image. Re-test after each change. Keep a small note of the working output resolution and physical setup so the next operator can reproduce it.
Give people a fallback
Show a short readable URL beside the code. That helps people who cannot scan, are using the same phone to watch a stream, or simply prefer typing. Use readable type and sufficient contrast. Never make a QR code the only way to access essential event information.
Before doors open
- Scan the final code from an audience position.
- Check the destination on mobile data as well as venue Wi-Fi when available.
- Verify that the landing page needs no unexpected login.
- Keep a local copy of the QR image and a plain-text copy of the URL.
- Have a still slide or printed fallback ready.
A portfolio link is useful only when it survives the venue. Treat the QR layer like any other output element: check the final signal, document what works, and keep a fallback.
Top comments (0)