For a typical SDR upload, export an MP4 with H.264 video, progressive scan, BT.709 colour, and the same frame rate as the source. Then use YouTube’s published bitrate recommendation for your resolution and frame-rate group; it is guidance for an upload, not a universal quality threshold.
HDR is a separate production workflow: it needs a real HDR grade and the corresponding colour tags, not just metadata added to an SDR file. Upload export settings also differ from the encoder settings used to send a live stream.
Start with the source frame rate
The safest frame-rate choice is usually the one your footage was recorded at. YouTube’s upload guidance lists common rates of 24, 25, 30, 48, 50 and 60 frames per second, and says content should be encoded and uploaded at its recorded frame rate. YouTube’s recommended upload encoding settings are the place to check if your editing software offers additional options or the source uses an unusual rate.
Frame rate describes how many distinct frames are shown each second. It is not the same as resolution: a 1080p video can be 25 fps or 60 fps, and a 4K video can be either. The right choice depends on the source and the motion you want to preserve. A spoken devotional recording made at 25 fps does not become more faithful just because it is exported at 60 fps.
Unnecessary frame-rate conversion can create repeated or blended frames, or make motion look uneven. If your source is 30 fps, exporting at 60 fps does not create the missing moments between frames. Likewise, converting 60 fps material to 30 fps removes temporal detail. Keep a conversion for a deliberate delivery requirement, rather than treating a larger number as an automatic quality improvement.
Interlaced footage needs a separate decision. YouTube recommends deinterlacing before upload; its example converts 1080i60 material to 1080p30. If your footage comes from an older camera or broadcast recording, check whether it is interlaced before export. Do not simply label interlaced footage as progressive, because a label cannot reconstruct the missing scan pattern.
For an always-on channel, a consistent source and export rate also make repeated segments easier to combine. If you are assembling several clips into a loop, inspect their frame rates before joining them. You can keep the video export workflow distinct from the broadcast workflow discussed in how to stream videos from local storage to YouTube Live with OBS.
Choose a container, codec and scan type
For a straightforward SDR upload, use MP4 as the container and H.264 as the video codec. The container is the file wrapper; the codec compresses the picture inside it. These are separate choices, and writing “MP4” on a file does not by itself say which codec was used.
A practical H.264 export baseline from YouTube’s upload guide includes progressive scan, High Profile, two consecutive B-frames, a closed GOP with a GOP length equal to half the frame rate, CABAC, variable bitrate and 4:2:0 chroma subsampling. Many editing applications expose only a subset of these controls, or set the technical details automatically when you choose an H.264 preset. Use the settings if they are available, but do not spend time searching for hidden controls if your software does not provide them.
Progressive video presents complete frames in sequence, which is the normal choice for contemporary web video. The alternative, interlaced scanning, divides a picture into fields and is associated with older video workflows. If your source is interlaced, deinterlace it as part of the export rather than carrying interlaced fields into a progressive upload.
YouTube’s encoding guide is an upload recommendation, not a statement that every other combination will be rejected. A different codec can make sense when your editor or delivery workflow requires it, but H.264 in MP4 is a broadly practical starting point. For a 24/7 channel, a file that exports consistently and plays correctly in your intended workflow is more useful than an advanced format that the rest of your process cannot handle.
Keep the image dimensions and aspect ratio intentional as well. A standard 16:9 video at 1080p is 1920×1080; at 4K it is 3840×2160. YouTube’s player adapts to other aspect ratios and devices, and its resolution and aspect-ratio guidance advises against baking black bars or padding into the picture. If your source is vertical or square, export it in that shape rather than shrinking it into a 16:9 canvas with permanent bars.
Set SDR colour correctly
For a standard-dynamic-range export, use BT.709 colour. This is YouTube’s recommended SDR colour space. Correct colour handling helps keep familiar tones and contrast consistent between your editing preview and playback, although the viewer’s display and environment still affect what they see.
Colour space is not a filter. If a video looks washed out, too dark, or overly saturated, adding a colour-space label without checking the actual grade may not fix it. Confirm that your editing project, export and source are using a coherent SDR workflow. Check the rendered file on a normal display before uploading, especially if the project contains footage from several cameras or clips downloaded from different sources.
Do not confuse BT.709 with HDR tags. An SDR picture can be assigned HDR-related metadata, but that does not create the wider brightness range, colour information or creative grade of genuine HDR. The HDR section below explains the additional work involved. If your material is intended for ordinary phone and computer playback, a properly managed BT.709 export is usually the more direct route.
Aspect ratio can also affect perceived quality. YouTube’s player adjusts to the video and the viewer’s device, so bars inserted to force every item into 16:9 can waste picture area or produce an awkward result. Let the player handle the dimensions where possible, and make sure the export matches the composition you actually want viewers to see.
Use the bitrate table for your resolution and frame rate
Bitrate is the amount of data used to represent video over time. Higher bitrate can preserve more detail in difficult material, such as fast movement, fine texture, grain or water, but it also creates larger files and longer uploads. The useful comparison is not “high versus low” in isolation; it is the recommendation for your chosen resolution and frame-rate group.
The table below reproduces YouTube Help’s published SDR upload recommendations. Standard frame rate means 24, 25 or 30 fps; high frame rate means 48, 50 or 60 fps. These are recommendations for uploads, not minimum acceptance requirements. YouTube Help does not state a publication year for this guidance, so check the current page before relying on a value for a time-sensitive workflow.
| Resolution | Standard frame rate | 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 |
Use the row that matches both the output resolution and frame-rate group. For example, an SDR 1080p file at 25 fps falls into the standard group; a 1080p file at 60 fps falls into the high-frame-rate group. That does not mean every 1080p video needs the same bitrate: the table distinguishes frame-rate groups, and the content itself can vary in complexity.
Variable bitrate allows the encoder to spend more data on complex scenes and less on simpler ones. That is why the export baseline uses variable bitrate rather than asking you to hold one constant rate throughout the file. If your application asks for a target and maximum bitrate, follow its terminology and use the YouTube recommendation as the reference point; do not interpret it as a guarantee that every scene will look identical after processing.
Higher export bitrate has costs. It increases file size and can make transfer slower, particularly on a limited connection. For a long pre-recorded programme, an unnecessarily large master can consume storage and take longer to upload without a visible gain on the devices your audience uses. Start with the relevant row and inspect the result rather than selecting the largest number simply because it is available.
Resolution should also reflect the source. Upscaling a 720p recording to 4K does not recover detail that was never captured. Conversely, reducing a detailed 4K source to 1080p may be sensible if the audience, upload time or file size matters more than preserving the original pixel dimensions. Choose a delivery size deliberately, then select its corresponding bitrate recommendation.
Handle HDR with a proper workflow
HDR is not a metadata switch that upgrades SDR. It is a production workflow involving appropriate capture or source material, colour management, a deliberate HDR grade, a supported export and correct tags. If you do not have an HDR-capable workflow or a reason to deliver HDR, keep the project in SDR and export BT.709 rather than relabelling it.
YouTube’s HDR guidance describes uploads from 720p through 2160p, with 10- or 12-bit colour depth, Rec. 2020 primaries and matrix, and a PQ or HLG transfer function. It recommends codecs that support 10-bit encoding with HDR metadata, including VP9 Profile 2, AV1 and HEVC/H.265. Consult YouTube’s HDR video upload guidance for the current technical requirements and what your editing application must deliver.
The HDR upload recommendations differ from the SDR table. As with the SDR figures, YouTube Help’s page does not state a publication year. They are not targets to apply to an SDR export.
| Resolution | Standard frame rate | High frame rate |
|---|---|---|
| 8K | 100–200 Mbps | 150–300 Mbps |
| 2160p (4K) | 44–56 Mbps | 66–85 Mbps |
| 1440p (2K) | 20 Mbps | 30 Mbps |
| 1080p | 10 Mbps | 15 Mbps |
| 720p | 6.5 Mbps | 9.5 Mbps |
| 480p, 360p | Not supported in table | Not supported in table |
Correct tags tell YouTube how the HDR file is encoded; they do not create an HDR grade or repair an SDR master. YouTube says it detects HDR metadata, makes HDR transcodes for capable playback, and creates an SDR conversion for other devices as needed. That processing is not a reason to skip checking the source grade and exported result. Review the video on an HDR-capable display if you can, and check how the SDR version appears as well.
Do not use a metadata tool to add HDR labels unless you know that the content was actually graded and exported for HDR. A wrong tag can misrepresent the picture and produce an unsuitable result. When the source is an SDR recording, a clean SDR export is the accurate choice, even if an HDR label looks like an easy route to a more impressive resolution menu.
Check audio, aspect ratio and the rendered file
Audio settings are part of the upload file, but they are independent of video resolution. YouTube lists AAC-LC, Opus or Eclipsa Audio at 48 kHz for audio uploads. Its recommended playback bitrates are 128 kbps for mono, 384 kbps for stereo and 512 kbps for 5.1; Eclipsa Audio is listed at 128 kbps per channel. These figures do not change because the picture is 720p or 4K.
For a music-led stream, check the mix on ordinary speakers or headphones, not only on studio monitors. Listen for clipping, sudden level jumps between sections, and an audio track that ends before the video. If the programme is built from several clips, check the transitions and make sure the loop does not introduce an unintended silence or cut. Guidance on mixing rain and thunder audio for a YouTube sleep stream offers a useful example of why audio continuity matters in a long-running programme.
Keep the intended aspect ratio and avoid adding black bars to the picture solely to make it fit a familiar canvas. YouTube’s player adjusts to individual videos and devices. A 16:9 export is common for landscape material, but a different ratio may be correct for a source designed that way. Check framing on a phone as well as a computer, because a crop that looks acceptable on a desktop can hide important text or devotional imagery on a smaller screen.
Before uploading, play the rendered file from beginning to end if the programme is short, or sample the opening, a few transitions and the ending for a longer file. Confirm that the export opens, picture and sound stay in sync, titles are legible, and the final frame behaves as intended. A technically correct preset cannot catch a title hidden under a crop or a source clip that was accidentally left muted.
For recurring programming, inspect a representative export before producing a batch. A short test file can reveal a wrong frame rate, colour shift, or audio problem without forcing you to re-export a full programme. Keep a note of the settings that worked for that source and editing project; when the source changes, verify rather than assuming the old preset still fits.
Keep upload exports separate from live encoder settings
An upload is a completed file that YouTube receives and processes. A live stream is a real-time feed sent by an encoder to YouTube’s ingestion service. Their settings answer different questions: an export bitrate controls the encoded file; a live bitrate controls the data being sent continuously while broadcasting.
YouTube’s live-streaming guidance recommends CBR and provides its own ingestion settings. Those values are not the upload bitrate recommendations in the table above. See YouTube’s live encoder settings when configuring a live encoder, and do not copy a live bitrate into an export preset just because both settings use Mbps.
This distinction matters for a 24/7 channel that loops pre-recorded material. A file might be exported once using the upload guidance, then played into a live broadcast whose encoder has separate requirements. For example, an SDR 1080p file exported for upload at a recommended rate is not the same thing as configuring OBS to send a continuous 1080p live feed. One is a stored video; the other is a stream that depends on the ongoing encoder and connection.
If you use a local computer to play and encode a loop, that computer and its network connection remain part of the live path. The export table cannot prevent an encoder from dropping frames or a connection from interrupting the broadcast. If the practical problem is keeping a pre-recorded file running without leaving your own computer on, StreamNeo removes that specific operational chore: it turns an uploaded file into a YouTube live stream that continues from the cloud, with monitoring and automatic restart if it drops.
For an OBS-based setup, keep the tasks separate: prepare a clean file, then configure the live encoder and test the broadcast. The guide to looping different videos in an OBS YouTube live stream addresses playback and scheduling rather than export quality. If you have trouble during a broadcast, diagnose the encoder and network using live-stream guidance, not by repeatedly raising the upload file’s bitrate.
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 is the best bitrate for a 1080p YouTube upload?
There is no single bitrate that is best for every 1080p upload. YouTube’s recommendation is 8 Mbps for standard frame rates of 24, 25 or 30 fps, and 12 Mbps for high frame rates of 48, 50 or 60 fps. Treat those as upload guidance and check the current official table if you need the latest values.
Should I upload at 30 fps or 60 fps?
Use the frame rate your video was recorded at unless you have a specific delivery reason to convert it. A 60 fps export does not add real motion detail to 30 fps footage, while reducing a 60 fps source to 30 fps discards frames. Match source and export first, then choose the corresponding bitrate group.
Can I turn an SDR video into HDR by adding metadata?
No. HDR metadata describes a correctly prepared HDR file; it does not create HDR colour or a genuine HDR grade from SDR footage. Keep SDR material in a BT.709 workflow unless you can complete and verify the HDR grading and export process.
Are YouTube upload bitrates the same as live-stream bitrates?
No. Upload recommendations apply to a video file, while live encoder settings apply to the real-time feed sent to YouTube. Use the upload table for exports and YouTube’s live encoder guidance for the broadcast settings.