Webflow File Storage

Webflow's Asset Manager is great for the images that make up a design, but it has a low ceiling — roughly 10 MB per file on most plans — and no real API for programmatic uploads. The instant your site needs to host a product demo video, a large downloadable PDF, a high-res press kit, or a font/SVG bundle you want to manage outside the designer, you hit the wall. files.link gives Webflow sites an external asset store: upload large or automated assets through a REST API, get permanent CDN URLs, and embed those URLs in Webflow elements without fighting the asset-size limit.

The integration is deliberately low-friction because Webflow doesn't run server code. For static assets, upload to files.link (dashboard or API), then paste the permanent CDN URL into Webflow wherever a URL is accepted: the link field of a Button, the source of a custom-embed video player, the href of a download link, or a background image via custom code in an Embed element.

For SVGs and icon sets you'd rather not inline, host them on files.link and reference them — they're served from the edge and cached like any other asset. There are no per-transformation fees, so you store the exact renditions you ship.

Where you do have a backend — say a Make/Zapier scenario or a small function reacting to a Webflow form submission or CMS change — wire the three-call upload flow (POST /v1/files/{folderId} → PUT presigned URL → POST /v1/files/confirm-upload) and write the returned URL into a Webflow CMS field through the Webflow API, so dynamic collection items point at externally hosted media.

For gated downloads (a lead magnet behind an email capture), upload private and have that backend mint an expiring signed URL after the form submits, instead of exposing a permanent public path on the page. Billing is prepaid credits with no monthly minimum and no separate egress charge, so a heavily downloaded asset or a launch spike draws down your balance instead of triggering a bandwidth bill. files.link handles only storage and delivery — your Webflow design, CMS, and hosting stay exactly as they are; the large bytes just live off-platform.