QR codes on digital signage: make the next step clear and usable
Use QR codes on public screens to connect a short message with useful mobile information, with practical checks for placement, destinations, scanning and maintenance.
Decide why somebody should scan
A QR code is a route to something else, not a complete message on its own. Before generating one, define what the viewer will gain by scanning it. The destination might be an event registration page, a menu, a product explanation or a feedback form. The purpose should be specific enough to explain in a short label beside the code.
Choose an action that makes sense in the physical setting. Someone walking through a corridor may not be able to stop safely, while a person seated in a waiting area has more opportunity. A code positioned above a busy till can obstruct the queue if customers need to move closer. Think about where the person will stand and what they will do with their phone after opening the destination.
Do not use a QR code to hide essential information that should be visible on the screen. A customer should be able to understand the basic offer before deciding whether to scan. A visitor should have a way to ask for help without a smartphone. The code can provide detail or a convenient next step, but it should not become an unnecessary barrier to the main purpose of the display.
Choose a destination that fulfils the promise
Link directly to the information described by the label. If the screen says “View today's menu”, the destination should make that menu easy to find rather than opening a general homepage with several competing choices. Reducing unnecessary navigation helps the viewer complete the intended action and makes it easier to verify that the code is still useful later.
Open the destination on an ordinary phone before publishing. Check loading, readability, forms and any login requirement. A page that works on a desktop may be awkward on a small screen, and an internal document may be inaccessible to the public. Test with the access level an actual viewer will have, without assuming your own signed-in session represents their experience.
Keep the destination stable where practical. A short-lived file-sharing link or a temporary campaign address can break after the artwork has been distributed. If a redirect or managed destination is used, understand who controls it and what happens if that service changes. Avoid relying on an account or subscription that nobody in the organisation is responsible for maintaining.
Label the code clearly
Explain the benefit in direct language. “Scan to view the event programme” is more useful than “Scan me”, because it tells the viewer what will happen. If the destination involves a form, booking or download, make that apparent before the person opens it. A clear label sets expectations and reduces the chance that viewers abandon a page because it differs from what they anticipated.
Include enough context for the label to stand alone. A code inside a rotating playlist may be encountered without the previous slide. Keep the relevant event name, product or purpose on the same screen. Do not separate the code from its explanation across different zones or slides unless their relationship remains unmistakable.
Provide an alternative when it is useful. A short readable web address or a staff assistance route can help people who cannot or prefer not to scan. The alternative should lead to the same useful information, and any printed address should be checked for spelling and legibility. Avoid a long tracking URL that is impossible to read or type from a distance.
Preserve the code's structure
Use a clear code with strong contrast and an adequate quiet area around it. Decorative backgrounds, overlapping logos and busy borders can interfere with scanning. The design should give the phone camera a clean target. If a generated code includes custom styling, test that exact final version rather than assuming the undecorated original proves it will scan.
Keep the code square and avoid stretching it to fit a layout. Distortion changes the pattern the camera needs to recognise. Export it sharply at a suitable size and inspect it after uploading, because compression or scaling can soften edges. Do not repeatedly resize a low-resolution screenshot when a fresh export from the original destination is available.
- Preserve a clear empty border around the code.
- Use a plain background with strong contrast.
- Avoid stretching, skewing or cropping the pattern.
- Keep decorative elements outside the scanning area.
- Inspect the final uploaded version for blur or compression.
- Test the exact screen output with more than one phone where practical.
Size the code for real scanning conditions
There is no single size that works for every installation. The useful size depends on viewing distance, screen resolution, lighting, camera behaviour and how much information is encoded. Begin with a generous target and test from the position where viewers are expected to stand. A code that scans while you hold a phone directly against the monitor has not been tested for a wall-mounted public display.
Check several distances and angles. Reflections, glare and a low mounting position can make scanning harder. Consider whether people can approach the display comfortably without blocking others. If the code is intended to be scanned from seating, test from those seats rather than a convenient standing position chosen by the installer.
Avoid making the code a tiny decorative corner element. If scanning is the intended action, the target deserves sufficient space and a clear label. If the layout cannot accommodate it, reconsider the composition or the action. Reducing the code until it technically fits can create a screen that looks complete but fails when someone tries to use it.
Give viewers enough time
A rotating slide must remain visible long enough for the person to notice the code, take out a phone, open the camera and scan. That sequence can take longer than reading a short headline. Test the whole process rather than measuring only the moment when a prepared camera recognises the pattern.
Avoid moving or animating the code while it is meant to be scanned. Keep it stable, and do not place transitions or overlays across it. If the playlist rotates quickly, consider a persistent code area or a separate static slide. The surrounding message can change, but the action should remain understandable and the destination should stay relevant to the content being shown.
Check what happens when the slide disappears during scanning. The viewer should not be left waiting through a long loop for another chance. A visible short URL can provide an alternative, but it does not excuse an impractical timing arrangement. If scanning is central to the message, give the interaction appropriate space and duration.
Review privacy and trust at the destination
Be clear about what the destination asks the visitor to provide. A feedback form may collect an email address, while an event booking page may request more information. Use the organisation's normal privacy process and collect only what is needed for the stated purpose. The screen should not imply that scanning is anonymous when the destination requires identifying information.
Use a destination that viewers can recognise and trust. A relevant branded address and consistent page design can help explain where they have arrived. Inspect any redirects and avoid unnecessary intermediate pages. Do not include private access tokens, personal identifiers or internal-only links in a publicly displayed code.
If measurement is used, understand what the resulting numbers actually mean. A page visit associated with a campaign link is not necessarily a unique person or a completed action. A scan can be repeated, abandoned or shared. Interpret the data in relation to the purpose and avoid presenting it as a precise count of people persuaded by the screen.
Test the complete published journey
Testing should begin at the physical display and end at the completed intended action, without submitting real personal information unnecessarily. Confirm that the code opens the correct page, the page is usable on mobile and any necessary follow-up step works. Use a test or preview path for forms where the service provides one, and avoid creating misleading production submissions simply to prove a button exists.
Screenific can display QR code content as part of a signage setup. Check the settings and output of the selected app, including the destination and any visible label. If the code is embedded in an uploaded image instead, verify the image after publication. In both cases, the final screen and destination are the evidence that matters.
Record the destination, content owner and review date alongside the screen asset. This makes it easier to update the code when a campaign ends or a page moves. Keep a list of locations using an important code where practical. Without that record, an obsolete destination can remain visible on a forgotten screen long after the original promotion has ended.
Maintain and improve the experience
Review codes periodically and whenever the linked content changes. Check that the destination still loads, remains relevant and does not unexpectedly require a different permission or login. A code pattern can remain perfectly readable while its destination becomes useless. Maintenance therefore includes both the screen and the page it opens.
Use observations to improve the design. If viewers raise their phones and repeatedly lower them without scanning, investigate distance, reflections, size or timing. If they scan successfully but abandon the destination, inspect the mobile page and the promise made by the label. The problem may be beyond the code itself.
Keep the interaction simple. One clear code tied to one useful action is often easier to understand than several competing codes labelled with vague icons. If multiple destinations are necessary, distinguish them clearly and allow enough space for each. The goal is a confident next step, not a display filled with patterns that viewers must decode conceptually before they can scan.
Frequently asked questions
How large should a QR code be on a digital screen?
Choose a size that scans reliably from the intended viewing position on the actual display. Distance, lighting, resolution and camera behaviour all matter. Test the final published code rather than relying on a universal size rule or a close-up editor preview.
Should a QR code move or animate?
Keep the code stable while viewers are expected to scan it. Motion, transitions and overlays can make recognition difficult. If the surrounding slide rotates, allow enough time for someone to notice the action, prepare a phone and complete the scan.
Can a QR code link to a private document?
A public viewer will need whatever access the destination requires. Check the link without relying on your own signed-in session. Do not expose private tokens or internal information through a public code; use an appropriately published destination for the intended audience.
What should I do when a campaign ends?
Remove or replace the code on every active screen and review its destination. Keep an owner and expiry record so the task is not forgotten. If the address remains accessible, make sure the page explains the current situation rather than presenting an expired offer as active.