For most SDR uploads, export a progressive MP4 using H.264, BT.709 colour, the source recording’s frame rate and natural aspect ratio, and AAC-LC audio at 48 kHz. Use YouTube’s bitrate table as a reference for your resolution and frame-rate class, not as an exact setting you must hit.
That gives you a practical starting point without changing footage unnecessarily. The guidance below separates YouTube’s recommendations from choices that depend on your project; it concerns uploaded video files, not live-stream encoder settings.
A practical YouTube upload preset
For a typical SDR video edited for YouTube, start with these export choices:
| Editor setting | Practical default | What to check |
|---|---|---|
| Container | MP4 | Choose a standard MP4 export, with Fast Start if your editor offers it. |
| Video codec | H.264 | Use progressive scan and the editor’s normal high-quality H.264 profile. |
| Frame rate | Same as the recording | Do not convert 25 fps footage to 30 fps just because that option is prominent. |
| Frame shape | Same as the source | Keep vertical, square or widescreen footage in its original shape. |
| SDR colour | BT.709 | Confirm that the export is tagged for the way the project was mastered. |
| Video bitrate | YouTube’s reference for the output | Treat its table as a guide, not a mandatory minimum or quality guarantee. |
| Audio | AAC-LC, 48 kHz | Choose stereo or another channel layout that matches your soundtrack. |
This preset is meant to make the editor’s export dialogue manageable. YouTube lists further H.264 details, including High Profile, CABAC, variable bitrate and 4:2:0 chroma subsampling, but many editors select sensible codec details automatically. If those options are exposed, you can use YouTube’s recommendations; you do not need to hunt down every advanced control before an ordinary upload.
A 1080p SDR video recorded at 30 fps is a straightforward example: export 1920×1080 progressive at 30 fps, use BT.709, and consult the standard-frame-rate 1080p reference of 8 Mbps. For a 1080p recording made at 60 fps, use 60 fps and consult the high-frame-rate reference of 12 Mbps. Those figures are recommendations, not a pass-or-fail threshold.
The useful distinction is between preserving the project and matching YouTube’s recommendation. Your export should represent the source honestly; bitrate is a practical encoding choice within that aim. If a setting is unavailable in your editor, a sensible standard export is generally more useful than delaying an upload to chase a named profile.
Choose an MP4 container and H.264 video
A container is the file format that holds the video and audio streams and their timing information. YouTube recommends MP4 as the container and H.264 as the video codec for uploads. They are common export choices, and most editing software can create them without a separate conversion step.
YouTube’s recommended H.264 details include progressive scan, High Profile, two consecutive B frames, a closed GOP whose length is half the frame rate, CABAC, variable bitrate and 4:2:0 chroma subsampling. These specifications can appear as codec or advanced export options. They are useful if you are configuring an encoder directly, but not every editor exposes each one, and you should not assume that a missing control means the file is unusable.
For a routine export, select MP4 and H.264, then inspect the rendered file or editor summary to confirm the broad choices. YouTube also advises against edit lists in the MP4 and recommends placing the moov atom at the beginning of the file, often labelled “Fast Start”. If your software has a Fast Start option, enabling it is a practical choice. If it does not, the important first check remains that the export completes and uploads correctly.
Do not confuse an upload codec with a live-stream protocol. A pre-recorded file is encoded, uploaded and processed as a video; a live broadcast sends a continuing signal under a different set of constraints. For a looped broadcast, the export may still be useful as source material, but the live encoder has its own settings. The distinction matters if you are following a guide such as how to stream a video file to YouTube Live without OBS: do not transfer live bitrate advice into an upload export without checking which workflow it describes.
H.264 is a good default, not a reason to re-encode a file repeatedly. Each lossy encode can discard detail, so, where possible, export once from the editing project rather than exporting a compressed file and then compressing that output again. If you receive a source in another format, check whether your editor can import it and create the final MP4 directly.
Preserve frame rate and aspect ratio
YouTube’s recommendation is to encode and upload at the frame rate in which the content was recorded. If the source is 24, 25, 30, 48, 50 or 60 frames per second, keep that rate unless your project has a specific reason to change it. YouTube also accepts other frame rates; the common values are examples, not a requirement to convert unusual footage.
Changing frame rate can create duplicated or blended frames, or require the editor to discard frames. That may make motion look less natural, especially in a camera pan or a moving subject. A 25 fps devotional recording does not become better merely because an export menu offers 30 fps. Match the project timeline to the source where practical, and check the exported file’s properties if you are unsure what the editor selected.
Interlaced footage is the exception to the simple preserve-everything rule: YouTube says to deinterlace it before upload. Its example converts 1080i60 to 1080p30. If you have old interlaced footage, use your editor’s deinterlace setting and inspect movement in the result; do not apply that conversion to progressive footage simply because it appears in the guidance.
For shape, use the natural aspect ratio of the source. The standard computer player ratio is 16:9, but YouTube’s player adjusts for other shapes, including vertical and square videos. A landscape 1080p project commonly measures 1920×1080, while a 4K 16:9 project commonly measures 3840×2160. These are examples of standard sizes, not a requirement to enlarge a smaller source.
Avoid adding black bars or padding to force a vertical clip into a widescreen frame, or a square clip into a horizontal one. Padding becomes part of the video image and does not improve its fit; the player can adapt to the video’s dimensions. If you are preparing a landscape loop from a particular source, review the framing before export rather than assuming that every project should be 16:9.
Resolution should follow the material and intended presentation. Exporting a low-resolution source at 4K does not restore detail that was never recorded, while reducing a genuine high-resolution project can discard detail. For an always-on playlist, source files may vary in shape and resolution; keep a clear record of each project’s intended output rather than applying one conversion preset blindly. For broader planning around source files and continuity, see how to upload new videos to a YouTube stream running on a VPS.
Set colour for SDR
For standard dynamic range (SDR) video, YouTube recommends BT.709. Set the project and export to BT.709 when the footage was mastered in that colour space, and make sure the export metadata describes the actual master. A colour-space label is not a correction tool: it cannot repair footage that was graded or converted incorrectly.
If your editor has separate choices for colour space, range and metadata, avoid changing them by guesswork. Range describes how the signal values are represented; YouTube notes that it converts full-range video to limited range. YouTube also warns that unsupported colour spaces can be converted. A mismatch between the image and its metadata can therefore change how the video is interpreted, even if the export dialogue reports a familiar resolution and codec.
For a normal SDR project, keep the workflow simple: confirm the footage and timeline are intended for SDR, select BT.709 for export, and avoid enabling HDR output unless you have deliberately worked in an HDR project. If the editor offers an automatic setting and you are not sure how the original material was mastered, consult the editor’s documentation or check the source properties before overriding it.
After export, watch a short section on a second display or device if colour is important. Look for obvious changes in brightness, washed-out tones or crushed shadow detail compared with the editing preview. A different screen can show images differently, so this check is not colour calibration; it is a useful way to catch a conspicuous export mismatch before uploading a long programme.
Choose bitrate by resolution and frame rate
YouTube publishes recommended upload video bitrates by resolution, frame-rate class and whether the video is SDR or HDR. The table below shows the SDR figures relevant to this guide. Standard frame rate means 24, 25 or 30 fps; high frame rate means 48, 50 or 60 fps.
| Output resolution | SDR, standard frame rate | SDR, high frame rate |
|---|---|---|
| 8K | 80–160 Mbps | 120–240 Mbps |
| 2160p (4K) | 35–45 Mbps | 53–68 Mbps |
| 1440p (2K) | 16 Mbps | 24 Mbps |
| 1080p | 8 Mbps | 12 Mbps |
| 720p | 5 Mbps | 7.5 Mbps |
| 480p | 2.5 Mbps | 4 Mbps |
| 360p | 1 Mbps | 1.5 Mbps |
For example, a standard-frame-rate 1080p SDR export has an 8 Mbps reference; a 1080p 60 fps SDR export has a 12 Mbps reference. Choose the row for the resolution you are actually exporting and the frame-rate class of the footage. If an editor offers variable bitrate, it can allocate more data to complex passages and less to simpler ones while using a target or range you set.
These numbers are not required minimums, strict limits or promises about the appearance of the processed YouTube version. YouTube explains that bitrate depends on codec and that resolution, aspect ratio and frame rate also matter; its formatting guidance says there is no recommended minimum value. A higher number can create a larger file without visibly helping a simple static scene, while a very low setting can make detail and motion look rough. The reference table helps you choose a starting point, not predict an exact result.
Content affects how a bitrate is used. A fixed camera showing a person speaking may be easier to encode than fast movement, foliage or fine patterns, but the same resolution and frame-rate reference is a sensible place to begin. If the file is unusually large or the image looks poor after processing, review the export and source before changing multiple settings at once. Make a short test export from a representative section when you can, then compare it with the timeline at normal viewing size.
Do not use this table for a live broadcast. A live stream is constrained by its continuing connection and encoder configuration; an uploaded video is processed after the file arrives. If you also operate an always-on channel, keep the two checklists separate. The practical trade-offs involved in running that broadcast are different from choosing an upload bitrate, as discussed in settings for reducing CPU load in an OBS YouTube live loop.
Set audio encoding to suit the soundtrack
YouTube lists AAC-LC, Opus and Eclipsa Audio as recommended upload audio codecs, with a sample rate of 48 kHz. For broad compatibility and an uncomplicated export, AAC-LC at 48 kHz is a straightforward default. The audio bitrate does not need to rise with video resolution; audio and video are separate parts of the file.
Select the channel layout that matches the material. YouTube’s recommendations include mono, stereo, stereo plus 5.1, and stereo plus Eclipsa Audio. A song or ordinary programme mix is commonly delivered as stereo; a single spoken voice may be mono if the source and edit are genuinely mono. Do not export a stereo soundtrack with duplicated channels just to select a larger channel count.
For its audio bitrate recommendations, YouTube lists 128 kbps for mono, 384 kbps for stereo and 512 kbps for 5.1. Use the value for the soundtrack layout if your editor asks for an audio bitrate. These are recommendations rather than a reason to upmix a stereo mix to 5.1. In particular, devotional music with a stereo arrangement should remain stereo unless the production itself has a real multichannel mix.
Listen to the final file, not just the timeline. Check the beginning and end for clipped speech, missing music, abrupt cuts or an unintended silent channel. If the source contains a noisy recording, choosing a higher export bitrate will not remove the noise; adjust or repair the audio in the editing stage, then listen again to the rendered result. For further troubleshooting, see how to fix distorted audio in an always-on YouTube podcast stream.
Check the upload before publishing
An upload can appear in low quality before higher-resolution versions are ready. YouTube says 1080p and 4K processing may take longer, potentially several hours. If a premiere or scheduled release needs those qualities available at publication, upload as unlisted first and wait until the available versions are ready before making the video public. For a channel that publishes a loop or playlist, build processing time into the handover rather than assuming the upload is instantly available in every quality.
Before upload, open the rendered file and check its duration, resolution, frame rate, picture shape, colour and audio. A quick review of the start, a representative middle passage and the ending can catch problems that an export progress bar cannot. If the file is meant for a continuous channel, verify that it begins and ends as intended and that any repeated segment does not introduce an unwanted pause or abrupt transition.
Upload the file and check playback on YouTube once processing is under way. Look for a mismatch between the local export and the YouTube rendition, and confirm that the expected quality options become available. YouTube’s official recommended upload encoding settings are the right reference if your editor exposes detailed codec controls; its resolution and aspect ratio guidance explains how the player handles different shapes. Keep those official pages available because guidance can change.
An upload export is not, by itself, a 24/7 broadcast. If your goal is to turn a prepared video into a continuous YouTube live channel without leaving a computer running, StreamNeo removes that specific operational task: you upload the file and provide your YouTube stream key, rather than keeping your own machine on to transmit it. That does not change the export guidance above or make YouTube processing, rights or channel policy irrelevant; it addresses the ongoing broadcast step for a YouTube-only stream.
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
Do I need to use exactly YouTube’s recommended bitrate?
No. YouTube’s figures are upload recommendations, not exact pass-or-fail settings or guarantees of quality. Use the reference for your export resolution and frame-rate class, then judge the resulting file and playback rather than assuming a different bitrate must fail.
Should I export every video at 30 fps or 16:9?
No. Keep the frame rate and aspect ratio that match the source where possible. YouTube’s player adjusts to vertical and square video as well as widescreen, so do not add black bars just to force another shape.
Is MP4 with H.264 compulsory?
YouTube recommends MP4 and H.264 for uploads, and they are a sensible default for a typical export. The detailed H.264 options are recommendations; if your editor does not expose every one, use its standard H.264 export and check the finished file.
Why does my upload initially look low-resolution?
YouTube may make lower qualities available before 1080p or 4K processing has finished. Higher-quality processing can take longer, potentially several hours. If quality options must be ready at launch, upload unlisted and wait for processing before making the video public.