For a 24/7 YouTube stream in India, start with 1920×1080 at 30 fps, H.264, CBR, a 2-second keyframe interval and stereo AAC audio. Treat this as a starting profile, not a guarantee that your connection will carry it continuously.
YouTube lists 14 Mbps as its recommended H.264 bitrate for 1080p30. If your sustained upload or encoder cannot maintain that with headroom, use 1280×720 at 30 fps instead, where YouTube lists 8 Mbps for H.264. Measure the connection at the streaming computer and at the time you expect to run the channel.
Start with a simple SDR profile
For devotional video, bhajan channels, lofi music, ambience, study loops and local information feeds, standard dynamic range, or SDR, is usually the sensible place to begin. It avoids adding HDR colour-management decisions to an unattended setup and is supported by a broad range of computers and capture workflows.
Use this as the initial OBS target:
| Setting | Starting value | Why it matters |
|---|---|---|
| Output resolution | 1920×1080 | Clear enough for text, artwork and ordinary video |
| Frame rate | 30 fps | Lower encoder and upload demand than 60 fps |
| Video codec | H.264 | Matches the bitrate figures used in this profile |
| Rate control | CBR | Keeps the outgoing stream at a predictable rate |
| Keyframe interval | 2 seconds | Matches YouTube's encoder guidance |
| Audio codec | AAC stereo | Suitable for music, speech and ambient audio |
| Audio bitrate | 128 Kbps | YouTube's listed stereo AAC guidance |
| Audio sample rate | 44.1 kHz | YouTube's listed stereo AAC guidance |
| Colour space | Rec. 709, 8-bit SDR | The relevant YouTube SDR target |
The figures in this table are platform settings, not a promise about an Indian broadband, fibre, fixed-wireless or mobile connection. YouTube's official encoder settings guidance gives separate recommendations for H.264, H.265/HEVC and AV1. The bitrate in this article is specifically for H.264, so do not carry it across to another codec without checking the matching table.
The encoder menu may use slightly different labels. OBS might show a hardware H.264 encoder supplied by your graphics hardware, or a software H.264 encoder using the processor. Select the option that produces H.264, then confirm the actual output in the stream information and OBS statistics rather than relying only on the name of the preset.
If the channel is built from a long video rather than a live camera, prepare the file first. Check that the loop has no unintended black frames, silent sections or sudden jumps. For rain, fireplace and other ambience, the guide on making a seamless nature loop for YouTube Live covers a problem that bitrate settings cannot fix: a visible or audible join will repeat for viewers.
Set resolution and frame rate before bitrate
In OBS, open Settings, then Video. Set the base canvas to match the material you are composing. If the source is a 1920×1080 video, use a 1920×1080 base canvas and output resolution. If the source is smaller, enlarging it does not create extra detail, although it may still be useful for keeping the channel layout consistent.
Set the output frame rate to 30 fps for the first test. Thirty frames per second is a practical balance for a 24/7 channel because it reduces work compared with 60 fps while remaining suitable for ordinary video, scrolling information and gentle movement. A static devotional image with music may not need 30 fps for visual reasons, but using a normal video profile can make the workflow easier to maintain.
YouTube's encoder guidance recommends allowing the platform to detect the stream resolution by default. Manual resolution is reasonable when you have a clear reason to control the output, such as matching a tested OBS profile or ensuring that a text-heavy layout remains predictable. Do not choose a larger output merely because the source or display supports it.
Frame rate and resolution are connected to encoder load. A computer that handles 1080p30 may struggle with 1080p60, especially when the scene contains scaling, filters, browser sources or animated overlays. Watch OBS's rendering and encoding statistics during a long test. Dropped frames caused by the network and skipped or lagged frames caused by the encoder are different faults, so record which counter is increasing.
If you are streaming from a spare computer, keep the scene simple before changing quality. A single video source, audio source and small logo is easier to diagnose than several browser panels and animated effects. The article on running a YouTube radio stream from a spare PC is useful when the machine has to operate unattended and you want to reduce unnecessary work.
Choose H.264 bitrate from sustained upload
For H.264 at 1080p30, YouTube lists 14 Mbps as recommended and 5 Mbps as minimum. The word “recommended” describes YouTube's platform guidance for that codec and output mode. It does not mean an Indian connection advertised at a particular download speed will sustain the stream, nor does it account for other devices sharing the connection.
YouTube's streaming tips recommend leaving 20% headroom in available upload bandwidth. In practical terms, do not treat the full measured upload result as available for OBS. If the streaming computer can sustain only a little more than the stream requires, a short speed-test result is not enough evidence for an unattended channel.
Measure upload at the actual location, using the same connection and preferably the same wired or wireless path that OBS will use. Test at the times the channel is likely to run. A household connection may behave differently when other people are on video calls, uploading files or watching high-resolution video. Download speed does not tell you how much upstream capacity OBS has.
The 14 Mbps H.264 recommendation also needs room for audio and normal variation. YouTube's 20% headroom advice is a planning margin, not a guarantee. If the available upstream repeatedly falls below the level needed for 1080p30 plus headroom, move to 720p30 rather than waiting for the stream to fail overnight.
YouTube's H.264 table also lists 17 Mbps recommended and 6 Mbps minimum for 1080p60, 8 Mbps recommended and 3 Mbps minimum for 720p60, 8 Mbps recommended and 3 Mbps minimum for 720p30, 4 Mbps recommended and 0.4 Mbps minimum for 480p30, and 4 Mbps recommended and 0.4 Mbps minimum for 360p30. These numbers belong to the corresponding H.264 modes. They are not generic bitrate targets and should not be applied to AV1 or H.265/HEVC.
This is why a channel should not copy a bitrate from a different platform or a different codec. The comparison in what bitrate Facebook Live actually accepts concerns another service and should not replace YouTube's current encoder table.
Use CBR and a 2-second keyframe interval
In OBS, open Settings, then Output, and select the streaming output mode. Choose H.264 through the encoder available on the computer and set rate control to CBR, or constant bitrate. CBR gives YouTube a more predictable incoming stream than allowing the bitrate to rise and fall freely.
Set the keyframe interval to 2 seconds. YouTube recommends a 2-second interval and says it should not exceed 4 seconds. A keyframe is a complete reference image from which later frames can be decoded. Regular keyframes help the platform process the stream and help playback recover after a disruption.
Do not try to compensate for a weak connection by changing the keyframe interval to an arbitrary value. It does not create upload capacity. Likewise, increasing the bitrate does not repair an encoder that is skipping frames because its processor or graphics hardware is overloaded.
If your OBS build exposes additional rate-control options, leave them at conservative defaults until the basic profile is stable. Options such as presets, profile, tuning and GPU usage affect encoder work and picture quality, but the correct choice depends on the encoder and computer. Test one change at a time and keep a note of the setting that was used.
The transport matters too. YouTube recommends RTMP or RTMPS ingestion and recommends RTMPS for encryption in transit. In YouTube Studio, create or schedule the encoder stream, then enter the stream URL and stream key in OBS. Treat the key like a password. If it is exposed, reset it in Live Control Room and replace it in OBS.
A key is not a substitute for testing. If the stream key is missing or does not appear as expected, use the relevant YouTube stream-key troubleshooting steps for India before changing encoder settings at random.
Configure AAC stereo audio
Set the audio output to AAC stereo at 128 Kbps and a 44.1 kHz sample rate for this profile. Those values follow YouTube's listed stereo AAC guidance. They are enough for speech, devotional vocals, ordinary music and ambient audio when the source itself is clean.
In OBS, check both the global audio sample rate and the source settings. A mismatch can cause resampling or unexpected sync behaviour. Keep the number of active audio paths small. For a prerecorded video with embedded audio, avoid also capturing desktop audio unless you have a specific reason, because the same sound may be sent twice.
Listen to a private or unlisted test on a phone and on headphones. A level that looks acceptable on the streaming computer can still be too quiet, distorted or uneven on another device. For a devotional or radio-style channel, a sudden loud intro is more disruptive than a small difference in average loudness.
Watch the OBS mixer for a period that includes speech, music and quiet sections. If the meter is constantly at the top, reduce the source level before applying more processing. If the audio disappears when the video loops, inspect the source and scene transition rather than increasing the AAC bitrate.
For a useful long-run test, leave the audio running while the computer performs its ordinary streaming work. Listen for gradual drift between speech and video. If the problem follows a prerecorded file, fix the file or source timing; changing YouTube's video bitrate will not correct an audio track with a bad duration.
When to step down to 720p30
Move from 1080p30 to 720p30 when either of two limits is sustained: the connection cannot provide the required upload with headroom, or the encoder cannot process the 1080p output without skipped or lagged frames. Do not wait for an overnight failure to confirm what a controlled test already shows.
For H.264 at 720p30, YouTube lists 8 Mbps recommended and 3 Mbps minimum. The lower output reduces the amount of picture information and usually reduces encoder work, but it is not a special India preset. It remains your responsibility to measure the available upstream at the actual location.
Use this comparison when choosing a profile:
| Candidate | H.264 YouTube figure | Choose it when | Trade-off |
|---|---|---|---|
| 1080p30 | 14 Mbps recommended, 5 Mbps minimum | Sustained upload and encoder capacity leave room above the stream requirement | More detail, more network and processing demand |
| 720p30 | 8 Mbps recommended, 3 Mbps minimum | 1080p is not stable or the source is modest in detail | Lower detail, simpler long-run operation |
| 480p30 | 4 Mbps recommended, 0.4 Mbps minimum | A further fallback is necessary after testing | Text and fine detail become harder to read |
The minimum figures are not targets for a reliable unattended channel. They describe the lower end of YouTube's listed range for the mode, not a guarantee of smooth delivery. If the connection varies around the minimum, a lower profile with real headroom may be more practical than selecting the highest resolution that works only during a short test.
Content also changes the decision. A slow-moving bhajan visual may remain watchable at 720p30, while a local news loop with small scrolling text may need careful testing. A lofi station made from a still image may gain little from 1080p if the artwork was created at a lower resolution. The right choice is stability and readable content, not simply the largest number.
If the computer is the constraint, inspect the encoder statistics before reducing upload. The article on whether FFmpeg needs a GPU for 24/7 YouTube streaming explains the wider distinction between processor capacity and graphics acceleration. The same principle applies in OBS: identify the failing resource before changing several settings at once.
Test stream health before leaving it unattended
Start a test with the same kind of movement and audio your audience will receive. A static screen can conceal a problem that appears when text scrolls, a video changes scene or music becomes more complex. Let the test run long enough to observe the connection and encoder under normal conditions, rather than relying on the first few minutes.
Open the Live Control Room preview and read the stream health messages. YouTube's streaming tips advise measuring upload, considering shared-network use and watching for connectivity disruption. Confirm that the watch page opens from another device and that the audio is present.
Keep OBS's statistics panel visible during the test. Network dropped frames suggest that the connection is not delivering the outgoing stream consistently. Skipped or lagged frames indicate an encoder or rendering problem. A healthy-looking speed test cannot rule out wireless interference, congestion, a busy router or a computer that heats up after several hours.
Use Ethernet where practical for a fixed streaming computer, but treat it as a way to remove one possible wireless variable, not as an uptime guarantee. Electricity, the ISP, the computer, the router and YouTube can each fail. A second encoder, power backup or cable can reduce one risk without removing all of them.
If the channel matters enough to need recovery planning, test the backup rather than merely buying or configuring it. YouTube describes a failover test in which you stop the primary encoder or disconnect its Ethernet cable and check whether the player rolls over to a backup encoder. Perform this before depending on the arrangement, and document which stream key and scene each encoder uses.
For an unattended cloud workflow, uploading the file once and keeping your own computer switched off removes the particular problem of a home PC needing to run all night. StreamNeo is designed for that handover from a prepared video to a continuously monitored YouTube broadcast, while you still need to check the source, stream key and YouTube channel settings yourself.
There is also a limit that bitrate settings cannot solve. YouTube says a stream longer than 12 hours may not be captured at all, and its DVR guidance warns that rewind can be limited or unavailable for streams longer than 12 hours. If you need a complete on-demand copy, record locally and verify the file, or plan shorter sessions and confirm each resulting archive.
Do not assume that one uninterrupted 24-hour broadcast will create a complete YouTube recording. A local archive also gives you evidence of what was actually sent if viewers report a missing section. For a music, news or devotional channel, check that the recording includes the opening, loop transition and any scheduled changes.
Normal latency is a reasonable starting point for an ambient or prerecorded channel with little audience interaction. YouTube explains that lower latency can increase playback buffering, while low and ultra-low latency are intended for interaction and do not support 4K. This is a use-case choice, not a special 24/7 rule.
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 14 Mbps enough for a 1080p30 YouTube stream?
It is YouTube's recommended H.264 video bitrate for 1080p30, not a guarantee for your connection. You also need upload headroom, and the measurement must reflect sustained upstream capacity at the streaming computer rather than an advertised download speed.
Should I use 720p30 on mobile broadband in India?
Choose based on measured stability, not the connection label. Test sustained upload at the location and operating time, then use 720p30 if 1080p30 cannot remain stable with headroom or if the encoder is overloaded.
Can I use the H.264 bitrate figures with AV1 or H.265?
No. YouTube publishes codec-specific recommendations, so use the table for the codec actually selected in OBS. The figures in this article are for H.264.
Will a 24-hour stream always have a complete YouTube archive?
No. YouTube says streams longer than 12 hours may not be captured, and DVR rewind may also be limited or unavailable. Keep a verified local recording or use shorter sessions if a complete archive matters.