File Upload Fields in HighLevel

Updated: February 6, 2026  | 
Author: Bill Stilwell

This post covers how File Upload Fields work, how to configure them, where uploaded files go, how to notify your team on submission, and the best use cases for collecting files through HighLevel forms.

Reading time: about 7 minutes.

What Are File Upload Fields in HighLevel?

File Upload Fields are a field type in the HighLevel form builder that allow contacts to attach and submit files as part of a form submission.

Instead of asking contacts to email documents separately – and then manually downloading, renaming, and filing them – a File Upload Field handles that entire process in one step. The contact selects a file from their device, attaches it to the form, and submits.

The file lands in their contact record automatically.

This is most useful for intake forms where collecting supporting documents is a required part of the onboarding process – medical clearances, signed paperwork, project briefs, ID documents, or reference images.

Find the form builder at Sites, then Forms in any HighLevel sub-account.

Where Uploaded Files Are Stored

When a contact submits a form with a file attached, the file is stored in that contact’s record in the CRM.

The file appears in the contact’s Files or Documents tab – visible to any team member who opens the contact record. No manual download is required.

No separate filing step is needed. The file is just there, associated with the right contact, from the moment of submission.

This CRM-native storage means file retrieval is contextual. A team member preparing for a client call opens the contact, goes to the Files tab, and has everything the client submitted – without searching a shared folder by filename.

Configuring a File Upload Field

Adding a File Upload Field to a form takes less than two minutes. In the form builder, locate the File Upload field type in the field selector panel and add it to the form canvas.

The field has a few key configuration options. The label is the instruction the contact sees – make it specific: “Upload your signed intake form (PDF)” rather than just “File Upload.” A specific label reduces incorrect file submissions and confusion.

Helper text below the field can provide additional guidance – the expected file format, the maximum file size, or a note about what happens with the file after submission. Contacts who see clear instructions submit the right file the first time more often than those who see a blank upload button.

Required vs. Optional

The Required toggle on a File Upload Field controls whether the form can be submitted without attaching a file.

When Required is enabled, the contact sees an error and cannot advance past the field without selecting a file. Use this for any intake step where the form submission is genuinely incomplete without the file – a medical onboarding form that requires a physician’s clearance, a contractor intake form that requires proof of insurance, a design project form that requires a reference image.

When Required is disabled, the field is optional. The contact can submit without uploading.

Use this for “attach if available” situations where the file improves the team’s context but is not strictly needed to proceed.

Accepted File Types

The File Upload Field settings allow configuration of accepted file types. Restricting the accepted types prevents contacts from uploading irrelevant or unsupported formats.

For a form requesting a signed document, accept PDF only. For a form collecting reference images, accept JPG and PNG.

For a form where the file type is genuinely flexible, leave the accepted types unrestricted.

File size limits apply and can vary. Check the field settings for the current maximum size.

For contacts who need to submit files larger than the limit – large design files, video footage, high-resolution photography – requesting a cloud storage link (Google Drive, Dropbox) via a text field is the more practical alternative.

Notifying Your Team on Upload

By default, a file submitted through a form lands in the contact record – but the team does not automatically know about it unless they check.

A workflow triggered by the Form Submitted event addresses this. When the form is submitted, the workflow fires and sends an internal notification to the relevant team member: “A new file has been submitted by [Contact Name].

View their record here: [link].”

The notification can be an email, an SMS, or an in-app notification – whatever the team member checks most reliably. This notification closes the gap between “file uploaded” and “team member knows to review it.”

For forms with high submission volume, the workflow notification can route to a shared inbox or a specific user based on the contact’s assigned team member, rather than notifying everyone on every submission.

Multiple File Upload Fields

A single form can include multiple File Upload Fields – one for each distinct document type required.

An insurance onboarding form might have separate fields for: “Upload your driver’s license,” “Upload your vehicle registration,” and “Upload your prior insurance declaration page.” Each field has its own label and required setting. Each uploaded file is stored separately in the contact record.

Adding multiple clearly labeled fields is better than one generic upload field that asks for everything at once. Contacts are less likely to miss a required document when each is called out explicitly.

What Can You Do With It?

• Collect intake documents without email attachments: Replace the “please email your signed form to…” instruction with a form field that handles the collection and storage automatically – no inbox management required on either side.
• Route client-submitted files directly to the contact record: Submitted files skip the download-rename-upload cycle entirely. The file is in the right place from the moment the form is submitted.
• Make file submission a required part of onboarding: For processes where the team cannot begin work without a specific document, making the file upload required prevents incomplete submissions from reaching the workflow downstream.
• Collect reference images and briefs for creative projects: A design project request form with a file upload field allows clients to attach brand guidelines, logos, or reference examples at the point of inquiry – before the first call.
• Trigger team notifications on every file submission: A Form Submitted workflow ensures the right team member knows a new file has arrived, rather than leaving it to chance that someone will check the contact record.
• Support multiple document types in one intake flow: Multiple named upload fields on a single form handle multi-document intake – a legal onboarding form, a medical intake form, or a contractor qualification form – in one organized submission step.

Key Definitions

Use Cases by Industry

Medical and Health Practices

A physical therapy practice’s new patient intake form includes a File Upload Field for the physician’s referral letter. The field is required – the practice cannot schedule an initial evaluation without the referral on file.

When the form is submitted, a workflow notifies the front desk that a new patient intake is complete and includes a link to the contact record. The referral is already attached.

The front desk confirms the referral is valid and schedules the evaluation – no email follow-up needed to collect the document.

Result: New patient onboarding is complete in one form submission. The referral is in the contact record before the first call is made to schedule the appointment.

Marketing Agencies – Project Intake

An agency’s new project request form includes three File Upload Fields: “Upload your current logo (SVG or PNG),” “Upload your brand guidelines (PDF if available),” and “Upload any reference images or examples (optional).”

The first two are required. The third is optional.

A Form Submitted workflow notifies the project lead with a link to the contact record where all three files are already stored.

Result: The creative team starts every new project with the brand assets already in the CRM. No back-and-forth emails collecting files that should have been provided at intake.

Insurance and Financial Services

An insurance agency’s client onboarding form includes required File Upload Fields for a driver’s license photo and the current insurance declaration page. A workflow on submission tags the contact as “documents submitted” and notifies the assigned agent.

The agent opens the contact record with both documents already there. The underwriting process begins the same day the form is submitted – rather than waiting for email follow-up to collect the documents that should have arrived with the initial application.

Result: Document collection is built into the intake step rather than a separate follow-up task. Agents spend less time chasing paperwork and more time processing applications.

Fitness and Personal Training

A personal trainer’s client onboarding form requires a physician’s clearance form for clients over 50 or with any indicated health condition. A conditional File Upload Field appears based on the contact’s answer to a health disclosure question.

Clients who need to submit the clearance upload it directly in the form. The trainer receives a notification and can verify the clearance before the first session.

Clients who do not need to submit one see a shorter form with the upload field absent.

Result: Medical clearance collection is automated and conditional – only the contacts who need to submit a clearance are prompted to do so.

Home Services – Project Estimates

A landscaping company’s estimate request form includes an optional File Upload Field: “Upload photos of the area (if available).” Clients who can take a phone photo of their yard or garden before the site visit upload it here.

The estimator reviews the submitted photos before the site visit and arrives with a preliminary scope in mind – reducing the visit time and improving the accuracy of the initial estimate.

Result: Optional photo submission improves estimate quality and site visit efficiency without adding friction for clients who prefer to skip the upload.

Who Is This For?

How to Add a File Upload Field

Step 1: Open the form builder

Go to Sites, then Forms in the sub-account navigation.

Open an existing form or create a new one. File Upload Fields work in standalone forms and in forms embedded within funnel pages.

Step 2: Add the File Upload Field

In the field type list or selector panel, find the File Upload option.

Drag it onto the form canvas at the position where the upload prompt should appear in the form flow.

Step 3: Set a specific label

Replace the default field label with a specific instruction: “Upload your signed intake form (PDF)” or “Upload your ID document (JPG or PNG).”

A specific label is the primary driver of correct submissions – contacts upload the right file when they understand exactly what is expected.

Step 4: Set the Required toggle

Enable Required if the form should not be submittable without the file. Leave it off for optional uploads.

Step 5: Configure accepted file types

In the field settings, configure any file type restrictions relevant to this upload.

For document forms, restrict to PDF. For image forms, restrict to JPG and PNG.

For flexible submissions, leave unrestricted.

Step 6: Add helper text

Add a brief helper text below the label explaining the expected format and any size limit: “PDF format only. Maximum 10MB.”

Clear helper text prevents the most common submission errors.

Step 7: Save and publish the form

Save the form. Republish the funnel page if the form is embedded there.

Standalone form links are active immediately after saving.

Step 8: Build a submission notification workflow

In Workflow Builder, create a workflow triggered by Form Submitted for this specific form.

Add a Send Internal Notification action – email, SMS, or in-app – alerting the relevant team member with a link to the contact record where the file is stored.

Step 9: Test the full upload flow

Submit a test form using a personal email and a sample file.

Confirm the file appears in the test contact’s Files tab, the notification workflow fires, and the confirmation message reaches the test email. Fix any issues before sharing the form publicly.

How Does It Connect to HighLevel?

• Document Storage: Files submitted through File Upload Fields are stored in the same contact-level storage system covered in Document Storage. Uploaded form files appear in the contact’s Files or Documents tab alongside any other files attached to that record.
• Workflow Builder: The Form Submitted trigger in Workflow Builder fires when a form with a File Upload Field is submitted. Use it to send internal notifications, apply tags, or initiate any downstream automation based on the file submission event.
• Forms and Surveys: File Upload Fields are available in both HighLevel forms and surveys. Forms on funnel pages, standalone form pages, and survey pages all support the file upload field type – the same behavior across all form contexts.
• Funnel Builder: Forms with File Upload Fields can be embedded in funnel pages – placing the file collection step directly in a lead capture or onboarding funnel flow without redirecting the contact to a separate form page.
• Client Portal: Contacts with Client Portal access do not see their uploaded form files in the portal by default – contact-level file storage and portal document visibility are separate systems. The portal primarily surfaces Documents and Contracts items rather than raw uploaded files.

Common Questions

What are File Upload Fields in HighLevel?

A field type in the HighLevel form builder that allows contacts to attach and submit files during a form submission. Submitted files are automatically stored in the contact’s CRM record – no manual download or re-attachment required.

Where do I add a File Upload Field in HighLevel?

In the form builder at Sites, then Forms. Add the field type from the field selector panel to the form canvas.

Available in standalone forms, funnel forms, and surveys.

Where are uploaded files stored after form submission?

In the contact’s CRM record under the Files or Documents tab. The file is associated with the contact who submitted the form and accessible to any team member who opens that contact record.

What file types can be uploaded through a HighLevel File Upload Field?

Common types including PDFs, images (JPG, PNG), and standard document formats. Accepted types can be configured in the field settings to restrict submissions to specific formats.

Check the field settings for current supported types.

Can I require a file upload in a HighLevel form?

Yes. Enable the Required toggle on the File Upload Field. The form cannot be submitted without a file attached to that field when Required is on.

Can a file upload on a form trigger a workflow in HighLevel?

Yes. Use the Form Submitted trigger in Workflow Builder for the specific form. Add an internal notification action to alert team members when a new file has been submitted.

Can contacts upload multiple files in one HighLevel form?

Yes, by adding multiple File Upload Fields to the same form – one per document type. Each field has its own label, required setting, and accepted type configuration.

Can I notify my team when a file is uploaded through a HighLevel form?

Yes. Build a workflow triggered by Form Submitted for the specific form.

Add a Send Internal Notification action that alerts the relevant team member with a link to the contact record where the file is stored.

Can I use File Upload Fields in HighLevel surveys?

Yes. Surveys support the same field types as forms, including File Upload. Add the field to a survey when respondents should be able to attach supporting documents with their response.

Is there a file size limit for uploads through HighLevel forms?

Yes. File size limits apply and can vary.

Check the field settings for the current maximum. For files exceeding the limit, request a cloud storage link via a text field instead of a direct upload.

To Wrap It Up

The gap between “we need this document from you” and “we have this document on file” is one of the most consistent friction points in service business onboarding. Email-based document collection means a separate request, a separate email thread, a manual download, and a manual filing step.

Every one of those is a point where the document can get lost, delayed, or missed.

A File Upload Field on the intake form closes that gap entirely. The client submits the form.

The document arrives. It is in the right place.

The team is notified. Nothing else needs to happen before the document is accessible.

The setup takes under 10 minutes – add the field, set the label, set required, add helper text, publish, build the notification workflow, test. After that it runs automatically for every submission.

The most important configuration decision is the label. A specific, clear label like “Upload your signed intake form (PDF, under 10MB)” produces correct submissions.

A vague label like “Attachment” produces questions, wrong files, and follow-up email exchanges that the field was supposed to eliminate.

Here is how to get started:

1. Go to Sites, then Forms and open the intake or onboarding form where file collection is needed
2. Add a File Upload Field from the field type list
3. Write a specific label describing exactly what the contact should upload
4. Enable Required if the submission is incomplete without the file
5. Configure accepted file types to match what is appropriate for the use case
6. Add helper text with format and size guidance
7. Save and publish the form
8. Build a Form Submitted workflow with an internal notification action
9. Test by submitting the form from a personal email with a sample file
10. Confirm the file appears in the test contact record and the notification fires

Test with the actual file type your contacts will use – not just any file. A form configured to accept PDF only will reject a JPG.

Testing with the right file format confirms the configuration matches the real-world submission before the form reaches a real contact.