File Upload in Framer Forms

A form file upload field in Framer is a native Forms Plugin component you drop onto your canvas. The user picks a file (or drags and drops), the file streams to secure storage over HTTPS, and the submission record stores a signed download URL. You receive that URL in the email notification and in any connected CRM record.

Unlike a Webflow or WordPress site where you typically need an S3 bucket and signed-URL middleware, Forms Plugin handles storage end-to-end. There is no AWS console to learn, no Zapier hop, no 25MB Gmail attachment ceiling to plan around.

File upload works in single-step forms and inside any PageFlow step. File data persists across Previous and Next navigation, so users can edit other fields without losing their attachment.

Forms Plugin accepts documents (PDF, DOCX, XLSX, PPTX, TXT, ZIP), images (JPG, PNG, WebP, SVG, HEIC), audio (MP3, WAV, M4A), and video (MP4, MOV, WebM). You restrict accepted types per field, which acts as a UX filter and a spam barrier.

Max file size is 50MB per file on Pro and Scale plans. For typical use cases (a CV, a portfolio PDF, a brand-asset image set, a short screen recording), 50MB is generous. If a workflow needs larger files (raw video, large DAW projects), recommend WeTransfer or a Google Drive link in a notes field instead.

Set the cap on the conservative side. A 5MB cap is enough for resumes and most brand assets, and it protects you from accidental large uploads that slow submission UX.

Uploads are transferred over HTTPS and stored with access controls. Download URLs in your submissions are signed and time-limited so a link cannot be shared past expiry. Only the form owner can retrieve files through the dashboard or CRM record.

If you handle sensitive submissions (signed contracts, ID documents, financial files), pair file upload with e-signature in the same form so the consent and the artifact arrive in one record. For long-term retention, download files into your CRM or document store on a regular cadence rather than relying on signed URLs as long-term archives.

HubSpot stores the signed download URL on the contact record as a custom property. You can build a workflow that emails the file URL to a teammate, opens a ticket, or attaches it to a deal record.

Mailchimp and ActiveCampaign store the URL on a contact merge field or custom field. Mailchimp does not host attachments inside the contact record itself, so the signed URL is the right pattern.

For Slack and Discord notifications via webhook, the signed download URL renders as a clickable link. Your team gets a ping with the link, opens, downloads.

If a downstream service requires the actual file binary (not a URL), use a webhook to forward submissions to a custom endpoint that pulls the file from the signed URL and re-uploads it where you need it.

Email attachments break above 25MB on Gmail and most providers. A form file upload field in Framer raises that ceiling to 50MB and replaces the attachment with a stable download URL.

Attachments also lack structure. A form upload arrives with the user's other fields (name, email, project type) on the same record, so you skip the back-and-forth of pairing a CV with its applicant.

Forms also reduce spam. Attachments from unknown senders go to spam folders or get blocked. A form submission is a known, authenticated event your team expects.