If you are uploading a finished video to YouTube, export it as a high-quality MP4 with H.264 video, progressive scan, and a frame rate that matches the recording. Choose variable bitrate using YouTube’s upload recommendations for your resolution and frame-rate band.
A live broadcast is a different job: it sends a real-time feed to YouTube’s ingest service, so live encoder settings such as constant bitrate apply there, not to a prerecorded upload. First decide which workflow you are configuring; the settings below keep the two separate.
First decide: upload or live broadcast?
The word “streaming” can mean either watching a video over the internet or sending a live broadcast. For encoding, the useful question is: are you uploading a finished file, or configuring a live stream that will be sent to YouTube as it happens?
An upload is a file that you render or export, then submit through YouTube. YouTube processes that file into versions for playback. The file does not need to maintain a live connection to your computer, and upload guidance does not call for live-style constant bitrate. For a normal finished video, use variable bitrate and the upload recommendations for its output resolution and frame rate.
A live broadcast is encoded as it is captured or played and transmitted to YouTube’s live ingest. The encoder must keep sending a stream in real time; YouTube’s live settings specify constant bitrate (CBR), supported ingest codecs and protocols, and a keyframe interval. Those recommendations belong to the live workflow only.
This distinction matters for a 24/7 channel. A recorded bhajan programme that you upload as a video uses the upload profile. Sending a continuous feed from OBS to YouTube Live uses the live profile, even if the pictures and music were recorded earlier. If you are planning to build a channel around previously recorded lessons, this guide to running recorded coaching lessons as a continuous stream covers the broader channel workflow; it does not change the encoding rules for each file or live feed.
Recommended export format for prerecorded uploads
For most standard uploads, set the export container to MP4 and video codec to H.264. YouTube’s recommended upload profile also specifies progressive scan, 4:2:0 chroma, variable bitrate, and a frame rate matching the footage. These are recommendations, not a claim that any file outside the profile will automatically be rejected. See YouTube’s recommended upload encoding settings when configuring a particular export panel, as controls and labels differ between editing applications.
The profile lists High Profile H.264, CABAC, two consecutive B frames, and a closed GOP with a GOP length of half the frame rate. Many editing tools expose some of these as advanced codec or keyframe options; others handle them in a preset. If your application offers the relevant settings, follow the YouTube profile. If it does not, prioritise a compatible H.264 MP4, the correct dimensions and frame rate, and suitable quality rather than abandoning an otherwise sound export to chase a label you cannot find.
For audio, YouTube’s upload guidance lists AAC-LC, Opus, or Eclipsa Audio, with a 48 kHz sample rate. Its recommended audio bitrates are 384 kbps for stereo and 512 kbps for 5.1; mono is listed at 128 kbps. Use the channel layout that matches your mix. A stereo devotional recording, for example, should not be exported as 5.1 simply because the option is present.
Choose the export colour settings with the source and delivery format in mind. YouTube recommends BT.709 for SDR uploads. Keep the transfer characteristics, colour primaries, and matrix consistent with the way the video was mastered; YouTube warns against using an RGB colour matrix. Incorrect metadata can cause a colour shift even where the encoded pixels appear sound in your editor.
HDR is not simply an SDR export with a different label. YouTube’s HDR guidance calls for correct metadata, including the relevant PQ or HLG transfer function, Rec. 2020 primaries, and Rec. 2020 non-constant-luminance matrix. It lists MOV, MP4, and MKV containers and recommends 10-bit-capable codecs such as VP9 Profile 2, AV1, or HEVC/H.265. If you did not master the source as HDR or cannot verify its metadata, do not mark an export as HDR just to seek a higher quality option. Check YouTube’s HDR upload guidance against the source and editor you are using.
You can usually make these choices in the export panel of the editor you already use. Look for format or container, video codec, frame size, frame rate, bitrate mode, audio sample rate, and colour space. A command-line tool such as FFmpeg can expose more control, but it also asks you to account for the source’s video and audio streams and colour handling. Without knowing those details, copying a generic command is more likely to change something unintended than to improve the file.
Match frame rate and use progressive scan
YouTube’s guidance is to encode and upload at the frame rate at which the content was recorded. If you recorded at 25 fps, keep 25 fps in the export; if the material was recorded at 50 fps, keep 50 fps. Do not convert a source to 60 fps merely because the number sounds higher. Changing the frame rate can create duplicated or blended frames, or discard motion information, without adding detail that was not captured.
The same principle applies to resolution and aspect ratio. Export at the resolution you actually intend to publish, and preserve the source’s native shape. YouTube describes 16:9 as the standard ratio for its computer player, but its player adapts to vertical and square video. Avoid adding black bars solely to force a vertical or square source into 16:9; the bars become part of the image and do not improve the underlying composition.
Use progressive scan for the upload. If your source is interlaced, deinterlace it before uploading rather than expecting the platform to reconstruct the intended motion from interlaced fields. This is particularly worth checking with older camera footage or a file exported from a broadcast workflow. Preview a moving section after deinterlacing: edges and motion should look coherent, not comb-like or unnaturally soft.
Frame rate, resolution, and source quality work together. A clean 1080p source at its recorded frame rate can make a better upload than an upscaled file labelled 4K. An export cannot restore detail lost through a poor original recording, heavy compression, or repeated re-encoding. If you prepare a playlist from videos with different dimensions, the choices for a single live canvas are a separate issue; the OBS canvas and output-resolution guide for mixed playlists explains that live layout problem.
Choose bitrate from YouTube’s recommendation table
For a prerecorded upload, use YouTube’s upload bitrate table as a quality target for the output resolution and frame-rate band. Do not substitute the live CBR table. The recommendations below are for SDR uploads and are listed on YouTube’s site as accessed in 2026; the page does not state a publication date.
| Output resolution | 24, 25 or 30 fps | 48, 50 or 60 fps |
|---|---|---|
| 720p | 5 Mbps | 7.5 Mbps |
| 1080p | 8 Mbps | 12 Mbps |
| 1440p (2K) | 16 Mbps | 24 Mbps |
| 2160p (4K) | 35–45 Mbps | 53–68 Mbps |
| 8K | 80–160 Mbps | 120–240 Mbps |
These are recommendations, not minimum upload gates. YouTube’s broader format guidance says there is no recommended minimum bitrate because the appropriate bitrate depends on codec; it advises optimising for frame rate, aspect ratio, and resolution. If an export dialog presents a bitrate range, use the matching row as your starting point, then consider whether the source can make meaningful use of that output size. More bitrate cannot recover missing source detail.
HDR upload recommendations differ from SDR. As listed on YouTube’s site in 2026 (accessed; publication date not stated), HDR guidance recommends 10 Mbps for 1080p at 24/25/30 fps and 15 Mbps at 48/50/60 fps; for 2160p, it gives 44–56 Mbps and 66–85 Mbps respectively. Do not use the SDR figures for an HDR master, and do not use the HDR table if your material is SDR. YouTube does not support its listed HDR upload targets at 480p or 360p.
The practical control is variable bitrate (VBR), not a fixed live transmission rate. Depending on the editor, you may see a target bitrate, a maximum bitrate, or a one-pass/two-pass choice. Use the YouTube table to guide the output quality setting for the relevant frame-rate band. A complex scene with foliage, confetti, or fast camera movement may need more data to preserve detail than a mostly static image, but the platform’s recommendation remains a useful starting point rather than a promise about the final playback rendition.
Audio has its own settings and should not be folded into the video bitrate figure. A 48 kHz stereo mix at YouTube’s recommended 384 kbps is distinct from the video stream’s Mbps recommendation. Keep the source mix clean and set the right channel layout; raising the video bitrate will not repair clipped or noisy audio.
Why YouTube re-encodes uploads
YouTube says it always re-encodes uploaded videos to optimise playback. That means the exported file is a source for platform processing, not necessarily the file viewers receive unchanged. YouTube creates playback versions suited to different circumstances; a good upload gives that processing a sound image, motion cadence, audio track, and metadata to work from. Its video and audio formatting specifications describe this re-encoding in the context of partner delivery guidance.
This is why choosing the largest bitrate available is not a complete quality strategy. If the export is an upscaled 1080p image, has the wrong frame rate, or carries incorrect colour metadata, a very high bitrate does not correct those choices. Start with a well-mastered source, preserve its aspect ratio and recorded frame rate, select an appropriate resolution, and then use the bitrate recommendation for that output.
Processing time can also affect what you see after uploading. YouTube notes that higher resolutions can take several hours to process. Early playback may offer fewer quality options than expected, and some devices or browsers may limit the available playback quality. Do not immediately re-export a sound file because its highest resolution is missing moments after upload; check its processing status and allow time for the versions to appear.
For a channel that repeats an existing file, the same logic still applies: the quality of the prepared source matters, but repeated exports can compound compression. Keep a high-quality master, and encode delivery copies from that master rather than repeatedly encoding an already compressed copy. If you are planning an always-on radio format from your own recordings, the article on running a continuous YouTube radio of your own tracks discusses the channel format; this upload guidance remains useful for preparing the tracks or programme file.
Live encoder settings are a separate workflow
For a live broadcast, configure the encoder for real-time ingest rather than applying the upload preset. YouTube Live recommends CBR and supports H.264, HEVC/H.265, or AV1 for RTMP/RTMPS ingestion, subject to its current settings. Its live guidance recommends RTMPS and a keyframe interval of two seconds, with an interval that must not exceed four seconds. Check YouTube’s live encoder settings before an event because the recommendation depends on resolution, frame rate, codec, and the current ingest options.
Live bitrate figures below are examples of YouTube’s recommendations for live ingestion, not upload targets. YouTube’s live settings table lists H.264 at 14 Mbps for 1080p30 and 17 Mbps for 1080p60; for 4K it lists 42 Mbps at 30 fps and 50 Mbps at 60 fps. For AV1 or H.265, the corresponding recommendations are 10 and 12 Mbps at 1080p30 and 1080p60, and 30 and 35 Mbps at 4K30 and 4K60. These figures are listed on YouTube’s site as accessed in 2026, with no page publication date stated. Consult the full live table for other resolutions and frame rates rather than extrapolating.
The difference between VBR for a file and CBR for a live feed follows from the jobs they do. A file can vary the data it uses across easy and difficult scenes; the receiver can process the completed file after upload. A live encoder has to send a continuous feed at a controlled rate to the ingest connection. Use the live bitrate recommendation for the specific codec and output mode, and ensure your internet connection can sustain the outgoing stream. A live connection that cannot consistently carry its configured rate can drop frames or disconnect; choosing a lower supported live output may be more practical than forcing a higher one.
Test the whole live path before relying on it overnight or during an event. Check that the correct stream key is selected, the picture is visible, audio is present and at a sensible level, and YouTube receives a stable feed. For a continuous channel, a restart plan matters as well as picture settings; the guide to creating a continuous YouTube livestream with a browser-based service covers a different operating approach from exporting and uploading a video.
StreamNeo removes the need to keep your own computer on to replay an uploaded file as a continuous YouTube broadcast: you upload the file once and provide your YouTube stream key, so the encoding and computer-availability problem is not an overnight task on your desk. It is a YouTube-only workflow; it does not replace an editor for preparing the source file, and the upload still needs appropriate export settings.
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 encode a video for YouTube?
For a standard prerecorded upload, export a high-quality MP4 with H.264 video, progressive scan, and the frame rate used in the recording. Use variable bitrate and consult YouTube’s upload recommendations for your chosen resolution and frame-rate band. Keep the audio, aspect ratio, and colour metadata appropriate to the source.
What bitrate should I use for 1080p or 4K?
For SDR uploads at 24, 25, or 30 fps, YouTube recommends 8 Mbps for 1080p and 35–45 Mbps for 4K. At 48, 50, or 60 fps, the recommendations are 12 Mbps and 53–68 Mbps respectively. Those upload figures are not live CBR settings; check the live table separately if you are broadcasting.
Should I use CBR or VBR for YouTube?
Use VBR for a prerecorded upload, following the upload guidance and bitrate table. Use CBR for a live broadcast, with a bitrate selected from YouTube’s live table for the chosen codec, resolution, and frame rate. The workflows have different requirements, so do not carry the live CBR instruction over to a file export.
Why does my upload not show its highest quality straight away?
YouTube processes uploads into playback versions, and it notes that higher resolutions can take several hours to process. Some devices and browsers may also offer fewer playback-quality options. Check processing status and allow time before deciding that a correctly exported file needs to be uploaded again.