Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows 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 reinstallFor a YouTube upload encoded with FFmpeg on a Hetzner VPS, choose the output resolution and frame rate to suit your source, then use YouTube’s SDR bitrate recommendations as a starting reference. YouTube recommends H.264 in MP4, progressive video, variable bitrate (VBR), 4:2:0 chroma subsampling, and keeping the source frame rate. The recommended bitrates are not caps: YouTube says no bitrate limit is required. YouTube’s upload encoding guidance is the reference for the settings below.
Choose resolution and bitrate
The figures below are YouTube’s current SDR upload recommendations, accessed in 2026. They are reference rates for an uploaded file, not a guarantee of visual quality or a mandatory maximum. Use the row that matches your intended output and the frame-rate class.
| Output resolution | 24, 25, or 30 fps | 48, 50, or 60 fps |
|---|---|---|
| 720p | 5 Mbps | 7.5 Mbps |
| 1080p | 8 Mbps | 12 Mbps |
| 1440p | 16 Mbps | 24 Mbps |
| 2160p (4K) | 35–45 Mbps | 53–68 Mbps |
Choose the output from the source and viewing goal rather than upscaling automatically. YouTube’s standard computer aspect ratio is 16:9, but its player adapts to vertical and square uploads. Preserve the source’s aspect ratio; a universal scaling expression would be unsafe without knowing its dimensions and intended framing.
Translate YouTube’s settings into FFmpeg options
Bitrate units and rate control
FFmpeg’s generic -b option is expressed in bits per second. For example, YouTube’s 8 Mbps reference corresponds to -b:v 8M for a video stream. The precise rate-control options depend on the encoder you select; consult the options supported by the installed FFmpeg build rather than assuming every encoder handles bitrate in the same way. YouTube recommends VBR and does not require a bitrate cap.
#1 Best Overall
Video format and frame rate
Use H.264 video in an MP4 container, progressive scan, and 4:2:0 chroma subsampling as the general upload target. Keep the encoded frame rate the same as the recorded source when possible; YouTube lists common rates from 24 through 60 fps. Interlaced material should be deinterlaced before upload. Avoid forcing a new frame rate or resolution without a reason, since the correct filter and conversion depend on the input.
Color, audio, and MP4 layout
For SDR, YouTube recommends BT.709. Unsupported color spaces may be converted by YouTube, but the exact conversion depends on source metadata and workflow. YouTube’s guidance lists AAC-LC or Opus audio at a 48 kHz sample rate. For MP4, its general recommendations include fast start, with the moov atom at the beginning of the file.
Build a command around your actual source
There is no single safe command for every video: scaling depends on the input’s dimensions, aspect ratio, and desired output, while rate control varies by encoder. Start by inspecting your installed FFmpeg and the file, then specify only the transformations you need.
- Check the available encoders and their options in your FFmpeg build. Confirm that the chosen encoder supports the rate-control settings you intend to use.
- Identify the source resolution, frame rate, scan type, aspect ratio, color characteristics, and audio sample rate. Use these properties to decide whether scaling, deinterlacing, or color conversion is necessary.
- Select a target resolution and frame-rate category, then choose the matching YouTube bitrate reference from the table. Convert Mbps to FFmpeg’s bits-per-second form, such as
8Mfor 8 Mbps. - Configure the selected encoder for H.264 and VBR using that encoder’s documented options. Set the output container to MP4, keep the source frame rate if practical, and provide compatible audio.
- Encode a representative segment or file on the VPS and check playback, dimensions, frame rate, audio, and output file size before committing to a large batch.
Do not treat a bitrate setting as a promise of quality: motion, source quality, encoder, and rate-control behavior all affect the result. A higher target bitrate can increase file size and transfer time without restoring detail absent from the source.
What a Hetzner VPS changes
Encoding time depends on CPU allocation and workload
Encoding video is CPU-intensive. Hetzner says shared-resource plans distribute CPU resources among instances and may burst above baseline. Its CCX dedicated-resource instances provide exclusive CPU resources; Hetzner recommends them for CPU-intensive applications and predictable production workloads. That distinction does not establish an encode time for any particular plan. Benchmark the actual input, codec, preset, output resolution, and concurrent workload on the VPS you will use. Hetzner Cloud FAQ
Budget for outgoing traffic
The encoded file must still be transferred to YouTube. Hetzner’s traffic documentation lists 20 TB for EU CX, CPX, and CAX Cloud Servers, while CCX allowances vary by region and plan; these are figures published on Hetzner’s page in 2024, not a universal allowance for every VPS. Verify the current outgoing traffic allowance for your exact product and location before planning repeated or large uploads. Hetzner Cloud traffic information
Common problems and fixes
- The upload looks softer than expected: Check the source quality, chosen output dimensions, and bitrate reference for the actual frame rate. YouTube’s figures are recommendations, not quality guarantees; increasing bitrate cannot recreate missing source detail.
- The command rejects a bitrate option: The option may not apply to the selected encoder. Check the installed encoder’s supported options and use its documented rate-control controls.
- The output has the wrong shape or black bars: Revisit the source dimensions and aspect ratio before choosing a scale filter. There is no universal scaling expression for arbitrary input.
- Color changes after upload: Check the source color metadata and SDR target. YouTube recommends BT.709 for SDR, but conversion results depend on the input and workflow.
- Encoding is unexpectedly slow: Measure the same input and settings on the target VPS. Shared CPU allocation, the selected encoder and preset, resolution, and concurrent tasks can change encode time.
- Repeated uploads run into traffic limits: Check the allowance for the precise Hetzner plan and region instead of relying on another product family’s published figure.
Or let it run in the cloud
If the goal is to keep uploaded documentaries playing as a YouTube live stream, rather than prepare an upload file, StreamNeo is a separate cloud option: upload a recording or build a playlist, add your YouTube stream key, and go live. Your computer and home connection do not have to stay on. It streams the uploaded video as made, 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 required.
Monthly pricing is $9.99 per month. StreamNeo plays uploaded videos to YouTube; it does not stream from a camera. See StreamNeo, or start the free first day.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →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.
