A dependable showroom stream from a spare PC depends on two separate things: the showroom media must keep playing, and the encoder must stay connected to YouTube. A looped video can address the first; stable power, enough PC capacity and upload bandwidth, and sensible monitoring support the second.
You can make a modest setup easier to recover and test, but no software setting guarantees uninterrupted service. Start with a simple scene and a realistic test, then decide whether a PC that needs attention is suitable for an unattended channel.
Treat playback and connection as separate jobs
A showroom feed might be a recorded product demonstration, a set of display slides, or a live camera pointed at a shop floor. These are different playout choices, but each needs a source that continues to provide video and audio to an encoder. If the source ends or freezes, the encoder may still be connected while sending the wrong picture, a still frame, or silence.
The other failure point is the connection from the encoder to YouTube. Your media can continue playing locally even if the internet connection drops; conversely, a healthy connection cannot fix a video that has stopped advancing. Think of the path as two checks: is the intended content moving at the source, and is the encoded feed arriving at YouTube with acceptable stream health?
This distinction makes troubleshooting clearer. If the YouTube preview shows a frozen image but the encoder remains connected, inspect the source and scene. If the local preview plays but YouTube reports connection trouble, look at upload stability, encoding load, and reconnect behaviour. Do not treat one green indicator as proof that every part is working.
For a prerecorded showroom presentation, a video loop is often simpler than leaving a camera or browser display running. A live camera or changing stock display may be necessary where the information must be current, but then you must also keep that source powered and available. Choose the source according to what viewers need to see, rather than assuming that “always on” means the same thing as “always current”.
Create the encoder stream in YouTube
In YouTube Live Control Room, create or schedule an encoder stream and enter its title, visibility and other metadata. YouTube provides the server URL and stream key that the encoder needs to send the feed. The key is a credential, not a public channel detail: keep it out of screenshots and shared documents, and reset it if you think someone else has access. See YouTube’s encoder setup guidance for the current workflow.
In OBS, select the service and enter the stream key using the connection details supplied by YouTube. Avoid putting the key in a public scene, chat message, or support request. If you change or reset it in YouTube, update the encoder before the next test; an old key can prevent a correctly configured PC from connecting.
Set the privacy and metadata deliberately. A private test can help you inspect the feed before a public showroom broadcast, but check the actual visibility setting again before the intended audience is meant to find it. If you schedule a stream, confirm that the scheduled event and the encoder output refer to the same broadcast rather than relying on memory from an earlier test.
The stream key identifies where the encoder sends its feed; it does not start the video source or keep the PC awake. That is why it is useful to finish YouTube configuration separately, then test the scene and connection together. For a broader walkthrough of a playlist-based channel, see how to set up a continuous YouTube radio stream with a playlist.
Choose a playout source that can loop
For a single prerecorded demonstration, create a simple OBS scene and add the file as a Media Source. Enable its Loop option, then watch it reach the end and begin again. Check the transition: a brief black frame or an audio pop may be acceptable for a store display, but it may look like a fault if it interrupts an important product detail or spoken explanation.
If the showroom needs several clips in sequence, a playlist source can be more suitable than manually swapping files. OBS documents a VLC Video source that can play a playlist and has Loop Playlist enabled by default; VLC must be installed, and the OBS and VLC architectures need to match. Refer to the OBS media sources guide before choosing that route. Test every item in the list, including the last-to-first transition, rather than assuming a working first clip proves the whole sequence is sound.
Use a local copy of the media where practical. If the file is on a removable drive or a network share, the source can disappear when that location disconnects or changes. Keep the file path stable and make a backup copy. If the video contains a voiceover, music or ambient sound, listen to the stream output rather than just the PC speakers; duplicated audio sources can create an echo, and a muted audio track can leave an otherwise polished feed silent.
A still image with a live camera inset, a playlist of demonstrations, and a single looping video all have different maintenance costs. A camera can show real-time activity but depends on camera power, framing and lighting. A looped presentation is easier to reproduce, but it can become stale. If you need to rotate content later, plan a controlled edit and test it before changing the live scene; the guide to adding videos to an always-on YouTube stream covers that separate workflow.
Check the spare PC and its power
A spare PC is not automatically capable of a long-running encode just because it opens OBS. Encoding demand depends on the output resolution, frame rate, encoder, scene complexity and the machine’s available CPU or GPU capacity. OBS notes that meeting basic operating-system or graphics compatibility requirements does not guarantee that a particular workload will perform adequately. A simple scene with one video source is a more sensible starting point than multiple animated overlays, browser sources and filters.
Before going live, run OBS with the exact scene and output you intend to use. Watch for rendering or encoding overload messages, stuttering in the local preview, unusually high system load, and unexpected fan or temperature behaviour. If the PC struggles, reduce the output demand and test again instead of hoping that the problem disappears after the broadcast has been running for hours.
Power is its own readiness issue. Check the power cable, socket, charger or power supply, and whether a brief local power interruption would shut the machine down. A battery-backed supply can be considered where short power cuts are common, but it is not a substitute for a stable electrical supply or a tested recovery plan. There is no universal sleep, update or firmware setting to prescribe for an unspecified PC: the right controls depend on the operating system, hardware and how the machine is used.
On the actual spare PC, review the current operating-system and manufacturer guidance for sleep behaviour, restart prompts and power recovery. Test changes while you can observe the device. Do not disable updates indiscriminately or assume that one setting prevents every restart. A small written note of which account runs OBS, where the media file lives and how to restart the broadcast is more useful to someone covering the channel than an undocumented collection of tweaks.
Software encoding on a spare PC is practical when you can test and maintain that machine. A dedicated hardware encoder may suit a setup where a PC is unavailable or a simpler appliance-style workflow is preferred, but it brings its own configuration and monitoring needs. Neither category removes the need to test the source, power and network as a complete path.
Match the stream to the upload connection
Measure the upload connection where the PC will actually sit and at the times the showroom is likely to stream. A speed test taken elsewhere or during a quiet period is only a snapshot. Wi-Fi can work, but if Ethernet is practical it removes one wireless link from the path; it does not fix a weak broadband service, a congested router or an unstable connection upstream.
YouTube recommends leaving 20% upload-bandwidth headroom beyond the total stream bitrate, and says to account for both primary and backup bitrate if you configure both. Treat that as planning guidance, not a guarantee that the connection will remain stable. YouTube also warns that connectivity disruptions can break a stream. Read its streaming tips and test the real feed on the intended connection.
Choose an output that both the PC and connection can sustain. YouTube’s encoder guidance covers supported formats and settings, including H.264, H.265 and AV1 options, CBR, and a recommended two-second keyframe interval; it says not to exceed four seconds. Its bitrate guidance is a starting point rather than a promise for every scene or network. Check the current YouTube encoder settings and bitrate guidance, then test the selected resolution and frame rate in practice.
A simple, relatively static product display may be easier to encode than fast camera movement or a scene full of animated overlays, but do not infer a specific bitrate from that alone. The chosen output still needs to look clear enough for product labels and detail while remaining within the capacity of the PC and upload. If it stutters, change one factor at a time and repeat the test so you know whether the improvement came from a lower output, a simpler scene or a more stable network.
If bitrate choices are unfamiliar, use a tested starting configuration rather than trying to maximise quality on the first attempt. The OBS bitrate guide for YouTube Live can help you understand that setting in context. Keep a note of the working output and connection conditions; a setting that holds on one network should not be assumed to hold after moving the PC or changing the scene.
Plan reconnection and recovery
OBS includes an automatic reconnect setting intended to help after some connection interruptions. Review it in the version of OBS you are using, and test what happens when the connection is briefly interrupted in a controlled way. Reconnection can help the encoder recover, but it cannot make an unavailable internet connection work or guarantee that viewers experience no interruption.
OBS’s connection troubleshooting guidance treats dropped frames and intermittent disconnections as signs to investigate network stability or a bitrate the connection cannot sustain. Check both the encoder’s messages and YouTube’s stream health rather than repeatedly restarting without identifying the symptom. The OBS stream connection troubleshooting guide is a useful reference when the local output and remote status disagree.
Decide what you will do when the stream needs attention. For a small shop, that might mean a named person checks the live preview and knows how to restart OBS and the event. For a channel that must continue outside staffed hours, consider whether relying on an unattended spare PC fits the consequences of a failure. A cloud service that turns an uploaded video into a YouTube live stream can remove the need to leave that PC running for a prerecorded loop; StreamNeo is one such option when the specific burden is keeping the local computer on and available.
That does not remove the need to check the YouTube event, content rights, audio, stream health or channel settings. It also does not change the fact that a prerecorded loop is not a live view of current showroom conditions. Choose the operating method around the promise you are making to viewers, and keep a recovery procedure even when some tasks are automated.
Test the whole setup and monitor health
Do a realistic test with the same media, scene, audio, encoder settings and network intended for the showroom. OBS recommends testing settings before the first stream. YouTube’s guidance recommends configuring encoders well ahead of an event and starting before it so you can check the preview. For a scheduled opening or promotion, use that time to confirm the right event is receiving the signal, not merely that OBS says it is streaming.
Inspect the Live Control Room preview and stream-health messages, then open the watch page from a separate device or browser session. Confirm that a viewer sees the intended picture and hears the intended audio. If you need a local archive, check that recording or archiving is planned separately; do not assume the online broadcast is also being saved on the PC.
YouTube says streams under 12 hours are automatically archived. If an archive matters, do not assume a longer session will be saved. Plan a deliberate session and archive workflow, and verify the current YouTube guidance before relying on a recording. This is one reason to weigh a single long broadcast against planned shorter sessions: shorter sessions may make archive handling more predictable, while each restart creates another point to test and schedule.
During operation, watch both ends when possible: OBS for source or encoding problems, and YouTube for incoming stream health. A periodic check can reveal a frozen source, muted audio or disconnection before someone reports it, but checks are not continuous protection. Keep contact details or steps available to whoever will respond, and record what the stream looked like when a problem began. That makes it easier to distinguish a recurring network drop from a file or scene issue.
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 loop a video on YouTube Live?
YouTube receives an encoder feed; the loop is made in the playout software. In OBS, add the video as a Media Source and enable Loop, then test the end-to-start transition and audio. A playlist can use an appropriate playlist source, but test every clip in order.
Can a spare PC run a showroom stream all day?
It may, if its encoding workload, power, source file and upload connection hold up under a realistic test. Basic compatibility does not establish that the PC can sustain your chosen output indefinitely. Review the machine-specific power guidance and arrange a way to notice and respond to faults.
Will automatic reconnect prevent interruptions?
No. OBS reconnect can help recover from some dropped connections, but it cannot restore a failed internet service or fix a source that has stopped playing. Monitor YouTube stream health and test recovery behaviour before relying on it.
Should I use one long stream or several shorter sessions?
That depends partly on whether you need a YouTube archive and how you can staff or monitor restarts. YouTube says streams under 12 hours are automatically archived, so plan separately if a longer session must be saved. Check the current official guidance and verify your own archive workflow before depending on it.