To show a QR code over a prerecorded property tour on YouTube Live, compose the tour and code together in OBS, then send that scene to a scheduled YouTube event using an encoder. The important test is not whether the code looks tidy on your OBS canvas; it is whether it remains visible and opens the right destination in YouTube’s composed preview and on representative phones.
Use a static image for a QR code that points to a fixed listing or information page. A browser overlay can suit a code whose destination may change, but whichever method you choose, check the actual encoded output before the public event. A code that is cropped, obscured, too small on a phone, or difficult to distinguish from the footage is not useful to viewers.
Prepare the tour video and QR destination
Start by deciding exactly what a viewer should reach after scanning. That might be a property listing, a page with floor plans and viewing arrangements, or a contact form. Open the destination on a phone and check that it loads without requiring an unexpected login. Confirm the address carefully before generating the code: a QR code faithfully points wherever its encoded data says, including a typo or an outdated page.
Generate or export the QR as an image file if the destination is fixed. Keep a clean version of the code, with its surrounding margin intact; avoid cropping tightly around the dark modules. If you need to change the destination after the stream is set up, a managed redirect or browser-based overlay may allow that, but it adds a dependency worth testing. A QR generator is not a YouTube feature, and YouTube does not verify that your destination is correct.
Prepare the tour file as a separate asset. Watch enough of it to know where the important identifying details appear: an address card, a room label, a close-up of a feature, or a spoken explanation. Those details affect where the code can sit without covering useful content. If the video contains music, identifiable people, or material supplied by someone else, confirm you have permission to use it in the live broadcast. YouTube’s livestream terms and conditions put responsibility for rights and compliance on the content provider; check the current terms for your situation.
Write down the event’s intended title and destination before building the scene. If the QR is meant to lead to the exact property shown, test that relationship too: a working link to the wrong listing is still a failure. For a test stream, use an unlisted event if suitable for your workflow, and use a test destination you control rather than inviting viewers to scan a live listing by mistake.
Add the tour as an OBS Media Source
In OBS, create a scene for the property tour. Add the prerecorded file as a Media Source and select the file on your computer. OBS documents media, image and browser sources in its Sources Guide. Source names that describe their job—such as “Tour video” and “Listing QR”—make it easier to check the scene later.
Set the source to play the file you intend to broadcast, then test playback from the beginning. Confirm that picture and audio behave as expected, and look for a black frame, an unintended pause, or an end-of-file state that would make the scene unsuitable. If the event is a single showing, a file ending may be acceptable; for a continuing loop, plan and test how the tour should repeat rather than assuming it will resume in the way you want.
Match the scene canvas to the intended stream layout and inspect the full frame. A tour recorded in one aspect ratio may not fill a different canvas cleanly. Avoid stretching it just to fill space: that can distort rooms and furnishings. If you use a fit or crop, check that doorways, windows, captions and other useful visual cues remain in frame. This is also a good point to check that the property is identifiable without exposing details you did not mean to show.
The OBS canvas is an editing view, not the final proof of what a viewer receives. It helps you arrange sources, but YouTube’s incoming feed and the versions delivered to viewers may differ in visible detail. Keep that distinction in mind throughout setup, particularly when judging the QR’s size and legibility.
Add the QR as an Image or Browser Source
For a stable destination, add the exported QR image as an Image Source. Keep the original image file somewhere OBS can continue to access it, and verify that the source is visible after saving and reopening the scene. If the file is moved or renamed, the source may no longer display the image you expect.
A Browser Source is another route when the QR is presented by a webpage or overlay that you need to update. Use the intended page address, then check the source in the scene rather than assuming the browser layer loaded correctly. A missing page, a loading indicator, a changed layout or an expired destination can all turn the intended code into a blank or unsuitable overlay. Browser-based content depends on the page being available and rendering properly during the broadcast, so test it in advance and again in the composed preview.
| Approach | Works well when | Main thing to test |
|---|---|---|
| Image Source | The destination is fixed and you want a straightforward overlay | The image stays available, clear and correctly positioned |
| Browser Source | The overlay or destination needs to be changed without replacing an image | The page loads and renders correctly in the scene and preview |
| Timed transparent video layer | The code should appear at planned points in the tour | Timing, transparency and visibility over each relevant shot |
A timed transparent video overlay may be useful if the code should appear only during selected parts of the tour, but it is a separate layer that must be prepared and checked just like the tour itself. Do not assume a downloaded overlay or third-party service will work with your particular scene without testing it. A persistent image is usually easier when viewers may join at any point and need time to scan.
The trade-off is between simplicity and changeability. A static image avoids a live webpage dependency but requires you to replace the file if the destination changes. A browser overlay can support changes, depending on how it is set up, but introduces another page and rendering state to verify. Neither approach establishes that viewers will successfully scan the code; that depends on the composed picture and viewing conditions.
Layer the QR above the video
In OBS’s Sources list, place the QR source above the tour Media Source. OBS draws higher sources in front of lower ones, so the image or browser layer needs to be higher in the list to appear over the footage. If you cannot see the QR, check that it is visible and not hidden behind the video source before changing its size or position.
Move the QR to a relatively stable area of the frame where it avoids important property details and any on-screen captions. Resize it using the source’s handles, then inspect a range of shots rather than a single attractive frame. A pale wall may provide contrast in one room, while a bright window or moving camera shot may make the same code blend into the scene. If necessary, use a simple contrasting backing as part of the graphic, but keep the code’s clear border intact.
Do not rely on a universal pixel dimension or viewing distance. The research and official guidance do not establish a size that guarantees scanning on every television, laptop or phone. A code that looks generous on a desktop canvas can become a small patch when the video is viewed in a mobile player. Use a size that is visibly legible in the actual preview, then test it from the phones and playback sizes your likely viewers use.
If the code covers a room feature, consider shifting it to another corner or showing it at planned intervals. A persistent code gives a viewer who joins late a chance to scan, but it can also obscure footage throughout the tour. A timed code can preserve the image in other moments, but a viewer may miss the appearance. Decide which matters more for this event, and test the chosen arrangement across the complete sequence.
For longer-running channels, playback behaviour and recovery matter alongside the overlay. If you are adapting a setup for a continuing stream, the guide to keeping a YouTube stream playing when an OBS video playlist ends covers a related failure point. For this property event, though, first make sure the tour and code compose correctly in the single scene you intend to send.
Connect OBS to the scheduled YouTube stream
Create or schedule the event in YouTube Studio, and check that the channel can use live streaming. YouTube says first-time activation may take up to 24 hours, so do not leave that first check until the event is about to begin. Its encoder setup instructions explain how to create a stream and connect an encoder.
Copy the event’s stream URL and stream key into the appropriate OBS streaming settings. Treat the key as a credential: YouTube describes it as functioning like the stream’s password and address. Do not put it in a public document, screenshot or message. If you think it has been exposed, reset it in YouTube Studio. If an OBS update or settings change makes the key disappear, the steps in restoring a YouTube stream key in OBS may help you identify what to check.
Before sending the feed, confirm the selected event in YouTube and OBS are the same one. A correct scene sent to the wrong event can waste the test or confuse viewers. Check the title, privacy setting and scheduled time in Studio, then verify the encoder is configured to use that event’s connection details. Keep a record of the event’s intended destination and schedule separate from the secret stream key.
YouTube recommends setting up an encoder well ahead of a broadcast, starting it before the event, and checking the Live Control Room preview. Follow its current live streaming tips, because platform guidance can change. Once OBS is sending, wait for YouTube to receive the feed and inspect the preview before making the event public or starting the event for viewers.
Test the preview and scan from phones
Start OBS’s encoder output early enough to let YouTube receive and process the scene. In Live Control Room, inspect the preview as a viewer would: is the QR visible in the encoded composition, is it still present when the tour moves to another room, and does anything cover it? Check the picture at the start, middle and end of the material rather than relying on the first frame.
Then scan from a phone using the YouTube preview or an unlisted test stream, not merely from the OBS canvas. Scanning the source image on a computer only proves that the original file contains a valid code. It does not test whether the encoded output preserves enough visible detail, whether the phone can focus on a screen, or whether the destination opens correctly from the displayed feed.
Use more than one representative phone and screen size where practical. Try the device you use for production and another common viewing setup, such as a phone with a different display size. View the stream at the size a viewer is likely to use, not only full-screen on a large monitor. Check that interface elements do not cover the code, and that it remains distinguishable against footage with different colours and motion. There is no evidence-based universal size or scan-success promise for all screens, so the test needs to reflect your actual output and audience conditions.
After each scan, confirm the destination is the intended listing or information page and that it loads on mobile data or the relevant viewer connection. If it fails, work through the chain: verify the destination itself, inspect the source in OBS, confirm the layer order and visibility, then review the YouTube preview and phone scan again. Change one thing at a time where possible so you can tell which adjustment helped.
YouTube also recommends checking representative audio and video and monitoring stream health. Listen for narration that is too quiet, missing audio or an abrupt end, and watch for warnings in the control room. A QR test is only one part of readiness; a clean code over frozen or silent footage is not a successful property tour. For a broader view of the ongoing checks used in always-on broadcasts, see how to monitor a 24/7 YouTube Live stream automatically.
Go live and monitor the event
When the preview and phone scans pass, start the event using the YouTube and encoder controls required by your workflow. Keep the tour playing correctly and continue watching Live Control Room for stream health or a change in the received picture. If the file stops, the overlay disappears or the event loses its feed, viewers may see a different result from the one you tested.
Have a simple response ready: know who can check the OBS scene, who can verify the listing page, and where the stream key is stored securely. Avoid changing several sources or event settings at once while viewers are watching. If a QR destination has to change during the event, first confirm that the replacement page works and that the updated code is visible in the actual feed.
End the stream using the controls appropriate to the event, then check that the event has ended as intended. YouTube says streams under 12 hours are automatically archived; consult the current platform guidance for the details that apply to your event. If the tour will be reused, retain the tested scene and asset locations, but review the listing URL and permissions before the next broadcast. A property listing can change even when the video file does not.
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 put a QR code over a prerecorded video on YouTube Live?
Yes. Use an encoder workflow such as OBS: add the prerecorded tour as a Media Source, add the QR as an Image or Browser Source, and put the QR layer above the video. Check the composed feed in Live Control Room and test it on phones before the public event.
Should I use an image or a browser overlay?
An image is straightforward when the destination is fixed and the code does not need to change. A browser overlay can suit a destination or presentation that needs updates, but you must test that the page loads and renders correctly in OBS and the YouTube preview. Neither method guarantees that every viewer can scan the code.
Why does the QR scan from my computer but not from a phone?
The original image may be valid while the composed or encoded picture is too small, obscured, low in contrast or difficult to focus on from a screen. Test the actual YouTube preview or an unlisted stream at representative phone sizes, then adjust the scene and try again.
Do I need to check rights for the property tour?
Yes. Confirm you have the necessary rights or permissions for the footage, music, people shown and any third-party material. Review YouTube’s current livestream terms and applicable requirements for your circumstances; a QR overlay does not change those responsibilities.