How we handle branded file uploads in FigForm
As indie builders, we all know the pain:
Every time a team wants "just a simple form with file uploads", it quietly becomes a mini project - styling the input, handling drag & drop, showing progress, letting people replace files, etc.
In FigForm, we tried to make file uploads feel like a native, visual building block instead of a special-case widget.
Here's what that looks like today:
You add an input and change its type to File inside the Figma-style editor.
You can adjust placeholder, typography, spacing, borders, background, and dimensions so it looks like the rest of your UI.
End users get a modern UX by default: drag & drop over an active drop zone, see upload progress, and manage files (view name, delete, replace) before they submit.
This ends up helping a few different personas:
Marketing/growth - UGC contests, asset submissions, co-marketing forms
HR - job applications with resumes + portfolios
Product & support - bug reports with screenshots/logs
Agencies - client asset intake across many brands, with on-brand styling per client
Under the hood we intentionally keep the icons + error texts consistent for now, to avoid weird edge cases across browsers/devices, but we let teams go as deep as they want on layout and styling.
If you're curious how we explain this to users, we just published a short help article that walks through the flow:
👉 Full article: https://figform.com/help-file-uploads
