For a standard SDR YouTube Live stream in OBS, use the AMD AMF hardware encoder available on your system, set rate control to CBR and set the keyframe interval to two seconds. Choose the bitrate from YouTube’s H.264 table for your output resolution and frame rate; AMF does not create a separate universal bitrate.
Those settings establish a sensible starting point, not a guarantee that a particular GPU, driver, upload connection or stream will perform well. Match the output to what you intend to broadcast, then test it with representative audio and movement before relying on it.
AMD AMF baseline for YouTube Live in OBS
AMF is AMD’s framework for hardware video encoding. If OBS offers an AMD hardware encoder on your system, you can select it for a YouTube broadcast; the available encoder choices and controls depend on the OBS build, GPU and driver. OBS documents AMD encoder support on Windows and Linux, but that does not mean every AMF option appears on every computer.
For the standard SDR workflow described here, H.264 is the straightforward starting codec. YouTube accepts several codecs, including H.264, HEVC and AV1, but choosing another codec involves the relevant ingest workflow and support in both your installed software and hardware. For a normal H.264 stream, set the bitrate according to YouTube’s resolution-and-frame-rate recommendations rather than a supposed AMF-specific preset.
In OBS, the controls are generally in the output settings for streaming, but exact labels and menu locations can vary between versions. Select the AMD encoder, then look for rate control, bitrate, keyframe interval and profile controls. If the expected encoder is missing, confirm that your GPU and installed driver are compatible with the OBS release you are using before changing unrelated settings. See OBS’s hardware encoding guide for its supported encoder information.
A common source of confusion is CQP. OBS’s AMD guidance in its Advanced Recording Settings Guide gives CQP and a CQ range of 16–23 for recording, alongside other recording settings. That is not YouTube’s live bitrate recipe. For a platform live ingest configuration, follow YouTube’s CBR guidance and set an actual bitrate. AMD’s rate-control documentation explains rate-control methods, but it does not establish one best live preset for every GPU and OBS version.
If you are setting up a long-running channel, encoder choices are only one part of making the broadcast practical. The content and operating arrangement matter too; for example, our guide to restreaming old videos to keep your YouTube channel live covers the separate question of looping existing material. First make sure the OBS output itself is configured for the stream you plan to send.
Select the intended output resolution and frame rate
Decide what resolution and frame rate the viewer should receive before choosing a bitrate. YouTube’s H.264 recommendations distinguish both: a 1080p30 broadcast and a 1080p60 broadcast do not have the same recommended ingest bitrate. Picking a higher frame rate or resolution changes the amount of video data you need to send, and it also changes the demands on the encoding and upload path.
In OBS, check the output resolution used for streaming rather than assuming the canvas resolution is what viewers receive. Also confirm the frames-per-second setting. If your source material is a still image, a devotional image with slow transitions, or a mostly static ambience scene, a higher frame rate may not add much to what the audience sees. A music performance, moving camera or fast-moving game may make a higher rate more relevant. These are content choices, not promises that one setting will look better on every display or connection.
You do not need to select the highest available output just because your hardware exposes it. A lower resolution or frame rate can be a more workable choice when the source is modest, the upload connection is constrained, or the GPU is already busy. Conversely, if your source and intended audience benefit from a higher output, check the corresponding bitrate and confirm that both the encoder and connection can sustain it.
Keep the output choice consistent while you test. If you change resolution or frame rate later, revisit the H.264 table and adjust the bitrate accordingly. This is particularly useful for a channel that alternates between a quiet loop and a more demanding live event: do not assume that a successful test of one scene validates a different output configuration.
Choose the corresponding H.264 bitrate
Use the recommended ingest bitrate in YouTube’s current H.264 table for the selected resolution and frame rate. The figures below are YouTube recommendations, not guarantees of picture quality or delivery stability. If your exact combination is not shown here, consult the full YouTube live encoder settings guidance rather than extrapolating from a nearby row.
| H.264 output | YouTube recommended ingest bitrate |
|---|---|
| 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 |
| 2160p (4K) at 30 fps | 42 Mbps |
| 2160p (4K) at 60 fps | 50 Mbps |
For example, if your intended output is 1080p60, the relevant YouTube recommendation is 17 Mbps. If it is 1080p30, the recommendation is 14 Mbps. The difference is a platform recommendation tied to those output modes, not an adjustment made because one configuration uses AMD AMF. Set the chosen value in OBS and make sure the connection can sustain it reliably.
YouTube also lists lower minimums in its table. A minimum should not be read as a target that suits every scene: the amount of movement and detail in your content affects the video data needed, while the connection has to carry the selected bitrate consistently. When uncertain, use YouTube’s published row for the mode you intend to send, then test it under conditions similar to the real broadcast.
Do not treat these figures as a promise about how the stream will appear to each viewer. YouTube processes the incoming stream, and viewers watch over connections and devices you do not control. Nor does choosing the table’s bitrate prove that your upload is adequate; a speed test is useful, but you should still observe an actual test stream for interruptions or dropped frames.
Set CBR and a two-second keyframe interval
For YouTube’s standard live guidance, set rate control to CBR and the keyframe interval to two seconds. YouTube says keyframes should be two seconds apart and not exceed four seconds. In OBS, the setting may be shown as a keyframe interval in seconds or in another version-dependent form; check the displayed meaning and confirm that the configured interval is two seconds.
CBR means the encoder aims to maintain the bitrate you set over the stream rather than varying it in the way a quality-based recording mode might. That makes it appropriate to YouTube’s stated live ingest guidance. It does not mean the connection itself is constant or that a stream cannot drop; it is a rate-control setting for the video encoder.
The distinction matters if you have followed an OBS recording tutorial. CQP is a quality-based rate-control mode listed in OBS’s AMD recording guidance, with a CQ range intended for that recording context. It does not specify a fixed YouTube ingest bitrate. Do not copy a recording CQ value into your live setup and assume it is equivalent to choosing a bitrate from YouTube’s table.
If OBS exposes additional controls such as profile, preset or B-frames, treat them as hardware- and version-dependent unless you have a specific reason to change them. The documented recording baseline is not evidence that those same values form a universally best streaming profile. Start with the controls YouTube specifies for live ingest, leave other choices at appropriate defaults when you are unsure, and validate the result.
Confirm encoder and connection capability
Before starting a public broadcast, confirm that OBS can use the AMD encoder and that the output settings persist after a restart. If the encoder option is absent or produces an error, check the OBS release, GPU compatibility and driver rather than assuming that every AMD graphics device exposes the same controls. OBS’s guide points to compatible GPU information; installed software and hardware determine what you can actually select.
The upload connection needs room to carry the video bitrate along with audio and other network traffic. YouTube recommends a reliable quality based on upload capacity and advises running a speed test. A speed test is a useful indication at one moment, not proof that the connection will remain unchanged overnight or when other people use the same network. Where possible, test from the same location and network arrangement you will use for the stream.
If you cannot reliably sustain the bitrate for your chosen mode, consider a lower output mode and use its matching row in YouTube’s table. Do not keep a high resolution and simply assume that a hardware encoder will compensate for a weak connection: encoding the video and transporting it to YouTube are different jobs. A compatible encoder may reduce the work done by the CPU, but it cannot make an unstable upload path stable.
YouTube supports RTMP and RTMPS for live input and recommends RTMPS. In YouTube Studio’s Live Control Room, select or create the stream and copy the server URL and stream key into OBS. Keep the key private, since it is what authorises software to send a broadcast to your channel. If YouTube does not allow your channel to go live, encoder changes will not resolve that account or access issue; see why YouTube may say live streaming is unavailable and check the current official account guidance.
HDR is a separate case, not a small adjustment to the standard SDR H.264 setup in this article. YouTube’s HDR instructions for OBS describe a workflow involving HEVC, a Main 10 profile, P010 colour format and Rec. 2100 PQ or HLG colour space options; the cited instructions recommend HLG. Only follow that route if the intended workflow and your GPU, encoder and OBS build expose the required choices. For ordinary SDR output, do not change colour settings to HDR just because your encoder supports hardware acceleration.
Test and monitor stream health
Make a private or unlisted test before relying on the configuration. Include audio and movement similar to the planned broadcast. A static screen with no sound may not expose the same issues as a music loop with visual transitions or a local news sequence with changing footage. YouTube explicitly advises testing with similar audio and movement before going live; its testing and stream-health guidance is worth checking before a scheduled event.
During the test, watch the stream preview in YouTube Studio’s Live Control Room and review stream-health messages. In OBS, open Statistics and look for dropped frames or encoder overload. These indicators point to different possible problems: network-related dropped frames suggest the delivery path needs attention, while encoder overload suggests the system may not be keeping up with the selected output or workload. Check the actual messages and conditions rather than treating any single indicator as a complete diagnosis.
Use the test to verify the full chain: the correct stream key and destination, audio reaching YouTube, the expected resolution and frame rate, and the intended picture appearing in the preview. Listen for clipped or missing audio as well as watching the image. If you change a setting to address a problem, run another test long enough to see whether the same conditions recur. A brief successful connection alone is not enough to validate a channel that is meant to run for hours.
For a channel that runs continuously, also decide how you will respond if the connection, computer or OBS session stops. OBS on your own machine needs that machine and its network connection to remain available. The operational question is separate from choosing the right AMF controls. For example, if the burden is keeping a computer running and restarting a broadcast after a drop, StreamNeo can take that specific repeat-running task off your local computer after you upload a video and connect your YouTube stream key; you still need to prepare the content and check the channel’s stream health.
A continuous playlist has different content and transition concerns from a one-off event. If you are preparing a loop of existing material, our guide to keeping a channel live by restreaming old videos may help with that separate workflow. For an event replay, the guide to keeping a conference live after it ends discusses the publishing choice; neither changes the need to test the encoder and output settings you use.
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
What are the best OBS settings for YouTube with an AMD GPU?
There is no single best AMF preset established for every GPU, driver and OBS version. For standard SDR H.264 live streaming, begin with CBR, a two-second keyframe interval and YouTube’s bitrate for your chosen resolution and frame rate, then test and monitor the broadcast.
What bitrate should I use for YouTube Live at 1080p60?
YouTube’s H.264 table recommends 17 Mbps for 1080p60. That is an ingest recommendation, not a guarantee that your connection can sustain it or that every viewer will see the same quality; test with your actual setup.
Should AMD AMF use CBR or CQP for streaming?
Use CBR for the standard YouTube live configuration described here, with bitrate selected from YouTube’s table. OBS’s CQP/CQ values for AMD are recording guidance and should not be treated as a live bitrate recommendation.
Can I use the same settings for HDR?
Not without checking YouTube’s separate HDR workflow. Its OBS instructions describe HEVC and particular profile and colour-format settings; use those only when your intended ingest path and hardware support them.