Why your video looks blurry after upload

Diagnose in five minutes

Do these in order; most cases are resolved by the second step.

1. Let it play for thirty seconds, then look again

   Adaptive streaming starts at a conservative rendition and steps up as it measures bandwidth. The first seconds are not representative.

2. Open the quality menu and pick the top rendition

   If the picture sharpens, the automatic setting was choosing lower for a reason: bandwidth, player size or a rendition not yet available.

3. Check whether processing has finished

   Shortly after upload, higher renditions may still be encoding. Wait, refresh and check the menu again.

4. Go fullscreen on a good screen

   A 1080p rendition in a 500-pixel embed is downscaled; blur there is the page, not the video. Fullscreen shows the rendition as encoded.

5. Inspect the source with ffprobe

   ffprobe -v error -show_entries stream=width,height,bit_rate,r_frame_rate,avg_frame_rate -of default=nw=1 source.mp4 tells you the resolution, bitrate and whether the frame rate is constant.

Symptom, likely cause, fix

Cause one: adaptive streaming and the first few seconds

VideoBB delivers video as HLS, and the player's automatic quality setting picks a rendition based on measured bandwidth and the size of the player. When playback starts it has measured nothing, so it begins low to avoid a stall, then steps up as segments arrive. On a fast connection the climb takes a few seconds; on a congested one it may hover at 480p or 720p for a while and rise later. This is the behaviour that makes video start instantly, and it is by design. The adaptive streaming guide explains the decision logic. The fix, if you need to see the top rendition now, is the quality menu. The quality levels help page shows where it is and how Auto behaves.

Cause two: the renditions are not all there yet

After an upload completes, the transcoder produces every rung of the ladder, and they do not all finish at once. A video can be playable while its higher renditions are still encoding, in which case the quality menu simply does not offer them yet. This is most noticeable with long or 4K uploads, where the top renditions are the slowest to produce. Give it time, then refresh. If a rendition never appears, the source's resolution is the usual reason. The ladder does not upscale, so a 1280×720 source will never gain a 1080p rendition. And 1440p and 2160p renditions only show in the menu for Premium viewers.

Cause four: content the encoder finds expensive

Some footage is hard to encode at any fixed bitrate. Fine, moving texture such as water, foliage, crowds, confetti and rain changes every pixel every frame. Film grain and sensor noise look like detail to an encoder and consume bits that should have gone to the subject. Fast whole-frame motion, handheld shake and rapid cutting all force the encoder to start from scratch often. When the budget runs out, the encoder blurs fine detail first, then blocks flat areas. That is why a talking head looks pristine at 5 Mbps and a concert crowd looks like watercolour.

Two fixes work. First, reduce what does not need encoding: use mild noise reduction on grainy footage and stabilisation on shaky footage. Second, give the source more bits so the second generation starts clean. What you cannot do is raise the rendition's target, which is fixed for everyone.

Cause five: the player is smaller than you think, or larger

The automatic quality setting takes the player's size into account, and size is measured in device pixels. A 640-pixel-wide embed on a standard display needs no more than 720p. The same embed on a phone or laptop with a 2× display is 1,280 device pixels wide and can use 1080p. If the player is small, the top renditions are never selected automatically, which is efficient and correct but can look like the video is stuck at a low quality. Conversely, a 720p source stretched across a wide layout will be upscaled by the browser and look soft no matter what the player does. Size the embed with the responsive embeds guide and match your source resolution to how large the video will actually be shown.

Fixes, in order of effort

• Wait, then choose the top rendition manually to confirm what is actually there.
• Size the embed to the space it has and test in fullscreen before judging the file.
• Re-export from the original project at roughly twice the top rendition's bitrate, constant frame rate, at the resolution you shot.
• Apply light noise reduction and stabilisation to expensive footage before export.
• For screen recordings, capture at native resolution with a larger interface scale.
• Replace an upscaled or doubly-compressed source with a clean one; nothing downstream can recover what it lacks.

When it really is the compression

Occasionally every check passes and a scene still shows artefacts at the top rendition. That is the encoder working within a fixed budget on content that exceeds it: a hosted ladder trades some peak quality for a stream that plays everywhere without stalling. The mitigations above narrow the gap, and Premium viewers gain 1440p and 2160p renditions with more room. The transcoding guide follows a file through the pipeline. If one video fails or looks broken everywhere while others play well, the playback problems help page explains how to report it.