How Much Bandwidth Does a China-Facing Site Actually Use? Estimating Monthly Transfer Before You Pick a Plan

“How much bandwidth do I need?” is one of the most common questions before buying a VPS, and one of the most commonly guessed. For a site serving a domestic audience on cheap transit, guessing high is harmless. For a China-facing site on premium routing, where each gigabyte costs the provider much more, the plan you choose is shaped by how much transfer it includes.

Guess too low and you hit your limit mid-month, right when a campaign or release is driving traffic. Guess too high and you pay for premium capacity you never use.

This guide walks through how to estimate monthly bandwidth for a China-facing site, with worked examples for four common workloads, and covers the hidden traffic that catches people out.

Bandwidth, transfer, and port speed

These terms get mixed up, so it helps to separate them. Port speed, such as 1 Gbps, is how fast data can move at any instant. Monthly transfer, often called bandwidth on plan pages, is the total amount of data that moves over the month, measured in gigabytes or terabytes.

A fast port doesn’t mean a large transfer allowance. A 1 Gbps port running flat out would move over 300 TB in a month, far more than most plans include. What you need to estimate is total monthly transfer, then check that the port can handle your busiest moments.

Also check how your provider counts traffic. On V.PS, listed transfer counts both directions, inbound and outbound combined. Most web traffic is outbound, but uploads, backups pulled in, and proxy traffic all count.

The basic formula

For most sites, monthly transfer comes down to a simple multiplication: the average data sent per visit or request, times the number of visits or requests per month, plus overhead for everything that isn’t a real user.

The tricky part is the average. A first-time visitor downloads every image, script, stylesheet, and font. A returning visitor with a warm browser cache may download only the HTML. Your real average sits somewhere between the full page weight and the HTML-only weight, depending on how many visitors come back and how well your caching headers work.

You can find your full page weight in your browser’s developer tools. Open the Network tab, disable the cache, reload, and look at the total transferred.

Example 1: A content site or blog

Say a Chinese-language blog gets 30,000 pageviews a month. A full page load, with images and fonts, is 1.5 MB. About half of pageviews come from returning visitors whose browsers have cached most assets, so they transfer about 300 KB each.

The average works out to roughly 0.9 MB per pageview, so 30,000 pageviews comes to about 27 GB. Add 30% for crawlers, bots, feed readers, and other automated traffic, and you’re at around 35 GB a month.

That’s small. A content site rarely runs into transfer limits unless it serves large images without optimization or embeds self-hosted video.

Example 2: An ecommerce store

A cross-border store gets 100,000 pageviews a month. Product pages are image-heavy, at around 3 MB for a first visit, and shoppers browse multiple products per session, so caching helps less with product images than with site-wide assets. Call the average 2 MB per pageview.

That’s 200 GB from pageviews. Add 25% for bots and crawlers, plus traffic from the admin panel, product image uploads, and order notifications, and the estimate lands around 260 to 280 GB a month.

Images are the lever here. Converting product photos to WebP or AVIF and serving correctly sized versions for mobile can cut the image share of that number by half or more.

Example 3: A mobile app API

A mobile app has 20,000 daily active users in China, each making about 150 API calls a day with an average response of 4 KB, and requests averaging 1 KB.

Responses come to 20,000 × 150 × 4 KB, or about 12 GB a day. Requests add about 3 GB a day. Over a 30-day month, that’s around 450 GB. If the app also serves images or media from the same server, add those separately.

APIs grow quietly. A new feature that polls every 30 seconds, or a response that starts including a large nested object, can increase transfer substantially. Enable gzip or Brotli where supported and measure the actual wire size; savings depend on the payload.

Example 4: A download mirror

A software company distributes a 500 MB installer to customers in China, with about 3,000 downloads a month, plus updates.

That’s 1.5 TB from the installer alone. Failed and retried downloads, people downloading on multiple devices, and update packages can add 20% to 50% on top. For a 20% to 50% overhead range, budget approximately 1.8 to 2.25 TB a month.

Downloads dominate everything else. If you serve large files, estimate them separately and add the rest of the site on top. Our guide to serving large file downloads to mainland China covers how to make those transfers efficient.

The hidden traffic most estimates miss

Bots and crawlers are the biggest. Search engines, SEO tools, AI crawlers, uptime monitors, and vulnerability scanners can easily account for a quarter or more of all requests on a public site. Check your logs before assuming your traffic is all human.

Backups count if they leave the server. A nightly 10 GB backup pushed to off-site storage is 300 GB of outbound transfer a month. Incremental backups with tools like restic or borg cut that dramatically.

Reverse proxies count twice. If your server sits in front of an origin elsewhere, every uncached byte comes in from the origin and goes out to the visitor, and both directions count.

Then there’s the smaller stuff that adds up: package updates, Docker image pulls, log shipping to an external service, replication to a second server, and images hotlinked by other sites.

How to convert speeds into monthly transfer

Sometimes you know your traffic as a rate rather than a total. A useful rule of thumb: 1 Mbps sustained around the clock for a 30-day month is about 324 GB.

So a server averaging 10 Mbps outbound over the month moves about 3.2 TB. Averages hide peaks, though, so check the busiest hours separately against your port speed. A China-facing site often has a sharp evening peak several times its daily average.

Measure instead of guessing

If the site already exists, measure it. vnStat is a lightweight tool that records interface traffic over time:

sudo apt install vnstat
vnstat -m

After a few days, vnstat -m shows monthly totals and vnstat -d shows daily ones. Your web server logs tell you which content drives the traffic. For Nginx’s default combined log format, this sums response body bytes in the current log file. It excludes headers, inbound traffic, and rotated logs, so it is not the provider’s billing total:

awk '{sum += $10} END {printf "%.2f GiB\n", sum/1024/1024/1024}' /var/log/nginx/access.log

Break it down by file type or URL path, and you’ll usually find a small number of files responsible for most of the transfer.

How to reduce transfer before you size up

Caching headers come first. Long cache lifetimes on versioned static assets mean returning visitors don’t download them again. Compress text responses with gzip or Brotli. Convert images to modern formats and serve responsive sizes.

Separate traffic by audience. Premium China routing is valuable for Chinese visitors but wasted on bots and visitors elsewhere. Serving non-Chinese traffic from a standard server, using GeoDNS to send only mainland visitors to your China-optimized server, keeps premium transfer for the users who need it.

Block or rate-limit abusive crawlers, and make sure large media files can’t be hotlinked by other sites.

Choosing a plan with headroom

Once you have an estimate, add 30% to 50% headroom. Traffic grows, campaigns happen, and you don’t want your busiest week to be the one where you hit your limit.

Check what happens when you exceed the limit. On V.PS, the Performance KVM VPS line, along with Nano and Storage, applies a port speed limit once transfer is used up, while other lines suspend service until the next month. Both are worth avoiding, but they affect your site very differently.

Finally, review usage monthly for the first few months. Real traffic is the best correction to any estimate.

Wrapping up

Estimating bandwidth for a China-facing site comes down to average transfer per visit or request, multiplied by volume, plus overhead for bots, backups, and everything else. A blog might use tens of gigabytes a month, a store a few hundred, an API several hundred, and a download mirror terabytes.

Measure if you can, reduce what you can, keep premium routing for the traffic that needs it, and add headroom before you pick a plan.

Thanks for reading! If you’re sizing a server for Chinese visitors, V.PS runs KVM VPS on its own networks in 11 cities across 3 continents, and the Performance KVM VPS in Tokyo and Singapore carries CTGNet, CUP, and CMIN2 routing to all three major Chinese carriers, with a public looking glass so you can test before you buy.

Ready to get started? Deploy a server or contact our team if you need help choosing a plan.

Frequently asked questions about VPS bandwidth for China-facing sites

How much bandwidth does a small website use per month?

A small content site with tens of thousands of pageviews usually uses tens of gigabytes a month. Image-heavy sites, stores, APIs, and file downloads use far more.

What’s the difference between bandwidth and port speed?

Port speed is how fast data can move at any moment, such as 1 Gbps. Monthly bandwidth or transfer is the total amount of data moved over the month. You need enough of both, but they’re sized separately.

Does V.PS count inbound and outbound traffic?

Yes. Listed transfer on V.PS plans counts both directions combined, so uploads, incoming backups, and proxy traffic count alongside outbound traffic.

How many GB is 1 Mbps per month?

About 324 GB, assuming 1 Mbps sustained continuously for a 30-day month.

What happens if I go over my VPS bandwidth limit?

It depends on the plan. On V.PS, Performance, Nano, and Storage plans apply a port speed limit, while other lines suspend service until the next month. Check your plan’s terms before you need them.

Why is bandwidth on China-optimized plans more limited?

Premium carrier routes like CTGNet, CUP, and CMIN2 cost providers much more per gigabyte than ordinary transit. Plans with premium China routing usually include less transfer than standard plans at a similar price.