In datarhei Restreamer, the documented video bitrate control appears in the encoding options after you select H264 as the video codec. It changes the outgoing bitrate when Restreamer is encoding the video; with the default copy setting, Restreamer passes the source video through unchanged, so that encoding bitrate setting is not applied.
Choose a target for the codec, resolution and frame rate you send to YouTube, then check that the streaming path can sustain it with room for audio and network variation. A bitrate change can help when the outgoing rate is unsuitable, but it does not by itself guarantee a stable stream.
When Restreamer’s bitrate setting applies
Restreamer distinguishes between copying a video stream and encoding it. In the documented encoding guide, the default video codec is copy: the source video is passed through unmodified. The bitrate option belongs to the encoding controls, so changing that option does not re-encode video while the codec remains set to copy.
This distinction explains a common puzzle: you change a bitrate value but the output does not appear to change. First check the selected video codec and whether the settings you are viewing belong to the encoding configuration. If the codec is copy, Restreamer is not using those encoding controls to alter the copied video. To request a different outgoing video bitrate, you need an encoding mode that exposes the bitrate setting, such as H264 in the documented guide.
Encoding is also different from publishing. Restreamer’s YouTube instructions describe configuring a Publication Service with a valid YouTube streaming ID and then monitoring the connected stream. They describe viewing the stream’s bitrate in the main window, not editing an encoding bitrate there. Look for the control in the encoding options, rather than assuming that a displayed live bitrate is an editable setting.
Restreamer has changed over time, and the documentation describing these controls is version-specific. Treat the names and layout as a guide to the setting’s function, not a promise that every installed release has identical screens. The Restreamer documentation is the place to check the instructions for your version. If you are preparing a file rather than changing a live encoding, the choices involved in converting MOV files for an OBS playlist are a separate part of the workflow.
Open encoding settings and select H264
In the Restreamer encoding configuration, select H264 for the video codec when you want Restreamer to encode the video and expose its encoding options. The documented guide says that choosing H264 reveals controls including preset, bitrate, FPS, profile and tune. It also describes re-encoding an H.264 source to change its bitrate: a source already using H.264 does not have to remain copied unchanged if you explicitly choose to encode it.
The practical sequence is to open the encoding settings for the stream, inspect the current video codec, and switch from copy to H264 if you intend to change the encoded output. Then confirm that the encoding controls are available before adjusting a value. If the setting is absent or labelled differently, check the documentation for the Restreamer version you are running rather than guessing at a control elsewhere in the publication setup.
Choosing H264 has a cost. Encoding requires processing, and Restreamer’s guide warns that it can use significant CPU resources. A small machine that can comfortably pass a source through may struggle when asked to encode it continuously. For a 24/7 channel, a bitrate target that looks right on paper is not enough if the encoder cannot sustain the chosen resolution and frame rate. The trade-off between processing demand and ease of operation is also relevant when choosing hardware or software video encoders.
You may not need to re-encode. If the source is already suitable for YouTube and the connection can deliver it, copying can avoid additional encoding work. If you need to change resolution, frame rate or bitrate, encoding provides that control, but test it under the workload you expect to run for the actual channel.
Locate the Bitrate option
Once H264 is selected, find the video Bitrate option among the encoding controls. Set the target in the units shown by your installed version. The purpose of this value is to set the encoded video’s output data rate; it affects both the amount of data sent to the external RTMP destination and the bandwidth needed to carry it. Do not confuse video bitrate with the total bandwidth consumed by the complete stream, which also includes audio and delivery overhead.
The documented Restreamer encoding guide explains the option and its relationship to image quality and bandwidth. It does not mean that entering a higher number automatically improves a stream. A higher target may preserve more detail where the source has motion or texture, but it also asks more of the upload path. If the connection cannot sustain the resulting traffic, raising the target can work against reliable delivery.
Make one deliberate change at a time. Note the original codec and target, choose a target that fits YouTube’s recommendation for your output mode, and apply or save the configuration as your version requires. Avoid changing bitrate, FPS and resolution together: if the result changes, you will not know which adjustment mattered. If the output remains at the source rate, return to the copy-versus-encode check before concluding that the bitrate control is broken.
Match the target to YouTube’s recommendations
YouTube’s recommended video bitrate depends on the codec, resolution and frame rate of the incoming stream. Its encoder settings guidance lists the following H.264 examples. These are platform recommendations, not a guarantee that a particular stream will be stable or that every source needs the same target.
| YouTube input mode | YouTube recommended H.264 video bitrate |
|---|---|
| 720p at 30 fps | 8 Mbps |
| 720p at 60 fps | 8 Mbps |
| 1080p at 30 fps | 14 Mbps |
| 1080p at 60 fps | 17 Mbps |
| 1440p at 30 fps | 21 Mbps |
| 1440p at 60 fps | 34 Mbps |
The codec matters. YouTube lists a lower recommendation for AV1 or H.265 than for H.264 in some matching modes; for example, its recommendation for 1080p at 30 fps is 10 Mbps for AV1/H.265 and 14 Mbps for H.264. Do not use an H.264 figure as a codec-independent rule. Confirm the codec YouTube is receiving and use the corresponding entry in the YouTube Live encoder settings guidance.
Resolution and frame rate matter too. A 1080p60 stream is not the same target as 1080p30, even though both are 1080p. If you are streaming a mostly static devotional image, lofi artwork or a text panel, that does not change YouTube’s published recommendation for the selected mode; it may affect how much visible benefit you get from a higher bitrate, but the recommended mode is still a useful starting reference. For a playlist built from clips with different dimensions, check that the output really is the resolution and frame rate you intend: this guide to keeping a 24/7 stream in 1080p with mixed-resolution videos covers that separate issue.
YouTube’s broader guidance also recommends constant bitrate (CBR) and a two-second keyframe interval, with intervals not exceeding four seconds. These settings are not substitutes for choosing a viable bitrate, but they belong in the same review when you are diagnosing delivery. YouTube recommends RTMPS for encrypted delivery. Check the current official guidance when setting up a new encoder, because recommendations and interface details can change.
Account for upload capacity and headroom
A YouTube recommendation is a target for the incoming video, not evidence that your internet connection can sustain it. Measure or otherwise assess the upload connection used by the actual Restreamer machine and network path. A speed test on a different device, at a different time or over a different connection may not represent what the stream can use throughout the day.
The total stream needs more capacity than the video figure alone. Audio adds traffic, and the network path can vary. Other devices uploading files, cloud backups or routine use of the same connection can reduce what remains available. Leave room for these demands instead of setting the video target equal to the best upload result you have ever seen.
As practical troubleshooting guidance, Restream Help recommends keeping video bitrate no higher than half of the measured upload speed. That is Restream’s rule of thumb, not a YouTube requirement and not a guarantee for every connection. Use it as a conservative check: if the YouTube recommendation for your chosen mode exceeds what your path can sustain with suitable headroom, consider a lower resolution or frame rate, or improve the connection, rather than forcing the recommended number onto an unsuitable link.
For example, suppose your chosen H.264 mode calls for 14 Mbps in YouTube’s table, but the streaming path cannot reliably provide the capacity needed to carry that video plus audio and overhead. You have a choice to make: retain the resolution and accept that the path may be constrained, reduce the output mode and use its corresponding recommendation, or change the network conditions. There is no bitrate number that makes an under-capacity link equivalent to a faster one.
A wired Ethernet connection can remove some sources of wireless variation where it is practical, but it cannot fix every issue between the encoder and YouTube. If you run a 24/7 channel from a cloud machine, consider the capacity and limits of that machine’s connection as well as the computer at your desk. This cloud PC setup guide helps frame the choice of where a continuous stream runs; the relevant point here is to evaluate the connection that actually sends the video.
Check stream stability after applying a change
Test the stream before relying on the new setting for a long broadcast. YouTube Help says: “Make sure to test before you start your live stream. Tests should include audio and movement in the video similar to what you'll be doing in the stream.” A still image test may not reveal the same load or visual changes as a moving camera, scrolling text, animated background or music video. Include representative audio and motion, and observe the stream long enough to see whether the problem recurs.
Check YouTube’s stream health messages as well as the encoded bitrate. YouTube diagnostics can report issues such as high or low bitrate, long keyframe intervals or insufficient incoming video. Those messages help distinguish a bitrate mismatch from a different delivery problem. If YouTube reports a low incoming rate, inspect the encoder output and network path; if the bitrate appears appropriate but the stream still drops, investigate the connection and device load rather than continuing to raise the target.
If the stream is unstable, work through a short fault-finding sequence. First verify that Restreamer is encoding rather than copying if you expect the configured target to change the video. Next compare the selected codec, resolution and frame rate with YouTube’s recommendation. Then check whether upload capacity is available consistently and whether other traffic is competing for it. Finally inspect the encoder’s CPU use and the Restreamer and YouTube messages around the time of a disruption.
If the encoder is overloaded, lowering bitrate alone may not solve the underlying processing issue. Restream’s troubleshooting guidance suggests reducing bitrate, resolution or FPS when the encoding device is overloaded; those adjustments reduce different demands and should be tested individually. If network speed remains low, the same guidance suggests a wired Ethernet connection where possible. A drop can also arise elsewhere in the chain, so do not treat the first visible bitrate warning as proof that it is the only cause.
Keep a note of the old and new setting, the time of the test, the selected output mode and what YouTube reported. That makes it easier to reverse a change or compare a later test without relying on memory. For an always-on channel, schedule the test before a quiet period or use a separate test broadcast where appropriate, rather than discovering the effect during a devotional programme, local news loop or scheduled music stream.
When the recurring task is keeping a file-based channel running without leaving your own computer on, StreamNeo removes that specific overnight computer-running chore: you upload the video, provide the YouTube stream key and can switch your computer off while the channel runs. It is YouTube-only, and it does not change the need to choose a suitable source or check the stream’s health.
When copying the source unchanged is relevant
Copy mode is useful when the source video already has the properties you want to send and there is no need for Restreamer to re-encode it. Passing the source through unchanged avoids asking the Restreamer encoding process to create a new video stream. That can be relevant for a continuous channel where processing headroom is limited, provided the source format and outgoing delivery are suitable for your YouTube setup.
Copy mode also means the encoding bitrate field is not the lever for changing the outgoing video. If the source file or feed has a bitrate that is unsuitable for your connection, changing the encode target while still copying will not alter that video. You would need to choose an encoding path and set the output deliberately, or prepare a suitable source before streaming. The same distinction matters if you are troubleshooting a loop: an unchanged source carries its existing video characteristics forward, while an encoded output can be configured separately.
Use encoding when you need Restreamer to change the video output, and copy when preserving the source is the appropriate choice. Neither mode is universally better. A source that is already right for the channel may not benefit from another encode, while a source that needs a different resolution, frame rate or bitrate requires a transformation somewhere in the workflow. Check your version’s documentation and test the resulting broadcast before making the choice part of a 24/7 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
How do I change the video bitrate in Restreamer?
In the documented encoding settings, select H264 to expose the video encoding options, then set the Bitrate target. The option applies when Restreamer encodes the video; it does not change video passed through with the default copy codec.
What bitrate should I use for a stable YouTube live stream?
Use YouTube’s recommendation for the codec, resolution and frame rate you send, then check that your upload path can sustain the video, audio and overhead with room to spare. There is no single target that makes every stream stable. If the recommended mode exceeds your capacity, consider a lower output mode or a more capable connection.
Why does changing the bitrate appear to do nothing?
Check whether the video codec is still set to copy. In that mode, Restreamer passes the source video through unchanged, so the encoding bitrate control is not re-encoding it. Also confirm you changed the encoding option rather than viewing the bitrate shown in the publication or monitoring window.
What should I check if the stream still buffers?
Check YouTube’s stream health messages, the actual upload capacity of the streaming path and the encoder’s device load. Confirm the output mode and codec, then test with representative audio and movement. If the device is overloaded or the connection cannot sustain the target, lowering bitrate, resolution or frame rate may help, but the result needs to be tested.