The client saw a soft image
Stop a video player dropping to 480p for clients.
Diagnose it, then take the ladder out of the path.
A client opens the link, watches the first thirty seconds, and writes back that it looks soft. Nothing about your export changed. What changed is the rung of the ladder the platform decided to serve. Here is how to tell a ladder drop from a machine problem, what the published ceilings and dimension gates actually say, and what happens when there is no ladder at all.
No credit card required. Cancel any time.
Updated September 2026
What a ladder is allowed to do
A published ceiling of 22,
and a floor at 0.3.
Vimeo is the one major platform that publishes its delivery ladder, which makes it the honest example. Every figure below is Vimeo’s own, and Vimeo states plainly that the bitrates listed for each resolution are a maximum, and that a video could transcode at a lower bitrate depending on the complexity of the image.
22 Mbps
4K, maximum
The top rung of Vimeo's standard H.264 ladder. The maximum, not the guaranteed rate.
7 Mbps
1080p60, maximum
The rung most client links actually play at, when the top rung is not chosen.
0.3 Mbps
240p, the floor
The bottom rung a player can drop to. The soft frame your client described lives here.
3,648 px
Gate for a 4K rung
Larger side, or 2,052 px on the smaller side. Miss it and the rung is never generated.
A rendition ladder is a set of copies of your film at descending quality. The player picks a rung based on the connection it measures, and switches rungs mid-play without asking anyone. That is the design working correctly. It exists so a stranger on a phone on a train never sees a spinner, and for that audience it is the right technology.
It is the wrong technology for a client sign-off, because the switch is silent. Your client does not know they watched 540p. They know the grade looked flat and the skin looked plastic, and they say so in an email you now have to answer. The one number nobody sees is the one that explains everything.
Before you change anything
Is it the ladder,
or is it the machine?
Four checks, in order, all of which the reader can run today without buying anything. Run them before you rebuild an export or move a library.
Read the player's own quality indicator
While the client watches, have them open the player's quality menu and read what it says. Two different answers matter. If it names a low rung while a higher one is listed, the ladder chose and the connection is the reason. If the top rung is not in the list at all, the platform never generated it, and no connection on earth will produce it.
Play the same file locally
Send the client the same export as a file and have them play it from their own disk. If the local file looks right, nothing is wrong with your export and nothing is wrong with their display. The softness was created in delivery. If the local file also looks soft, stop reading about players and go back to the export settings.
Try a second network
The same link, on a phone hotspot, then on the office line. A drop that appears on one network only is a ladder reacting to that network, which usually means an office VPN, a shared conference line or a hotel. A drop that follows the client from network to network is not the ladder.
Measure the file you uploaded
Open the export and read its pixel dimensions, not the label on the timeline. A 3,840 by 2,160 master clears Vimeo's 4K gate; a 3,440-wide ultrawide export does not clear the 3,648 larger-side gate, and its smaller side of 1,440 does not clear 2,052 either. That film gets a 2K top rung and a client who wonders why 4K is missing.
The gate is the check almost nobody runs
The platform you cannot diagnose
YouTube publishes
no delivered bitrate, at any resolution.
YouTube states that it always re-encodes videos to optimize their playback quality. It publishes a detailed table of recommended upload bitrates, 8 Mbps for 1080p at standard frame rate, 35 to 45 Mbps for 2160p, along with a full encoding spec: H.264 High Profile, closed GOP of half the frame rate, two consecutive B frames, 4:2:0 chroma subsampling.
What it does not publish, anywhere, is what a viewer receives. Not a delivery ladder, not a per-resolution bitrate, not a floor. The only related figure on any of its pages is that 1080p Premium is an enhanced bitrate version of 1080p, which tells you a normal 1080p stream is something less than that without saying what either number is.
So there is no diagnosis to run. You can confirm that quality dropped, and you cannot reason about what the drop cost, because the baseline is unpublished. If a client is approving work on a YouTube link, the honest position is that you do not know what they saw. One YouTube behaviour is worth knowing regardless: a fresh upload is initially processed in low quality, and a 60-minute 4K 30fps video can take up to four hours to finish high-resolution processing. A soft image on a link sent ten minutes after upload may simply be a film that is not finished processing yet.
What you control today
Four fixes
before you change host.
Clear the gate on purpose
Export at dimensions that clear the top rung's gate with room to spare, rather than at whatever the timeline happened to be. If a delivery is ultrawide or anamorphic, pad it to a shape whose larger side clears 3,648 pixels. It is an ugly workaround and it is the only one that makes the top rung exist.
Give the encoder a clean source
Vimeo's own upload guidance asks for a constant rate factor of 18 or below, a 1:1 pixel aspect ratio, a constant frame rate, and 10 to 20 Mbps at 1080p or 30 to 60 at 4K. None of this raises the delivery ceiling. All of it stops you handing the platform a source that transcodes worse than it had to.
Wait for processing before you send the link
On YouTube the first version live is a low-quality one, and high-resolution processing on a long 4K film can run for hours. Sending a review link the moment the upload bar fills is a self-inflicted quality complaint.
Do not review over a hotel or conference line
A ladder cannot tell the difference between a bad connection and a busy one. If the sign-off matters, agree with the client that the first viewing happens on a known network. This is a workaround, not a fix, and it puts the burden on the person you are asking to approve the work.
Notice what none of these do. They improve the source and the odds. They do not move the ceiling, because the ceiling is the platform’s, not yours, and they do not stop a mid-play switch, because the switch is the whole point of the ladder. If the drops keep happening, the ladder itself is the thing to remove.
The structural fix
Take the ladder out,
so there is no rung to fall to.
uncompressed.io does not transcode. There is no encode step on upload and no rendition ladder anywhere: the player is handed the exact bytes you uploaded, through a short-lived link. Your file is the ceiling, and there is no lower copy in existence for a player to quietly switch to.
Vimeo and YouTube figures from their own help centres, fetched 5 September 2026. Vimeo states the listed bitrates are a maximum and that a video could transcode lower depending on image complexity. What plays here is decided by the viewer's browser decoder, not by a platform rule. ProRes 422, ProRes 4444 and DNxHR are hosted at full size for client download rather than played in a browser. 8K plays when the viewer's hardware decodes it.
The practical consequence for the problem on this page is narrow and complete. A client who opens the link sees the export you approved, at the bitrate you exported it at, on every play, on every network, for the life of the link. There is no quality menu to check because there is nothing to choose between. Delivery is not metered either: the Terms make storage the only meter, with no bandwidth caps, and the pricing page carries unlimited views, uploads and viewers on every plan, the free Starter plan included. What each plan buys is storage: 5 GB free on Starter with one film at a time, 100 GB on Lite, 500 GB on Pro, 1.5 TB hot plus 1 TB cold on Max, 2 TB hot plus 2 TB cold on Vault.
The honest trade
Without a ladder,
it buffers instead.
This is the part a page that only sells would leave out. A ladder is not a defect. It is a deliberate exchange of image quality for uninterrupted playback, and removing it means making the opposite exchange.
What you gain
Certainty. The frame your client judges is the frame you graded, and a complaint about the image is now a real note about your work rather than a network artefact. Nothing silently substitutes a lower-quality copy mid-play, because no lower-quality copy was ever made.
What you give up
Graceful degradation. A 180 Mbps export needs a connection that can carry 180 Mbps. When the line cannot, the player pauses and waits rather than switching down. On a train, on hotel wifi or on a congested mobile network, a heavy master will stall where a ladder would have kept moving at 540p.
Who should stay with a ladder
Anyone publishing to a general audience on unknown connections: marketing films, public launch videos, anything embedded on a site that strangers on phones will hit. For that audience, playback that never stops is worth more than a bitrate nobody in it can perceive, and a platform with a ladder is the correct tool.
Who should drop it
Anyone whose viewer is being asked to judge the image: a client approving a grade, an agency signing off a spot, a colourist reviewing a pass, a director watching a cut. That audience is small, known, usually on a decent line, and entirely capable of waiting five seconds for a buffer. What it cannot do is approve a rendition and believe it approved your film.
The choice is per-audience, not per-company, and most working studios need both. The public launch film can live on a platform with a ladder, where its job is to reach strangers. The review link, the deliverable and the reel go where nothing is re-encoded, because their job is to represent the work exactly. Sizing that second library is the only real decision left, and 5 GB of it is free to try with your own footage.
Questions
Frequently asked
How do I tell whether the platform dropped the quality or my client's machine did?
Three checks, in this order. Read the player's own quality indicator while the client watches: on a platform with a rendition ladder it names the rung being served. Have the client play the same export from their own disk; if the local file looks right, the softness happened in delivery, not in your export. Then try a second network, a phone hotspot against the office line. A drop that follows the network is the ladder reacting. A drop that follows the machine is decode or display.
My upload is 4K but the player never offers 4K. Is that my connection?
Not necessarily. Vimeo publishes dimension gates that decide which rungs are generated at all: a 4K rendition needs a larger side of at least 3,648 pixels or a smaller side of at least 2,052 pixels, and 2K needs 2,432 or 1,368. A film that misses its gate never gets that rung made, so no amount of bandwidth will produce it. Check the pixel dimensions of the file you uploaded before you blame the line.
What bitrate does YouTube actually deliver at 1080p?
Nobody outside Google knows. YouTube publishes recommended upload bitrates, 8 Mbps for 1080p at standard frame rate, and states that it always re-encodes videos to optimize their playback quality. It publishes no delivered video bitrate at any resolution. An upload recommendation is not what a viewer receives, and anyone quoting one as a delivery figure is guessing.
If there is no ladder, what happens when a client is on bad wifi?
The player buffers. That is the honest trade. A ladder degrades the image so playback never stops; no ladder keeps the image and stops playback instead. For a colourist, a client approving a grade or an agency signing off a spot, a pause is information and a mushy frame is a lie. For an audience on mobile networks, the ladder is the better technology.
What should I actually upload for a client review?
A high-bitrate export in a codec the browser decodes, 100 to 200 Mbps in H.264 or HEVC, at the pixel dimensions you want the client to see. The player streams that file at that bitrate. ProRes 422, ProRes 4444 and DNxHR are hosted at full size for client download rather than played in a browser. Camera RAW never streams anywhere; finish first, then upload.
Does sending a bigger file cost me more?
Not in delivery. Storage is the only meter here, and the Terms state there are no bandwidth caps; the pricing page carries unlimited views, uploads and viewers on every plan, free included. A 180 Mbps export watched forty times costs the same as a 5 Mbps one. What it costs is hot storage, and the free Starter plan gives you 5 GB of it to test the difference with your own footage.
Send the file, not a rendition of it
uncompressed.io hands the player the exact bytes you uploaded. There is no ladder, no ceiling below your file, and no bandwidth meter on any plan.
Sources
- 1.Vimeo Help Center: guidelines for determining playback resolution (delivery ladder, maximum bitrates, rendition dimension gates) (fetched 5 September 2026)
- 2.Vimeo Help Center: how transcoding works ("re-encoded into several formats") (fetched 5 September 2026)
- 3.Vimeo Help Center: recommended upload settings (CRF 18 or below, constant frame rate, 1:1 pixel aspect ratio, per-resolution upload bitrates) (fetched 5 September 2026)
- 4.Vimeo Help Center: video above 4K (HEVC delivery, device and browser support, mobile excluded) (fetched 5 September 2026)
- 5.YouTube Help: recommended upload encoding settings (upload bitrates, H.264 High Profile, 4:2:0 chroma, closed GOP) (fetched 5 September 2026)
- 6.YouTube Help: supported file formats ("YouTube always re-encodes videos to optimize their playback quality") (fetched 5 September 2026)
- 7.YouTube Help: video processing and upload quality (initial low-quality processing, up to 4 hours for a 60-minute 4K 30fps video) (fetched 5 September 2026)
- 8.YouTube Help: 1080p Premium ("an enhanced bitrate version of 1080p") (fetched 5 September 2026)
- 9.uncompressed.io pricing: plans, storage, unlimited views and viewers (fetched 5 September 2026)
- 10.uncompressed.io Terms: storage is the only meter, no bandwidth caps (fetched 5 September 2026)