Add a file field to your native Framer form without iframes or a separate form tool. Resumes, RFPs and design mockups upload straight from the visitor's browser. No storage setup needed: files go to FramerSend storage, or to your own AWS S3, Google Drive or Supabase Storage if you connect one.
Your Framer Form UI
sarah_connor_senior_designer_resume.pdf
4.2 MB • Upload Complete
What Happens Behind The Scenes
FramerSend checks the file and signs a short-lived upload address. The file goes from the visitor's browser straight into your bucket or folder, and your form submits its link.
AWS S3 / Google Drive / Supabase
s3://my-agency-vault/resumes/sarah_resume.pdf
Your CRM (HubSpot, Notion, Klaviyo)
Submission arrives with the file link
Choose Your Private Storage Destination
Paste a Google service account key (or an OAuth refresh token) and share your folder with it. Uploads land in the folder you choose.
Upload into your own S3 bucket in any AWS region, or an S3-compatible service such as Cloudflare R2 or DigitalOcean Spaces.
Connect your existing Supabase project. Uploads go into your bucket; if it does not exist yet, FramerSend creates it as a private bucket.
Compare FramerSend against native Framer forms, expensive plugin licenses, and external iframe tools.
| Feature / Solution | FramerSend | Framer Native | Form Plugins | Typeform / Jotform |
|---|---|---|---|---|
| File Uploads Support | ✅ Native (S3, Drive, Supabase) | ❌ Not Supported | ⚠️ Requires $119+ Pro Tier | ⚠️ Requires $35+/mo Plan |
| Pricing & Cost | $5/mo, $39/yr or $69 lifetime (every connector) | Included in Framer site | $119 - $399 one-time | $420 - $1,000+/year |
| Framer Canvas Design | 100% Native Framer Canvas | 100% Native Framer Canvas | Plugin Component | Clunky iframe embed |
| Storage Destination | Your private S3 / Google Drive | N/A | Their cloud / custom | Typeform servers |
| CRM & Email Sync | Simultaneous 100+ CRMs | Sheets & Webhook only | Requires Zapier/Make | Extra integration fees |
| Monthly Submission Cap | Unlimited | Plan-capped (100 - 500) | Unlimited | Strict plan limits |
Setup
No storage setup needed: uploads go to FramerSend storage (25 MB per file, 250 MB per free account, 1 GB with a plan, files kept 90 days, private links).
For files up to 100 MB, connect Google Drive, AWS S3 or Supabase Storage and use it as the form's destination or its File Upload Storage. For S3, add a bucket CORS rule that allows PUT from your site.
In Framer, open the File Upload plugin by FramerSend, pick your form, select your Form on the canvas and click Insert. Style the field in the right panel.
Everything you need to know about Framer form file uploads
When a visitor adds a file, the File Upload field asks FramerSend for permission. Our server checks the form, your plan, the file type and the size, then returns a short-lived signed upload address in your storage: a presigned URL for AWS S3, a signed upload URL for Supabase Storage, or an upload session for Google Drive. The browser uploads the file straight there, FramerSend checks that it arrived, and the field puts the file link into your form. The file itself never passes through FramerSend's servers.
Yes, with FramerSend storage: up to 25 MB per file, free forever with a free FramerSend account, no card needed, also after the 14-day trial. The file links land in your form submission, so Framer's own email notification delivers them too. Uploads to your own AWS S3, Google Drive or Supabase storage, and sending submissions to your CRM or other tools, are part of every plan (free for 14 days).
With FramerSend storage, up to 25 MB per file and 250 MB in total per free account (1 GB with a plan). With your own storage, up to 25 MB per file by default, and you can raise the limit to 100 MB per file in the form settings. Executables and scripts (.exe, .sh, .php, .js and similar) are always blocked, and you can limit the accepted types in the field's File types setting, for example ".pdf, image/*". Visitors can add several files to one field.
By default in FramerSend storage: no setup needed, 25 MB per file, 250 MB per free account, 1 GB with a plan, files kept 90 days, and your form receives private signed links valid for those 90 days. If you connect your own AWS S3 bucket, Google Drive folder or Supabase Storage bucket to the form, files go there instead and FramerSend does not keep a copy. Your submissions log records each upload's name, size and link.
With Secure Private Uploads on, your form receives signed links that expire: 7 days for S3 and 30 days for Supabase. For Google Drive, the file stays visible only to people who can open the folder. With it off, the form receives public links when your bucket allows public reads (otherwise signed links), and Drive files are shared with anyone who has the link. A Supabase bucket that FramerSend creates for you is private.
Yes. The links are part of the form submission, in the field you name ("Files" by default), so they reach your destination like any other field: email, HubSpot, Notion, Slack, Google Sheets and the rest.
Yes, once: add a CORS rule to the bucket that allows PUT requests from your website's domain, so browsers may upload to it. Supabase Storage needs no extra setup. For Google Drive, use a Shared Drive folder, since Google may refuse uploads to a service account's own My Drive.
No. FramerSend sends both the form fields and the file links to your destinations without Zapier or Make.
File uploads to FramerSend storage (25 MB per file) are free forever with a free account. Your own storage and every FramerSend connector are included in every plan, from $5 a month.
Free account, no card needed • 14-day free trial of every connector • Monthly, yearly or lifetime • 14-day refund guarantee