Do File Downloads Count Against Your Webflow Bandwidth?

What Webflow Actually Counts as Bandwidth

Bandwidth, on Webflow, is the total volume of data its CDN delivers from your site to visitors in a billing month. That’s broader than most builders assume. It’s not just your traffic numbers — it’s every byte of every response: HTML, CSS, JavaScript, fonts, images, video, and every file someone downloads.

A few details that catch people out:

Downloads count, fully. A PDF, a ZIP, a media file hosted on your Webflow site adds its full size to your bandwidth every single time it’s requested.
Bots count. Webflow doesn’t separate human visitors from crawlers. Search engines, uptime monitors, and scrapers all draw down the same allowance.
Errors and redirects count. Even a 404 page or a 301 redirect is a response Webflow had to serve, so it counts too.

The takeaway: bandwidth isn’t a measure of how popular your site is. It’s a measure of how much data leaves Webflow’s servers on your behalf — and downloadable files are some of the heaviest data you can put on the meter.

The Limits Just Got Tighter (May 2026)

In Webflow’s May 2026 pricing update, the bandwidth allowances on site plans changed — and not in your favour. The Basic plan includes 10 GB per month. The Premium plan’s allowance was cut from 100 GB to 50 GB.

If you have files on your site, that 50% reduction at the top tier is the kind of change you only notice once you’ve already crossed the line.

What Happens When You Go Over

Webflow doesn’t bill you a per-gigabyte overage rate. The mechanism is different, and arguably sharper:

Exceed your limit in one month and you’ll get a notification, but no charge.
Exceed it again the next month — two consecutive months over — and Webflow automatically upgrades your site to a higher plan or bandwidth add-on at the start of your next billing cycle, and charges you for it.

Because it’s an automatic tier bump rather than a metered cent-per-GB charge, the jump can be steep and lumpy. Builders have reported bills moving from around $25/month to well over $150/month after a forced upgrade — a several-hundred-to-over-a-thousand-dollar swing across a year, triggered by traffic they didn’t plan for.

The Math on a Single File

Here’s the part that surprises people. You don’t need viral traffic to blow a bandwidth budget — you just need one popular download.

Take a 5 MB brochure or services guide. Modest file, nothing unusual. Now imagine it does what you actually want it to do and gets downloaded 500 times in a month:

5 MB × 500 downloads = 2,500 MB = 2.5 GB

That’s 2.5 GB gone — a quarter of an entire Basic plan’s monthly allowance — from a single file doing its job. Put a handful of case studies, a media kit, and a few client deliverables on the same site and the allowance disappears fast. The better your content performs, the faster you reach the limit — which is exactly backwards from what you want.

The Standard Advice: Move Files Off Webflow

This is well-trodden ground. Search for how to reduce Webflow bandwidth and you’ll find the same recommendation everywhere: stop hosting downloadable files on Webflow. Move them to object storage — Cloudflare R2, AWS S3, or similar — and link to them externally. Once a file is served from somewhere other than Webflow’s CDN, it no longer counts toward your Webflow allowance. Simple in principle.

In practice, doing it by hand is the friction nobody mentions: spin up a storage bucket, configure a CDN in front of it, manage credentials, upload each file, copy the URL back into Webflow, and repeat that dance every time a file changes. Most builders try it once, find it tedious, and quietly go back to dropping files straight into the Webflow asset manager.

Where DocVault Fits

DocVault is the turnkey version of that advice, built into the Webflow Designer. You upload a file in a panel that lives inside Webflow — no tab switching, no bucket configuration, no credentials to manage — and DocVault handles the rest:

Files are stored on Cloudflare R2, which charges zero egress fees. No matter how many times a file is downloaded, you don’t pay per-download bandwidth costs.
Files are served from their own CDN — on the DocVault domain or a custom one you control, like files.yoursite.com — not through Webflow. So every download bypasses Webflow’s CDN entirely and contributes nothing to your Webflow bandwidth.
The URLs are permanent. Replace a file and the link serves the new version instantly; your Webflow buttons and embeds never break.

The result is the outcome the standard advice is reaching for, without the manual plumbing: your downloadable files are off the Webflow meter, served fast from a global edge network, on URLs that outlast any plan change. Your Webflow bandwidth goes back to covering what it’s actually for — your site — instead of being drained by every brochure click.

The Quick Version

Every file Webflow serves counts toward your plan’s bandwidth — downloads included.
The May 2026 update cut Premium bandwidth from 100 GB to 50 GB; Basic sits at 10 GB.
Two consecutive months over your limit triggers an automatic, billed plan upgrade.
One 5 MB file downloaded 500 times is 2.5 GB — popular content burns the allowance fastest.
Hosting files outside Webflow takes them off the meter; DocVault does that automatically, from inside the Designer, with zero egress fees.

If your files are currently sitting in the Webflow asset manager, they’re on the meter right now. DocVault takes them off it — and the move takes minutes, not a migration project.