Skip to content

File uploads

A File Upload field lets a respondent attach a file to their answers. You find it in the Advanced group of the Fields list.

LimitValue
File typespdf, png, jpg, jpeg, gif, webp, heic, doc, docx, xls, xlsx, ppt, pptx, csv, txt
SizeUp to 4 MB per file (and not empty)

A file outside these limits is turned away as soon as the respondent picks it, with This file type is not accepted or Files must be between 1 byte and 4MB.

A file arrives in two steps, just like the answers around it:

  1. When the respondent submits, the file is attached to the response. You can open it in the responses console while you review, before anything is written to your records.
  2. When the response is processed, the file is linked to the record the response creates or updates. From 1.2 this works however long the response waits before it is processed.

Until then, the file is visible only on the response. If a file is missing from a record, check that the response has been processed. If the file could not be attached, the response says so in its Result / Error column. See Processing responses onto records.

If a visibility rule hid the upload question, the file is never linked to the record, even if it uploaded successfully. Answers to questions a respondent could not see never reach your data.

Each form can accept up to 250 MB of files and signatures in any 24 hours through Sliick Edge. This protects your org’s file storage.

  • When a form’s budget is used up, respondents who add a file or sign see This form cannot accept more uploads right now. Please try again later. This lasts until older uploads fall outside the 24-hour window.

  • A single file bigger than the whole budget gets This file is larger than this form accepts in a day.

  • The budget is shared by everyone answering that form. While it is used up, a form with a required file or signature cannot be submitted.

  • To change it, go to the File uploads panel on the Admin Dashboard and enter a whole number in Megabytes per form per 24 hours. The default is 250. The number applies to every form, but each form has its own budget. It is not a per-form setting.

    The File uploads panel on the Admin Dashboard with the Megabytes per form per 24 hours box and Save

  • Uploads on an Experience Cloud site, or from inside Salesforce, do not count. One exception: the budget is counted per uploading user, and guest uploads on an Experience Cloud site belong to the site’s default owner for guest records. If that same user also uploads through the REST API, the guest uploads count towards that budget.

Files from uploads a respondent starts but never submits stay in your org until scheduled clean-up removes them.

The responses Sliick Edge receives are in the REST API reference.

  • A closed form does not accept uploads. If a form is not accepting responses, or has reached its response limit, it will not take files either, so nobody leaves files behind for a response that cannot be sent.
  • Save and continue keeps files. A respondent who saves and comes back later finds their uploaded files still attached. See Save-and-continue.
  • “This form does not accept file uploads” means the form has no File Upload field, or the link points at a different form than you think.
  • Mapping a File Upload field to Salesforce shows a warning when you publish. It does not stop you publishing. It is there because files are handled differently from ordinary answers.
  • The field has a green tint in the Fields list, along with Signature, Payment, GPS Location and Barcode, because it needs the full form to work. See Field types.