For a recorded church service, start with YouTube’s H.264 guidance: CBR, a two-second keyframe interval, and AAC stereo at 128 kbps. Use 1080p30 only if the source recording, encoder and sustained upload connection can support it; otherwise test a lower output such as 720p30.
A single scheduled rebroadcast and a channel intended to run around the clock are different jobs. OBS can send a prepared programme to YouTube, but no set of output values guarantees an unattended stream will stay live; plan around the duration, monitoring and recovery you actually need.
Decide what continuous means
If you mean one recorded Sunday service shown as a live event, treat it as a scheduled broadcast with a defined start and finish. You can prepare the recording in OBS, send it to the event created in YouTube Studio, check the preview and end the event when the programme is over. This is a manageable event workflow, but it still depends on the computer, OBS and the upload connection remaining available during the broadcast.
If you mean a 24/7 channel, the question is not simply which encoder preset to choose. You need to decide what happens after the service ends: whether another recording follows, whether content repeats, whether the channel must remain live overnight, and whether a long broadcast needs a single archive. The YouTube Live Control Room 24/7 setup guide can help frame that operational choice without confusing it with image quality.
YouTube’s encoder workflow says streams under 12 hours are automatically archived. Do not assume a longer continuous session will appear as one complete archive; if replay matters, decide how you will handle the programme and its recording before you start. A recurring or overnight channel also needs a plan for checking stream health and responding if OBS, the computer or connectivity stops sending.
A practical OBS starting profile
The table is a starting point, not a universal profile. For video bitrate figures below, the values are YouTube’s H.264 recommendations as listed on YouTube Help in October 2026; use the current encoder guidance when setting up an event because recommendations can change. Test the chosen settings with your actual recording and connection.
| OBS or stream choice | Starting point | When to change it |
|---|---|---|
| Service and transport | YouTube over RTMPS, if your OBS workflow offers it | Follow the server URL and stream key shown in Live Control Room. YouTube recommends RTMPS for encrypted transport. |
| Video encoder | H.264 | YouTube also lists H.265 and AV1 for RTMP/RTMPS, but only choose another codec if your OBS version, encoder and planned workflow support it reliably. |
| Rate control | CBR | YouTube specifies constant bitrate for RTMP/RTMPS ingestion. |
| Keyframe interval | 2 seconds | YouTube recommends two seconds and says not to exceed four seconds. |
| Output resolution and frame rate | 1080p30 if source, system and connection permit; otherwise test a lower setting such as 720p30 | Match the output to the source and sustained upload, not merely the largest available number in OBS. |
| Audio | AAC stereo, 128 kbps | Use this as a baseline, then listen to the programme preview or test recording for clear speech and balanced levels. |
| Colour for SDR | Rec. 709 | Avoid an HDR workflow unless the source and the complete delivery chain are prepared for it. |
| Local safety recording | Optional separate recording output, with MKV as a practical container | Test the additional load. OBS notes that a separate recording configuration can use resources. |
For a simple H.264 setup, YouTube lists 14 Mbps as its recommended video bitrate for 1080p30 and 8 Mbps for 720p30. These are platform recommendations, not assurances that your church’s internet connection can sustain them. The appropriate setting also depends on the amount of detail and movement in the recording and on whether the selected encoder can keep up.
Set the values under OBS’s output and video settings, but do not treat a saved profile as proof that a real broadcast will work. Encoder names and controls can differ according to computer and OBS configuration. If the computer becomes overloaded, a smaller output or a hardware encoder available on that computer may be more practical than pushing a higher-quality setting it cannot maintain.
Match resolution and bitrate to the recording and connection
Begin by inspecting the actual service file. If it was recorded at 720p, streaming it at 1080p does not restore missing detail. If it contains small scripture text, slides or a wide shot, look closely at those parts when comparing output settings. A mostly static pulpit shot and a programme with camera movement, transitions or close-ups can behave differently at the same resolution and bitrate.
YouTube’s H.264 recommendations, as listed on YouTube Help in October 2026, give 1080p30 a 5 Mbps minimum and 14 Mbps recommendation, and 720p30 a 3 Mbps minimum and 8 Mbps recommendation. These are reference points for the video stream, not a guarantee of stable delivery. YouTube also advises leaving 20% upload bandwidth headroom. That means the connection’s sustained available upload needs to exceed the stream’s bitrate, with room for ordinary variation and other traffic.
Do not base the decision on a speed test run at a quiet moment alone. Consider whether other devices share the connection, whether uploads or backups run during the service, and whether the connection behaves consistently for the planned duration. A wired Ethernet connection is worth considering where practical, but it cannot correct every ISP or router problem. If the required headroom is not available, lower the output resolution and bitrate, then test again rather than hoping the connection will improve on the day.
The guide to resizing 4K video for a YouTube loop is relevant if the church recording is larger than the stream output you can reliably support. Resizing can reduce the work at broadcast time, but assess the result on real slides and text: an export that looks acceptable on a small preview may not preserve details viewers need to read.
Frame rate is another source constraint. A 30 fps output is a reasonable starting point for many recorded services, but choose in light of the original file and the computer’s ability to encode it. OBS’s overview notes that 60 fps can be more demanding than 30 fps, so increasing frame rate has a resource cost as well as a possible visual benefit. For a typical speaking service, a stable lower frame rate is generally more useful than an ambitious setting that drops frames.
Set keyframes, audio and a local copy
Keep the live keyframe interval at two seconds as the straightforward YouTube baseline. YouTube recommends two seconds and advises that the interval should not exceed four seconds. The keyframe interval is a delivery setting, not a remedy for a weak connection or overloaded encoder. If OBS exposes the value in seconds or frames, verify what the control means in your version rather than assuming the field is expressed in the same units everywhere.
For the audio output, AAC stereo at 128 kbps is YouTube’s recommended simple baseline. A church recording may contain speech, organ, congregational singing and room sound, so listen to the actual feed rather than judging by the number alone. Check that the service is audible in the OBS mixer and that no unintended desktop sound or live microphone is mixed over the recording. Watch for a muted source, clipping, or a large mismatch between speech and music.
If you want a local copy as a safeguard, OBS allows streaming and recording output to be configured independently in Advanced output mode. OBS recommends MKV for recording because an ungraceful stop does not corrupt the entire file in the way an unfinished MP4 can. If you need MP4 afterwards, OBS provides remuxing. A separate, higher-quality recording configuration can add system load, so test it during the same conditions as the stream.
There is a trade-off between having a clean local archive and preserving encoder capacity for the live output. Avoid selecting a lossless recording preset for a routine church archive without a specific need: it can create very large files. Use a practical recording quality, keep enough storage available, and verify that both outputs work before relying on the local copy.
Configure OBS and YouTube Live
Create or schedule the event in YouTube Studio and use the stream URL and key supplied in Live Control Room. Treat the stream key as a password: anyone who obtains it may be able to send a feed to the channel. The guide to revoking a leaked YouTube stream key explains what to do if you think the key has been exposed. Do not put it in a public document, message or screen recording.
Prepare the complete programme in OBS, for example as a media source, and confirm that its video and audio appear as intended. The precise controls for looping or building a playlist can vary, so do not assume that loading one file creates a reliable all-night schedule. If repeated content is the goal, test the exact transitions and file order before the public broadcast. The guide to looping a single video without a black screen covers the separate problem of what viewers see at a loop boundary.
Connect OBS to the YouTube event using the provided connection details, then begin sending the feed early enough to inspect YouTube’s Live Control Room preview. Check the picture, audio and stream health before starting the scheduled event. Follow the auto-start and auto-stop choices configured for that event; do not assume they match the controls used for a previous service. The official YouTube encoder settings guidance covers supported ingestion settings, and YouTube’s live settings help explains event options such as DVR. DVR is a viewer control that allows pausing and rewinding; it is not an encoder quality setting.
For a one-event rebroadcast, agree in advance who will end the YouTube event and when OBS should stop sending. Check the result afterwards, including any local recording you made. For an around-the-clock channel, describe the schedule and archive expectation accurately; the event configuration is not itself a complete unattended operating plan.
Test the whole path before the service
A useful test resembles the programme you plan to broadcast. Include speech, singing or music, any slides with small text, and the movement or transitions that appear in the recording. Check the OBS preview and listen on another device if possible. A silent room tone or a still frame does not put the same demands on the encoder or reveal the same audio problems as the service itself.
Use a private or otherwise appropriate test event if you need to check the complete path without presenting a public service. Confirm that OBS is sending, YouTube receives a preview, and the sound remains in sync and intelligible. Look at OBS’s dropped frames and encoder warnings as well as YouTube’s stream health. If you change the bitrate or output resolution, repeat the test; a change that appears small in the settings may affect the connection or computer differently under sustained use.
Test for the duration that is practical, especially if the real programme is long or the workflow is intended to continue beyond one service. Check the power plan so the computer will not sleep, and avoid running updates, backups or other demanding tasks during the broadcast. Keep the stream key private and have someone responsible for checking the event, rather than assuming that a green preview at the beginning proves the rest will be uninterrupted.
Monitor a long broadcast and plan for recovery
During a service, watch both the OBS status and YouTube’s stream health. If the picture freezes, audio drops or the connection degrades, note whether the problem is encoder load, network delivery or the source itself before changing several settings at once. YouTube’s streaming tips warn that a connectivity disruption can break a stream. A lower bitrate can help when upload capacity is the constraint, but it cannot resolve every cause of interruption.
A person monitoring the broadcast can respond to an unexpected pause, restart OBS if appropriate, or communicate with viewers. For a one-off service, that may be enough alongside a tested local recording. For a 24/7 channel, relying on someone to sit beside a computer overnight is a different operating burden. StreamNeo can remove the need to leave a church computer running for a prepared programme by taking an uploaded video and stream key for a cloud-run YouTube broadcast, but you should still check that the file, channel settings and intended schedule meet your needs.
Make a recovery plan that says who has access to the event, where the approved recording is stored, and what should happen if the live feed stops. Do not promise viewers that an event will never drop. If a complete archive matters, take account of YouTube’s under-12-hour archive guidance and decide how you will retain or divide longer programming. A local MKV recording can help preserve a copy, but it too needs storage checks and a test that confirms it is actually being written.
Choose the workflow that fits the job
For a single recorded service, OBS is useful when you want to control the scene, combine sources or have a person operating the broadcast. It also makes it possible to keep a local recording with separate output settings. The trade-off is that the computer and connection must remain ready, and a person must know how to check the preview and respond to problems.
For a repeated schedule or channel that should continue while the church computer is off, compare the workload rather than treating OBS settings as the whole solution. The church channel workflow comparison may help you think through what should be operated locally and what can be handled without leaving your own computer on. Whichever method you use, verify the exact file, event controls, stream key handling and archive expectation before announcing a schedule.
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
Is 1080p30 the best setting for every recorded church service?
No. It is a useful option only when the source, encoder and sustained upload support it, with enough headroom for a stable connection. If the source is 720p or the system and connection struggle, test a lower output instead of scaling up by default.
What bitrate should I try for 720p30 or 1080p30?
YouTube’s H.264 guidance lists 8 Mbps for 720p30 and 14 Mbps for 1080p30, with minimums of 3 Mbps and 5 Mbps respectively, as listed on YouTube Help in October 2026. YouTube also advises 20% upload headroom, so the connection must offer more than the stream bitrate in sustained available capacity. These figures are guidance, not a prediction of how your particular network will perform.
Can OBS keep a church channel live all day and night?
OBS can send a prepared programme, but settings alone do not ensure an unattended stream stays live. The computer, power, software and network still matter, and longer sessions raise archive and monitoring questions. Test the intended duration and decide who responds if the feed stops.
Should I record locally while streaming?
A local copy can be useful if you need an archive or a backup of the programme. OBS recommends MKV as a recording container because an interrupted recording is less likely to lose the whole file, and OBS can remux it to MP4 afterwards. Test separate recording and streaming together, since recording can add system load.