YouTube Video Quality Guide: 1080p vs 4K, Bitrate, and What Actually Matters

Why Quality Matters When Downloading YouTube Clips

Here's something a lot of people don't know: the quality you get when you download from YouTube depends on what YouTube has stored, not just what you request. YouTube processes every uploaded video through its own encoding pipeline before storing it. The original file the creator uploaded might have been a pristine 4K ProRes file from a professional camera. What YouTube stores and serves is a set of compressed versions at multiple resolutions.

When you use a download tool, you're accessing one of those compressed versions. You're not getting the original. You're getting YouTube's processed copy. Understanding what that copy contains, how it was compressed, and how any additional re-encoding by the download tool affects it is what this guide is about.

This matters for practical reasons. You want to download a clip to use in a video project. You pick 1080p. The clip looks fine streaming but looks noticeably worse in your editing software. Why? Because the bitrate of YouTube's 1080p stream may be lower than you expected, and if the download tool re-encoded it during processing, you've added another compression step on top of YouTube's already-compressed version.

Understanding the quality chain helps you make better decisions: which resolution to choose, when format selection matters, when it doesn't, and when the source quality is simply the limiting factor regardless of what you request.

Resolution Explained: What the Numbers Actually Mean

Resolution measures how many pixels are in the video frame. More pixels means finer detail can be represented, if the rest of the quality chain supports it.

Label	Actual pixel dimensions	Total pixels	Common name
360p	640 x 360	230,400	Standard mobile (low bandwidth)
480p	854 x 480	409,920	Standard definition
720p	1280 x 720	921,600	HD (High Definition)
1080p	1920 x 1080	2,073,600	Full HD
1440p	2560 x 1440	3,686,400	2K / QHD
2160p	3840 x 2160	8,294,400	4K / UHD
4320p	7680 x 4320	33,177,600	8K

The jump from 1080p to 4K isn't just "a little more pixels." 4K has exactly four times as many pixels as 1080p. That's a significant increase in the amount of information the video contains. On a large enough screen (a 55-inch TV viewed from 6 feet, or a 27-inch monitor viewed from 2 feet), the difference between 1080p and 4K is genuinely visible. On a 6-inch phone screen, it is not visible at all. The pixels are smaller than the resolving power of your eyes at that viewing distance.

The viewing distance factor

There's a well-established formula for the minimum viewing distance at which a given resolution is distinguishable from a lower one. At normal viewing distances on phone screens, 1080p and 4K are visually identical to essentially all human viewers. On a large TV viewed from a sofa, the difference between 1080p and 4K is perceptible but subtle. This matters when deciding whether 4K download is worth the significantly larger file size.

Bitrate: The Number Everyone Ignores But Matters Most

Resolution tells you how many pixels there are. Bitrate tells you how much data is used to represent those pixels per second. And this is where most people's understanding of video quality breaks down.

Bitrate is measured in megabits per second (Mbps). Higher bitrate means more data is used to describe each frame. More data means less compression artifact, better detail, smoother gradients, and cleaner motion. Lower bitrate means more compression, more artifact, and worse perceived quality regardless of how high the resolution is.

1080p at 2Mbps looks worse than 720p at 8Mbps. This is not a hypothetical. This is measurable and visible. Resolution without sufficient bitrate is not quality.

This is the core concept. Resolution is the ceiling. Bitrate is the floor. You need enough bitrate to actually use the resolution you have. A 4K video at 5Mbps is going to look blocky and compressed. A 720p video at 10Mbps is going to look clean and sharp.

Why this matters for YouTube downloads specifically

YouTube applies different bitrates to different resolution streams. The bitrates they use are not always as high as you might hope, particularly for older videos uploaded before they upgraded their encoding. When you request "1080p" from a download tool, you're getting 1080p at whatever bitrate YouTube has stored that stream at. For many videos, that bitrate is lower than what you'd get from a Blu-ray or professional production file.

Variable bitrate vs constant bitrate

Two ways to allocate bits over a video:

Constant bitrate (CBR): Every second of video gets exactly the same amount of data. A complex action scene gets the same bits as a static shot of a talking head. This means complex scenes look worse than they could (not enough bits) and simple scenes look better than they need to (too many bits wasted). CBR is used for streaming where buffering stability matters more than efficiency.

Variable bitrate (VBR): The encoder allocates more data to complex frames and less to simple ones. A static shot needs very few bits because most of the frame is identical to the previous frame. An explosion scene needs many bits because every pixel is changing. VBR produces better quality at the same average bitrate. Almost all modern video encoding uses VBR.

For downloads: VBR files are more efficient and better quality at equal file sizes. When YTCut produces output files, it uses VBR encoding for exactly this reason.

How YouTube Compresses Video

When you upload a video to YouTube, it goes through YouTube's encoding pipeline before being stored and served. Here's what actually happens:

The upload processing pipeline

1. Your original file arrives at YouTube's servers in whatever format you used (MP4, MOV, ProRes, etc.).
2. YouTube's encoding pipeline processes it, generating multiple versions at different resolutions and bitrates.
3. Multiple codec versions are created. YouTube maintains both H.264 and VP9 versions (and increasingly AV1) for each resolution.
4. These multiple versions are stored distributed across Google's infrastructure.
5. When a viewer watches the video, YouTube selects the appropriate version based on their device, connection speed, and player settings.

Codec choices YouTube makes

H.264 (AVC): The compatibility codec. YouTube serves H.264 to older devices and browsers that can't handle VP9 or AV1. H.264 is less efficient than VP9: it needs roughly twice the bitrate to achieve the same visual quality. YouTube keeps H.264 versions available because universal compatibility still matters.

VP9: Google's own codec, significantly more efficient than H.264. A VP9 file at 5Mbps looks roughly equivalent to an H.264 file at 10Mbps. YouTube has served VP9 by default to Chrome and modern browsers since around 2015. Most YouTube streams you've watched in the last several years were VP9.

AV1: The next generation after VP9. Even more efficient than VP9: roughly 30-50% better compression at equivalent quality. YouTube began rolling out AV1 encoding for content starting around 2018-2019, accelerating through the 2020s. As of 2026, AV1 is available for a significant portion of YouTube's content, particularly newer uploads. Not all devices can decode AV1 in hardware, which limits its adoption.

How YouTube decides which codec to serve you

YouTube selects the codec based on what your browser or device supports. Chrome (and most Chromium-based browsers) supports all three. Safari on older iOS versions may fall back to H.264. The YouTube app on recent Android devices typically gets VP9 or AV1. The specific codec you receive affects both file size and quality of any download.

Google's Official Recommended Upload Bitrates

Google publishes recommended bitrates for YouTube uploads. These are what they suggest creators use when uploading. The actual bitrates YouTube stores and serves after processing may differ, but the upload recommendations give you a useful reference for what "good quality" looks like at each resolution.

Resolution and frame rate	Google's recommended bitrate (SDR)	Google's recommended bitrate (HDR)
1080p at 24/25/30fps	8 Mbps	10 Mbps
1080p at 48/50/60fps	12 Mbps	15 Mbps
1440p (2K) at 24/25/30fps	16 Mbps	20 Mbps
1440p (2K) at 48/50/60fps	24 Mbps	30 Mbps
2160p (4K) at 24/25/30fps	35 to 45 Mbps	44 to 56 Mbps
2160p (4K) at 48/50/60fps	53 to 68 Mbps	66 to 85 Mbps

Notice the range at 4K30: 35 to 45 Mbps. That's the recommended bitrate for uploading 4K content. But YouTube compresses this further before serving it. What YouTube actually serves a viewer at 4K is significantly lower than this. YouTube's 4K VP9 stream is typically in the 15-20 Mbps range for most content, depending on content complexity.

This is why downloading a 4K YouTube video does not give you studio-quality 4K footage. It gives you YouTube's compressed-for-distribution 4K, which looks great on screen but is meaningfully more compressed than the original upload.

What YTCut Downloads

Understanding what YTCut actually does to your video is important for setting expectations.

For MP4 downloads

YTCut fetches the best available video stream from YouTube for your selected resolution (or the best available if you chose "Best"), processes the segment you've defined (applying the start and end cut points), and re-encodes the output as H.264 video in an MP4 container. The re-encoding uses H.264 with a CRF value of approximately 21, which produces excellent quality output. CRF 21 is considered "visually lossless" to most viewers in most content.

The re-encoding step is necessary for two reasons: applying the precise cut points requires re-encoding the segment boundaries, and producing an MP4 file from YouTube's VP9 stream requires transcoding since VP9 isn't typically containerized in MP4.

For WebM downloads

WebM output uses VP9 video codec with a CRF of approximately 32. VP9 is more efficient than H.264, so CRF 32 in VP9 produces quality comparable to CRF 21 in H.264, at a smaller file size. WebM/VP9 is a good choice when file size matters and the destination can play WebM (web embedding, Discord, modern apps).

The quality chain for a YTCut download

Original camera footage (lossless or very high bitrate) becomes YouTube's stored compressed version (VP9 or H.264, bitrate depends on resolution and content), which then becomes YTCut's re-encoded output (H.264 CRF 21 or VP9 CRF 32).

Each step in this chain is lossy. The quality of your final download is bounded by the weakest link. A video that was originally recorded on a phone camera in 2012 at 720p with terrible audio is not going to produce a high-quality download regardless of how well YTCut encodes it. A video that was originally shot on a professional cinema camera and uploaded at 4K with a high bitrate can produce an excellent download even after two generations of lossy compression, because the source quality was high enough that two rounds of good-quality compression still leaves plenty of detail.

How to Choose Quality in YTCut

The quality selector in YTCut gives you options typically labeled by resolution height: 360p, 480p, 720p, 1080p, 1440p, 2160p (4K), and "Best available." Here's how to think about which to pick.

"Best available"

This tells YTCut to fetch the highest quality stream YouTube has for the video. For most recent videos this is 1080p or higher. For older videos it might be 720p. This is the right choice when: you want the best possible quality, file size is not a concern, and you're going to use the clip for any kind of further production or editing work.

1080p specifically

The practical sweet spot for almost all use cases. Looks excellent on any screen up to about 32 inches. Creates manageable file sizes. Plays on every device. Upload it to any platform. If you're not sure what to pick, pick 1080p.

720p

Good for: clips that need to be small files (Discord 8MB limit, email attachment, slow upload speeds), content that will be displayed at small sizes anyway, quick sharing where quality is secondary to speed. At 720p with reasonable bitrate, quality is still very good for most content. The file size is roughly half of 1080p.

480p and below

Practical only when file size is severely constrained. Looks noticeably soft on modern screens. Voice and podcast content where you're extracting audio only: doesn't matter (audio quality is independent of video resolution). For any visual content you care about: go higher.

4K (2160p)

Only makes sense when: the source video actually has 4K content (uploading a 1080p video doesn't create a real 4K version at YouTube), you have a 4K display and are viewing at close enough distance to benefit, or you're doing professional production work where you want maximum pixels for cropping flexibility. Discussed more in the next section.

The 4K Myth: When Higher Resolution Doesn't Help

4K content has been heavily marketed as a significant quality upgrade. For most YouTube downloading use cases, the 4K myth creates expectations that aren't matched by reality.

YouTube's 4K bitrate vs 4K promise

YouTube serves 4K content at approximately 15-20 Mbps for typical content (VP9). Professional 4K production content is shot and edited at bitrates of 100 Mbps or higher. YouTube's 4K streams are significantly compressed relative to production-grade 4K.

Compare this to YouTube's 1080p stream, which is typically served at 4-8 Mbps depending on content and codec. The 4K stream has more pixels but also more compression artifacts per unit area because more pixels need to be described with a relatively modest bitrate increase.

When 4K from YouTube actually helps

Viewing on a 4K display at close distance: yes, the additional pixels are useful. The finer detail in a sharp, well-lit scene is visible on a 27-inch 4K monitor viewed from a normal desk distance.

Cropping flexibility in production: if you download a 4K clip and you need to punch in (zoom in to a smaller area of the frame) without losing too much resolution, the extra pixels give you room. A 4K video punched in to 50% is still 1080p. A 1080p video punched in to 50% is 540p, which is soft.

When 4K from YouTube doesn't help

Viewing on a 1080p monitor: your screen physically cannot display more than 1080p. Downloading 4K just means your player downscales it to 1080p before you see it. The file is 4x larger than necessary.

Viewing on a phone: at 6 inches of screen size, 1080p already exceeds the resolving power of human vision at normal holding distance. 4K is invisible on most phone screens.

Source video that wasn't shot in real 4K: many YouTubers use cameras that upscale or process footage to nominally 4K. If the camera's sensor is 1080p and it upscales to 4K before sending to YouTube, you're downloading a 4K file that contains 1080p of actual detail.

The most common scenario where 4K is not worth it: downloading a talking-head YouTube video at 4K for viewing on a laptop. The laptop screen is 1080p, the content is a person talking, the file is four times larger than necessary. Download at 1080p.

Codec Comparison Table

A codec (coder-decoder) is the algorithm that compresses and decompresses video. The choice of codec significantly affects both file size and quality at any given resolution.

Codec	Also known as	Compression efficiency	Hardware support	Compatibility	Best use case
H.264	AVC, MPEG-4 Part 10	Baseline (older)	Excellent (every device since ~2010)	Universal	Sharing, compatibility, streaming
H.265	HEVC	~40-50% better than H.264	Good (most devices since ~2015)	Good but not universal (Safari handles it well, some Android issues)	High-quality archiving, Apple ecosystem
VP9	VP9	~30-40% better than H.264	Good (software decode universal, hardware decode varies)	Good in browsers, poor in some video players	Web video, YouTube streaming, efficient web embeds
AV1	AV1	~30-50% better than VP9	Improving (new phones and GPUs have hardware AV1 decode)	Growing (Chrome, Firefox, recent Android, not all devices)	Future of streaming, YouTube for new content
VP8	VP8	Similar to H.264 or slightly worse	Good	WebM containers, mostly replaced by VP9	Legacy web video

The practical implication for downloads

When you download from YouTube as MP4, you get H.264. Maximum compatibility. Plays everywhere. Slightly larger files than VP9 at equivalent quality.

When you download as WebM, you get VP9. Better compression efficiency. Smaller files at equivalent quality. Slightly less compatible (doesn't play in older media players by default, doesn't play in QuickTime on Mac without additional codecs).

For most sharing purposes: MP4/H.264. For web embedding or when file size matters and you know the recipient's player can handle VP9: WebM/VP9.

File Size Reference for Video Downloads

What are you actually downloading in terms of file size? These are approximate sizes for YTCut MP4 downloads at H.264 CRF 21, which produces high-quality output.

Resolution	1 minute	5 minutes	10 minutes	30 minutes
480p	approx 8-12 MB	approx 40-60 MB	approx 80-120 MB	approx 240-360 MB
720p	approx 15-25 MB	approx 75-125 MB	approx 150-250 MB	approx 450-750 MB
1080p	approx 30-50 MB	approx 150-250 MB	approx 300-500 MB	approx 900 MB to 1.5 GB
1440p	approx 60-90 MB	approx 300-450 MB	approx 600-900 MB	approx 1.8 to 2.7 GB
2160p (4K)	approx 100-180 MB	approx 500-900 MB	approx 1-1.8 GB	approx 3-5.4 GB

The ranges exist because file size depends heavily on content complexity. A static talking-head video has minimal motion between frames and compresses very efficiently. An action-packed game video or high-motion sports footage has significant frame-to-frame changes that require more data to encode. The same resolution and settings can produce files that differ by 2x or more depending on content type.

The reference point Google provides: a 10-minute 1080p video at their recommended 8 Mbps upload bitrate would be approximately 600MB as a raw stream. At H.264 CRF 21 (which varies based on content), a 10-minute clip might be 300-500MB for typical content. The VBR encoding allocates bits based on complexity rather than maintaining a fixed rate.

When to Choose Each Format from YTCut

Decision framework, not just a list of facts.

Choose MP4 when:

• You're sharing the clip with anyone and don't know exactly what they're using to play it
• You're uploading to any social media platform (Twitter, TikTok, YouTube, Instagram, Reddit)
• You're bringing the clip into a video editing project
• You need it to play on a TV, a game console, or any device other than a modern computer
• You're not sure which to pick

Choose WebM when:

• You're embedding the video on a webpage and want the best compression
• File size is specifically constrained (Discord free tier, email size limits)
• You're on a Linux or Chrome OS environment where VP9 is natively supported everywhere
• You know the recipient has a modern browser or player that handles WebM

Choose MP3 or M4A (audio only) when:

• You want only the audio track and don't need video
• The content is primarily speech (podcast, lecture, interview)
• You're creating a ringtone or audio clip
• File size is a concern and audio is all that matters

How FFmpeg CRF Values Work

CRF stands for Constant Rate Factor. It's the quality metric that FFmpeg (the underlying engine that processes video encoding) uses for variable bitrate encoding. Understanding CRF values helps you understand what quality setting means in technical terms.

The CRF scale for H.264

CRF values for H.264 range from 0 to 51. Lower number means higher quality, larger file. Higher number means lower quality, smaller file.

• CRF 0: Mathematically lossless. Enormous files. Never used for practical distribution.
• CRF 18: Visually near-lossless to most viewers. Files are large but not absurd. Good for archiving and master files.
• CRF 21-23: The sweet spot for high-quality distribution. Excellent quality, manageable file sizes. This is what YTCut targets for MP4 output.
• CRF 24-26: Good quality, noticeably smaller files. Acceptable for web streaming where bandwidth matters.
• CRF 28: Visibly compressed to most viewers on close inspection. Block artifacts start appearing in complex motion.
• CRF 32 and above: Noticeably lower quality. Used only when file size is severely constrained.

CRF for VP9

VP9's CRF scale works differently: range is 0-63, and because VP9 is more efficient, the same perceived quality is achieved at a higher CRF number than H.264. CRF 32 in VP9 produces quality comparable to CRF 21 in H.264, at a smaller file size. This is why YTCut uses a higher CRF number for WebM/VP9 output than for MP4/H.264 output.

Why CRF 21 specifically for H.264?

CRF 21 is widely considered the "safe" high-quality setting for H.264 distribution. Below CRF 18, file sizes become impractical without perceivable quality improvement. Above CRF 23, some viewers in some content types start to notice compression. CRF 21 sits comfortably in the zone where quality is excellent and files are manageable for a wide range of content types including gaming, talking head, nature footage, and animation.

Practical Quality Tips

Never re-encode lossy to lossy unnecessarily

This is the single most important practical tip. Every time you re-encode a lossy video (like an MP4 from YouTube), you add another generation of compression artifacts. These accumulate. Take your downloaded clip directly from YTCut into your editing project without intermediate re-encoding. Export your final edit from your editing software at high quality. Don't convert the file through additional tools in between unless you have a specific reason to.

Wrong workflow: YTCut download (MP4) becomes a different format conversion (loses quality) becomes editing project export (loses more quality). Three generations of lossy encoding.

Right workflow: YTCut download (MP4) goes directly into editing project. Final export is the only additional encoding step. Two generations total.

Always start from the best source available

If a video exists at multiple resolutions on YouTube, download the highest quality that's useful for your purpose. You can always scale down from 1080p to 720p. You cannot scale up from 720p to 1080p without losing quality. Download higher, use lower if needed.

VBR beats CBR for downloads

When you have a choice between constant bitrate and variable bitrate encoding, VBR produces better quality at the same average file size. YTCut uses VBR encoding. FFmpeg defaults to VBR when using CRF mode. For your own encoding projects: use CRF (VBR) rather than setting a fixed bitrate target unless you have a specific reason (streaming servers sometimes require CBR).

The source quality ceiling

No download tool, no encoding setting, no codec can give you better quality than what YouTube has stored. If the original video was shot in low light on a webcam at 720p with heavy noise, no amount of downloading at "best available" quality produces a clean, sharp, noiseless clip. The ceiling is always the source. Focus your quality efforts on content that was well-produced to begin with, and don't expect download settings to fix bad source material.

Check your output, not just your settings

Settings tell you what the encoder attempted. The output file tells you what actually happened. After downloading a clip you care about, play it back on the device you intend to use it on. Watch it at full size. Listen to the audio in headphones. If something looks wrong or sounds wrong, the settings didn't achieve what you expected. Adjust and try again rather than trusting settings blindly.

Frequently Asked Questions

Why does my downloaded clip look worse than the video looked on YouTube?

Three most likely reasons. First: YouTube's adaptive streaming adjusts quality in real-time based on your connection. What you saw streaming may have been at a higher momentary bitrate than the download version. Second: the download tool re-encoded the video, adding a compression step. Third: you downloaded at a lower resolution than what YouTube was streaming. Check what resolution you selected and whether the download resolution matches what you were watching. If you downloaded 720p and were streaming at 1080p, that explains the difference.

Does 60fps make a difference for downloaded clips?

Yes, significantly for motion-heavy content. 60fps (and 48fps) provide smoother motion that's clearly visible in gaming footage, sports, and fast action. For a talking-head video or slow-moving content, 30fps is indistinguishable from 60fps to most viewers. YouTube stores separate streams for 30fps and 60fps content. The 60fps streams have higher bitrate requirements because there are twice as many frames to encode per second. When downloading gaming or action content: get 60fps. For lectures and static content: 30fps is fine.

What's the best format to download if I'm going to edit the clip in Premiere or DaVinci?

MP4 with H.264. Both Premiere Pro and DaVinci Resolve handle H.264 MP4 natively and well. The CRF 21 quality that YTCut uses gives you high-quality source material for editing. Avoid converting to an intermediate format before editing. Just bring the MP4 directly into your timeline. If you need ProRes or DNxHD for specific proxy workflows, export from your editing software rather than trying to convert the download first.

Why is the 4K version sometimes a smaller file than I expected?

Because YouTube's 4K stream at VP9 is very efficient. VP9 compresses dramatically better than H.264 per pixel. A 4K VP9 file can actually be a smaller file than a 1080p H.264 file for some content types, while still looking better on a 4K display. This is not a bug or an error. It's VP9 working as designed. If you specifically need H.264 for compatibility and download 4K, the file will be much larger because H.264 is less efficient per pixel.

Does HDR content download differently than SDR?

YouTube serves HDR content only to displays and players that support it. If you download a video that has an HDR version, whether you get HDR or SDR depends on your playback environment during download and the capabilities YTCut detects. HDR video contains a wider range of brightness values and requires HDR-capable displays to show correctly. On an SDR monitor, HDR video often looks washed out or over-saturated. For most purposes, SDR is more compatible and more practical for downloaded clips.

What bitrate does YouTube actually serve for 1080p?

It varies by content, age of the video, and whether the video has been through YouTube's newer encoding passes. Typical range for 1080p VP9 (what most modern browsers receive): approximately 2.5 Mbps to 8 Mbps depending on content complexity. The average is roughly 4-5 Mbps for typical content. Fast-moving content (gaming, sports) gets more bits. Slow-moving content (talking head, screencasts) gets fewer. These are significantly lower than what Google recommends for uploads because YouTube further compresses after the upload encoding.

Is there any quality loss when YTCut cuts a video?

Yes, technically. Cutting a video at non-keyframe boundaries requires re-encoding the frames at the cut point. YTCut re-encodes the entire segment (not just the cut point) at high quality (CRF 21 for H.264). The result is very close to the source quality but is not bit-for-bit identical. For most practical purposes this is imperceptible. If you need truly lossless cutting (for professional production or archival where any re-encoding is unacceptable), you'd need a tool that cuts only at keyframe boundaries without re-encoding, which means your cut points must align with YouTube's keyframe structure (typically every 2-4 seconds).