Webflow Bandwidth Limits: What Agencies Should Budget

Webflow bandwidth limits are set per site, not per Workspace, and come in three self-serve levels: 1 GB on the free Starter plan, 10 GB on Basic, and 50 GB included with Premium, which can be extended to 2.5 TB with bandwidth add-ons. Going over the limit on a Basic or Premium plan does not take the site offline and does not produce a charge that same month: surge protection absorbs the first billing month over, and only a second consecutive month over triggers an automatic upgrade. For an agency, the number worth budgeting is the price above the limit: Webflow's published add-ons take a Premium site from $45/month at 100 GB to $999/month at 2.5 TB on yearly billing, which works out at a flat $0.40 per GB.

What are the Webflow bandwidth limits on each Site plan?

Webflow's bandwidth limits are 1 GB on the free Starter plan, 10 GB on Basic and 50 GB on Premium, and each limit applies to a single published site rather than to every site in the Workspace. Basic costs $15/month billed yearly and Premium $25/month billed yearly. Premium is the only self-serve plan that sells extra bandwidth, in twelve tiers topping out at 2.5 TB (Webflow pricing page). Plan pricing beyond bandwidth is covered in my guide to Webflow pricing plans.

Site plan	Price (billed yearly)	Included bandwidth	What is available above the limit
Starter	Free	1 GB	No add-ons, and Starter is not on Webflow's surge protection list
Basic	$15/mo	10 GB	Surge protection, but no add-ons. Sustained overage moves the site to Premium
Premium	$25/mo	50 GB	Surge protection plus eleven paid bandwidth tiers to 2.5 TB

One May 2026 change matters for older client sites: when the legacy Business plan merged into Premium, its bandwidth allowance dropped from 100 GB to 50 GB, and Webflow states that sites which had exceeded 50 GB in the previous two billing months had add-ons attached automatically (Updated pricing and simplified plans for May 2026). For the dates on which the wider plan changes reach each account type, see my post on whether Webflow is worth it in 2026.

What actually counts toward Webflow bandwidth?

Webflow counts total bandwidth as every byte its CDN delivers for a published site, and the definition is broader than most agencies assume (Bandwidth overview). Five things count against a Webflow site's monthly allowance:

• HTML, CSS and JavaScript delivered on every page load, not only media files
• Images, video and font files, which Webflow groups as asset bandwidth
• Traffic from any type of user agent, bot or non-bot, so AI crawlers and scrapers count
• Traffic with any status code, including 404s and redirect chains
• Requests for assets already deleted from the CMS, which cached pages and external links keep firing

The user-agent rule is the one I quote most often to agency partners, because a crawler bills to the client's Site plan at exactly the same rate as a real visitor. The deleted-asset case is the sneakier failure mode: Webflow's usage dashboard labels those files with a "(deleted)" marker, and they keep consuming bandwidth after the launch that removed them.

What happens when a Webflow site goes over its bandwidth limit?

Exceeding a Webflow bandwidth limit for one billing month costs nothing on a paid plan. Webflow calls this surge protection and lists it for Basic and Premium Site plans as well as legacy CMS and Business plans, so the free Starter plan is not covered: on Basic or Premium the site is not throttled, not suspended, and not billed for the overage. If usage exceeds the same limit for a second consecutive billing month, Webflow automatically upgrades the Site plan or bandwidth add-on at the start of the next billing month, sizing the upgrade to the lower of the last two months' usage (Surge protection for overages).

Two details in that mechanism cost agencies real money. First, a billing month is not a calendar month: for annual subscribers it starts the day the subscription started, so a site subscribed on March 5 is measured March 5 to April 4, and calendar-month analytics will misjudge which month tipped over. Second, Webflow does not issue refunds for bandwidth overages, and an annual plan that auto-upgrades keeps its billing cycle while the new plan is charged prorated (Webflow Help Center). Bandwidth also affects moving a site into a client's Workspace, covered in how to transfer a Webflow site to a client.

How much does every Webflow bandwidth tier cost?

Webflow publishes the full bandwidth add-on ladder on its pricing page, and the eleven paid tiers run from +$20/month for an extra 50 GB to +$974/month for an extra 2.45 TB on yearly billing, roughly 50% higher on monthly billing (Webflow pricing page). Added to the $25/month Premium base, that is a total site cost of $45/month at 100 GB, $199/month at 500 GB and $999/month at 2.5 TB. Every step of that ladder prices at a flat $0.40 per GB per month, so any tier can be worked out as $25 plus 40 cents for every gigabyte above the 50 GB Premium includes. The one wrinkle is a $6 discount that appears at the +450 GB tier and carries up through every tier above it, which is why 500 GB costs $199 rather than the $205 the rule alone would predict.

Total bandwidth	Add-on	Add-on price (yearly)	Total per month
50 GB	Included with Premium	$0	$25
100 GB	+50 GB	+$20	$45
150 GB	+100 GB	+$40	$65
200 GB	+150 GB	+$60	$85
300 GB	+250 GB	+$100	$125
400 GB	+350 GB	+$140	$165
500 GB	+450 GB	+$174	$199
750 GB	+700 GB	+$274	$299
1 TB	+950 GB	+$374	$399
1.5 TB	+1.45 TB	+$574	$599
2 TB	+1.95 TB	+$774	$799
2.5 TB	+2.45 TB	+$974	$999

What should an agency budget for Webflow bandwidth per client site?

An agency can size a Webflow bandwidth budget before the site exists by multiplying average page weight by expected monthly pageviews: a 2 MB page at 25,000 views a month is about 50 GB, which lands exactly on the Premium ceiling, and every gigabyte above that costs 40 cents. Quote the result as a variable line item on the hosting invoice rather than folding it into a fixed retainer. In my projects, a marketing site of 20 to 40 pages with compressed images stays comfortably inside the included 50 GB, and the sites that break that ceiling are almost always the same three types: self-hosted video, large photography galleries, and campaign sites taking a paid traffic spike. Before signing a hosting retainer, read the real trend in Site settings, then Site usage, which holds bandwidth history from April 1, 2024 onward and exports it as CSV (Bandwidth overview). Contract language that names the included tier in gigabytes and rebills anything above it at Webflow's published price follows the same logic as my note on pricing Webflow projects as an agency.

Where do agencies go wrong on Webflow bandwidth?

Agencies go wrong on Webflow bandwidth in three ways: absorbing an automatic tier upgrade silently instead of rebilling it, leaving deleted assets serving from cache after launch, and loading script bundles site-wide when only one page needs them. Each pattern has a price attached:

• Silent absorption. The agency swallows the auto-upgrade rather than raising it with the client. Moving from the $25 tier to the $199 tier costs an extra $2,088 a year, and Webflow states it is unable to issue refunds for bandwidth overages.
• Deleted assets that keep billing. A hero video swapped out at launch still serves from cached pages and external links, and Webflow's dashboard marks it "(deleted)" while it continues to consume the allowance.
• Site-wide script bundles. A tracking or animation bundle pasted into site-wide custom code downloads on every page of the site, including the pages that never use it, multiplying its weight by the whole page count.

How do you reduce Webflow bandwidth usage?

The fastest way to reduce Webflow bandwidth usage is to fix the assets Webflow's own usage dashboard already flags, because it measures each one against six published thresholds (Bandwidth overview):

• Image over 2,000 px on either dimension: re-upload it at display size
• GIF over 1 MB: replace it with a muted, looping MP4
• Image not in WebP or AVIF: convert it with the Assets panel Compress action
• Self-hosted video over 100 MB: move it to YouTube or Vimeo, or re-encode it lower
• Font file over 80 KB loaded more than 1,000 times: remove unused weights and styles
• JavaScript or CSS bundle over 250 KB: move it from site-wide custom code to the one page that needs it

Image compression is where the volume is, but the 250 KB bundle rule is the fastest single fix, and deciding where each script belongs is covered in my guide to custom code in Webflow. For agencies delivering under someone else's brand, the bandwidth tier belongs in the handover document alongside the rest of a white label Webflow workflow.

Want a straight answer on what a client site will cost to host?

Webflow's published ladder prices every tier, but no table can tell you which tier a specific client site is heading for. Send me the site and I will read its Site usage dashboard with you, name the tier its current trend lands on, and point at the three assets to fix first so it does not get there. That is a 15 minute call and you leave with a figure you can put straight into a hosting quote. Book a 15 minute call.