File sizes, types and bandwidth

Two limits matter when you upload: how big a single file can be, and how much you’re storing in total. Both depend on your plan.

Bandwidth isn’t one of them. DocBeam doesn’t meter what your visitors download, on any plan.

Maximum file size

Plan	Largest single file
Free	50 MB
Starter	100 MB
Pro	500 MB
Unlimited	2 GB

For comparison, Webflow’s own asset uploader caps out at 10 MB. DocBeam’s free plan takes files five times that size, which is usually why people find us in the first place.

If a file exceeds your plan’s ceiling, the upload is rejected before any bytes are stored and you’ll see a message naming the limit. Nothing is partially uploaded.

Storage and document count

Plan	Storage	Documents
Free	250 MB	10
Starter	5 GB	100
Pro	25 GB	500
Unlimited	100 GB	unlimited

Both are checked before an upload starts. DocBeam also looks ahead: if a file would push you past your storage limit, it’s refused up front rather than failing halfway through.

Your current usage is visible in the Designer panel’s usage bar and on the dashboard’s Files page.

See /#pricing for the full plan comparison.

Bandwidth is unlimited on every plan

There’s no bandwidth allowance in DocBeam, on any tier. Serve a 500 MB video to ten thousand people and nothing throttles, meters or bills you for it.

The only per-request accounting DocBeam does is counting downloads, which is there so you can see what’s popular — not to limit anything.

Downloads don’t touch your Webflow bandwidth

This is the part that saves people money.

Files you upload to DocBeam are stored on Cloudflare R2 and served by DocBeam’s own CDN, on files.docbeam.io or your own custom domain. A visitor downloading your 40 MB brochure is talking to DocBeam’s infrastructure, not Webflow’s.

Webflow never sees the request, so it never counts against your site plan’s bandwidth allowance.

That matters more than it used to. Webflow reduced the bandwidth included with its Premium plan in the May 2026 pricing update, and exceeding your allowance two months running triggers an automatic, billed plan upgrade. Heavy PDFs and video are usually the first thing to push a site over.

For Webflow’s own current figures and a worked example, see Webflow bandwidth explained.

File types

DocBeam’s server accepts whatever you send it. There’s no server-side allow-list, so nothing gets rejected for being an unusual format.

What you’ll notice in practice is the Designer panel’s file picker, which filters to the types DocBeam is built for:

Documents — PDF, Word, Excel, PowerPoint, plain text, CSV
Images — PNG, JPEG, GIF, SVG, WebP
Archives — ZIP, GZIP
Video — MP4, WebM, MOV, AVI
Audio — MP3, WAV, OGG, AAC, FLAC

The dashboard’s upload area applies no type filter at all, so if you need something outside that list, upload it there.

Video and large downloads

DocBeam’s CDN supports range requests. In plain terms: a browser can ask for just part of a file rather than all of it.

That’s what makes video scrub properly — jump to the middle of an MP4 and the player fetches only that section — and it’s what lets an interrupted download of a large file resume instead of restarting.

Nothing to configure; it’s on for every file.

Download counts

Every served request is counted. A few details worth knowing:

It counts requests, not unique visitors. One person downloading a file three times is three downloads.
Requests answered from a browser’s own cache aren’t counted, because they never reach DocBeam.
Individual download events are kept for 90 days. The lifetime total per file is kept indefinitely.

The dashboard’s “bandwidth saved” figure is simply each file’s size multiplied by its total downloads — an estimate of what would have gone through Webflow’s allowance if you’d hosted these files there instead.