OBS can send a live property tour to YouTube continuously, provided your camera, computer and upload connection can sustain the broadcast. You still need to create or select the YouTube live event, check the incoming preview and press Go Live in YouTube Live Control Room.
The right setup depends on whether you are moving through a property with a camera, showing one fixed view, or looping prerecorded tour footage. A stream under 12 hours can be automatically archived by YouTube, but a longer run needs a local recording and a manual upload plan if you want a reliable replay.
Start with the property-tour source
Before opening OBS, decide what is actually producing the picture. A moving camera tour, a fixed camera and a prerecorded video are not interchangeable sources. Each has different risks, scene requirements and monitoring needs.
| Tour source | OBS approach | Main risk to test |
|---|---|---|
| Moving camera or phone feed | Capture the camera or feed as a video source, with a microphone or separate audio input | Wireless dropouts, motion blur, changing audio levels and accidental framing |
| Fixed camera | Add a webcam or capture device to a simple scene | Static focus, room noise, overheating and a view that becomes unhelpful over time |
| Prerecorded tour footage | Add the media file and decide whether it should stop, restart or move to another file | The file ending, visible loop points, silence and copyright or permission issues |
For a moving walk-through, keep the route simple enough that the operator can watch the camera and the stream. A gimbal or stabilised camera may make the result easier to watch, but it does not solve upload instability. If the camera is connected over Wi-Fi, test the exact route rather than testing only beside the router.
A fixed view can work for an entrance, showroom, construction site or furnished room, but it needs a reason for viewers to stay. Use a title card, timetable, contact method or changing information only when it is genuinely useful. A property tour that shows an empty room for hours without context may be technically live but not useful to the viewer.
For prerecorded footage, check that you have permission to use the video, music, voices and any visible people or property details in both the live broadcast and the replay. Google’s full live production guidance says producers should obtain the necessary clearances for live, rebroadcast and on-demand audio and video. Local property, privacy, advertising and access rules may also apply, so check the current requirements for the location rather than assuming that a live broadcast changes them.
If your source is a prepared video rather than a camera, first make sure the file itself is suitable for a long broadcast. The guide on preparing video files for a 24/7 YouTube loop stream covers a different source pattern, but its file-checking discipline is useful here: inspect the beginning, end, audio and visible transitions before asking OBS to play it unattended.
Build OBS scenes and sources
Install OBS Studio on the computer that will encode the broadcast, then create scenes around what the viewer should see when the tour changes state. Do not build one complicated scene and hope it will cover every interruption.
A practical starting set is:
- Tour: the moving camera, fixed camera or current media source.
- Opening card: property name, location, viewing instructions and any necessary notice.
- Holding scene: a still image or short suitable clip for a camera change, break or temporary loss of the main source.
- Contact or schedule: a restrained panel with the next viewing time or a contact route, if relevant.
Add the sources inside each scene and arrange them in the preview until the important parts of the room are visible. A wide room may look acceptable in OBS but lose doors, windows or text when viewed on a phone. Check the preview at the same aspect ratio that you intend to publish.
For a fixed webcam, select the device as a video capture source and confirm its resolution and frame rate. For a camera with HDMI output, you will generally need a capture device between the camera and the computer. Do not assume that a camera output is available to other applications simply because the camera has a screen.
For prerecorded footage, add the media source and inspect its playback behaviour. Decide whether it should restart when it ends and whether OBS should move to a holding scene between files. If you use several files, name them clearly and test the transition in sequence. A black frame, a desktop view or an OBS error message can become public if it is not covered by a deliberate scene.
Keep text large enough for a phone and away from the edges. Property footage often contains fine detail, so avoid covering room features with a large permanent banner. If you plan to offer both horizontal and vertical viewing, design the layouts before the broadcast. YouTube documents horizontal and vertical live formats, but the vertical format cannot be added after the stream has begun. A wide room tour may need a separate crop rather than simply squeezing the horizontal view into a tall frame.
OBS is responsible for preparing and sending the encoder feed. It does not make the YouTube event public by itself, and it does not replace a person checking the broadcast. Save a copy of the OBS profile and scene collection once the test setup works, so a later change can be reversed.
Choose a bitrate your connection can sustain
Bitrate is the amount of video data OBS sends each second. A higher value can preserve more detail in walls, foliage and room movement, but it also requires more stable upload capacity. The sustainable setting is more important than selecting a resolution that the connection cannot carry all night.
YouTube’s current encoder guidance lists these H.264 recommendations:
| Output | YouTube recommended video bitrate | Practical use |
|---|---|---|
| 720p at 30 fps | 6 Mbps | A sensible starting point for a limited or variable connection |
| 1080p at 30 fps | 10 Mbps | More detail for a stable connection and a tour with useful room texture |
| 1080p at 60 fps | 12 Mbps | Smoother movement, but more data and more encoder work |
These are platform recommendations, not a promise that your particular computer or connection will deliver them. YouTube also recommends constant bitrate, a two-second keyframe interval and compatible audio and video settings. Its encoder settings and bitrate page should be checked again before a long production because platform guidance can change.
Run a speed test at the location and at the time you expect to broadcast. A result from a quiet afternoon may not describe the connection during the evening. Leave headroom rather than setting the video bitrate equal to the entire measured upload capacity. Other devices, cloud backups, software updates and short network variations still need somewhere to go.
If the connection is limited, reduce the output before trying to force a higher bitrate. A stable 720p feed is usually more useful than a 1080p feed that drops frames or becomes unavailable. You can also consider 30 frames per second rather than 60 when the tour does not require very smooth movement. This reduces the amount of data and processing without changing the basic viewing plan.
Audio needs its own check. Room tours can contain speech, footsteps, traffic and air-conditioning noise. Set the microphone so normal speech is clear without clipping, then listen on headphones and on a separate phone. A quiet image with unintelligible instructions is still a failed tour.
For more detail on choosing a stable setting on a restricted connection, use the OBS settings for YouTube Live with limited upload speed in India. The relevant setting for your property is the one that survives a representative test, not the one with the largest number in the output menu.
Test movement, audio and stream health
Test the complete chain before making the event public. This means the actual camera, cable or wireless route, microphone, OBS profile, YouTube event and viewer device. A short test that uses a still image cannot tell you whether a moving tour will remain watchable.
Walk the route at the pace you expect during the broadcast. Turn towards windows, dark rooms and reflective surfaces. Watch for autofocus hunting, exposure changes and motion blur. If the operator will speak while walking, test speech at the distance and direction used in the tour rather than speaking directly into the microphone at a desk.
Start OBS and send the feed to a test or unlisted YouTube event. Open the preview on a separate phone or computer using a different connection if possible. Check the full picture, sound delay, captions or text, camera orientation and whether the video remains understandable when the viewer is not sitting beside the encoder.
Watch OBS for dropped frames and connection warnings. YouTube also displays stream health information in Live Control Room. YouTube’s encoder guidance says to test with audio and movement similar to the real broadcast and to monitor stream health while live. Its live encoder troubleshooting guidance is useful when the preview is delayed, the connection is unstable or the encoder cannot maintain the configured output.
Test interruptions deliberately. Disconnect and reconnect the camera if the production plan allows it, switch scenes, pause the media source and restore the network connection. The goal is not to prove that nothing can fail. The goal is to learn what the viewer sees when a source fails and what the operator must do next.
A yellow or red connection indicator, rising dropped frames or repeated buffering should be treated as a production problem rather than ignored. Lower the bitrate, simplify the scene or resolve the network issue before a public run. The reconnect behaviour guide explains why a reconnect plan matters for a long-running feed.
Connect OBS to YouTube Live Control Room
Create or schedule the live event in YouTube Studio. Set the title, description, privacy and other event details there, then copy the stream key for that event into OBS. Treat the key like a password and do not put it in a public screenshot or document.
In OBS, open the stream settings, choose YouTube or the appropriate custom service, select the recommended server option where available, and paste the matching key. Check every character before saving. A key for one event may not be the key you intended to use for another event.
Start streaming from OBS first. This sends the encoder feed to YouTube but does not necessarily make the broadcast public. Return to Live Control Room and wait for the preview to appear. Confirm that the image, audio and title are correct, then press Go Live in YouTube when you are ready for viewers to receive the event.
This distinction matters when a property owner or colleague is reviewing the feed. They can inspect an unlisted or otherwise controlled event before publication, while the encoder is already sending the signal. YouTube’s live streaming setup instructions describe the event and encoder steps, but use the current Live Control Room labels because the interface may change.
If you schedule the event, allow time for the preview check before the advertised start. Do not publish a holding screen containing unfinished notes, a private phone number or internal instructions. Keep the description accurate about whether the feed is live, prerecorded, or a mixture of both.
Start and monitor the continuous feed
Once you press Go Live, assign a person to watch the broadcast. That person does not need to stare at the screen without interruption, but they should have a schedule for checking the image, sound, connection status, camera position and source playback.
For a moving tour, monitor the operator’s battery, route and communication method. For a fixed camera, check focus, lighting and whether something has moved into the frame. For prerecorded material, check that the file has not ended and that a loop or transition has not exposed the desktop.
Keep a written response plan beside the computer. It can be short:
- Check whether OBS is still sending frames.
- Check the source, microphone and scene in OBS.
- Check stream health in YouTube Live Control Room.
- Switch to the holding scene if the main view is unusable.
- Lower the bitrate or stop the broadcast if the connection cannot recover.
- Record what happened before restarting the event.
Do not promise viewers that a stream will remain live simply because OBS is open. Power loss, operating-system updates, hardware faults, local network changes and service interruptions can all stop a broadcast. A manual check and a recovery procedure are part of the setup.
If chat is enabled, moderate it as a separate responsibility. A property tour can reveal a location, a room layout or people in the background, so do not let the desire to keep the feed running override a privacy concern. If an owner or occupant asks for a scene to be removed, use the holding scene while you decide what to do.
For a cloud-hosted workflow, StreamNeo removes the need to leave the tour computer running by taking an uploaded video and sending it to YouTube after you provide the stream key, with automatic monitoring and restart handling when the feed drops. It is relevant to prerecorded tours rather than a live moving camera, and you should still check the resulting YouTube broadcast and the content permissions yourself.
Plan recording and streams over 12 hours
A continuous broadcast and a continuous archive are separate requirements. Google’s production guide says streams under 12 hours are automatically archived. It also advises that streams longer than 12 hours should be recorded by the production team for manual upload. Do not assume that YouTube will preserve one unlimited replay of a long-running event.
If the tour will run for more than 12 hours, enable local recording in OBS and confirm where the files will be saved. Check that the storage drive has room for the planned recording, that the folder is not synchronised in a way that interrupts writing, and that the computer will not sleep. A recording is only useful if it completes and can be opened afterwards.
Use a recording format and workflow you understand before the public run. Test a short recording, close OBS normally and open the file in a separate player. Check the picture, sound and file length. If a long recording becomes corrupted or is difficult to edit, a manual upload may not be a practical archive plan.
Plan the handoff before the 12-hour point. You might end the event, save the local file, create a new event and begin again, or continue the live feed while keeping a separate local record for later editing. The right choice depends on whether viewers need one uninterrupted URL, whether a replay must cover the whole tour and whether a person is available to manage the change.
If you stop and restart, explain the change in the description or holding scene so viewers do not mistake the new event for a fault. Keep the old event available only as long as its privacy and property details remain appropriate. When uploading the local recording, check the title, thumbnail, description, music and visible personal information again rather than treating the recording as automatically cleared.
Long broadcasts also need a storage and naming convention. Include the property identifier, date and segment number in each filename, but avoid putting private access details in filenames that might later be shared. Keep a simple log of the event URL, start time, stop time, interruptions and the final recording location.
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
How do I keep a YouTube property tour live all day?
Use OBS to send the camera or prerecorded source to a YouTube live event, then monitor the source, connection and stream health during the day. An all-day run still needs a recovery plan for power, network, camera and software failures.
Does OBS automatically make a YouTube stream public?
No. OBS sends the encoder feed to YouTube, but you normally need to open Live Control Room, wait for the preview and press Go Live. The event’s privacy and publication settings are controlled in YouTube.
Will YouTube save a 24/7 livestream?
Do not rely on one automatic replay for a broadcast longer than 12 hours. For that type of run, record locally and plan a manual upload or a deliberate sequence of shorter events, following the current YouTube guidance.
Should a property tour use 1080p at 60 fps?
Only if the camera, computer and upload connection can sustain it during representative movement and audio. YouTube lists 12 Mbps as its recommended H.264 video bitrate for 1080p at 60 fps, but a stable 720p or 1080p30 stream is preferable to a higher setting that drops frames.