A QR code that scans instantly from a business card can fail completely from a screen. Video adds three problems print never has: compression that eats the code’s fine detail, motion that smears it, and a viewer who needs a good eight seconds to notice the code, pull out a phone, and aim.
Here’s the full workflow: when a QR code actually belongs in a video, getting a source file that survives export, layering it in CapCut, Premiere Pro, or DaVinci Resolve, and the size, timing, and contrast numbers that decide whether anyone scans it.
When a QR Code Belongs in a Video (and When It Doesn’t)
The test is one question: is the screen a different device from the viewer’s phone? If yes, a QR code is the fastest bridge between the two.
Where QR codes earn their place:
- Event and conference screens — session slides, sponsor loops, “join the Q&A” prompts. The audience is seated with phones in hand.
- Trade-show booth loops — a video running unattended on a monitor works the booth all day; the QR code is its handshake.
- Digital signage — lobby displays, menus, retail screens. Viewers stand close and already expect codes here.
- TV and CTV spots — a spoken URL is forgotten in seconds; a code held on screen for ten gets scanned.
Where they don’t: regular YouTube uploads. Most YouTube watch time already happens on a phone — asking a viewer to point a phone at a phone is pointless — and YouTube gives you clickable alternatives: description links, cards, and end screens (covered in the YouTube end screen guide). Bake a QR into a YouTube video only when the file will also play outside YouTube: screened at an event, running on a kiosk, downloaded and passed around.
Start With a File That Survives Scaling and Compression
Two rules for the source file, both about protecting the code’s fine structure:
Get it as SVG or a large transparent PNG. An SVG scales to any resolution with perfectly sharp module edges, which is exactly what you want when the same code goes on a 1080p loop today and a 4K signage screen next month. If your editor won’t import SVG (CapCut won’t), use a transparent PNG at 1,000×1,000 px or larger, and never scale it up in the timeline. QRocket’s free QR generator exports both SVG and high-resolution PNG, which covers every editor in this article.
Keep the URL short and the error correction high. A shorter URL produces a code with fewer, larger modules — and larger modules survive H.264 compression far better than dense ones. Then set error correction to Q (25% recoverable) or H (30%): it adds density back, but it’s the buffer that keeps the code scannable after the encoder softens it. Short URL first, high correction second.
Layering the Code in Your Editor
Mechanically, a QR code is just a static overlay: a still image on the track above your footage.
CapCut
Desktop: Media → Import the PNG, drag it to a track above your video, then drag the corner handles to size it and place it in a corner. Mobile: Overlay → Add overlay, pick the PNG, pinch to size. No blend mode needed — leave it on Normal; the transparency in the PNG does the work. If you’re new to CapCut’s layer stack, the CapCut overlays tutorial covers it in detail.
Premiere Pro
Drop the PNG on V2 above your footage, select it, then Effect Controls → Motion → Position and Scale. Set an exact scale value rather than eyeballing — you’ll want the same size on every deliverable.
DaVinci Resolve
Edit page: place the PNG on V2, then Inspector → Transform → Zoom and Position. Resolve also imports SVG via Fusion if you need true resolution independence.
Placement rules that apply everywhere
- Corners, not center. Bottom-right or bottom-left reads as “supporting info”; center reads as an interruption.
- Respect safe margins. Keep the code at least 5% of the frame width away from every edge — 10% if the video will ever play on a TV, where overscan can crop edges.
- Park it over a low-motion area. A code over a static wall or a color band stays readable; a code over moving footage fights a shifting background at its edges.
- Don’t animate it. No slides, spins, or pulses while the code needs to be scannable. Fade it in, then hold it dead still.
How Big the Code Needs to Be
The classic rule: scanning distance ÷ 10 = minimum code width. A viewer 2 meters away needs a code about 20 cm wide on the physical screen. Modern phone cameras beat this in good light, but the 10:1 ratio is the number to design to, not to gamble past.
Translated to frame height on a 1080p canvas:
| Viewing situation | Typical distance | Code height |
|---|---|---|
| Laptop / desktop viewer | 0.5–0.75 m | 10–12% of frame (110–130 px) |
| Standing signage, booth monitor | 1.5–2.5 m | 20–25% of frame (220–270 px) |
| TV across a living room | 2.5–3 m | 25%+ of frame, held longer |
The TV row deserves honesty: at 3 m, the 10:1 rule asks for a 30 cm code — nearly half the height of a 55“ screen. Real CTV ads compromise around 25% of frame height and rely on motivated viewers pausing or stepping closer. That’s a reasonable trade, but make it knowingly, not by leaving the code at whatever size looked tidy in the timeline.
Timing: 8 Seconds Is the Floor
Watch someone actually scan a code: notice it, decide to act, unlock the phone, open the camera, aim, wait for the detection. That chain takes 5–6 seconds when it goes well. So:
- 8–10 seconds on screen is the minimum for a code appearing mid-video.
- A static end card of 10–15 seconds is the ideal — nothing competing for attention, nothing about to cut away.
- On signage and booth loops, keep the code up for the entire loop in a corner, or give it a long hold every cycle. Someone walking up mid-loop shouldn’t have to wait 40 seconds for it to come back.
And if the video loops all day, make the loop itself clean — a visible stutter at the splice point pulls eyes away at exactly the wrong moment. The seamless loops guide covers why loops jump and how to fix them.
Contrast and the Quiet Zone Over Busy Footage
Scanners need two things your footage will happily destroy: contrast and breathing room.
- Put the code on a solid backing card. A white rounded rectangle behind a dark code is the boring, correct answer. A “transparent” code floating directly over footage scans only when the footage cooperates, which it won’t for the whole runtime.
- Preserve the quiet zone. The blank border around the code — at least 4 modules wide on every side — is part of the spec, not padding. Backing card edges, text, and logos must stay outside it.
- Dark code on light background. Inverted (light-on-dark) codes fail on a meaningful share of scanner apps. If your video is dark, that white backing card is doing double duty.
- Keep effects off the code. Film grain, glitch passes, and vignettes are texture over exactly the fine detail the scanner needs. Mask effects out of the code region, or apply them below the QR layer.
Finally, export at a generous bitrate — blocky compression artifacts inside the code are the invisible killer. The bitrate logic in the YouTube export settings guide applies to any H.264 delivery, signage included.
Test on a Real Phone Before You Publish
Not the PNG. The final exported video, on a screen, from a realistic distance:
- Play the export on the target screen, or the closest size you have.
- Stand where the audience will stand and scan with both an iPhone and an Android camera app.
- Check the worst case: screen at partial brightness, some glare, code on screen for its shortest duration.
- Screenshot the final rendered frame and run it through a free QR checker — it confirms the code still decodes after compression has had its say, and catches quiet-zone and contrast problems while there’s still time to fix them.
Ten minutes of testing is cheap. A trade-show loop with a code nobody could scan runs for three days.
FAQ
What’s the smallest a QR code can be on screen?
Work backward from viewing distance: distance ÷ 10 = minimum physical code width on the screen. For a viewer at arm’s length from a laptop, 10–12% of frame height is enough; for standing signage at 2 m, plan for 20–25% of a 1080p frame. When in doubt, bigger — nobody has ever failed to scan a code for being too large.
How long should a QR code stay on screen?
Eight to ten seconds minimum for a mid-video appearance, and 10–15 seconds for a dedicated end card. On unattended loops, keep a corner code up for the whole loop so late arrivals don’t wait for it to cycle back.
Can I put a QR code directly over moving footage?
Put a solid backing card behind it and position it over the calmest area of the frame. A code composited straight onto busy footage loses edge contrast every time the background shifts, and grain or glitch effects over the code region make it worse. Card, quiet zone, low-motion corner — then it’s reliable.
Why does my code scan from my monitor but not from the venue screen?
Usually distance: the venue screen is viewed from 3 m, not 60 cm, and the code is now far below the 10:1 size rule. The other suspects are heavier compression on the delivered file, a dimmer screen with glare, and cropping from TV overscan clipping the quiet zone. Test the actual export at the actual distance and the cause shows itself quickly.
