A spare PC can run a nonstop sermon stream if it can encode your chosen picture and sound settings without overheating, dropping frames or going to sleep. OBS handles the composition and encoding, but the computer still needs a real camera or video source, an audio feed, a stable connection and a plan for recovery.
Start by tracing the complete signal path: camera or sermon video into the PC, audio into the PC, OBS combining the sources, and YouTube receiving the encoded broadcast. Then test that path for longer than a short Sunday rehearsal before treating the stream as dependable.
Check the spare PC and operating system
The first question is not whether OBS installs. It is whether this particular computer can keep encoding your chosen stream for the time you need. OBS publishes baseline requirements for supported operating systems and graphics hardware, but its own guidance makes clear that meeting those requirements does not prove that a machine can handle a particular workload. Resolution, frame rate, encoder choice, scene complexity and other applications all change the load.
Download OBS from the official OBS system requirements page, then run its Auto-Configuration Wizard. The wizard considers available hardware and network conditions and gives you a starting point. Treat that result as a starting point, not as a reliability certificate.
Before the first test, record what the spare PC actually has:
| Check | Why it matters | What to do |
|---|---|---|
| Operating system | OBS features and device drivers vary by platform | Install current updates that are appropriate for the computer, then confirm OBS recognises the system |
| Processor and graphics | Encoding can use substantial CPU or GPU capacity | Watch OBS statistics during a test rather than relying only on specifications |
| Memory and storage | Other applications and recordings can compete for resources | Leave unnecessary applications closed and avoid recording locally unless you need it |
| Power | Sleep, battery switching or a loose cable can stop a broadcast | Use reliable mains power and set the operating system not to sleep during the stream |
| Network connection | A working web browser does not prove a stable upload path | Prefer a wired connection where practical and test the actual upload route |
| Ventilation | Continuous encoding can expose heat problems | Keep vents clear and check the PC during a longer run |
The computer does not need to be dedicated permanently, but it should be dedicated while the broadcast is running. Do not use it for unrelated downloads, games, operating-system maintenance or presentations that might unexpectedly take over the display or network.
A modest scene and a conservative output setting are usually easier to keep stable than a complex arrangement with several animated sources. If the PC struggles, reduce complexity before buying equipment. A clear camera and intelligible sermon audio are more valuable than an elaborate layout that causes encoding overload.
Connect the church camera and sound feed
A spare PC cannot create a church camera view or mixer feed by itself. You need to identify the equipment already used in the room and decide what the online viewer should receive: a live sanctuary camera, a pastor camera, presentation slides, recorded sermon material, or a mixture.
A USB webcam normally connects directly to the computer. An HDMI camera or video switcher needs a compatible input on the PC. If the computer has no such input, a USB HDMI capture card may be needed, but only after you confirm the camera output, capture format, drivers and operating-system support. A capture card is not required simply because the source is a camera.
If the church already has capture hardware, test it before purchasing another device. Some cameras output different HDMI formats depending on their menu settings, and a card that accepts one format may not accept another. Check the exact documentation for both devices. A USB webcam may be the simpler choice for a small setup, while an existing HDMI camera may provide a better position or picture if the signal can enter the PC reliably.
Audio deserves its own inspection. The cleanest church arrangement may be an output from the sound desk, but the available output and level depend on how that desk is configured. Other arrangements use a microphone connected to the computer or a microphone built into a webcam. Do not assume that the audio viewers hear in the sanctuary is automatically available to OBS.
Trace the audio cable from the source to the computer, then select that input explicitly in OBS. During a test, have someone speak at the normal sermon level and watch the OBS mixer meters. Listen on a second device as well. A meter moving does not prove that the correct microphone is selected or that the online result is free from hum, delay or distortion.
If slides are part of the service, decide whether OBS will capture presentation software, receive a dedicated output, or use separate image sources. Software such as Proclaim can be part of a church presentation workflow, but it remains another application that must be tested with the camera and sound path. Avoid capturing the entire desktop if a cleaner source is available, because notifications and unrelated windows can then appear in the broadcast.
Keep a simple diagram beside the PC:
camera or switcher → capture input → OBS
sound desk or microphone → audio input → OBS
OBS → YouTube Live
When a fault occurs overnight, this diagram gives the volunteer a place to begin. If the camera is visible but there is no audio, the problem is probably in the audio path or OBS source selection rather than in YouTube.
Compose the programme in OBS
Install the current OBS release from the OBS Project website, create a scene and add only the sources required for the sermon. A basic scene might contain a camera or capture device, a slide source and a discreet title graphic. Add the intended audio input separately and name each source clearly.
Use one simple scene first. Add a second scene only when you have a real operational reason, such as switching from a holding slide to the sanctuary camera. Every additional source can introduce another device, application window or failure point. If volunteers will operate the stream, names such as Sanctuary camera, Sound desk, and Opening slide are easier to understand than default names.
Open OBS’s audio mixer and make sure the correct input moves when someone speaks. If desktop audio is enabled, confirm exactly what it captures. Unwanted desktop audio can include a browser video, a system alert or a video-call notification. Disable sources you do not need rather than trying to remember not to use them later.
For a sermon stream, set the camera framing before going live. Leave enough room for the speaker to move without leaving the frame, and check whether text on slides can be read on a phone. A source that looks acceptable on the operator’s large monitor may be too small in the public viewing window.
The output settings need to match both the PC and the connection. Higher resolution and frame rate require more work from the encoder and more upload capacity. Thirty frames per second may be a more practical starting point than sixty for a mostly static sermon view, but the right choice depends on the camera, the content and the machine. OBS explains these trade-offs in its overview guide.
Use the Auto-Configuration Wizard, apply a modest configuration, and measure the result. Do not increase settings because the spare PC appears idle for the first few minutes. Continuous encoding can reveal heat, driver and resource problems that are not visible in a quick setup check.
Create or select a YouTube Live stream
In YouTube Studio, open Live Control Room and create or schedule the broadcast. YouTube’s encoder streaming instructions describe the stream URL, stream key and encoder workflow. Follow the current instructions shown for the church’s channel, because the available controls and first-time requirements can change.
If live streaming has never been enabled on the channel, YouTube says activation may take up to 24 hours. Do not discover this on the morning of the first public service. Enable the feature in advance, confirm the channel owner can access Live Control Room, and allow time for account or channel checks.
Choose the intended visibility carefully while testing. A private or unlisted broadcast can help you check picture and sound without directing the public to an unfinished stream. Confirm the actual viewing page on a separate phone or computer, preferably using a different connection from the encoder.
YouTube also lets you decide how the broadcast is organised in the channel. Give the stream a clear title, description and thumbnail if viewers will find it publicly. If the church has a recurring schedule, document which broadcast is reused and which one is created for a particular service. This reduces the risk of starting the wrong event or leaving an old scheduled stream untouched.
If the channel contains recorded sermon material as well as live services, keep the archive plan in mind. A continuous viewing feed and a collection of easy-to-find individual sermons are not necessarily the same thing. A guide to making a YouTube playlist play continuously on a live stream may be useful when the church is deciding whether a PC-based live camera is the right format for material that is already recorded.
Enter the stream URL and protect the key
In OBS, open the streaming settings and select the service or custom server option that matches YouTube’s instructions. Enter the stream URL and stream key copied from Live Control Room. Do not type a key from memory or reuse an old note without checking which YouTube broadcast it belongs to.
YouTube documents RTMPS as encrypted RTMP and provides the appropriate ingestion details in Live Control Room. Where the encoder supports it, use the current RTMPS option shown by YouTube. The YouTube RTMPS documentation is the right place to check the current method rather than relying on a screenshot from an older setup.
Treat the stream key like a password. Do not put it in a public screen recording, a volunteer handbook that is shared widely, a chat message or a photograph of the OBS window. If a key is exposed, replace or reset it in YouTube Studio and update OBS. Keep access to the channel and the encoder settings limited to people who need it.
Check that the selected YouTube stream and the selected OBS profile belong together. It is possible to have valid credentials pointing at the wrong channel or event. Before starting publicly, compare the channel name, scheduled title and preview shown in Live Control Room.
The upload connection must also be considered here. A church guide may recommend at least 5 Mbps upload for its workflow, but that is not a universal guarantee for every resolution, frame rate, encoder setting or shared network. Other activity on the same connection can reduce the capacity available to the stream. Test from the building and at the time of day when the stream will actually run.
Test audio, video and connection
Do not make the first public sermon the first complete test. Start an unlisted or private stream and view it on a second device. Check the camera framing, slide legibility, audio balance, scene changes, lip-sync and the delay that viewers experience.
Speak at normal volume and play the soundboard feed as it will be used during a service. Watch the OBS meters for clipping and listen for hum or a doubled signal. If the sanctuary uses a mixer, ask the audio operator to confirm which output is being sent to the PC. A feed that sounds right in the room may still be too quiet or too strong for the stream.
Watch OBS’s statistics while the test runs. Look for dropped frames caused by the connection, rendering or encoding overload. These labels point to different problems, so note what changes when you lower output settings, close another application or switch from wireless to wired networking.
Test the recovery actions as well. Briefly disconnect the network cable only if you can do so safely, then observe what OBS and YouTube report when the connection returns. Do not assume that a reconnect notice means the public viewing page has recovered. Check the page from the second device and record what the volunteer should do if it does not.
A short test can catch an incorrect microphone or missing capture device, but it cannot establish overnight reliability. Run the complete arrangement for a meaningful period before depending on it. During that period, check the PC’s temperature, power state, ventilation, dropped frames and the viewing page rather than leaving it entirely unattended.
Keep a written test sheet with the date, OBS settings, source names, network used and any faults found. This makes later troubleshooting more useful than the instruction to “try the stream again”. If a setting changes, note why and repeat the relevant test.
Start and monitor the broadcast
On the day of the broadcast, start the PC early enough to confirm that the camera, audio input and presentation sources are present. Open OBS and Live Control Room, check the preview, then start the encoder. Confirm that YouTube has received the signal and that the public viewing page shows the intended picture and sound.
Do not rely only on the OBS preview. The preview shows what OBS is producing, while the second device confirms what has travelled through YouTube and reached a viewer. Keep that second device’s audio muted to avoid creating a feedback loop in the room.
During the first part of the service, monitor the OBS statistics and listen to the public page. Check that the stream has not fallen back to a different microphone, lost the camera after a device reconnect, or displayed a desktop window. If the church has more than one volunteer, assign one person to the room and another to the online feed rather than asking the camera operator to diagnose everything.
If the stream drops, record the time and the visible symptom before changing several things at once. Check power, the network connection, the source device and OBS status in that order. A clear record helps distinguish an internet interruption from an encoder overload or a disconnected capture device.
For recorded material or a holding loop, review the channel’s content plan as well as its technical setup. The advice in Reused Content and 24/7 Loops is relevant when sermon recordings, slides or other material are repeated beyond a live service. It does not replace checking the church’s rights and YouTube’s current policies for the material being used.
Plan for overnight operation and recovery
A “nonstop” stream needs a recovery plan, not just a start button. Decide who checks it, how they reach the building or PC, and what they do if the encoder stops. Keep spare cables and the source-device instructions where the volunteer can find them, but do not change equipment on the basis of a guess while the broadcast is live.
Set the operating system not to sleep during the planned run. Prevent automatic updates or restarts from interrupting the broadcast where the platform allows it, while still applying updates during a planned maintenance window. Keep the computer ventilated and avoid covering it with papers or placing it in a closed cabinet.
A local power interruption can stop both the PC and the network equipment. If the church needs the stream to continue through such an event, consider the practical limits of its power arrangement and decide whether a person can restart the setup. A spare PC alone does not provide power backup, a second internet connection or a replacement camera.
The same applies to network failure. A reconnect setting may help OBS resume after a brief interruption, but it is not a substitute for testing the actual recovery behaviour. Record the correct order for restarting the camera, capture device, OBS and YouTube event. Keep the stream key out of that document unless the document is protected.
YouTube states that streams under 12 hours are automatically archived. For a broadcast intended to run beyond that boundary, do not assume that one uninterrupted feed will produce one complete, replayable sermon archive. Decide whether the priority is a continuous viewing channel, separate sermon replays, or both, then confirm the current archive and broadcast behaviour in Live Control Room before launch.
If the church discovers that maintaining a PC overnight is the main difficulty, compare that approach with a workflow that does not leave the church computer running. The practical differences between 24/7 streaming without a PC and a local OBS setup include source flexibility, recovery responsibility and how the church manages the stream key.
A cloud workflow can remove the need to keep this spare PC powered and supervised for an uploaded, prepared video, but it does not replace a live camera and sound path at the church. For that specific case, StreamNeo removes the overnight computer task by turning an uploaded file into a YouTube broadcast after you provide the channel credentials, while live sanctuary sources still need their own capture and operating arrangement.
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 any old spare PC run OBS all night?
No. OBS may install and open on a computer that still cannot encode your chosen resolution and frame rate reliably for a long period. Use the wizard, run the actual camera and audio sources, watch the statistics and test power, heat and network behaviour before depending on it.
Do I need a capture card for a church camera?
Only when the camera or switcher sends HDMI and the PC has no compatible capture input. A USB webcam can connect directly, while an existing capture device may already solve the HDMI connection. Check the exact output format, drivers and operating-system support before buying a card.
Should the stream use the church sound desk or a microphone connected to the PC?
Use the source that gives a controlled, intelligible signal and that you can test before going live. A sound-desk feed can be appropriate, but its output level and connection must be confirmed with the audio operator. Select the input explicitly in OBS and listen on the public viewing page.
Is one continuous YouTube broadcast best for sermon archives?
Not always. YouTube says streams under 12 hours are automatically archived, so a long-running feed may not provide the archive structure the church expects. Decide whether viewers need a continuous channel, individual sermon replays, or both, and verify the current Live Control Room behaviour before launch.