Collect Files & Images on Web Forms

What they're for#

A web form can collect files and images from visitors — a résumé on a careers form, an ID document on an application, a photo on a support request. There are two field types: File upload (any allowed file) and Image upload (images only).

Add an upload field#

Upload fields come from your target module, just like any other field. If the module has a File or Image field, it shows up in the builder's Available Fields panel — drag it onto the canvas or click the + next to it. (Adding fields is covered in Adding & Configuring Web Form Fields.)

💡

Don't see an upload field in Available Fields? The module needs a File or Image field first — a web form can only show fields that already exist on its module.

What the visitor sees#

A file picker under the field label. The visitor chooses a file and it uploads immediately — a small spinner shows while it's working.
Each uploaded file appears as a chip with its name and a ✕ to remove it.
Multiple files — for a standard file/image field, visitors can add several files; each new selection is added to the list rather than replacing it.
Image fields accept images only. If the field has cropping turned on, the visitor crops their image to a square before it's uploaded (and a single cropped image replaces any previous one).

Size & type limits#

A helper line under the field shows the limit — for example "Max 5 MB". The defaults are 5 MB for an image field and 10 MB for a file field, unless the field is configured with a smaller limit, and the platform enforces an overall ceiling (10 MB).

A file over the limit is rejected on the spot with "{filename} is larger than {N} MB."
A file whose type isn't on the allowed list is rejected with "File type .{ext} is not allowed." — this is enforced on the server, so disallowed files never attach.

💡

The per-file size limit, allowed file types, and image cropping are part of the field's definition on the module, not the form. On the form itself you set the label, placeholder, help text, and whether it's required — see Configuring a field.

Where the files end up#

When the form is submitted, the uploaded files are stored on the new record and travel with the submission, so your team can open them from the record or from the submissions list.

💡

If you mark an upload field required, the visitor must attach at least one file before they can submit — handy for "attach your résumé" or "upload proof of purchase."

Was this article helpful?

Ready to implement this?

OpenAI Engage and apply what you just learned to your own workspace.

Open AI Engage CRM