Video hosting
Video hosting is the infrastructure that takes a video file and makes it stream well to any device. It covers ingest, encoding into several qualities, packaging into streaming formats, storage, delivery through a CDN (a network of servers close to viewers) and playback. Without it, a site hands every viewer one large file and hopes the connection keeps up. Hosting can be public, where anyone can watch, or private, where your own app decides who plays each video.
How does video hosting work?
An uploaded video is first ingested and checked, then transcoded into a bitrate ladder: the same video at several resolutions and bitrates, for example 1080p, 720p, 480p and 360p. Each version is cut into segments a few seconds long and packaged as HLS or DASH, often using CMAF, a shared segment format, so one set of files serves both.
The segments are stored at an origin and cached on CDN edge servers. When a viewer presses play, the player reads a manifest, the index that lists every version, starts with one it can fetch quickly, then switches up or down as the connection changes. That switching is adaptive bitrate streaming. It is what makes video start fast on good networks and keep playing on weak ones.
Video hosting vs. serving MP4 files from your own server
A plain MP4 on a web server or storage bucket plays as a progressive download: the browser pulls one file at one bitrate. There is no lower quality to fall back to on a weak connection, and no higher quality on a fast one. A phone on a moving train pulls the same bitrate as a TV on home fiber, and stalls when it cannot keep up.
Every view also moves the file's full bitrate for as long as it plays, so bandwidth grows in a straight line with views. Because the player is a bare video element, nothing reports startup time or stalls per view, and problems arrive as complaints. Hosting replaces the single file with an adaptive ladder, edge delivery and a player that reports what happened. That is why a course platform serving thousands of students, or an OTT catalog played on TVs and phones, rarely stays on raw MP4 for long.
Public vs. private video hosting
Public hosting puts a video where anyone with the link, or anyone browsing the platform, can watch it. Free public platforms such as YouTube work this way. They bring reach, but the player, the recommendations beside it and the ads around it belong to the platform, and so does most of the viewing data.
Private hosting keeps the decision about who watches inside your own app. An unlisted link is not private, because the stream URL can be copied and shared. Real access control happens at playback time. A signed URL carries a token with an expiry, and requests are refused once it lapses. DRM (digital rights management) goes further and encrypts the segments, so only a licensed player can decrypt them. Course platforms usually stop at signed URLs; OTT catalogs with studio content add DRM. Many teams run both: private hosting inside the product, and short clips posted to public platforms for reach.
What does a video hosting stack include?
A complete stack has the layers below. Which one matters most depends on the product: OTT services lean on DRM and large-screen quality, course platforms on signed access, and short-video apps on startup time in vertical feeds. A gap in any one layer shows up as a playback problem.
- Encoding turns each upload into the ladder, using codecs such as H.264, HEVC or AV1.
- Packaging builds the HLS or DASH manifests and segments.
- Storage and an origin keep every rendition of every video.
- A CDN delivers segments from servers near the viewer.
- The player handles adaptive switching, captions and DRM.
- Access control (signed URLs, tokens, DRM) and analytics (startup time, rebuffering, errors per view) close the loop.
How is video hosting priced?
Hosts usually price four things. Encoding is charged per minute of source video, or per output rendition. Storage is charged per gigabyte or per minute stored, and since every rung of the ladder is a stored file, the ladder shapes it. Delivery is charged per gigabyte sent or per minute watched. DRM, captions and analytics are often add-ons.
The billing model matters more than any single rate. Per-rendition encoding grows with the size of the ladder, and per-gigabyte delivery grows with bitrate, so a host that bills this way charges more as quality goes up. Per-minute delivery tracks watch time instead. Before choosing, model a month of your real library and viewing under each billing model, not just the headline price.
How does FastPix handle video hosting?
FastPix runs the whole hosting pipeline behind one API. Uploads arrive through resumable SDKs for web, iOS, Android and Flutter, or are pulled from S3, GCS, Azure Blob or any HTTPS URL, with webhooks on upload, encode and ready. Existing libraries move in bulk from other video platforms or S3 with the FastPix Migration Tool. Each video gets a per-title ladder in H.264 and HEVC (H.265) as standard, with AV1 available on request, packaged just in time as CMAF for HLS and DASH, so playback can start before the full encode finishes.
Delivery runs on a multi-CDN network of 300+ points of presence with per-viewer routing, and you can serve video and images from your own custom domain. Thumbnails render at any frame and size, as JPG, PNG or WebP, and follow the video's access policy. Playback IDs are public, signed with expiring tokens, or protected with Widevine, FairPlay and PlayReady DRM. The free, open-source FastPix Player runs on web, Android (built on Media3), iOS, tvOS and visionOS (built on AVPlayer) and Flutter. FastPix has ready-made plugins for WordPress, Moodle, Strapi and Sanity: the WordPress plugin adds uploads, embeds, AI captions and signed playback, including on LearnDash, TutorLMS and LifterLMS sites, and the Moodle plugins bring tracked video activities into Moodle courses. Where recordings must stay in one location, FastPix can set the storage region on request; ask FastPix which regions are available.
Standard encoding is free at every resolution up to 4K and counted once per source minute, not per rendition. Storage bills per rendition-minute and streaming per minute watched, and a resolution cap at 720p, 1080p, 2K or 4K shapes the bill. The free plan covers 10 videos, 100,000 streaming minutes a month and 30 live minutes, with no card.
