Bandwidth is the resource budget VPS buyers understand least, because the marketing language is deliberately vague. “Unmetered”, “unlimited”, and “10 TB included” describe three very different commercial arrangements, and only one of them is genuinely safe to build on without watching a counter. This page explains what each term actually commits the provider to, and how to estimate your real monthly transfer before you choose a plan.<\/p>\n\n\n\n
| Model<\/th> | What it means<\/th> | Risk to you<\/th><\/tr><\/thead> | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Metered with overage fees<\/td> | A fixed allowance, then a per-GB charge (often $0.01-$0.10\/GB)<\/td> | A traffic spike produces a real invoice; costs are uncapped in principle<\/td><\/tr> | ||||||||||||||||||||||||||||
| Metered with hard cap<\/td> | A fixed allowance, then the port is blocked or the server suspended<\/td> | Site goes offline at the limit rather than costing money<\/td><\/tr> | ||||||||||||||||||||||||||||
| Metered with throttling<\/td> | A fixed allowance, then port speed drops (commonly to 1-10 Mbps)<\/td> | Site stays online but slow; no extra charge<\/td><\/tr> | ||||||||||||||||||||||||||||
| Unmetered<\/td> | No transfer accounting, but a fixed port speed (e.g. 100 Mbps or 1 Gbps)<\/td> | You cannot exceed the port speed, so cost is predictable<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n “Unlimited” is almost always unmetered-with-a-port-cap in practice, because a physical port cannot transfer more than its speed allows. When a provider advertises unlimited bandwidth, the actual limit is the port speed. At 100 Mbps sustained, the theoretical monthly ceiling is around 32 TB; at 1 Gbps it is roughly 324 TB. That is far more than most budget servers will ever move, which is why the promise is easy to make.<\/p>\n\n\n\n How much transfer you actually need<\/h2>\n\n\n\nEstimate from page weight, not from visitor count. A typical optimized WordPress page with images served locally is 1.5-2.5 MB on first load; with a CDN handling static assets, the origin server may only serve 200-400 KB per page view.<\/p>\n\n\n\n The CDN row is the important one. Moving images, CSS, and JavaScript to a free CDN tier routinely removes 80-95% of origin transfer. A site that needs a 4 TB plan to serve a million views can serve the same traffic from a 1 TB plan with the static assets offloaded, which is the single highest-leverage bandwidth optimization available on a budget.<\/p>\n\n\n\n The behaviour at the limit is the part worth reading in the terms of service before you buy. Under throttling, expect the port to drop to 1-10 Mbps, which is enough to keep a low-traffic site up and not enough to serve images at normal speed. Under overage billing, expect the charge on the next invoice, sometimes after the allowance is exceeded by a wide margin if no alert is configured. Under a hard cap, expect the service to stop.<\/p>\n\n\n\n Configure a transfer alert regardless of the model. Most providers expose monthly usage in the control panel and by API; a daily check that emails you at 70% and 90% of your allowance converts a surprise into a planned upgrade.<\/p>\n\n\n\n Match the plan to your measured usage plus 50% headroom. A personal blog or portfolio site almost never needs more than 1-2 TB. A small business site with images served locally fits comfortably in 2 TB. Sites with meaningful media traffic should either move static assets to a CDN or buy a plan with a higher allowance, and the CDN route is usually cheaper: a 1 TB plan plus a free CDN tier costs less than a 4 TB plan, and it also improves latency.<\/p>\n\n\n\n |