Bandwidth and Egress Charges Explained for Cloud Hosting

Bandwidth charges in cloud hosting are usually based on how many gigabytes leave the provider's network each month. Inbound traffic is typically free, outbound traffic (egress) is billed per gigabyte after any free allowance, and traffic between regions can be billed too. If your site is mostly text pages, egress is a minor line. If you serve images, video, software downloads or large API responses, it can become your largest cost. This guide explains the terms, shows how to estimate your own volume, and lists practical ways to lower it.

Terms you will see on pricing pages

Ingress: data coming into the provider. Usually free.
Egress: data going out to the internet, to users, or to another provider. Usually metered.
Transfer allowance or included bandwidth: the amount of outbound data included in a plan. Some providers pool the allowance across all your servers.
Inter-region and inter-zone transfer: traffic between two regions or availability zones of the same provider. It may be cheaper than internet egress but is not always free, and it matters if you replicate databases.
Bandwidth versus transfer: bandwidth is a speed (how fast data can move, for example 1 Gbps), while transfer is a volume (gigabytes per month). Some plans limit one, the other, or both.
Metered versus unmetered: unmetered plans do not count gigabytes but may limit port speed or fair-use.

How to estimate your monthly transfer

You need one number: gigabytes sent out per month. Three ways to get it.

From server or CDN logs. Add up the bytes sent in response to requests over a month.
From your current host. Cpanel-style dashboards and cloud consoles show monthly transfer.
From a formula. Monthly egress = monthly page views x average page weight in MB / 1,024.

Here is an illustrative example: a store receives 150,000 page views per month, and the average page, including images, scripts and styles, weighs 2.5 MB when nothing is cached. That gives 150,000 x 2.5 = 375,000 MB, or about 366 GB. At an illustrative 0.09 dollars per GB, that is about 33 dollars. If the site grows to 1.5 million page views, the same math gives about 3,660 GB and roughly 330 dollars. Add video and the number can multiply.

Real traffic is lower than this formula when browsers cache assets, and higher when bots, crawlers and API clients hit your site. Check your logs for automated traffic that costs you money without bringing customers.

Price structures

Structure	Typical shape	What to watch
Included allowance, then per-GB overage	A set number of TB per month with a rate beyond that	Pooling rules and the overage rate
Tiered per-GB pricing	The rate drops as monthly volume rises	The first tier is the most expensive
Free allowance, then flat per-GB	A small free amount, then a constant rate	Free amounts are small relative to media workloads
Unmetered with fair use	No per-GB charge but limits on speed or abuse	Terms that allow throttling
CDN pricing	Per-GB rate for edge delivery, often lower than origin egress	Request fees and regional rate differences

Why egress feels expensive

Egress pricing has an effect beyond the bill: it affects how easy it is to change providers. Moving a large archive out of one cloud can cost real money, which is part of switching costs. Some providers have reduced or waived egress fees for customers who are leaving, and regulation in some regions has pushed on this, but policies and eligibility change. If you expect to switch, read the current policy before storing many terabytes. See also our guide to when to switch providers.

Seven ways to lower transfer costs

Put a CDN in front of static content. A CDN stores copies of images, scripts and downloads near users. It reduces origin traffic and often costs less per gigabyte than direct egress.
Compress responses. Gzip or Brotli compression for text, and modern image formats such as WebP or AVIF, shrink payloads noticeably.
Optimize images and video. Resize images to the size they are shown. Use adaptive streaming for video rather than serving one huge file.
Set cache headers correctly. Long cache lifetimes on files that do not change keep browsers and CDNs from re-downloading them.
Keep chatty services in the same region and zone. Avoid sending database replication or microservice traffic across regions unless you need it.
Block abusive bots. Rate limiting and a web application firewall can reduce scraping and attack traffic that you would otherwise pay to serve.
Pick a plan whose structure fits. If you are bandwidth-heavy, a provider with a generous included allowance may beat a lower compute price.

Worked comparison

This is an illustrative example. Suppose you expect 5,000 GB of transfer per month.

Provider A charges 0.09 dollars per GB with a free 100 GB: (5,000 - 100) x 0.09 = 441 dollars.
Provider B includes 4,000 GB in a 40-dollar plan and charges 0.01 dollars per GB beyond that: 40 + (1,000 x 0.01) = 50 dollars.
Provider A with a CDN that offloads 80 percent of traffic at 0.04 dollars per GB: 1,000 GB of origin egress at 0.09 = 90 dollars plus 4,000 GB through the CDN at 0.04 = 160 dollars, for 250 dollars total, before the free allowance.

Differences like these explain why the cheapest server is not always the cheapest hosting. Use the egress estimator to test your own numbers.

Mistakes to avoid

Assuming "unlimited bandwidth" means no limits. Read the acceptable-use policy.
Ignoring traffic between your own servers and regions.
Hosting large public downloads on a metered server without a CDN.
Forgetting that backups sent to another provider count as egress.

When to consult a professional

If bandwidth is central to your business model, such as video or software distribution, talk to a network or CDN specialist and request quotes with committed volumes. Large customers can often negotiate rates.

Frequently asked questions

Is inbound traffic really free?

At most large providers, yes. Some private networking features or gateways may still charge for data they process, so read the specific service page.

Does a CDN always save money?

Not always. It saves when many requests can be served from cache. For highly dynamic or private content with little caching, benefits are smaller.

What is a terabyte in gigabytes?

Providers vary between 1,000 and 1,024 gigabytes per terabyte. The difference is small, but check how your provider counts.

Are API calls to other services billed as egress?

If the traffic leaves the provider's network, usually yes. Calls to services inside the same provider and region are often cheaper or free.

Sources

National Institute of Standards and Technology — cloud computing background
Federal Trade Commission — business consumer protection guidance
FinOps Foundation — cloud cost management guidance