For an encoder-based YouTube Live promotion, add the QR code as an image source in your streaming scene, layer it above the video, and check that viewers can scan it from the actual stream playback. The important test is not whether the code looks sharp in your editor; it is whether a phone can read it in the compressed picture viewers receive and open the right store page.
First choose the page the code should open, then make and place the image, and test it on a separate viewer device. YouTube Live does not provide a built-in QR overlay in this workflow: the code is part of your encoder scene, so its placement and readability are yours to verify.
Choose and test the promotion destination
Decide what a viewer should see after scanning before generating the code. It might be a particular product, a current offer, or the shop’s main page. Use the narrowest destination that fulfils the purpose: a code described as “this week’s offer” should not lead to a general page where the viewer has to search for the offer.
Open the address yourself on a phone, preferably using the same kind of connection your audience might have. Check that the page loads, the product or offer is still there, and the page works on a small screen. If the offer depends on a date, stock level, location, minimum spend, or other condition, read it as a viewer would. Make sure the on-screen wording does not imply terms the destination fails to show.
If you change the destination later, check whether your QR service makes a static code or offers a redirect you can update. A static code normally encodes its destination directly; changing the printed or overlaid image is then the straightforward way to change the destination. A managed redirect may let you change where it leads, but that introduces another service and another point to check. For a simple promotion, a static image is often enough. Do not choose a service merely because it promises tracking; decide whether you need that feature and understand what information it collects.
Keep the encoded address as simple as practical. Long addresses can produce a denser pattern, which may be harder to read when the code is displayed small or softened by video compression. Do not remove useful destination information just to shorten a link, and do not assume a short-looking code will scan at any size. The playback test settles that question for your layout.
A QR code is one route to the destination, not the only one. Put a short, readable offer or store address in the video description or another appropriate channel as a fallback. Viewers watching on a phone may find it awkward to scan a code displayed on that same phone; they may need another screen or a way to open the link separately. A code cannot remove that device constraint.
Create or download the QR image
Generate the code only after you have settled on the destination. Download it as a clean image file, such as PNG, with a dark code on a plain, light background. Avoid a patterned background, gradients through the code, decorative shapes over its centre, or a logo that masks part of the pattern. These treatments may look polished in a design preview but can make the camera’s job harder.
Keep a clear margin around the pattern rather than cropping tightly to its outer squares. The blank margin helps distinguish the code from nearby graphics. Leave it intact when you resize or crop the image. If the generator lets you choose a correction level or export dimensions, the settings may affect the image’s density and file appearance; they do not replace testing from stream playback.
Use a reliable generator or create the code with a tool you already trust. Check its terms and privacy practices if you enter a customer-specific or private link. For a public store destination, a basic static code is usually easier to maintain than a service account you might forget to renew. The QR image itself does not need to be animated: motion belongs in the promotion video, while a steady code gives the camera a stable target.
Save a copy of the final image alongside your promotion assets and give it a descriptive filename. Keep a note of the destination it encodes. This helps when you return to the scene weeks later and need to tell whether its image belongs to the current offer or an earlier one. Before broadcasting, scan the saved image directly as an initial check; that confirms the file encodes the page you intended, but it does not prove that the live overlay will be legible.
A guide from UseQR gives 200 by 200 pixels on a 1080p canvas as a rule of thumb for an overlay, not as a YouTube requirement or a guaranteed minimum. Treat any fixed size you encounter the same way: a code’s useful displayed size depends on its pattern, contrast, stream quality, screen, and viewing distance. Use a sensible starting point, then adjust based on a scan from actual playback rather than relying on one number.
Add it as an image source in the scene
This method applies to an encoder-based production, where you compose the picture in software such as OBS or in another encoder that supports image sources. In OBS, add the saved file through Sources → + → Image, then choose the image. OBS’s Sources Guide explains how sources are added, ordered, positioned and resized. The same principle applies in other software, though its menu names will differ.
The scene has a stacking order: sources higher in that order appear over sources beneath them. Put the QR image above the promotion video source and above any background it needs to cover. If it is underneath the video, it can exist in the scene list and still be invisible. Check the preview after adding it rather than assuming the source order is right.
If the promotion video is one element in a larger scene, choose whether the code should persist throughout the loop or appear only during a call to action. A persistent overlay is simple, but it can compete with the product throughout the video. A timed appearance can give the promotion room to breathe, but every relevant scene or segment must include the image at the intended time. If your loop switches scenes, verify each one; an overlay added to one scene will not necessarily appear in another.
After placing it, lock the image source if your software offers that control and you have finished positioning it. This is a convenience, not a technical requirement: it reduces the chance of nudging or resizing the code during later scene edits. Keep the image file in a location the encoder can still access when the broadcast starts; a broken file path can leave the source missing even though the scene worked during setup.
YouTube’s encoder guide describes software and hardware encoder workflows. A QR overlay does not itself require buying a dedicated physical device: the key requirement here is an encoder scene that supports layering an image. Choose your production method for the wider needs of your channel, not for a QR-code feature alone.
Position and size it above the video
Start with an area that is visually quiet and remains clear for the full period when the code is meant to be visible. A plain corner or a stable panel designed into the promotion may work better than a corner where captions, product details, channel branding, chat, or alerts appear. Watch the whole loop, not just one frame. An area that is empty at the start may be covered by a product shot or text later.
Use the encoder preview’s transform controls to move and resize the image. Keep its proportions square; stretching a square QR image into a rectangle distorts the modules and can undermine readability. Avoid cropping away the margin. If your scene has a border or label around the code, leave enough room that the code is visually distinct from it, rather than running the pattern right to the edge of other graphics.
Position it where it can be noticed without hiding what the promotion is about. A code placed over a product’s label, price, face, or essential demonstration defeats the purpose of a clear offer. If the composition is busy, revise the promotion video or create a calm space for the overlay rather than making the code larger until it covers important content.
Check placement at the output canvas’s intended aspect ratio and resolution. A code may look comfortable in a large editing preview yet take up too much of a smaller viewer’s picture, or become difficult to distinguish when the stream is reduced for a phone. YouTube transcodes live streams for viewing on different devices and networks; its encoder settings guidance is useful context for why the delivered picture can differ from the source preview. Your own viewer-side test is what tells you whether this particular overlay survived.
If your video loop contains several promotional messages, consider whether the same destination applies to all of them. One fixed code can confuse viewers if a later segment advertises a different product or offer. Either make the message and destination consistent throughout, or coordinate the code and wording with the segment where they appear. Review the transition points so a viewer is not left looking at an offer while the code has already changed—or vice versa.
Check readability without obscuring the promotion
Look at the scene both as a composition and as a sales message. Does the code stand apart from the footage? Does it cover a label, price, product detail, caption, or other information a viewer needs to understand the offer? Does a text prompt tell viewers what the code is for without suggesting a result you cannot guarantee? Keep the invitation factual: for example, “Scan to view the current offer” is clearer than an unqualified promise about savings or availability.
Contrast helps, but the area behind the code must remain consistent. If the video moves through bright and dark scenes, a transparent code image may be easy to read in one shot and lost in another. A plain, light backing behind a dark code can stabilise the contrast. That backing should not be confused with a YouTube standard; it is a practical design choice to test against the footage.
Check other overlay elements too. Captions and text should remain readable, and the code should not sit beneath a chat panel, alert, or other source that hides part of it. Where a platform or encoder layout adds labels around the video, inspect the final picture rather than only the source canvas. Leave space for any visual elements you know will be present in playback.
For a long-running channel, the promotion can outlast the offer. Write down who will replace the image or remove the overlay and when to do it. A stale code may still scan perfectly while leading to a promotion that has ended, so scanability alone does not make the message current. If the video loop is scheduled or reused, add the QR image and its destination to the same asset checklist as the video and audio.
When the overlay becomes difficult to scan, change one factor at a time: enlarge it, simplify the background behind it, increase contrast, or reduce nearby detail. Then recheck that it does not obscure the promotion. Increasing its size is not automatically the answer; an uncluttered, stable code that takes up less space can be more useful than a large code placed over the product.
Preview and scan from viewer playback
Connect the encoder to YouTube using the current stream settings for the intended broadcast. YouTube’s Live Control Room settings help covers the stream URL and key used in an encoder workflow. Use the Live Control Room preview before starting a public broadcast, and follow YouTube’s live streaming tips on previewing and testing the setup. A scene preview catches composition mistakes, but it is not proof that a viewer can scan the code.
For the meaningful test, watch the stream’s actual playback on a separate device. Put the stream on a phone or another screen at a realistic viewing distance, then use a second phone to scan the displayed code. Test the stream output, not a screenshot from your editing software and not the original QR image. This is the only way to include the effects of the complete video, encoder output, YouTube delivery and viewer screen in the check.
Scan more than once if the video is moving behind the overlay or if the code appears only for part of the loop. Try it during the quiet and busy sections, and after playback has settled at a typical viewing quality. Confirm that the scan opens the intended page, not merely that the camera recognises a pattern. Check the page again on the test phone so you know it loads and displays the right promotion there too.
If the code does not scan reliably, pause before going live and work through likely causes. Is it too small in the viewer’s picture? Does the background change behind it? Has compression softened the edges? Is the pattern crowded by nearby lettering or clipped at the margin? Adjust the scene or regenerate a simpler image as needed, then repeat the viewer-side test. Do not infer a universal minimum size from someone else’s successful setup; screen size, viewing distance, code complexity and stream conditions differ.
A loop may be played for hours, but viewers arrive at different points and may see only part of a call to action. Make the code visible for long enough to be useful, and ensure the offer prompt makes sense whenever it appears. There is no promise that a viewer will notice or scan it. Your job is to make a correct, legible route available and to check that it remains so in playback.
For a channel that needs the video to keep running while the operator’s own computer is switched off, StreamNeo can take away the job of keeping that computer on for the broadcast; prepare and test the composed video and QR overlay before relying on the continuous stream. It does not edit OBS scenes, and the QR setup and viewer-side scan test remain part of your production work.
Keep a short pre-broadcast record: the destination checked, the image version used, the scene where it is placed, and the device playback test completed. If you later replace the offer, update the code and repeat the test rather than assuming that a successful earlier broadcast verifies the new image. YouTube advises creators to preview and test before going live; its guidance is a useful routine, not a guarantee that every viewer’s connection or screen will behave the same way.
If the channel runs a changing playlist, make sure the overlay’s timing matches the content sequence; our guide to displaying different videos in a YouTube Live playlist covers the separate challenge of changing video without ending a stream. For a loop that runs across local audience schedules, the Indian Standard Time playlist scheduling guide can help with the broadcast plan. If you are comparing ways to keep a channel on air, the 24/7 YouTube stream setup with Restream and Lightsail versus EC2 for always-on streaming cover different operating choices; neither changes the need to test the QR in the viewer picture.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
Does YouTube Live have a built-in QR overlay?
No. For the encoder workflow described here, the QR code is an image source in the scene you compose before sending the stream to YouTube. YouTube’s encoder guidance explains how encoder streams are produced; OBS documents image sources and their ordering in a scene.
Is a QR image of a particular pixel size guaranteed to scan?
No YouTube-specific minimum QR overlay size is established in the cited guidance, and no single size guarantees a scan across screens and viewing distances. Treat published size suggestions as starting points, then test the code from actual playback on a separate device.
Can I test the code by scanning it in the encoder preview?
You can use the preview to check placement and visibility, but scan the actual viewer playback as well. That test includes the delivered picture and lets you confirm that the destination opens correctly on a phone.
Will adding the code guarantee scans or sales?
No. A clear code makes a route to the store available, but viewers may not notice it, may be watching on the same phone they would need to scan with, or may choose not to visit. Keep the destination current and do not treat scans or purchases as assured outcomes.