Free tool
Find out what's eating your Webflow bandwidth
Webflow tells you how much bandwidth you've used. It doesn't tell you what's using it. Drop in the asset export and this will — duplicates nobody knew were there, images being sent at full size to every phone, files you deleted months ago that are still being served.
No account, no sign-up, and your file never leaves your browser — the analysis runs entirely on this page.
Drop your asset export here, or click to choose
In Webflow: Site settings → Usage → Bandwidth, then export the asset details. It's a CSV, usually well under a megabyte.
Nothing is uploaded. The file is read and analysed in your browser.
What it looks for
Images served at full size to every device. Webflow generates responsive versions of some uploads but not all — and pre-converting an image to AVIF or WebP before uploading can stop it doing so entirely. The result is a phone downloading the same file a desktop does.
Duplicate assets. Replacing an image in the CMS opens your computer's file picker rather than the asset panel, so a replace is a fresh upload and the old file stays behind — still referenced, still serving.
Deleted files that are still being served. Marked deleted, still drawing bandwidth, usually still linked from a published page.
Oversized SVGs and unsubset fonts. A 500 KB SVG is un-simplified path data, not a complex drawing. A font shipped as OTF rather than subset WOFF2 is roughly twice the size it needs to be, downloaded by every visitor.
What it won't do
It won't give you one headline number. The findings overlap — a duplicated image with no responsive versions appears in two of them — so adding them up produces a figure larger than your entire bandwidth bill. Each finding shows its own share and we leave it there.
It won't tell you to delete anything blindly. The duplicate check matches on filenames, so a deliberate variant can look like a duplicate. That finding is marked medium confidence for exactly that reason — review each group before removing anything.
Once you know what's heavy, you can move it
Most of what this tool finds is fixable inside Webflow, and the report says which. The one thing it can't fix is downloads themselves — every PDF, brochure and video your visitors pull draws on your allowance for as long as it lives on Webflow's CDN.
DocBeam serves those files from its own CDN with a permanent link, so they stop counting entirely. Free plan takes files up to 50 MB — five times Webflow's own ceiling.