Contact Form with File Upload Template
A contact form where attachments belong. Screenshots, documents, and briefs arrive with the first message instead of the third email.
Get in touch, and if a file explains it better, attach it. Screenshots, briefs, spreadsheets: whatever shows us what words would take paragraphs to say.
Images, PDFs, spreadsheets, or docs: attach what tells the story.
Some messages cannot travel as text. The screenshot of the error, the brief that explains the project, the spreadsheet with the discrepancy highlighted: these are the message, and a contact form without attachments forces a ritual everyone knows: "thanks for reaching out, could you send a screenshot?", followed by two days of waiting. This template ends the ritual by letting the file arrive with the first message.
The subject line and the file cap. The subject line is borrowed from email on purpose. When messages arrive with files, you triage differently, and a sender-written subject makes the responses view scannable the way an inbox is. The message field's placeholder ("context first, then what you need") structures the note so attachments arrive explained rather than orphaned, because a file without context is a puzzle. The upload block allows four files at 10MB each, which covers the real cases: multiple screenshots of a flow, a brief plus a reference document, before-and-after images. "Who are we talking to?" keeps the name question warm on a form that might otherwise feel like a filing system.
A general channel, capped at four. Topic dropdowns and department pickers stay off: this template is a general channel, and the attachment capability is the specialization. If you need routing too, the multi-department template accepts a file block in two clicks. Uploads cap at four, because four files is a conversation while forty is a transfer job that belongs in proper file-sharing. The people who reach for it: design and print studios receiving briefs and reference material, accountants and bookkeepers whose clients send statements and receipts, property managers collecting photos of the leaky ceiling, IT contractors receiving error screenshots, and anyone whose reply to a first message is usually "can you send me the file?"
Run it, and keep it whole. Narrow the accepted file types in the block's settings if you only ever want images or only PDFs, since narrower is safer and sets expectations. Every upload is verified against its declared type before you download it, and files are delivered as attachments rather than opened in the browser, the safe default for handling strangers' documents. Turn on notifications so the message and files announce themselves, and remember the response stores everything together, so no more searching an inbox for the attachment that belongs to the thread. The ending confirms that message and files arrived together. That "together" is the entire product: context and evidence in one record, reviewable in one sitting, answerable in one reply.
Frequently asked questions
What file types and sizes are accepted?
Images, PDFs, Office documents, CSVs, and zips, up to 4 files at 10MB each on this template. You can narrow the allowed types per block in the editor.
Is it safe to receive files from strangers?
Uploads are validated against their declared type by content inspection, and downloads are served as attachments rather than rendered inline, a cautious default.
Where do the files end up?
Attached to the response itself. Message and files stay together in the responses view, so you never hunt through an inbox to reunite a note with its screenshot.
Can I make attaching a file mandatory?
Mark the upload block as required in the editor. Useful when the file is the point, like receipt submissions or photo documentation.