Understanding bandwidth and egress fees in hosting
By CloudCostly editorial team Published July 3, 2026 Updated July 12, 2026
When you compare hosting, RAM and vCPU are easy to reason about. Bandwidth is where bills go sideways, because providers treat it very differently. This guide explains how bandwidth and egress fees work, when they matter, and how to keep them under control.
What bandwidth means in hosting
Bandwidth, or data transfer, is the volume of data moving in and out of your server. In practice the number that matters is outbound transfer, the data you send to visitors, because inbound is usually free. How a host bills this outbound traffic makes a big difference to your total cost.
Metered vs unmetered
Budget VPS hosts usually include a large allowance, often tens of terabytes a month, or advertise unmetered transfer on a shared port at a fixed speed. Hyperscale clouds work the opposite way: compute is cheap to start, but every gigabyte of egress is billed. For a busy media site, that difference can dwarf the cost of the server itself.
How egress fees work on hyperscalers
On AWS, Azure and Google Cloud, data leaving the network is charged per gigabyte, often with tiered pricing that gets cheaper at high volume but is rarely free. Transfer between regions and out to the internet are billed separately. The instance price is only part of the story, which is why a cheap-looking cloud VM can produce a surprising bill.
When bandwidth matters most
If you serve large files, video, or lots of images, included bandwidth can matter as much as CPU. A media-heavy site on a metered cloud can pay more for traffic than for compute. A text-based site, by contrast, uses little bandwidth and can ignore the issue. Know which camp you are in before choosing a host.
Estimating your bandwidth
| Site type | Rough monthly transfer |
|---|---|
| Small blog | A few GB to tens of GB |
| Busy content site | Hundreds of GB |
| Image-heavy store | Several TB |
| Video or downloads | Tens of TB or more |
A simple estimate is average page weight multiplied by monthly page views, plus headroom. If that number is large, prioritise included bandwidth.
How to keep traffic costs down
Three habits cover most of it. Put a CDN in front of static assets so the edge absorbs the traffic. Prefer hosts with generous included transfer if your workload is bandwidth-heavy. And use object storage that does not charge egress for large media. Together these can turn a scary bandwidth bill into a rounding error.
Which hosts give the most bandwidth
Budget European hosts lead here, bundling 20 TB or more into low monthly prices, and some advertise unmetered transfer. If bandwidth is your constraint, these are worth a close look. See the plans with the most included traffic on our bandwidth cost page, and compare providers on the providers page.
Inter-region and inter-zone transfer
Egress to the internet is the obvious cost, but on hyperscalers data moving between regions, and sometimes between availability zones, is also billed. This catches people who spread a system across regions for resilience and then pay every time services talk to each other. If you run a multi-region setup, design it so chatty components stay in the same region, and be deliberate about what genuinely needs to cross a boundary. On a single flat-rate VPS this whole category of cost simply does not exist, which is part of why simple architectures are often cheaper.
The economics of a CDN
A content delivery network can look like an extra cost, but it usually saves money on a bandwidth-heavy site. The CDN serves cached assets from the edge, so those bytes never leave your origin and never incur origin egress. Many CDNs include a generous free tier, and even paid plans are cheap per gigabyte compared with hyperscaler egress. The result is faster delivery for visitors and a smaller origin bill, which is why a CDN is one of the first things to add when traffic grows.
A worked example
Consider a media site serving 10 TB of images a month. On a metered cloud charging around nine cents per gigabyte after a small free allowance, that traffic alone could cost several hundred dollars, dwarfing the price of the server. Put a CDN in front and cache the images, and most of that 10 TB is served from the edge for a fraction of the price, while the origin egress drops to a trickle. The same workload on a budget VPS that includes 20 TB of transfer would incur no overage at all. The lesson is that for media-heavy sites, the bandwidth model can matter more than every other spec combined.
How to monitor your egress
You cannot manage traffic costs you cannot see, so make egress visible. Your host's dashboard usually shows monthly transfer, and on hyperscalers the billing breakdown separates egress as its own line. Server-side tools and analytics reveal which pages, files and endpoints generate the most outbound data, which is often a handful of large images or a popular download. Once you know where the bytes go, the fixes are targeted: cache the heavy assets, compress them, or move them behind a CDN. A monthly glance at your transfer figures catches a runaway before it becomes an expensive surprise.
Image and video optimisation
Much of a typical site's bandwidth is images, so optimising them is one of the highest-leverage things you can do. Serving modern formats like WebP or AVIF, sizing images to the space they occupy rather than shipping huge originals, and lazy-loading below-the-fold media can cut image bandwidth by half or more. For video, hosting it on a dedicated video service rather than serving raw files from your origin avoids enormous transfer bills. These changes also make your site faster for visitors, so they pay off twice: lower costs and better performance.
Network quality, not just quantity
Included terabytes are only half the bandwidth story; the quality of the network matters too. Two hosts can both advertise generous transfer while delivering very different real-world speeds, depending on how well their network is connected to the wider internet and how much they oversell capacity. A well-peered provider routes your traffic efficiently to visitors, while a poorly connected one can feel slow even with a large allowance. Reviews, looking-glass tests and the experience of other users are the best guide here, since raw transfer numbers do not capture how the network actually performs under load.
Planning for growth
Bandwidth needs rarely stay still, so plan for the direction of travel. A site that adds video, grows its audience, or launches a downloads section can see transfer climb quickly, and a plan that was comfortable can become a bottleneck or a cost. The safe approach is to choose a host whose bandwidth model scales gracefully, whether that is generous included transfer or a CDN that absorbs the growth, so that success does not trigger a painful migration or a shock invoice. Reassess your transfer every few months against your traffic, and adjust before the ceiling arrives rather than after.
Choosing a host for bandwidth-heavy sites
If your project is fundamentally about serving lots of data, choose your host with bandwidth first. Budget European providers that include 20 TB or more, or advertise unmetered transfer, are natural fits and avoid per-gigabyte anxiety entirely. Pair one with a CDN and object storage for media, and even a large, popular site stays affordable. Our bandwidth cost page lists the plans with the most included transfer, and the plans page lets you weigh that against the rest of the specs.
Estimating a realistic monthly figure
To size bandwidth without guesswork, do a quick calculation. Take your average page weight, the total size of everything a page loads, and multiply by your expected monthly page views, then add a margin for downloads, media and growth. A content site with a one megabyte average page and a hundred thousand monthly views uses roughly a hundred gigabytes, comfortably within any plan. An image or video site with heavy pages and the same traffic can use ten times that, which is where included allowances and a CDN start to matter. Running this simple estimate before choosing a host tells you whether bandwidth is a non-issue or the deciding factor.
Bandwidth and the case for a simple architecture
One underrated way to avoid bandwidth surprises is to keep your architecture simple. A single flat-rate server with generous included transfer, fronted by a CDN, has no inter-region fees, no per-gigabyte egress, and no complex bill to decode. The moment you spread services across regions or lean heavily on metered cloud egress, traffic costs become harder to predict and easier to run up. For most sites, the simplest setup is also the cheapest and the easiest to reason about, which is a good argument for resisting complexity until you genuinely need it. Compare included-bandwidth plans on our plans page to see how far a simple setup stretches.
Conclusion
Bandwidth is the hidden variable in hosting costs. Metered egress on hyperscalers can quietly dominate a bill, while budget hosts include generous transfer. Estimate your traffic, cache with a CDN, and choose a host whose bandwidth model fits your workload. When in doubt, our calculator helps you compare the all-in cost.
Frequently asked questions
What is egress?
Egress is data leaving a provider network, mainly the traffic sent to your visitors. On hyperscalers it is metered and billed per gigabyte, which is the main way a cloud bill grows beyond the instance price.
What does unmetered bandwidth mean?
It means the provider does not cap or bill your transfer, usually on a shared port at a fixed speed. It is common on budget VPS hosts and great for bandwidth-heavy sites, though the port speed still limits throughput.
How much bandwidth does a website need?
A typical content site uses modest bandwidth, but image and video-heavy sites can use terabytes a month. Estimate average page weight times monthly page views, then add headroom.
How do I reduce bandwidth costs?
Use a CDN for static assets, compress images and enable modern formats, prefer hosts with generous included transfer, and use object storage without egress fees for large media.