A b2b enquiry form file upload is an attachment field on a business enquiry form that lets a buyer send a brief, specification, drawing or tender document along with their contact details. It earns its place only when the document changes how you quote or qualify the lead, which is why it belongs in a deliberate B2B lead generation design and not in a form by default.
Most form plugins and CRM form builders can add the field in a few clicks. Deciding what it should accept, where the files land, who can open them and how long you keep them is the part that decides whether it helps your pipeline or becomes an unmonitored folder of personal information. This post, part of our guide to B2B lead generation in South Africa, covers those decisions using documented limits from Gmail, HubSpot and OWASP, and the POPIA sections that apply.
Quick Answer
A b2b enquiry form file upload is worth adding only when the document changes the quote, such as a spec sheet, drawing, bill of quantities or tender pack, and it should stay optional. Allow a short list of file types, set a size cap, store the file outside the public website, and weigh a CRM record or private folder against a plain email attachment. Where uploaded files contain personal information, POPIA section 19 requires reasonable safeguards for it, so decide the retention period before you switch the field on.
In this guide
Not sure your enquiry form needs an upload field?
Send us your current form and we will tell you which fields help you qualify and which ones cost you submissions.
Get a Free AuditWhen Does a B2B Enquiry Form File Upload Earn Its Place?
A file upload earns its place when the attached document lets you quote, scope or qualify without a second round of emails, and it costs you leads when the attachment is only something a salesperson might find interesting. The test is whether your team would otherwise ask for the document before giving a price.
| Enquiry type | Upload field? | Why | Best for |
|---|---|---|---|
| Request for quotation with a spec, drawing or bill of quantities | Yes, optional | The document defines the price; asking for it later adds a delay | Manufacturing, construction, signage, packaging, engineering |
| Tender or RFP response | Yes, but consider a link | A tender pack can run to several documents; a shared link sidesteps email size caps | Consulting, IT services, professional services |
| Compliance or document review (contracts, certificates, financials) | Not on the first form | Documents carry personal and confidential information; collect after you have qualified the lead | Accounting, legal, BEE consulting |
| General enquiry or demo request | No | A text box covers the need; an extra field adds friction without changing the response | SaaS, agencies, recurring services |
| Job applications or supplier onboarding | Separate form | Different purpose, different retention and different people reading it | Any business with a careers or vendor page |
The pattern: upload belongs where the buyer already has a document and expects to send it. If the buyer has to create something just to complete your form, you have added work for them at the moment they are least committed. Our guide to quote form optimization covers the wider question of which fields a quote request needs.
Takeaway
A B2B enquiry form should accept a file only when the document changes the quote or the qualification decision. For general enquiries and demo requests, a plain text field gets the same information with less friction.
What Should an Enquiry Form File Upload Field Accept?
An enquiry form file upload field should accept only the file types your team genuinely opens to quote the job, with a size cap and a clear label telling the buyer what to attach. Everything outside that list is risk with no commercial upside.
OWASP's file upload guidance tells developers to allow only safe and critical extensions for business functionality, and to use an allowlist, not a blocklist. For a typical SA B2B form that usually means PDF, the common Office formats and one or two image types. Add CAD or drawing formats only if someone in your business can open them.
Set the limits before you publish
Three settings do most of the work:
- Accepted types. List them in the field label ("PDF, Word or Excel") so buyers do not find out on submit.
- Maximum size. OWASP recommends a file size limit to protect storage and prevent denial of service from excessive uploads. Choose it from your real delivery route (next section), not from the plugin default.
- Number of files. One enquiry form upload field for one document is simpler to build and to review. Platforms differ here: HubSpot's documentation says a buyer who clicks Choose file a second time overwrites the original selection, so multi-file behaviour is worth testing on your own form.
Write the label like an instruction
"Attach your specification or drawing (optional, PDF or Word)" tells the buyer what you want, what format works and that they can submit without it. "Upload file" does none of that.
Where Should Uploaded Files Go: Email, Cloud Folder or CRM?
An uploaded file can reach your team by email attachment, by a stored link in a private folder, or as a file attached to a CRM contact record, and each route trades a different risk: email carries size limits and scattered copies, while a stored link or CRM record removes the email limits but brings the platform's own limit and a retention duty.
| Delivery route | How it works | Main risk | Best for |
|---|---|---|---|
| Attach to the notification email | The form emails the file to a sales inbox | Size limits and bounces; the file sits in several mailboxes with no access control | Very small forms with small documents and one recipient |
| Store privately and email a link | The file saves on the server or cloud storage; the email carries a link | Links shared too widely; storage that is publicly reachable | Most SME sites on WordPress or similar |
| Attach to the CRM record | The form platform or integration stores the file against the contact | Platform file limits; files outliving the lead | Teams with a working CRM and a defined follow-up process |
The email route has hard numbers behind it. Google's Gmail help page states that for personal Gmail accounts the limit is 25 MB per attachment, and that above it Gmail removes the attachment and adds a Google Drive link. For work and school accounts the limit is set by the Google Workspace administrator, so your own mailbox and your prospect's mail system may not agree.
Email transport also makes files bigger: SMTP2GO's explainer, a vendor blog, puts Base64 encoding growth at roughly 33% to 40%, and it recommends keeping total message size under 10 MB where you can. Treat that 10 MB as a practitioner recommendation, not a standard.
The CRM route has its own documented behaviour. HubSpot's forms documentation gives 100 MB as the limit for a file upload field, says the file is stored in a hidden folder in your file manager, and adds a link to the contact record. If you run a CRM, check what your own platform does with form files before you promise a buyer anything. Our guide to a CRM that feeds your pipeline covers how enquiries should land and who owns them afterwards.
Is your enquiry form losing leads before the sales team sees them?
Tell us how your form delivers submissions today and we will map where an enquiry can stall between the click and the first reply.
Request a Free ConsultationTakeaway
Pick the maximum file size from your delivery route. A 25 MB Gmail attachment limit applies to personal accounts, Workspace admins can set different limits, and email encoding adds roughly 33% to 40% to the size in transit. A stored link or a CRM attachment removes the email limits but brings the platform's own limit and a retention duty.
How Do You Secure a File Upload on a Business Form?
Securing a file upload means treating every submitted file as untrusted input, which is the position OWASP's File Upload Cheat Sheet takes: validate several ways at once, store the file somewhere it cannot be run, and scan it.
The cheat sheet's relevant points for a business form owner are:
- Do not trust the declared file type. OWASP notes the Content-Type is supplied by the user and is easily spoofed, so a file's label does not prove its content.
- Rename the file. It recommends changing the filename to something generated by the application, such as a random identifier, instead of keeping the name the sender chose.
- Store outside the public web root or on separate infrastructure, so an uploaded file cannot be fetched and executed as part of your website.
- Scan. It advises running the file through antivirus or a sandbox where available.
You do not need to implement these by hand. You do need to ask your developer or form plugin vendor which of them the setup covers, and confirm the answer rather than assuming it. Spam is a separate problem that arrives through the same door, and an open upload field invites it; our guide to WordPress form spam prevention covers the filtering side.
What Does POPIA Mean for Documents Sent Through a Form?
POPIA applies to an uploaded document wherever it contains personal information, and a spec sheet, contract or company profile can carry names, contact details or other personal information about people who never filled in your form. Two sections matter most: section 19 on security and section 14 on retention.
Section 19(1) requires a responsible party to secure the integrity and confidentiality of personal information in its possession or under its control by taking appropriate, reasonable technical and organisational measures. Section 19(2) spells out the working steps: identify reasonably foreseeable internal and external risks, establish and maintain safeguards, regularly verify they work, and keep them updated as new risks appear. In our judgement, not a legal conclusion, a form that accepts files from the public and drops them in a shared inbox with no access control is hard to square with that standard.
Section 14(1) says records of personal information must not be retained longer than necessary for the purpose they were collected, with exceptions such as a legal requirement, a lawful business need, a contract or consent. Section 14(4) adds that once you are no longer authorised to keep a record, you must destroy, delete or de-identify it as soon as reasonably practicable. In practice: decide how long you keep an RFQ attachment from a lead that went nowhere, and set a reminder or an automated deletion. If an upload is ever exposed, our post on POPIA security compromise notification covers what follows. For the wider compliance picture, see POPIA-compliant lead generation.
This is general information, not legal advice. The section summaries above are based on the Act's text as reproduced on popia.co.za, not on a copy of the Act itself; the Act is published on gov.za. Check the wording with your own adviser before you build a retention policy on it.
Takeaway
An enquiry form file upload turns your form into a document intake point. POPIA section 19 requires reasonable safeguards for any personal information that arrives, and section 14 limits how long you keep it, so write down the storage location, the people with access and the deletion date before launch.
How Do You Add an Upload Without Losing Submissions?
An upload that does not cost submissions is optional, placed after the contact fields, and backed by a fallback for when the file fails or is missing. A required upload turns a quick enquiry into a task, and buyers on a mobile connection may not have the document to hand.
No credible figure for how upload fields change B2B form completion turned up in the research for this post, so test it on your own traffic instead. Four practical moves:
- Mark the field optional unless your quote genuinely cannot start without it.
- Put it last. The buyer has already committed time to the name, company and need fields, and a bounced upload then costs less.
- Give an alternative. A line such as "Or email it to us after you submit" keeps the lead if the upload fails.
- Confirm receipt on screen and by email, naming the file, so the buyer knows it arrived. If the confirmation never lands, see our post on a WordPress contact form not sending email.
Then measure it. Compare completion with and without the field and track upload errors separately from successful submissions, using the setup in lead form tracking. If the field depresses submissions, a two-step flow that asks for the document after the first submit often fits better, which is the logic behind progressive profiling.
Want a second opinion before the form goes live?
Share the form and the follow-up process and we will give you a short audit of fields, routing and tracking.
Book a Free ConsultationWhy South African Businesses Choose Growth Pulse Media
Growth Pulse Media is led by Dirk van Greuning, who built and scaled a large South African ecommerce business before founding the agency and writes about lead generation from an operator's perspective. All work is executed in-house, and the client load is limited so senior attention stays on each account. If you want that thinking applied to your pipeline, our B2B lead generation service starts with how enquiries are captured, qualified and followed up, and the form is one part of that chain.
Who This Is NOT For
You get a handful of enquiries a month and answer all of them by phone. A text box and a phone number do the job. An upload field adds maintenance and a security duty without changing the outcome.
You want to collect sensitive documents through the first enquiry. IDs, financial statements and contracts belong on a secure client portal after you have qualified the lead, not on a public form.
You are looking for a plugin tutorial. This post is about the decision and the controls around the field. Your form platform's own documentation covers the exact setting names.
Frequently Asked Questions
Should a B2B enquiry form include a file upload?
Include a b2b enquiry form file upload only when the document changes your quote or qualification, such as a specification, drawing or tender pack. For general enquiries and demo requests, a text box is enough. Keep the field optional so buyers without the document can still submit.
What file types should an enquiry form allow?
Allow only the types your team genuinely opens, usually PDF, common Office documents and perhaps an image format. OWASP's guidance recommends an allowlist of safe, business-critical extensions rather than blocking known bad ones. State the accepted types in the field label.
What is a safe maximum file size for an enquiry form upload?
There is no universal figure; choose it from how the file is delivered. Gmail's personal-account attachment limit is 25 MB and Workspace limits are set by the admin, while encoding adds roughly 33% to 40% in transit. As a practitioner rule, SMTP2GO suggests keeping total email size under 10 MB, or you can store the file and send a link.
Does POPIA apply to files uploaded through my contact form?
Yes, where a file contains personal information, and business documents often do. Section 19 requires appropriate, reasonable technical and organisational measures to secure it, and section 14 says records must not be kept longer than necessary for their purpose, subject to listed exceptions. This is general information, not legal advice.
Is it better to email the file or store it in a CRM?
Storing the file and sending a link, or attaching it to a CRM record, removes the email size limits but brings the platform's own limit and a retention duty. Email attachments run into size limits and spread copies across inboxes without access control, though they can suit a small form with small documents. Check your own platform's file limits and storage behaviour before choosing.
Need Your Enquiry Form to Qualify Leads, Not Collect Clutter?
Growth Pulse Media reviews enquiry forms, CRM routing and tracking for South African B2B businesses, covering GA4, Google Ads and Meta Ads attribution alongside the form itself. No obligation — we’ll get back to you within 24 hours.
Get Your Free Consultation

