The upload tax
Why your video looks worse after uploading.
And what actually fixes it.
You exported a clean master and the platform played back something softer. Nothing went wrong: your file was the input to a second encoder, one tuned for the platform's delivery bill rather than your grade. Here is the mechanism, the numbers, and what survives.
No credit card required. Cancel any time.
Updated September 2026
The short answer
Your upload is an input.
What streams is their output.
Every consumer platform re-encodes every upload. The player never touches your file; it streams the copy their encoder produced, at the bitrate their delivery budget allows.
The mechanism is ordinary lossy compression run a second time, outside your control. MDN’s codec guide states the rule plainly: the more compression you achieve, the more loss of detail and fidelity. When you upload, your export gets decoded and fed through the platform’s encoder with the platform’s settings. You chose your export bitrate. They choose the streaming one, and the two numbers are far apart.
How far apart is documented. YouTube’s own upload guidance asks for 35 to 45 Mbps on standard-frame-rate 4K, and 53 to 68 Mbps at 60 fps. What we measured coming back at the 4K playback rung was about 13 Mbps. Vimeo publishes its ceiling itself: 22 Mbps maximum at 4K, 7 Mbps at 1080p 60fps, 2.5 Mbps at 720p. Your master streams at a small fraction of the rate you finished it at.
None of this is malice, and none of it is a bug. A platform delivering video to millions of viewers tunes its encoder for its own bandwidth bill, not for your grade. That trade is fine for reach. It is the wrong trade for a client review link or a portfolio piece, where the picture is the whole point.
uncompressed.io
Vimeo, 4K ceiling
YouTube, 4K
Vimeo ceiling read from Vimeo's playback-resolution guidelines, September 2026. YouTube figure measured, August 2026. The 200 Mbps example sits inside the browser's hardware-decode band: decoders top out around 300 to 400 Mbps, and 100 to 150 Mbps is the safe no-drop band.
Same master, same frame
Drag the line.
One 4K master, uploaded once to each platform, played back at maximum quality, identical frames grabbed. Ours on the left of the divider, Vimeo’s re-encode on the right.
VimeoThe test methodology
Destination by destination
What each destination does
to a 4K upload.
The tax is universal, but the rate varies. This is what the vendors themselves document, plus the two figures we measured.
Vimeo, Dropbox, and Google Drive cells read from vendor help documentation, September 2026. YouTube delivered figure measured, August 2026; its upload guidance is Google's own recommended settings. Instagram publishes no equivalent playback documentation we could verify, so its cells carry no numbers.
The pattern runs past the big platforms. Every general-purpose cloud treats video playback as a convenience feature with its own documented ceiling, and the ceilings are lower than most people sending a “quick preview link” realize:
1080p
Google Drive ceiling
Maximum playback resolution, any plan, any source file
480p
Box Business preview
Standard Business accounts are capped at 480p in Preview
~6 Mbps
OneDrive / SharePoint
Documented streaming ceiling at 1080p
30 min
Dropbox Basic links
Stream cap on a shared link when the file owner is on the free plan
Damage limitation
Exports that take less damage.
You cannot switch the platform’s encoder off. You can feed it a source it will damage less. Four levers, all mechanism, no folklore.
Feed it more than it needs
Export above the platform's recommended rate, never below it. YouTube itself asks for 35 to 45 Mbps on standard-frame-rate 4K and 53 to 68 Mbps at 60 fps. A starved source forces the second encoder to guess twice.
Upload the top resolution
Bitrate budgets live on rungs. Vimeo's published ladder gives the 4K rung a 22 Mbps ceiling while 1080p 60fps gets 7 Mbps and 720p gets 2.5 Mbps. Upload the highest rung you mastered so the least-starved encode exists at all.
Never compress twice
MDN's codec guide is blunt: more compression, more loss, and each lossy generation stacks on the last. Upload the export straight from your NLE, not a screen recording of it, and not a file another platform already re-encoded.
Watch the flat and the dark
Encoders starve smooth gradients first. Netflix's banding research puts the false staircase edges in skies, sunsets, dark scenes, and flat backgrounds, and finds a little dithering noise reduces their visibility. Check those shots before the client does.
These levers reduce the tax; none of them removes it. The platform’s encoder still writes every pixel the viewer sees. When the file itself is the deliverable, move it through a channel that never re-encodes: see delivering final files to clients.
The honest fix
Platforms that do not re-encode exist.
The consumer platforms are not broken. They are built for reach on other people’s connections. When the point is the picture, host somewhere that streams the file itself.
uncompressed.io streams the exact bytes you upload. Your export’s codec did the compressing once, under your control, and no second encoder ever runs: a 200 Mbps master streams at 200 Mbps, and the audio track streams exactly as exported. The player carries no platform branding on any plan, and every feature is on every tier including the free one. Storage is the only meter.
The honest trade
For what byte-for-byte hosting means in practice, read the guide to video hosting that doesn’t compress. If the work is client-facing, the review room puts timecoded notes and approvals on top of the same untouched stream, and the Vimeo comparison lines the two players up number by number.
Questions
Frequently asked
Why does my video look blurry after uploading?
Because the platform re-encoded it. Your upload is the input to their encoder, which targets a much lower streaming bitrate than your export: Vimeo documents a 22 Mbps maximum at 4K, and we measured YouTube 4K playback at about 13 Mbps in August 2026. Lower bitrate means discarded detail, and soft, blocky playback is what discarded detail looks like.
How do I stop Instagram from compressing my video?
You cannot switch it off; consumer social platforms re-encode uploads for mobile delivery, and Meta publishes no playback bitrate documentation we could verify, so we print no numbers for it. The levers that help are the same everywhere: upload the highest resolution you mastered, export at a generous bitrate, and never upload a file that has already been through another platform's encoder.
Does YouTube compress even high-quality uploads?
Yes, every upload. YouTube's own guidance asks creators for 35 to 45 Mbps 4K uploads at standard frame rates, then serves a far smaller re-encode; we measured about 13 Mbps at the 4K rung in August 2026. A better source still helps, because the second encoder guesses less when it starts from a clean master.
Should I upload 4K even if the project is 1080p?
Upload the highest resolution you actually mastered. Platform bitrate budgets are set per rung: on Vimeo the 4K rung gets a 22 Mbps ceiling while 1080p at 60 fps gets 7 Mbps and 720p gets 2.5 Mbps. If a 4K master exists, uploading it is the only way the least-starved encode is on offer at all.
What video hosting does not compress your video?
uncompressed.io streams the exact bytes you upload, with no re-encode and no bitrate ceiling below the file's own, on every plan including the free 1 GB tier. The trade is stated plainly: viewers on very slow connections buffer instead of being dropped to a mushy low-quality rung.
Host your work at full bitrate
uncompressed.io streams the exact bytes you upload. No re-encode, no bandwidth caps, no platform branding, on every plan.
Sources
- 1.Guidelines for determining playback resolution (Vimeo Help Center) (documented maximums: 22 Mbps at 4K, 7 Mbps at 1080p 60fps, 2.5 Mbps at 720p; read September 2026)
- 2.Recommended upload encoding settings (YouTube Help) (4K SDR upload guidance: 35-45 Mbps at 24/25/30 fps, 53-68 Mbps at 48/50/60 fps)
- 3.Store and play video in Google Drive (Google Drive Help) (maximum playback resolution 1920x1080 on any plan; videos process before shared playback)
- 4.Dropbox video and audio playback FAQs (Dropbox Help) (1080p preview cap for Basic owners, 30-minute stream cap on their shared links, preview bitrate not addressed)
- 5.Video Processing at Dropbox (Dropbox Tech Blog) (Dropbox's own description of previews as decode and re-encode transcodes; published February 2014)
- 6.Introducing Box Preview (Box Support) (Business accounts limited to 480p video in Preview)
- 7.Video playback overview (Microsoft Learn) (OneDrive/SharePoint streaming ladder tops out at 1080p and roughly 6 Mbps)
- 8.Web video codec guide (MDN) (lossy compression and banding mechanisms)
- 9.CAMBI: a banding artifact detector (Netflix Tech Blog) (where banding appears and why dithering reduces its visibility)