Adaptive streaming, explained without the acronyms

The idea is simple even if the vocabulary around it is not. Instead of one video file sent to everybody, several versions exist at different qualities, and the one that gets sent depends on the device and the connection asking.

The problem it solves

Pick a single file and you have to choose who to disappoint.

Encode for quality and a shopper on a weak mobile signal waits, buffers, and leaves. Encode for the weak signal and everyone on a desktop gets a soft, blocky video that makes the product look worse than it is — and product video that flatters the product is the entire point.

There is no single file that is right for both. Adaptive delivery is the admission that the question has more than one answer.

What actually happens

The video is encoded at several resolutions — 480p, 720p, 1080p — and the player, or the server, works out which is appropriate from what it can see about the device and the network. A phone on a slow connection receives the light version. A desktop on fibre receives the full one.

The shopper is aware of none of it. They see a video that starts quickly and looks as good as their connection allows.

Why it matters more for stores than for entertainment

Somebody watching a film will wait ten seconds for it to start. They have committed to the next two hours; ten seconds is nothing.

Somebody scrolling a collection page has committed to nothing at all. A video that has not started within a second or two has lost, and it does not get a second chance, because they have already scrolled past. Adaptive delivery is not about picture quality here — it is about starting at all.

The mobile reality

Most video traffic on a store is mobile, and mobile connections are far more variable than anyone building on a desk imagines. The same shopper is on fast home wi-fi in the evening and a patchy signal on the train in the morning, and they expect the site to work in both.

This is the single strongest argument for adaptive delivery: it is the difference between a store that works on a train and one that does not.

What you have to do about it

Ideally nothing. Encoding into multiple versions and choosing between them is work a platform should do on upload, without a merchant needing to know the word “bitrate”.

The one thing worth doing on your side is uploading a decent source. Everything derived from it inherits its quality, and no amount of clever delivery recovers detail that was never in the file.