For a 24/7 YouTube kids story channel, choose OBS bitrate from YouTube’s live-ingest guidance for your resolution, frame rate and codec—not from its recommendations for uploaded videos. For H.264 at 30 fps, YouTube lists 3 Mbps minimum and 8 Mbps recommended for 720p, or 5 Mbps minimum and 14 Mbps recommended for 1080p; use the higher format only if your upload connection can sustain it and a test stream stays healthy.
The Made for Kids audience designation is a separate YouTube setting based on who the content is made for. It does not change the encoder bitrate. Treat the stream settings, connection test and audience designation as distinct parts of your launch checklist.
Choose 720p30 or 1080p30 first
Settle the output format before entering a bitrate in OBS. The relevant choice here is 720p30 or 1080p30: resolution describes the picture dimensions, while 30 fps describes how many frames are sent each second. YouTube’s live guidance gives different targets for different formats and codecs, so a bitrate value cannot be chosen reliably in isolation.
For a children’s story loop, consider what is actually on screen. A mostly static illustration with slow transitions can be readable at 720p, particularly on a phone. Full-screen artwork with small text, detailed backgrounds or gentle animation may benefit from 1080p, but only when the source material has that detail and the connection can carry the higher bitrate steadily. Upscaling a low-resolution file does not create detail that was not in the original.
A useful starting decision is the least demanding format that shows the story clearly. If the artwork and any on-screen text remain legible at 720p, begin there. If important details look soft, try 1080p and compare the same scene. Keep the frame rate at 30 fps unless the material and intended presentation give you a specific reason to use a different rate; YouTube’s figures below are tied to their listed resolution and frame-rate rows.
This is a trade-off, not a quality ranking. A stable 720p stream may be a better overnight choice than a 1080p stream whose bitrate repeatedly falls behind. You can also make a short private or unlisted test before committing your regular channel schedule. For background on how output choices vary with a different sort of loop, see the OBS settings guide for a YouTube gaming rerun in India. Its gaming context is different, but the need to match output settings to the actual content and connection is shared.
Use YouTube live-ingest values, not upload-video guidance
An OBS broadcast is a live ingest, so use YouTube’s live encoder settings page. Its H.264 table lists a minimum and a recommended bitrate for each supported resolution and frame rate. These are YouTube’s technical recommendations, not results from an independent performance study and not universal settings for every codec or frame rate.
YouTube separately publishes guidance for videos uploaded as files. Those figures concern preparing an upload, not sending a live signal from OBS. For example, the upload page’s H.264 SDR guidance gives different values for 1080p video than the live-ingest table does. Applying upload-file guidance to a live broadcast confuses two different workflows. Use the YouTube live encoder settings page for the stream and the upload encoding recommendations only when preparing a video file for upload.
For the two 30 fps formats in this guide, the H.264 values are:
| Live output format | YouTube H.264 minimum | YouTube H.264 recommended |
|---|---|---|
| 720p at 30 fps | 3 Mbps | 8 Mbps |
| 1080p at 30 fps | 5 Mbps | 14 Mbps |
YouTube’s live table also has separate entries for other frame rates, resolutions and codecs. If you select HEVC/H.265 or AV1 rather than H.264, look up that codec’s row instead of copying the H.264 numbers. Likewise, do not carry these 30 fps figures over to 60 fps output. The table is a lookup for a particular combination, not a general rule that one bitrate suits every stream.
YouTube gives RTMP/RTMPS and H.264, H.265/HEVC or AV1 among its live ingest options. The particular codec you can use depends on the encoder and settings available to you. YouTube also recommends CBR encoding and a keyframe interval of two seconds, with no interval longer than four seconds. Use the current YouTube guidance for the format you actually configure; menu names and available controls can vary between OBS versions and hardware encoders.
Set an OBS bitrate target for the chosen format
In OBS, locate the output or streaming encoder controls for your installed version and choose the codec and rate control that match your intended YouTube live configuration. Set CBR, then enter the bitrate corresponding to the chosen row in YouTube’s live table. Set the keyframe interval to two seconds where the encoder exposes that control. The exact labels and location are not safe to assume across different OBS releases or graphics hardware, so check the controls shown on your own system rather than following a menu path for a different version.
For an H.264 720p30 output, 8 Mbps is YouTube’s recommended value and 3 Mbps its listed minimum. For H.264 1080p30, the recommended value is 14 Mbps and minimum is 5 Mbps. The minimum is not the sensible target merely because it exists: it is a lower boundary in the table, not a promise that every connection at that rate will remain stable or that every illustration will look equally clear. Choose the recommended value only if your real connection can sustain the full outgoing stream and your test confirms it.
A practical way to decide is to make one change at a time. Start with the format that suits the artwork, apply its H.264 live value, and test. If the upload connection struggles at 1080p30, reducing resolution to 720p30 and then using the 720p row is more coherent than leaving the output at 1080p while forcing an unrelated bitrate. If 720p30 is stable and clear, there is no requirement to move to 1080p simply because it is available.
Bitrate is not the only encoder setting that contributes to a consistent signal. YouTube’s advanced settings guidance includes progressive scan and square pixels, along with other encoder parameters. It specifies stereo audio at 44.1 kHz and 128 kbps, and Rec. 709 for SDR. These are guidance for encoding and signal characteristics, not reasons to inflate the video bitrate. If your audio is mono narration over still images, listen to the test and make sure it is intelligible; do not assume a higher video bitrate fixes an audio problem.
For a looped story channel, the content file should also be checked before a long run: confirm the opening and ending behave as intended, and that picture and narration stay in sync. A bitrate setting cannot repair a source video that has a silent section, an abrupt transition or the wrong aspect ratio. If black bars are distracting around your story illustrations, the aspect-ratio explanation can help you separate a source-layout issue from an encoder issue.
Check upload stability and test the stream
A speed test gives you a snapshot of upload capacity; a 24/7 stream needs a connection that remains usable over time. Test from the same network and location that you expect to use for the broadcast, ideally when other devices are using the connection in their normal way. Do not set the target based on the best number you have ever seen if the connection commonly varies in the evening or when someone else starts a video call.
Your upload capacity has to carry the outgoing video stream and its audio, while the connection itself must remain stable. A headline speed-test result is not a guarantee of steady performance for hours. If the available upload varies around the intended target, choose the less demanding format or test at a lower setting. YouTube’s live guidance says to test upload bitrate and recommends testing before starting a live stream. Its streaming troubleshooting guidance also makes reliability of the internet connection a practical concern, not a property of the bitrate number alone.
Test with the same sort of picture and sound the audience will get. A still title card is not a representative test if the regular loop includes moving illustrations, transitions and speech. Run the test with that representative material, then check the stream health messages in YouTube’s Live Control Room. Look for an unstable or interrupted signal and listen to the audio on a separate device. Make a note of the output format, codec and bitrate that passed the test so you can restore them if you change a setting later.
A useful test includes the whole path: OBS sending, YouTube receiving, and a viewer playback check. Seeing OBS report that it is connected does not establish that the received stream looks and sounds right. If the YouTube preview reports a problem, first confirm that the selected codec and ingest settings agree with the live guidance; then reduce the output demand or check the connection rather than changing several unrelated encoder controls at once.
For a channel that must continue while you are asleep, decide in advance what you will do if the stream drops. A local OBS setup depends on the computer, power and internet connection staying available, and it still needs someone able to notice and respond to a failure. If a dropped local connection is the operational pain you are trying to remove, StreamNeo lets you upload a video once and run it as a YouTube live stream without leaving your own computer on, with the broadcast monitored and restarted automatically if it drops. This does not remove the need to check your source file, channel settings or test result.
If a stream disconnects during your own test, diagnose the actual symptom before replacing the bitrate target. The guide to OBS reporting a disconnected YouTube server addresses a connection failure; it is more useful to distinguish that from a stream that remains connected but has poor video health. Keep a record of what changed and what improved, so an overnight problem does not lead to guesswork the next evening.
What the bitrate table does not determine
The table does not tell you whether your channel is ready to go live, whether your connection will remain stable, or how long a particular broadcast will continue. It only supplies technical bitrate recommendations for a defined ingest format. A 24/7 plan needs a separate operational check: channel eligibility, source-file readiness, power and internet continuity, stream monitoring and a recovery plan.
YouTube says that a channel needs to be verified and must not have live-streaming restrictions in the preceding 90 days to start live streaming. Its help page also lists concurrent active-stream limits per channel and per stream key. Those concurrency caps should not be read as a maximum duration for one stream or proof that a stream will run continuously for a day or longer. The YouTube live streaming requirements and restrictions page is the place to check current account requirements; do not infer a 24/7 guarantee from a bitrate recommendation or a concurrency limit.
Nor does the table decide which resolution will make a story channel successful. Viewer devices, source-art quality, narration clarity and the pace of motion all matter to whether the presentation feels clear. Try the same passage at each candidate format and assess legibility on a phone as well as a larger screen. A higher number is only useful when it carries detail the viewer can see and the connection can sustain.
Treat archive availability and interruption behaviour as separate questions too. Do not assume that a live stream will remain available as a replay forever, or that an ended broadcast will automatically resume in the way your schedule expects. Check YouTube’s current live controls and think through the consequences of a drop, including whether viewers will find the next stream and whether your channel can be monitored.
Set Made for Kids separately
Audience designation is a YouTube content setting, not an OBS encoding parameter. If your stories are made for children, set the audience accurately in the appropriate YouTube channel or live-stream setup. The designation should reflect the content and intended audience; it should not be chosen to influence bitrate, stream quality or discovery. YouTube’s guidance on setting your channel or video audience explains how to identify content as Made for Kids.
YouTube says some features are unavailable on Made for Kids live streams, including live chat and live chat donations, comments, the notification bell, personalised advertising, Super Chat and Super Stickers. Those are audience and product-feature consequences. They do not change the H.264 ingest values in the bitrate table, so do not lower or raise your OBS target because of the audience designation.
For a children’s story channel, consider how you will communicate with viewers when chat is unavailable and how you will present channel information without relying on features that may not be available. Confirm the audience setting while preparing the stream rather than treating it as an encoder checkbox. If the channel includes different kinds of videos, review the setting at the level YouTube provides for the channel and individual content, and use the current official guidance where the correct choice is unclear.
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
Should I use 8 Mbps or 14 Mbps in OBS?
Those are YouTube’s recommended H.264 live values for 720p30 and 1080p30 respectively, not interchangeable targets. Choose the row for your output format, then check whether your upload connection and a representative test can sustain it. If not, choose the less demanding format and its corresponding row.
Can I use YouTube’s 1080p upload-video bitrate for an OBS live stream?
No. The upload encoding page covers video files you upload, while OBS sends a live ingest signal. Use YouTube’s live encoder table for resolution, frame rate and codec, and consult the upload recommendations only when preparing a file for upload.
Does Made for Kids change the OBS bitrate?
No. Made for Kids is an audience designation in YouTube, and it affects feature availability such as live chat and personalised advertising. Select bitrate from the live-ingest settings for your codec, resolution and frame rate.
Does a successful test guarantee that a 24/7 stream will stay live?
No. A test helps you catch problems in the setup and connection under the conditions you tested; it cannot guarantee future network, power or platform continuity. Monitor stream health and have a plan for noticing and responding to interruptions.