Reviewed by the SEOPointz team · Last reviewed June 2026. We checked current CDN and bandwidth pricing and the encoder guidance behind the numbers below before publishing. SEOPointz may earn a commission from some links; it never changes what we recommend.
Hosting a website is one problem. Hosting video that hundreds of people watch at the same time — without buffering, blurry frames, or a bill that triples overnight — is a different one entirely. A normal shared hosting plan is built to serve text and images measured in kilobytes. A single hour of 1080p video can move several gigabytes per viewer, and the cost of getting that wrong is an audience that closes the tab before your content loads. This guide explains what actually matters when you put video on the web, and how to size your hosting before, not after, your first traffic spike.
Why ordinary web hosting buckles under video
The core issue is bandwidth, and the math is unforgiving. Your outgoing bandwidth requirement is roughly your video bitrate multiplied by the number of people watching at once. A 3 Mbps stream watched by 100 concurrent viewers needs about 300 Mbps of sustained outbound throughput — and sensible engineers add 20–30% headroom on top so a sudden surge doesn’t trigger buffering. Most entry-level shared plans simply cannot hold that line, and many quietly throttle or suspend accounts that try. Video also hammers disk read speed and, if you transcode on the fly, CPU. The takeaway: don’t evaluate a host on storage alone. Evaluate it on sustained bandwidth and what happens when you exceed your allowance.
Bitrate and resolution: the numbers that drive your bill
Bitrate decides both your quality and your cost. For uploaded 1080p, YouTube’s encoder guidance lands around 8–15 Mbps, with roughly 4,500–6,000 kbps for 1080p at 30 fps using H.264. Push to 4K and you’re into the 35–45 Mbps range. Switching your codec from H.264 to H.265 (HEVC) can cut those requirements by nearly half at the same visual quality — a meaningful saving when you pay per gigabyte delivered, though it costs more CPU to encode and isn’t supported on every old device. Pick the lowest bitrate that still looks clean for your content; talking-head footage tolerates far less than fast motion or screen-share text.
Adaptive bitrate is non-negotiable
You should never serve one fixed file to every viewer. Adaptive bitrate streaming (ABR), delivered over HLS or DASH, packages several versions of the same video and lets each viewer’s player switch automatically based on their connection. A typical ladder runs five to eight rungs — for example 240p around 400 kbps, 360p near 800 kbps, 540p around 1.5 Mbps, 720p around 2.5 Mbps, and 1080p around 5 Mbps, with a 4K rung at 15–25 Mbps for premium content. The viewer on hotel Wi-Fi gets a watchable stream instead of an endless spinner, and your mobile audience stops burning data. The trade-off is storage and processing: every rung is a separate encode you have to create and store.
Transcoding: where your CPU bill hides
Building that ladder is called transcoding, and it is computationally expensive — especially for live, multi-bitrate HD streams. Simply delivering an already-encoded file to viewers needs very little server power; generating six variants in real time needs a lot. This is the single biggest reason people outgrow a basic VPS. You have three honest options: pre-transcode on-demand video once and store every rung, lean on a platform that transcodes for you, or run GPU-accelerated encoding for live work. For anything live, assume you need dedicated CPU or GPU resources, not a shared slice.
Use a CDN — the origin is not the delivery network
The biggest practical upgrade for video is separating storage from delivery. A content delivery network caches your video at points of presence near viewers, so a watcher in Madrid isn’t pulling frames from a server in Virginia. CDNs also absorb the concurrency that would crush a single origin. Pricing is usually per gigabyte and varies sharply by geography: video CDN rates run from roughly $0.005 to $0.08 per GB depending on region, with North American traffic cheap and South American transit far pricier. Bunny.net, for instance, advertises rates around $0.01/GB and bundles an adaptive-streaming product; AWS CloudFront and IO River are common alternatives. Always model your monthly delivery cost against your real audience geography before committing.
Choosing the right setup for your scale
| Approach | Best for | Watch out for |
|---|---|---|
| Shared hosting | A handful of short clips, low traffic | Bandwidth caps and throttling; not built for concurrent streams |
| VPS / cloud server | Modest on-demand libraries you control | You manage transcoding and scaling yourself; CPU limits on live |
| Dedicated / GPU server | Live streaming and heavy real-time transcoding | Higher fixed cost; over-provisioned if traffic is sporadic |
| Object storage + CDN | Scaling on-demand video to large, global audiences | Per-GB delivery cost can climb fast with popular content |
| Managed video platform | Teams that want ABR and DRM handled for them | Less control; per-minute or per-stream pricing adds up |
Frequently asked questions
Can I just host my videos on regular shared hosting?
For a few short, low-traffic clips, sometimes — but most shared plans cap or throttle sustained bandwidth and weren’t designed for concurrent streaming. The moment you have real viewers, the math forces you toward a CDN or dedicated resources.
How much bandwidth do I actually need?
Multiply your stream’s bitrate by your peak concurrent viewers, then add 20–30% headroom. A 3 Mbps stream with 100 simultaneous viewers needs roughly 300 Mbps before headroom — plan for the peak, not the average.
Is a CDN worth it for a small channel?
If your audience is geographically spread or you expect occasional spikes, yes — per-GB pricing means you pay for what you use, and the buffering protection alone usually justifies it. For a tiny, local audience you can wait, but build with the switch in mind.
For a deeper look at squeezing performance out of your stream, read our guide to web hosting for video content and optimizing streaming performance, and since latency is half the battle, see why speed matters so much in web hosting.
