How big should a QR code be on a digital sign? Size by scanning distance
Quick answer: DigitalSignage.com's rule of thumb for a QR code on a screen is that the code should be at least one tenth of the scanning distance, so 7.2 inches (18 cm) for a viewer 6 feet away and 12 inches (30 cm) at 10 feet, plus a blank quiet zone of 4 modules on every side. On a 55-inch 1080p display that is about 290 pixels at 6 feet and 480 pixels at 10 feet. Keep the URL short so the modules stay large, use dark modules on a light background, and leave the code on screen for 15 seconds or more.
Key facts
- The 10:1 rule is a planning estimate: QR side length is about one tenth of the scanning distance, so a code scanned from 10 feet should be at least 12 inches wide.
- A 55-inch 1080p display has 40 pixels per inch, so a 12-inch code needs about 481 pixels and a 7.2-inch code needs about 288 pixels.
- ISO/IEC 18004 specifies a quiet zone of 4 modules on every side, so a 25-module code occupies a 33-module square on screen.
- A version 2 code (25 by 25 modules) holds 26 bytes at error correction level M, while an 89-character tracking URL needs version 6 (41 by 41 modules).
- Error correction level M recovers about 15 percent of damaged codewords and is the usual choice for screens; level H recovers about 30 percent.
- A common planning figure for display time is 15 seconds or more, because a viewer has to notice the code, take out a phone and aim it.
- The QR component is part of mediaCLOUD Plus+ from $3 per screen per month; on the free plan you upload the QR code as an image.
Last updated October 25, 2026.
How big should a QR code be on a digital sign?
A QR code on a screen should be at least one tenth of the distance from which people will scan it, which is the 10:1 rule of thumb used across the signage and print industries as a planning estimate. At 6 feet that means 7.2 inches, at 10 feet 12 inches, and at 20 feet 24 inches, measured on the code itself without its quiet zone.
The rule exists because a phone camera has a fixed field of view and a limited number of sensor pixels. At twice the distance, every module (one black or white square of the code) covers half as many camera pixels in each direction. Below a certain module size the decoder can no longer separate the squares, and the scan fails or takes several seconds of hunting. One tenth is a working minimum; one eighth is a safer target for crowds and older phones.
The 10:1 figure assumes a moderately dense code of roughly 25 to 33 modules across. A code packed with a long URL has smaller modules at the same overall size and behaves as if it were further away. That is why the URL length section below matters as much as the inch figure. Treat the rule as the starting point, then test with two or three different phones at the real distance.
QR code size by scanning distance: inches, centimetres and pixels
The table converts the 10:1 rule into the side length of the code and into pixels on common 1080p screens, using each screen's real pixel density: 51.2 PPI for 43 inches, 40.0 for 55, 33.9 for 65 and 29.4 for 75.
| Scanning distance | Minimum QR side | 43-inch 1080p (51.2 PPI) | 55-inch 1080p (40.0 PPI) | 65-inch 1080p (33.9 PPI) | 75-inch 1080p (29.4 PPI) |
|---|---|---|---|---|---|
| 3 ft (0.9 m) | 3.6 in (9 cm) | 184 px | 144 px | 122 px | 106 px |
| 6 ft (1.8 m) | 7.2 in (18 cm) | 369 px | 288 px | 244 px | 211 px |
| 8 ft (2.4 m) | 9.6 in (24 cm) | 492 px | 385 px | 325 px | 282 px |
| 10 ft (3.0 m) | 12 in (30 cm) | 615 px | 481 px | 407 px | 352 px |
| 12 ft (3.7 m) | 14.4 in (37 cm) | 738 px | 577 px | 488 px | 423 px |
| 15 ft (4.6 m) | 18 in (46 cm) | 922 px | 721 px | 610 px | 529 px |
| 20 ft (6.1 m) | 24 in (61 cm) | does not fit | 961 px | 813 px | 705 px |
| 25 ft (7.6 m) | 30 in (76 cm) | does not fit | does not fit | 1,017 px | 881 px |
Bottom line: at 10 feet a QR code needs about 12 inches, which is 481 pixels on a 55-inch 1080p screen, and beyond 20 feet the code no longer fits on screens of 55 inches or less.
The pixel figures are side length times PPI, rounded. On a native 4K canvas (3840 by 2160) double every pixel number, because the same physical inch holds twice as many pixels. "Does not fit" means the code is taller than the visible screen height: 21.1 inches on a 43-inch display and 27.0 inches on a 55-inch display, before adding the quiet zone.
If the honest scanning distance is beyond 15 feet, the better fix is usually to move the code rather than enlarge it. Put a second, smaller code on a screen near the queue, the counter or the door, where people actually stand still. For how far viewers stand from screens of each size, see the screen size and viewing distance guide.
What is the QR code quiet zone, and how many modules does a code have?
The quiet zone is the empty margin around a QR code, and ISO/IEC 18004 sets it at 4 modules wide on all four sides. It must be the same light color as the code's light modules. Text, a frame, a photo edge or the screen bezel inside that margin can stop a scanner from finding the three corner position markers.
The module count depends on the QR version, which the generator picks from the length of the data. Version 1 is 21 by 21 modules, and each version adds 4 modules per side. More data means a higher version, more modules and smaller modules at the same overall size.
| QR version | Modules per side | With quiet zone | Bytes at level L | Bytes at level M | Bytes at level Q | Bytes at level H |
|---|---|---|---|---|---|---|
| 1 | 21 | 29 | 17 | 14 | 11 | 7 |
| 2 | 25 | 33 | 32 | 26 | 20 | 14 |
| 3 | 29 | 37 | 53 | 42 | 32 | 24 |
| 4 | 33 | 41 | 78 | 62 | 46 | 34 |
| 5 | 37 | 45 | 106 | 84 | 60 | 44 |
| 6 | 41 | 49 | 134 | 106 | 74 | 58 |
Bottom line: a URL of 26 characters or fewer fits version 2 at level M (25 modules), while an 89-character tracking URL needs version 6 (41 modules), so the short URL gets modules 64 percent larger at the same code size.
Byte capacities are the ISO/IEC 18004 values for byte mode, which is what generators use for URLs with lower-case letters. The 64 percent figure is 41 divided by 25. Size planning should therefore include the quiet zone: a code drawn 400 pixels wide with 25 modules needs a 528-pixel clear square, 400 plus 4 modules of 16 pixels on each side.
Which QR error correction level should a screen use?
Level M is the usual choice for a QR code on a digital sign: it recovers about 15 percent of damaged data and keeps the code less dense than Q or H. Screens do not get scratched or torn like paper, so the extra redundancy of level H mainly buys tolerance for glare spots and a logo placed in the middle.
| Level | Recovers about | Density cost | Use it on screens when |
|---|---|---|---|
| L | 7 percent | Lowest, largest modules | Short URL, clean indoor screen, no logo |
| M | 15 percent | Moderate | The default for most signage |
| Q | 25 percent | Higher | Small logo in the center, some glare |
| H | 30 percent | Highest, smallest modules | Larger logo, outdoor glare, glass in front |
Bottom line: choose M unless you add a logo, and remember that every step up shrinks the modules, which costs scanning distance unless you also make the code bigger.
A centered logo works because it deliberately damages modules that error correction then rebuilds. Keep the logo under roughly a fifth of the code's width as a planning figure, never cover the three corner squares, and retest at distance after adding it.
What colors and contrast does a QR code on a screen need?
A QR code on a screen scans most reliably as dark modules on a light background with high contrast, ideally near black on white. Colored codes work when the dark color is genuinely dark: navy #003366 on white has a WCAG contrast ratio of 12.61:1 and scans like black, while orange #FF6600 on white is only 2.94:1 and often fails.
Inverted codes, light modules on a dark background, are allowed by the standard as reflectance reversal, but not every phone camera app reads them reliably. On dark-themed slides, put the code on a white tile with its quiet zone rather than inverting it. The contrast ratios here use the same formula explained in the color contrast guide.
Screen brightness and reflections also change what the camera sees. A glossy panel facing a window can throw a bright hotspot across the code. Matte or anti-glare displays, a slight downward tilt and a brightness level matched to the room, as described in the display brightness guide, all help. Avoid gradients, photos behind the code and thin stylised modules; scanners expect square, flat modules.
How long should a QR code stay on screen?
A common planning figure is to keep a QR code on screen for at least 15 seconds per appearance, or better, to pin it in a fixed zone for the whole loop. Scanning is a sequence: notice the code, decide to act, unlock the phone, open the camera, aim and wait for focus. Each step takes seconds.
A code that appears on one 8-second slide in a 2-minute loop is visible for less than 7 percent of the time, so most passers-by never see it at the moment they are ready. A fixed corner zone, or the same code on every slide in the same position, solves this. Avoid transitions that slide or zoom the code; a moving code is hard to aim at, and a code that leaves mid-scan frustrates the viewer.
Add a one-line call to action next to the code, such as "Scan for the full menu" or "Scan to book a table". People scan when they know what they will get. The QR code integration guide has use cases by industry and call-to-action examples.
Should you use a static or a dynamic QR code?
Use a dynamic QR code when the destination may change or when you want scan counts; use a static code for permanent targets like Wi-Fi details or a fixed homepage. A dynamic code encodes a short redirect URL, so you can change where it points without changing the code on screen.
| Option | What the code contains | Can you change the target later? | Scan tracking | Best for |
|---|---|---|---|---|
| Static QR | The final URL or data | No, regenerate and republish | Only through UTM tags on your own analytics | Wi-Fi, permanent pages, contact cards |
| Dynamic QR | A short redirect URL | Yes, in the redirect service | Built into the redirect service | Campaigns, menus, offers that change |
| Static QR with a short link | Your own short domain | Yes, if you control the redirect | Your redirect logs plus UTM | Teams that want control without a QR vendor |
Bottom line: dynamic codes are smaller and changeable because they hold a short URL; the trade-off is a dependency on the redirect service staying online and paid.
How do you track QR code scans from digital signage with UTM?
Add UTM parameters to the destination URL so your web analytics can separate screen traffic from everything else: utm_source for the screen network, utm_medium for the channel and utm_campaign for the message. A separate utm_content per location tells you which screen drove the visit.
The catch is length. An 89-character URL with four UTM tags pushes the code to version 6, which has 41 modules across. Put the UTM-tagged URL behind a short redirect instead, and the code on screen stays at version 2 with 25 modules. Scan counts then come from the redirect, and on-site behaviour comes from the UTM tags. For setting goals around these numbers, see digital signage goals and KPIs.
Worked example: a QR code on a 55-inch lobby screen scanned from 8 feet
A hotel lobby has a 55-inch 1080p display, and guests stand about 8 feet away at the reception queue. The code links to a breakfast menu with UTM tracking.
| Step | Calculation | Result |
|---|---|---|
| 1. Minimum code size | 8 ft x 12 = 96 in, divided by 10 | 9.6 inches |
| 2. Convert to pixels | 9.6 in x 40.05 PPI | 385 pixels minimum |
| 3a. Long URL (89 characters) | Version 6 at level M, 41 modules; 385 / 41 = 9.4, round up | 10 px per module, 410 px code |
| 3b. Short redirect URL (25 characters) | Version 2 at level M, 25 modules; 385 / 25 = 15.4, round up | 16 px per module, 400 px code |
| 4. Add the quiet zone (short URL) | 400 + 2 x (4 x 16) | 528 px clear square |
| 5. Physical size (short URL) | 400 / 40.05 and 528 / 40.05 | 10.0 in code, 13.2 in with quiet zone |
| 6. Fit check | 528 / 1,080 screen pixels high | 49 percent of the screen height |
| 7. Module size compared | 16 / 40.05 versus 10 / 40.05 | 0.40 in versus 0.25 in per module |
Bottom line: both codes are about 10 inches wide, but the short URL gives 0.40-inch modules instead of 0.25-inch modules, so it scans faster and from further away for the same screen space.
Rounding up to a whole number of pixels per module matters. A module drawn 15.4 pixels wide gets resampled, and some modules end up 15 pixels and others 16, which blurs edges. Export the code at exactly 400 by 400 pixels, or as SVG, and place it at 100 percent scale. PNG keeps edges sharp; JPEG adds compression artefacts around each square.
Because the code with its quiet zone takes half the screen height, the layout puts it in a right-hand zone of about 560 by 1,080 pixels, beside the menu photo, and keeps it there for the whole loop. That is the pinned-zone approach from the display-time section, worked out in real pixels.
How to do this in DigitalSignage.com
In DigitalSignage.com, you add a QR code to a scene in SignStudio, either with the QR component on mediaCLOUD Plus+ or by uploading the code as an image on the free plan. The SignStudio components documentation lists URL, Wi-Fi, vCard and text as QR data types.
- Generate the code at the pixel size from the table, with level M and a short URL, and export it as PNG or SVG. Free plan users then upload it to SignStudio Resources like any other image.
- On mediaCLOUD Plus+, add the QR component to the scene instead and enter the URL or data.
- Place the code in a fixed zone of the scene editor with clear space around it, and add a short call to action in a text component.
- Publish to the screen and scan it with two different phones from the real distance before you sign off.
Whether the QR component lets you set the error correction level, the module size or the quiet zone directly is not described in our documentation; ask support (support@digitalsignage.com, live chat at https://chat.digitalsignage.com/). The image method gives you full control over all three.
Frequently asked questions
How big should a QR code be on a digital sign?
Make the code at least one tenth of the scanning distance, a planning rule of thumb called the 10:1 rule. That is 7.2 inches (18 cm) for a viewer 6 feet away, 12 inches (30 cm) at 10 feet and 18 inches (46 cm) at 15 feet, measured on the code without its quiet zone. On a 55-inch 1080p screen that is about 288, 481 and 721 pixels. Add a quiet zone of 4 modules on every side and test with real phones.
What is the minimum QR code size in pixels on a TV screen?
It depends on distance and screen size, not on a fixed pixel count. Multiply the minimum size in inches (distance in inches divided by 10) by the screen's pixels per inch. A 55-inch 1080p TV has 40 PPI, so a code scanned from 6 feet needs about 288 pixels, and a 43-inch 1080p TV at 51 PPI needs about 369 pixels for the same distance. Use a whole number of pixels per module so edges stay sharp.
Can a QR code be scanned from 20 feet away?
Yes, if it is large enough: the 10:1 planning rule calls for about 24 inches (61 cm) at 20 feet, which is 961 pixels on a 55-inch 1080p screen and nearly the full 27-inch screen height. In practice it is better to put a smaller code where people stand still, such as the counter or the queue, than to fill a distant screen with one code.
How long should a QR code stay on a digital signage screen?
A common planning figure is at least 15 seconds per appearance, because viewers need time to notice the code, unlock a phone, open the camera and aim. Pinning the code in a fixed zone for the whole loop works better than showing it on one slide. Avoid sliding or zooming transitions on the code, since a moving target is hard to scan.
Can I put a QR code on digital signage for free?
Yes. On the DigitalSignage.com free plan, which covers the first 3 screens, you generate the QR code elsewhere and upload it to SignStudio as a PNG or SVG image. The built-in QR component is part of mediaCLOUD Plus+, from $3 per screen per month. Either way, size the code by scanning distance and keep it on screen long enough to scan.
Do colored or inverted QR codes work on screens?
Colored codes work when the dark modules are genuinely dark and the background light: navy #003366 on white has a contrast ratio of 12.61:1 and scans well, while orange #FF6600 on white is only 2.94:1 and often fails. Inverted codes, light on dark, are allowed by ISO/IEC 18004 but some phone camera apps do not read them reliably, so put the code on a white tile on dark slides.
Should a QR code on a sign be static or dynamic?
Use a dynamic code for campaigns, menus and offers that change, because it holds a short redirect URL that you can repoint and it reports scans. Use a static code for permanent data like Wi-Fi details. Dynamic codes are also physically easier to scan, since a short URL needs fewer modules, such as 25 instead of 41 for a long tracking URL.
Which QR error correction level is best for digital signage?
Level M, which recovers about 15 percent of damaged data, suits most screens. Move to Q (25 percent) or H (30 percent) only when you place a logo in the center or the screen sits behind glass with glare. Higher levels add modules, so make the code larger to keep the same scanning distance.
Related guides
- QR code integration for digital signage: use cases, calls to action and tracking tools
- Screen size and viewing distance: how far viewers stand from each screen size
- Typography and viewing distance: sizing the call-to-action text next to the code
- Display brightness in nits: reducing glare that blocks scans
- SignStudio scene editor: zones, text and image placement
- Screen resolution standards: pixel density at 1080p and 4K
- Digital signage goals and KPIs: turning scan counts into results
- Color contrast for digital signage: the contrast ratio formula and tested color pairs
- Screen mounting height and viewing angle: where the code ends up relative to eye level
Try it on your own screens, free
DigitalSignage.com, which publishes this guide, runs a permanent free plan: the first 3 screens are free forever (no credit card, no ads, no time limit), then from $3 per screen per month with volume pricing via a public calculator. The free SignPlayer runs on Windows, Mac, Android and Android TV, Chrome OS, Raspberry Pi, iPad or any modern web browser, so the hardware you already own usually works. Start free · pricing · How 11 vendors compare on price
This guide is maintained by MediaSignage, pioneers of digital signage technology since 2006.