Video hosting, explained
What happens between dragging a file onto an upload page and a stranger pressing play on a phone: storage, transcoding, adaptive streaming and the delivery network in between.
Video hosting is a service that stores your uploaded video, turns it into versions that stream well and delivers them to viewers through a player. With a host, you never serve multi-gigabyte files from your own web server.
Guides in this hub
- ExplainerWhat is video hosting?A plain-English tour of what a video host does with your file after upload. It also shows the point where a video tag on your own server stops being enough.8 min readRead
- ComparisonVideo hosting vs YouTubeYouTube is a video host, an audience and an advertising business at once. A dedicated host is only the first of those. Here is how to decide which combination you actually want.7 min readRead
- ComparisonSelf-hosting vs a video hosting platformServing your own mp4 is simple, cheap and works until it doesn't. This is a clear account of what you are taking on when you self-host, and what a platform is really doing for you.7 min readRead
- Deep diveVideo hosting for businessTraining clips, product demos, support tutorials and internal news: business video has different needs from entertainment. Privacy, control and reliability come before reach.8 min readRead
- Deep diveVideo hosting costs: storage and bandwidthVideo costs money in two places: keeping it and sending it. Both can be estimated from numbers you already have. This guide shows the arithmetic and where the surprises hide.8 min readRead
A web page is a few hundred kilobytes. A ten-minute 1080p video is a few hundred megabytes. The person watching expects the first frame within a second and no stalls for the next ten minutes. Those two facts are why video hosting is a separate job from ordinary web hosting.
The file is too large to treat like an image. It is too varied to send at one quality to every device. And it is too heavy to serve from one machine once many people press play at once. This hub follows the file in order: upload, storage, transcoding, playlists and delivery. Each stage has its own guide, and this page is the map.
Stage one: getting the file in
Uploading is the part people underestimate. Browsers were built for forms, not for 3 GB files on hotel Wi-Fi. The uploading hub covers the whole process.
Why plain form uploads fail
A plain HTML form upload fails silently if the connection drops at 97 percent. So serious hosts accept uploads in chunks over a resumable protocol.
VideoBB uses tus, an open protocol built on HTTP. The client asks the server how many bytes it already has, then continues from there. That is what lets an upload survive a laptop lid closing. Resumable uploads explained goes into the protocol itself.
What VideoBB accepts
Files up to 4 GB are accepted in any of the common containers: mp4, mkv, avi, mov, webm, m4v, mpg, wmv, flv, ts and 3gp.
Stage two: storing the source
The file you upload is the mezzanine, the master copy every later version comes from. Hosts keep it in object storage, not on a web server's disk. Object storage is built for large files that never change. It copies them across machines and is billed by the gigabyte, not by the server.
Why the original is rarely what viewers get
The original is the wrong bitrate for most connections. It may be in a container browsers cannot play, such as mkv or avi. And it is a single quality, with no way to step down when a phone moves from Wi-Fi to a weak mobile signal.
If the difference between an mkv and the H.264 stream inside it is not yet clear, read container vs codec.
Stage three: transcoding into a ladder
Transcoding decodes the source once and encodes it again several times, at different sizes and bitrates. The result is called a bitrate ladder. Each rung is then cut into segments a few seconds long and listed in a playlist.
The VideoBB ladder
On VideoBB the ladder is 144p, 240p, 360p, 480p, 720p and 1080p for every upload. When the source is large enough, 1440p and 2160p are made too, and Premium members can watch them. Segments are six seconds long.
Why low quality appears first
Transcoding is the most computing-heavy step in the pipeline. VideoBB runs it in two passes. The first makes thumbnails and the small renditions, so the video can play quickly. The second adds the larger ones. That is why a fresh upload may play at low quality before the higher rungs appear. Video transcoding explained covers what the encoder does and why it takes as long as it does.
What each stage produces
The same ten-minute upload, followed through the pipeline.
| Stage | Input | Output | Where it lives |
|---|---|---|---|
| Upload | Your file, in chunks | One verified source file | Object storage |
| Transcode | Source file | Six to eight renditions, segmented | Object storage |
| Package | Renditions | Master playlist plus one media playlist per rung | Object storage, cached at the edge |
| Deliver | Playlists and segments | A stream that adapts to the viewer's bandwidth | CDN edge, then the player |
Stage four: adaptive delivery
The player never downloads the whole video. It streams it in segments with HTTP Live Streaming (HLS), which Apple specified and published as RFC 8216. The video streaming hub explains every part of this stage.
How the player switches quality
The player fetches a master playlist that lists the rungs. It picks one and requests segments a few at a time, timing how fast each arrives. If segments arrive faster than they play, it steps up a rung at the next segment. If the buffer is draining, it steps down.
That is why a video keeps playing through a bandwidth dip instead of freezing on a spinner. VideoBB's player shows this as an automatic quality setting next to the manual rungs. What is HLS streaming and adaptive bitrate streaming explained cover the details.
Why a CDN sits in front
Because everything is plain HTTP, a content delivery network (CDN) can cache the segments. It keeps copies of popular segments on servers close to viewers. So a video watched by ten thousand people in one evening is served mostly from cache, not from origin storage. CDN for video delivery explains what that changes about cost and speed.
Frequently asked questions
Is video hosting the same as web hosting?
No. Web hosting serves pages and small files from a server. Video hosting adds a processing pipeline: transcoding, segmenting and playlists. It also adds a delivery layer, with adaptive streaming through a CDN. You can host a small video on a web server. But you cannot get adaptive quality, resumable uploads or thumbnails without building those pieces.
Do I lose quality when a host transcodes my video?
Every re-encode loses something. But a well-made 1080p rung at a sensible bitrate looks very close to a good source. Quality loss mostly comes from a poor source: upscaled footage, low bitrate or heavy compression before upload. Upload the best file you have and let the host make the smaller rungs. See why video looks blurry after upload for the usual causes.
Can I host a video privately?
Yes. VideoBB lets you set each video to public, unlisted or private. Unlisted means anyone with the link can play it, but it is not listed or searchable. Private means only you can play it. Embeds follow the same setting, so a private video does not play on a third-party page. The help page on embedding a video on your own site shows how embeds work.
Sources
- RFC 8216: HTTP Live Streaming — The HLS specification: playlists, segments and rendition switching.
- tus resumable upload protocol — The open protocol VideoBB uses for chunked, resumable uploads.
- MDN: HTTP range requests — How browsers seek within a progressively downloaded file.
- Apple: HTTP Live Streaming documentation — Apple's HLS authoring and deployment guidance.