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.

START WITH 5 GB FREE

Video hosting for filmmakers · 5 GB free · Paid plans from USD 9/month

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 peaked around 30 Mbps and averaged in the mid-20s (September 2026). Vimeo publishes its ceiling itself: 22 Mbps maximum at 4K H.264, 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

200 Mbps master streams at 200 Mbps

Vimeo, 4K H.264 maximum

22 Mbps max

YouTube, 4K peak

≈ 30 Mbps

050100150200Mbps

File data rates are not visual-quality scores or universal playback guarantees. Browser performance depends on codec, profile, hardware and connection. Vendor rates refer to the documentation or measurements identified in this article’s sources.

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.

↔

Vimeo

The test methodology

We uploaded the exact same master, let each platform process it completely, grabbed identical playback frames, and exported both sides at the same maximum-quality settings. Nothing on this page favours our side. Zoom to 100 percent for one image pixel per screen pixel, the view a filmmaker checking compression actually uses.

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.

YouTube

Vimeo

Instagram

Dropbox link

Google Drive

What theviewer gets

The exact bytesyou uploaded

A re-encode

A re-encode,capped ladder

A re-encode(no spec to cite)

A transcodedpreview

A processed,capped stream

4K deliveredbitrate

The file's own,no ceiling below it

≈ 30 Mbps peak

22 Mbps for 4K H.264 max

No figure wecould verify

Not addressedin their FAQ

No 4K playbackat all

The fine print

Unlimited streams;no per-view charges apply

Asks for 35-45 Mbps4K uploads first

2 TB/month delivery cap,then a Custom or Enterprise quote

Basic-owner links:1080p, 30 min stream cap

Processes before playback;1080p ceiling on any plan

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 H.264 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. No per-view charges; plans vary by storage and team seats.

Choose an export for your viewer

Browser playback depends on the codec, profile, device and connection. Test a short export with the recipient. Slower connections can buffer; ProRes and camera RAW playback require a compatible macOS app setup.

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 H.264, 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 the 4K60 rung peaking around 30 Mbps and averaging in the mid-20s in September 2026, and a single 4K clip as low as 13 Mbps in August. 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 H.264 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 5 GB tier. The trade is stated plainly: viewers on very slow connections buffer instead of being dropped to a mushy low-quality rung.

Let your client see the film you exported

Upload a short browser-compatible export and share it with one client. Check the picture, collect feedback and choose a paid plan when you need room for more films.