What is video hosting?

The problem hosting solves

Video is the heaviest thing on the web by a wide margin. A single 1080p file encoded at a moderate 5 Mbps uses about 2.25 GB per hour of playback. That is arithmetic, not a statistic: 5 megabits per second times 3,600 seconds, divided by 8 bits per byte. Serve that to a hundred simultaneous viewers and you need a sustained 500 Mbps of upstream bandwidth from wherever the file lives. Ordinary web hosting plans are not built for that and neither is the mental model of a file that gets downloaded and then played.

The second problem is variety. Viewers arrive on phones with weak signal, laptops on fibre, televisions on Wi-Fi in a far corner of the house. One file at one bitrate is wrong for most of them: too big for the phone, needlessly small for the television. The third problem is compatibility. Browsers play a narrow set of containers and codecs natively, and the file that came out of your camera or editor may not be among them. A video host exists to absorb all three problems. Then you can treat video the way you treat an image: upload it, get a link, put it on a page.

What happens to your file, in order

Each step below is a separate system with its own failure modes.

1. Ingest

   The upload is received in chunks over a resumable protocol, so a dropped connection resumes from the last confirmed byte rather than starting again. VideoBB uses tus for this and accepts files up to 4 GB. How to upload 2 GB video files covers the practical side.

2. Inspect

   The host probes the file to learn its container, video codec, audio codec, resolution, frame rate, duration and whether it is actually a video at all. Files that fail this check are rejected before any expensive work begins.

3. Store the source

   The original is written to object storage as the mezzanine copy. Everything else is derived from it, and it is what a re-encode would start from if the rendition set ever changes.

4. Transcode

   The source is decoded once and encoded into a ladder of renditions. On VideoBB that is 144p through 1080p for every upload. 1440p and 2160p are made too when the source is large enough, and Premium members can watch them.

5. Segment and package

   Each rendition is cut into short segments and described in an HLS playlist. A master playlist lists all the rungs so the player can switch between them.

6. Generate assets

   Thumbnails and scrub-bar preview images are extracted automatically, so the video has a poster frame and a hover preview without any manual work.

7. Deliver

   Playlists and segments are served over HTTP through a content delivery network, and the embeddable player fetches them a few segments at a time, adapting quality to the connection.

Why the file is transcoded rather than served as-is

It is tempting to think of transcoding as an unnecessary detour. You uploaded a perfectly good mp4; why not just send it? The answer is that a single file cannot adapt. Almost every host delivers video with HTTP Live Streaming, which Apple documents in its HLS guide. It gives the player a choice of rungs and lets it switch between them at segment boundaries. That choice only exists if the host has produced the rungs. The video streaming hub follows this delivery side step by step. Transcoding is also where compatibility is fixed: an mkv containing H.265 becomes a set of H.264 segments that any browser can decode. Video transcoding explained goes deeper into the encoding step, and H.264 vs H.265 vs AV1 explains why the output codec matters.

Progressive download vs adaptive streaming

Both use plain HTTP. The difference is in what the player is allowed to do.

When a video tag on your own server is enough

Honesty matters here, because a host is not always necessary. Say you have one short clip on a low-traffic page. The mp4 is properly encoded, with its index at the front, and most viewers have good connections. Then <video src="clip.mp4"> works. Browsers support seeking through HTTP range requests, and the page will play. The self-hosting comparison lays out the point at which that stops being true, and how to embed video on a website shows both approaches side by side.

Signs you have outgrown a plain file

Any one of these is usually enough to justify moving the video to a host.

• Files larger than a few hundred megabytes, where a failed upload or a failed download is expensive to repeat.
• Viewers on mobile connections who complain of buffering, which a single-bitrate file cannot fix.
• Source footage in a container or codec browsers do not play natively, such as mkv, avi, wmv or H.265 in mp4.
• More than a few simultaneous viewers, where the web server's uplink becomes the bottleneck.
• A need for privacy controls, such as unlisted or private videos, that a public URL cannot provide.
• A wish for thumbnails, scrub previews and a consistent player without building them yourself.

Ownership, privacy and where the video appears

A hosting platform in the sense used here is not the same as a public video site. On VideoBB every video has a privacy setting, so you can host a training clip that only people with the link can watch, or a private draft nobody else can. The embed guide explains how the player fits into your own pages. Video hosting for business covers the questions companies tend to ask about control and continuity. If discoverability is the goal instead, make the video public and give it a clear title and description.