Every file you upload to YouTube gets converted — so the useful question is not "did YouTube compress it" but "where in the chain did the picture get worse." In a lot of cases the answer is not the upload at all. It is the player you are watching it in.
Three lines in YouTube's own help pages, read together, explain most reports of "it looked fine in my editor and looks mushy on YouTube." Two of them are about playback, not encoding.
What YouTube actually does to your file
YouTube's upload page states the conversion plainly: "Your video will be converted to the highest resolution available to ensure successful playback on different devices and networks."
Two things fall out of that sentence. Conversion is not conditional — there is no "leave my file alone" path. And the stated goal is successful playback across devices and networks, which is not the same goal as preserving your master.
Processing is the second step, and it does not finish all at once. The same page says: "You can view the estimated processing time for SD, HD, and 4K videos. Higher qualities such as 4K or HD may take more time to process." It lists what that depends on — "quality, video length, video format, and traffic" — and adds "For optimal processing time, verify your YouTube account."
No number of minutes appears anywhere on that page, so nobody can honestly tell you how long HD takes. The takeaway: the quality menu right after publishing is not necessarily the final one, because the higher tiers are the ones called out as slower.
The fastest fix: read the player before you touch the file
Open your video, open the quality menu in the player, and compare the top entry with what you uploaded. That one check splits the problem in half.
If the top entry is lower than your upload resolution, wait and re-check, then read the codec note below. YouTube does not document what decides which tiers appear on a given video and player, so check the official documentation rather than working from a guess.
If the top entry matches your upload and you selected it manually and it still looks soft, the problem is in the file you handed over. That is the case the rest of this page covers.
One requirement catches 4K uploaders specifically. YouTube's recommended-encoding page carries this note directly under its bitrate table: "To view new 4K uploads in 4K, use a browser or device that supports VP9." Read the subject of that sentence — it is about viewing, and it points at your browser or device, not at your file. A 4K upload that caps below 4K on one machine and plays fine on another is behaving exactly as that note describes.
That page also opens with the line "These features are only available to partners who use YouTube Studio Content Manager," and everything on it is framed as recommended settings. An MP4 that misses several of them still uploads.
Give YouTube a file it does not have to work around
Since the conversion always runs, the only lever you control is what goes in. YouTube's recommended settings are specific: "Container: MP4", "Video codec: H.264", "High Profile", "Progressive scan (no interlacing)", "CABAC", "Closed GOP. GOP of half the frame rate." and "Chroma subsampling: 4:2:0". At the container level it asks for "No Edit Lists (or the video might not get processed correctly)" and "moov atom at the front of the file (Fast Start)" — the wording there is might, not will.
For bitrate, YouTube is explicit that it is not enforcing anything: "Variable bitrate. No bitrate limit is required, though we offer recommended bit rates below for reference." The SDR table it offers for reference:
| Resolution | Standard frame rate (24, 25, 30) | High frame rate (48, 50, 60) |
|---|---|---|
| 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 |
HDR uploads get their own, higher table — 10 Mbps at 1080p, 44–56 Mbps at 4K — and YouTube marks HDR as "Not supported" at 480p and 360p. Audio is on a separate axis: "Audio playback bitrate is not related to video resolution," with 384 kbps recommended for stereo.
The official page does not document what happens when you come in under these figures. Treat the table as a target, not a threshold.
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
That runs in your browser tab — the file is read from disk, re-encoded locally and handed straight back, so nothing is uploaded to a server on the way to fixing an upload problem. The high-quality preset fits this case: you are not squeezing under a size cap, you are producing a clean H.264 MP4 for YouTube to convert. For the knobs rather than a preset, the video compressor exposes them, and how to compress a video without losing quality covers which ones move the needle.
Other causes, in rough order of likelihood
You uploaded a resolution between 4K and 8K. YouTube's resolution page notes: "In 2022, we started removing support for playback at resolutions between 4K and 8K. For example, we may no longer support playback at 5K." The word doing the work is playback — this is not an upload rejection, and a 5K master uploads normally. It just may not come back out at 5K. For 16:9, YouTube asks you to encode at 7680x4320 (8K), 3840x2160 (4K), 2560x1440, 1920x1080, 1280x720, 854x480, 640x360 or 426x240.
You baked black bars into the frame. YouTube is direct about this: "For best results, avoid adding padding or black bars directly to your video. Padding interferes with YouTube's ability to change the player dynamically to your video size and the viewer's device." The player adds its own padding where needed — for vertical video on a computer browser, padding that is "white by default, and dark gray when Dark theme is turned on."
Frame rate or interlacing. Two verbatim recommendations: "Content should be encoded and uploaded in the same frame rate it was recorded" and "Interlaced content should be deinterlaced before uploading." YouTube lists 24, 25, 30, 48, 50 and 60 as common, then says "other frame rates are also acceptable" — so this is about matching your source, not picking from a list.
Colours look wrong rather than soft. Different failure. YouTube recommends BT.709 for SDR and documents what it does with untagged files: where "the upload color space has unspecified TRC," it "assumes BT.709 TRC," and the same for unknown or unspecified matrix and primaries. It also unifies similar spaces — "BT.601 and BT.709 TRC are identical, and YouTube unifies them to BT.709." An untagged export is being interpreted, not read.
It is a Short. YouTube states: "You can upload Short videos with a maximum resolution of 1080p." A 4K vertical master is not buying you anything in that surface.
You re-uploaded something you downloaded from YouTube. YouTube's own download feature for your uploads gives you "MP4 files of YouTube videos that you've uploaded to YouTube in either 720p or 360p, depending on the video size." Round-tripping that back through an upload starts from 720p at best.
How to tell it worked
Re-open the quality menu after waiting rather than judging in the first minute — the higher tiers are the slow ones. Select the top resolution explicitly instead of trusting Auto, and if 4K is the target, watch on a browser or device that supports VP9. If the menu offers your source resolution and that tier looks right, the pipeline is doing its job.
If re-encoding did not help, check that you are not actually hitting a size or length ceiling — YouTube video too large to upload covers those. More upload and export fixes live in the fix guides.
FAQ
Does YouTube compress my video? Your file is converted, in YouTube's words, "to the highest resolution available to ensure successful playback on different devices and networks." YouTube does not publish the output bitrates or codec rules behind that conversion, so anyone quoting exact numbers is guessing. What is documented: the conversion always happens.
Why does my 4K upload only play up to 1440p? Two documented possibilities. The 4K tier may still be processing — YouTube says "higher qualities such as 4K or HD may take more time to process." Or your playback environment is the limit: "To view new 4K uploads in 4K, use a browser or device that supports VP9."
How long does YouTube take to process HD or 4K? No official number exists. YouTube only says processing time "can depend on a number of factors including quality, video length, video format, and traffic," and that Studio shows an estimate for SD, HD and 4K. Check the estimate on your own upload.
Should I upload at a higher bitrate than YouTube recommends? Nothing stops you — YouTube states "No bitrate limit is required, though we offer recommended bit rates below for reference." But the official page never describes what happens above or below those figures, so there is no documented gain to promise. Hitting the recommended number is the defensible target.
Why did my colours change after uploading? Most likely your export did not declare its colour metadata. YouTube documents that it assumes BT.709 when TRC, matrix or primaries are unspecified, and that it unifies functionally similar spaces before processing. Exporting with explicit BT.709 tags removes the guesswork.
Every quoted line above comes from YouTube's official help pages on uploading, recommended upload encoding settings and video resolution, checked 16 September 2026. YouTube changes these pages — verify against the official documentation before relying on them. The rest of the browser-side toolkit is at all Clapr tools.
