What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
For a 4K 60 fps YouTube Live stream on Linux, use NVENC with a constant-bitrate H.264 stream at YouTube’s recommended 50 Mbps, or HEVC at 35 Mbps if your workflow and hardware support it. Set a 2-second keyframe interval, use RTMPS, and verify that your GPU, driver, and FFmpeg build can sustain the chosen settings before going live.
Recommended 4K60 settings for YouTube Live
YouTube’s live encoder guidance recommends these rates for 2160p60: 50 Mbps for H.264 and 35 Mbps for HEVC or AV1. Its listed minimums are 14 Mbps and 10 Mbps, respectively. These are ingestion recommendations, not a guarantee that every scene will look equally good at the same rate.
| Setting | 4K60 starting point | Notes |
|---|---|---|
| Resolution and frame rate | 3840×2160, 60 fps | Use progressive video; confirm the input and output are actually 4K and 60 fps. |
| SDR codec and bitrate | H.264, 50 Mbps | YouTube’s recommended 2160p60 target; listed minimum is 14 Mbps. |
| Alternative SDR codec and bitrate | HEVC, 35 Mbps | YouTube’s recommended 2160p60 target; listed minimum is 10 Mbps. Hardware and ingest workflow must support it. |
| Rate control | CBR | YouTube recommends constant bitrate. |
| Keyframes | Every 2 seconds | At 60 fps, set GOP to 120 frames. YouTube recommends no more than 4 seconds. |
| B-frames | 2 | YouTube’s recommended advanced setting. |
| Reference frames | 1 | YouTube’s recommended advanced setting. |
| Protocol | RTMPS | YouTube recommends RTMPS for a secure connection. |
For SDR, use Rec. 709 color and an 8-bit workflow. For HDR, the codec and pixel format need to match the source and its metadata; the HDR path is covered below.
Check the Linux, GPU, and input before encoding
NVENC settings only work when the installed GPU, driver, and FFmpeg build expose the requested encoder and capabilities. Do not assume that every NVIDIA GPU can encode 4K60 with every preset in real time.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →#1 Best Overall
- AI Performance: 767 AI TOPS
- OC mode: 2632 MHz (OC mode)/ 2602 MHz (Default mode)
- Powered by the NVIDIA Blackwell architecture and DLSS 4
- Axial-tech fan design features a smaller fan hub that facilitates longer blades and a barrier ring that increases downward air pressure
- A 2.5-slot design maximizes compatibility and cooling efficiency for superior performance in small chassis
- Confirm GPU and driver visibility: run
nvidia-smi. Resolve driver or device visibility problems before testing FFmpeg. - Check the installed FFmpeg encoders: run
ffmpeg -encoders | grep nvenc. Look forh264_nvencfor the H.264 template orhevc_nvencfor HEVC. - Inspect local encoder options: run
ffmpeg -h encoder=h264_nvencorffmpeg -h encoder=hevc_nvenc. Option support varies by FFmpeg build and GPU. - Inspect the input: use
ffprobe INPUTto check video dimensions, frame rate, audio streams, and format. Adjust stream mapping if there is no audio stream or the desired stream is not the first one. - Check upload capacity: the encoder needs to send its target bitrate continuously, with additional headroom for network variation and audio. A connection that only barely reaches the video rate is not a reliable basis for a live event.
- Get private ingest details from YouTube: use the RTMPS ingestion address and stream name/key provided for your stream. Keep the key private.
SDR H.264 command for a file input
This is a starting template for a pre-recorded file, not a command tested against every Linux distribution or GPU. Replace INPUT with the input path and replace the ingest placeholder with the RTMPS address and stream key shown in YouTube Studio. Avoid putting a real key in public logs, shell history, or a script shared with others.
ffmpeg -re -i INPUT
-map 0:v:0 -map 0:a:0?
-c:v h264_nvenc -preset p5 -tune hq
-rc cbr -b:v 50M -maxrate 50M -bufsize 100M
-g 120 -bf 2 -profile:v high
-pix_fmt yuv420p -r 60
-c:a aac -b:a 128k -ar 44100
-f flv "RTMPS_INGEST_URL/STREAM_KEY"What the command does
-rereads a file at real-time pace instead of sending it as fast as possible. It is appropriate for file input; live capture sources may require different input options and pacing.-map 0:v:0 -map 0:a:0?selects the first video stream and the first audio stream if one exists. Remove or change the audio mapping if the intended audio is elsewhere.-c:v h264_nvencselects NVIDIA’s H.264 encoder.-preset p5 -tune hqis a conservative starting point, not a universal best setting. Use a higher-quality preset only if the specific system can encode sustained 4K60 in real time.-rc cbr -b:v 50M -maxrate 50Mconfigures a constant 50 Mbps video target, matching YouTube’s recommended H.264 rate for 2160p60.-bufsize 100Mis an illustrative two-second live VBV buffer at 50 Mbps. YouTube’s guidance does not mandate this buffer value.-g 120sets a 120-frame GOP, equivalent to two seconds at 60 fps.-bf 2sets two B-frames.-profile:v high -pix_fmt yuv420pselects a common 8-bit H.264 SDR combination. Make sure it matches the source and the actual encoder’s capabilities.-r 60requests 60 fps output. It does not guarantee that a non-60-fps input becomes smooth 60 fps; inspect the source and consider the effect of frame duplication or conversion.-c:a aac -b:a 128k -ar 44100encodes AAC audio at 128 kbps and 44.1 kHz. Confirm that this is appropriate for the source audio and check audio during a private stream test.-f flvuses the streaming container expected by this RTMP/RTMPS-style output.
YouTube recommends two B-frames and one reference frame. The command sets the former; reference-frame control is encoder- and build-dependent. Check ffmpeg -h encoder=h264_nvenc for the supported option on your installed build rather than adding an unverified flag.
Rank #2
- Powered by the NVIDIA Blackwell architecture and DLSS 4
- Powered by GeForce RTX 5070 Ti
- Integrated with 16GB GDDR7 256bit memory interface
- PCIe 5.0
- WINDFORCE cooling system
HEVC for SDR: when and how to use it
YouTube’s recommended HEVC bitrate for 2160p60 is 35 Mbps, lower than its H.264 target. If your GPU, FFmpeg build, and YouTube ingest workflow support HEVC, change the video encoder to hevc_nvenc and set -b:v 35M -maxrate 35M. Keep CBR and a two-second GOP (120 frames at 60 fps). Select a pixel format and HEVC profile supported by the installed encoder and appropriate to the source; check the local encoder help rather than copying H.264-only profile or pixel-format settings blindly.
NVIDIA’s Video Codec SDK 13.1 FFmpeg documentation includes a 4K60 HEVC live example with a 20 Mbps target, a 40 Mbps VBV buffer, GOP 120, B-frames, lookahead, and split encoding. That example is NVIDIA’s encoder guidance, not YouTube’s current recommended HEVC ingest rate; for a YouTube-bound stream, use YouTube’s 35 Mbps target unless you have a deliberate bandwidth constraint.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallRank #3
- Powered by the NVIDIA Blackwell architecture and DLSS 4. System Requirements: Minimum 850W PSU with 16-pin 12V-2x6 (12VHPWR) connector required. Verify before purchasing.
- Military-grade components deliver rock-solid power and longer lifespan for ultimate durability. Compatibility: 348mm (13.7") length, 3.6 slots, 4.3 lbs. Confirm case clearance and slot spacing. GPU bracket included.
- Protective PCB coating helps protect against short circuits caused by moisture, dust, or debris
- 3.6-slot design with massive fin array optimized for airflow from three Axial-tech fans
- Phase-change GPU thermal pad helps ensure optimal thermal performance and longevity, outlasting traditional thermal paste for graphics cards under heavy loads
HDR requires a different, source-matched path
Do not treat HDR as a quality toggle or paste HDR color flags into an SDR command. YouTube’s live encoder settings specify HEVC for HDR and 10-bit HDR, and list Rec. 709 for SDR. The page does not support AV1 for HDR. NVIDIA’s YouTube HDR guidance specifies HEVC Main 10 and Low or Normal latency, not Ultra Low.
Use HEVC Main 10 only when the source is genuinely HDR and its transfer function, primaries, range, and metadata are known and preserved correctly through the pipeline. The correct flags depend on the actual input; incorrect signaling can make HDR appear washed out or otherwise wrong. Check the input metadata and conduct a private test stream on the target playback devices before an event.
Rank #4
- Powered by the NVIDIA Blackwell architecture and DLSS 4
- Powered by GeForce RTX 5060
- Integrated with 8GB GDDR7 128bit memory interface
- PCIe 5.0
- WINDFORCE cooling system
Latency, preset, and quality trade-offs
| Choice | What it changes | How to decide |
|---|---|---|
| H.264 vs. HEVC/AV1 for SDR | YouTube lists different 2160p60 bitrate targets: 50 Mbps for H.264 and 35 Mbps for HEVC or AV1. | Choose a codec supported by the GPU, FFmpeg build, and ingest workflow. A lower target is not automatically better if compatibility or image quality suffers. |
| SDR vs. HDR | SDR uses the Rec. 709 path; HDR requires 10-bit HEVC and correct source color signaling. | Match the actual content and capture pipeline, not the desired label. |
| Quality preset vs. faster preset | Higher-quality presets can increase encoding work; a faster preset can reduce that load. | Use the best preset that sustains real-time output on your specific GPU during a representative test. |
| Latency vs. quality | Latency choices change the encoder’s operating trade-offs. YouTube classifies 4K streams as normal latency. | Do not choose Ultra Low latency for the NVIDIA YouTube HDR path; NVIDIA specifies Low or Normal for HDR. |
The YouTube bitrate figures describe its receiving recommendations, not a performance benchmark for a particular GPU. Official guidance does not establish which Linux GPU model will sustain 4K60 with a given preset. Test the actual configuration under sustained load.
Test the stream before the event
- Start with a private or otherwise non-public test stream using the same resolution, codec, preset, keyframe interval, audio, and network path planned for the event.
- Choose a representative section with motion and detail. A static desktop or title card does not expose the same encoder and bitrate demands as fast movement.
- Watch FFmpeg output for encoder errors, dropped frames, or failure to keep up with real time. Monitor the GPU and system load while the stream runs.
- Check YouTube’s stream health and listen to the audio on a separate playback device. YouTube recommends testing audio and representative motion and monitoring stream health.
- If the test is unstable, change one variable at a time: first verify the upload connection and input frame rate, then try a faster preset or a lower supported output target, and repeat the test.
Troubleshooting common failures
| Symptom | Likely cause | What to check or change |
|---|---|---|
| “Unknown encoder” or no NVENC encoder listed | FFmpeg build lacks the encoder, or the expected encoder name is unavailable. | Check ffmpeg -encoders, install/use a build with NVIDIA hardware-encoding support, and inspect the exact encoder help. |
| NVENC initialization or device error | GPU/driver visibility problem, unsupported feature, or incompatible build/options. | Run nvidia-smi; confirm the GPU supports the codec, profile, bit depth, and resolution; remove unsupported options identified by local encoder help. |
| Encoder cannot keep up or frames drop | The selected GPU and preset cannot sustain the requested workload, or the input is not behaving as expected. | Check sustained GPU load and input properties; use a faster preset and test again. Do not infer a universal 4K60 capability from the NVENC brand alone. |
| YouTube reports unstable or insufficient stream | Upload bandwidth variation, bitrate mismatch, or dropped output. | Check stream health and the connection under sustained load. Ensure the video target matches the selected codec’s YouTube recommendation and leave network headroom. |
| Wrong dimensions or frame rate | Input properties or output conversion do not match the intended 3840×2160 at 60 fps. | Inspect with ffprobe; confirm the source, mapping, and frame-rate conversion rather than relying on -r 60 alone. |
| No audio or wrong audio | The input has no first audio stream, or the desired track is mapped differently. | Inspect audio streams with ffprobe, change the map, and listen during a private test. The ? in the template makes audio mapping optional; it does not create audio. |
| HDR appears washed out or incorrect | Color metadata, transfer function, bit depth, or source format was signaled incorrectly. | Verify the source is HDR, preserve correct metadata, use the HEVC Main 10 workflow, and test on the intended playback path. |
| Stream key rejected or stream does not connect | Wrong or outdated ingest address/key, malformed output URL, or an account-specific setup issue. | Copy the current RTMPS address and stream key from YouTube, keep the key private, and verify the destination in YouTube Studio. |
Or let it run in the cloud
If the goal is an always-on YouTube channel playing uploaded video, rather than a live camera or desktop capture, StreamNeo is a cloud alternative: upload a recording or build a playlist, add your YouTube stream key once, and go live. The cloud keeps it running without a computer, OBS, or home connection staying on. It supports video as uploaded up to 4K 60fps at one flat price per slot, with automatic recovery if YouTube drops the stream. The first day is free with no card; the Monthly price is $9.99 per month. UPI and cards are available in India, and cards are accepted worldwide. Learn more at StreamNeo, or start the free first day.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsBest Value
- Powered by the NVIDIA Blackwell architecture and DLSS 4 OC mode: 2640MHz/Default mode: 2610MHz (Boost Clock)
- Military-grade components deliver rock-solid power and longer lifespan for ultimate durability
- Protective PCB coating helps protect against short circuits caused by moisture, dust, or debris
- 3.125-slot design with massive fin array optimized for airflow from three Axial-tech fans
- Phase-change GPU thermal pad helps ensure optimal thermal performance and longevity, outlasting traditional thermal paste for graphics cards under heavy loads
Frequently Asked Questions
Does this command work with a live camera input?
The example is for a file input paced with -re. A capture device needs its own input syntax and should be tested with the same output settings.
Can I use AV1 instead of H.264 or HEVC?
YouTube lists a 35 Mbps recommendation for AV1 at 2160p60, but AV1 support depends on the specific GPU, FFmpeg build, and ingest workflow. YouTube’s cited settings do not support AV1 for HDR.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
