A QR code can stay on screen during a looping YouTube Live product demo and give viewers a direct route to the product page or another useful destination. Create the code for the page you intend viewers to visit, test it separately, add its image to your encoder layout, then check it in YouTube’s live preview before starting.
The important checks are practical: the code should remain visible without covering product details or controls, and it should be scannable on the kinds of screens your audience uses. No placement or image setting can guarantee that every viewer will be able to scan it, so inspect the finished stream rather than relying on how it looks in the encoder workspace.
Choose a destination that will still be useful
Decide what the viewer should see after scanning. For a product demonstration, that might be the product detail page, a page with specifications, a booking form, or a contact page. Make the destination specific enough to help someone who has just seen the demo, rather than sending every viewer to a general home page and expecting them to find the relevant item.
Open the destination on a phone before making the QR image. Check that it loads, that the product or offer shown matches the demonstration, and that the page is usable on a small screen. A desktop page that requires side-to-side scrolling or hides the key information below several banners may be a poor landing place for someone watching on a phone.
If the product is available only in a particular region, check the page from the audience’s likely location and explain any restriction in the stream or on the page. A QR code simply opens a destination; it does not make a product available, reserve stock, or explain changing terms. Keep claims in the video, the overlay, and the linked page consistent.
For a campaign or a short-lived offer, consider whether the address itself will remain valid after the stream ends. A printed or recorded QR image may continue circulating in clips or screenshots. Avoid a destination that will become an error page as soon as a temporary campaign is over, unless you have a plan to replace or redirect it. If you need to change the destination later, use a method that you understand and test the resulting page before returning to the live layout.
A looping video deserves the same care as a one-time presentation. If a product changes, a link expires, or the offer ends, the repeated demo can continue sending viewers to outdated information. Put the destination check on the same maintenance list as checking the video file and its product details.
Generate the image and test it independently
Once the destination is settled, use a QR generator or your own design workflow to create an image. Save or export the result in a format your encoder can display as a graphic. The exact controls differ between tools, so check the current documentation for the QR generator and encoder you use rather than assuming a particular menu or file option.
Before adding it to the stream, test the image on a separate device. Display the QR image on a screen, then use a phone camera or QR reader to scan it. Confirm that it opens the intended destination, not merely that the camera recognises a code. If you use a short link or redirect, test the final page after the redirect as well.
Repeat the check with the actual exported image, not only the generator’s preview. An image can be changed by resizing, cropping, compression, or placing it on a background. Test the version you will load into the encoder so you can catch a damaged or incomplete export before it becomes part of the broadcast.
Test from a reasonable viewing distance and with the phone and screen you expect viewers to use, where possible. A code that scans when enlarged on your monitor may be harder to use in the full stream. Check it at the size and position you plan to show in the video, and see whether a brief pause or a clearer product shot makes the code easier to capture. These are practical checks, not a promise that all screens, viewing conditions, or camera apps will behave alike.
Keep an unaltered copy of the working image. If you later change its position or size in the encoder, you can return to the original rather than repeatedly exporting a modified version. If you generate a replacement code because the destination changes, test the replacement independently too; a successful test of the previous image says nothing about the new one.
Add the QR image as an encoder overlay
YouTube supports encoder-based live streams for more advanced production, including layouts with graphics and overlays. The basic workflow is to add the QR image to the encoder’s scene or layout as a graphic layer, then position it over the product video. YouTube explains the encoder workflow in its guide to creating a live stream with an encoder.
The names and steps for adding an image vary by encoder and software version. Do not follow menu directions written for a different version without checking them. If you use OBS, consult the OBS Project Help Portal for current software guidance; for another encoder, use that product’s own documentation. The general task is to load the image as a visual source, place it in the intended scene, and confirm that it appears over the video rather than behind it or outside the visible canvas.
After adding the image, play or scrub through the loop and watch how the overlay sits at different moments. A placement that works during a close-up of packaging may cover a label when the camera view changes. If the video contains cuts, pans, or changing product angles, look at each of those portions rather than judging from one still frame.
For a product demo that repeats, make a deliberate decision about whether the code stays on screen continuously or appears only during a suitable part of the loop. A persistent image is easy to find but can distract from the item or cover changing details. A timed graphic can leave more of the product unobstructed, but viewers may miss it if they arrive at another point in the loop. Choose the behaviour that suits the material and confirm it repeats as intended.
If the encoder manages several scenes, profiles, or versions of a stream, make sure the QR image is included in the one actually used for the live broadcast. A correctly prepared graphic in an unused scene will not appear to viewers. A useful way to think about the workflow is to treat the final scene as a production asset, like the loop itself; this is also relevant when you are building a looping intro and outro for a channel.
Keep it clear of product details and controls
Place the code where it does not hide the feature being demonstrated, a product label, a price shown in the video, or any controls the viewer needs to understand. The best location depends on the footage: leave a clear area in one shot, then check that the same position remains clear when the camera angle changes. There is no universal corner that works for every demo.
Keep the graphic within the visible video area and away from edges where it could be clipped or obscured in a player. Watch the output as a viewer would see it, not just the encoder canvas. YouTube’s live streaming overview describes live formats and helps explain why checking the intended layout matters, particularly if you use more than one format.
A code that occupies too little of the frame may be difficult to scan; an overly prominent one can dominate the product shot. Adjust it while viewing the complete video frame, then test the actual on-screen result with a phone. Do not rely on a rule of thumb expressed as a fixed number of pixels or a contrast ratio: the display size, source video, playback window, and viewer distance all affect what is usable.
Also check the image against the background behind it. If it blends into a moving or detailed section of footage, a restrained solid panel or margin may help distinguish the code, provided it does not obscure the product. Ensure the code itself remains unaltered and visibly separated from nearby graphics. Then repeat the independent scan test on the rendered layout.
If you broadcast both horizontal and vertical versions, check each layout separately. A graphic that sits neatly beside a product in one crop may be cut off, moved into a detail, or reduced in apparent size in another. YouTube documents both horizontal and vertical live formats; do not assume the overlay will adapt automatically to every crop or scene. Check the layouts that you actually plan to use.
Connect the encoder to YouTube Live
In YouTube Studio, create or select the live stream and open the Live Control Room. YouTube’s encoder instructions explain how to connect using the stream URL and stream key supplied there. Enter those details in the encoder’s streaming configuration, taking care not to expose the stream key in a screenshot, recording, or public message. Treat it as a credential for your broadcast.
The encoder and YouTube Studio handle different parts of the job. The encoder produces the video layout, including the product footage and QR overlay. YouTube receives that outgoing stream and presents it in the live workflow. The overlay is not added by pasting the QR image into the YouTube description; it must be part of the video output from the encoder if you want it visible on screen.
Before a continuous broadcast, confirm that the loop itself repeats cleanly and that the encoder is connected to the intended stream. For practical background on the playback side, see how to loop pre-recorded videos on YouTube Live with FFmpeg. That is a distinct workflow from adding an image overlay, but it helps clarify that looping video and overlay placement are separate parts of the finished picture.
Connection and restart behaviour depend on the selected software and setup. If you are using an encoder that can reconnect automatically, test that behaviour rather than assuming the QR graphic will remain present after a reconnect or scene change. Guidance on reconnecting FFmpeg during a meditation stream covers a related continuity concern, but check the current documentation for the encoder and workflow you actually use.
Check the live preview before starting
Use YouTube Studio’s preview to inspect the incoming stream before you make it public. Confirm that the video is moving, the audio is as expected, and the QR overlay is present in the output. YouTube’s encoder settings and stream health guidance recommends testing with audio and video movement like the planned stream and monitoring stream health during the event.
Look at the preview at the size a viewer might use, not only in a large production window. Check the whole loop, including the moments when the product moves or the scene changes. If you will stream in multiple aspect ratios, inspect each relevant preview. A code may be visible in the encoder and still fall outside the final crop.
Then test scanning from the preview itself using a second device. This is a separate check from scanning the original exported image: the live output passes through the encoder and YouTube’s streaming path, and the viewer sees it inside a player on a screen. If it is difficult to capture, adjust the layout or footage and repeat the preview check. Do not start on the assumption that a successful scan of the source image proves the live version works.
You can ask someone else to view the preview on a phone they commonly use, especially if your own display and camera combination is unusually favourable. Ask whether they can identify the destination after scanning, too. A code that technically opens a page can still be confusing if the landing page is unexpected or hard to use.
Before going live, make one final pass for details that are easy to miss: the correct destination, the intended scene, no clipped edges, no hidden product feature, and a preview that matches the format you plan to broadcast. If a change is made after the test, preview and test that changed version again.
Keep the destination and loop in step
A 24/7 demo is not a one-off asset. When the video, product page, contact route, or offer changes, review the code and the landing page together. If a product is discontinued, a page is moved, or a seasonal offer ends, a viewer may still encounter the old loop in the meantime. Updating the video without updating the destination can leave the two telling different stories.
Keep a simple record of what the current QR image points to and which loop or scene uses it. This need not be a complex system; a filename or production note can prevent confusion when you return to the stream later. If someone else maintains the channel, make sure they can identify the current image and destination before replacing a scene or restoring an older project.
For ongoing streams, the computer or encoder used to prepare the layout may not be the same thing that keeps a channel running continuously. If you prefer not to leave your own computer operating, StreamNeo can take an uploaded video and run it as a YouTube live stream while your computer is off, which removes the need to keep that machine running for the broadcast; prepare and test the finished video and overlay before it is used. It is YouTube-only, so it is not a fit if your destination is another platform.
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
Can I add a QR code directly in YouTube Studio?
For an encoder-based stream, put the QR image into the encoder’s scene or layout so it is part of the video sent to YouTube. YouTube Studio is where you configure and preview the live stream, but the graphic needs to be present in the encoder output.
Should the QR code stay visible throughout the loop?
That depends on the footage and how viewers arrive at the stream. Keeping it present makes it available at different points, while showing it only during a suitable section can leave more of the product unobstructed. Preview the full loop and choose the approach that suits the demo.
How do I know whether viewers can scan it?
Test the exported image separately, then test the code in YouTube’s preview on a screen and phone similar to those your audience may use. If it is hard to scan, change the layout or its display in the video and test again. No test can guarantee success across all devices and viewing conditions.
Does one overlay work for horizontal and vertical streams?
Not necessarily. Different crops can move the image out of view or make it less useful, so inspect each format you intend to broadcast and adjust the layout if needed. Recheck the preview after any change.