Salesforce Forms: Every Option, Compared

“Which Salesforce form should I use?” Wrong first question. The right one is: who’s filling it out, and where?

That single answer narrows your options from a dozen down to one or two. Public visitor on your website? You want Web-to-Lead or Web-to-Case. Internal rep updating a record? Dynamic Forms. A multi-step application or onboarding flow? Screen Flow. Something no native tool can handle? LWC or a third-party builder.

This guide walks through every Salesforce form type Salesforce gives you — native, pro-code, and third-party — and tells you which one actually fits. No fluff. No “Salesforce is the leader in CRM.” Just the decision.

What “Salesforce Forms” Actually Means

A Salesforce form isn’t one thing. It’s any input surface — public or internal — that reads from or writes to a Salesforce object.

That covers a lot of ground:

• A marketing landing page that captures leads
• A support page that opens cases
• A lightning page where a sales rep edits a record
• A multi-step application that spins up a contact, an opportunity, and a task in one shot
• A licensed application form for a permit or policy

Every one of these is a “Salesforce form.” They just live in different places and serve different people. That’s why creating forms in Salesforce isn’t a single tutorial — it’s a decision about which tool maps to your use case.

Key Takeaway: “Salesforce forms” is a category, not a feature. The right tool depends entirely on where the form lives and who fills it out.

The 3-Second Decision Tree

Before scrolling through every option, answer these three questions:

1. Who fills it out? → Public visitor, authenticated customer, or internal Salesforce user?
2. What does it create or update? → Lead, Case, or a custom object?
3. How complex is the logic? → One screen, multi-step, or conditional branching?

If your answer is…	Use this
Public visitor → Lead	Web-to-Lead
Public visitor → Case	Web-to-Case
Public visitor → anything else (or branching logic)	Screen Flow on an Experience site, or a third-party builder like FormAssembly or Gravity Forms
Internal user → record edit with conditional fields	Dynamic Forms
Internal user → multi-step guided process	Screen Flow
Industry-specific (insurance, health, public sector)	OmniScripts (OmniStudio)
Custom UX, heavy branding, external auth	Lightning Web Component

The Litmus Test: If you can describe the form without the word “custom,” you probably don’t need code. Start with the native no-code tools first.

Native No-Code Form Options

These are the Salesforce form builder tools that ship with the platform. No AppExchange install, no third-party license.

Web-to-Lead: The Public Lead Capture

Web-to-Lead is the classic. A simple HTML snippet you embed on your site that turns visitor submissions into Lead records — up to 500 leads per day by default.

Best for: marketing landing pages, contact-us forms, newsletter signups, gated content.

Limits: one form = one Lead. No conditional logic. No file uploads. Basic spam protection via reCAPTCHA.

For the full setup including anti-spam, routing, and embedding on your website, read the Salesforce Web Forms guide. If you’re on WordPress, the Salesforce Web-to-Lead form WordPress tutorial walks through embedding step by step. In a hurry? Our Web-to-Lead form builder tool generates the HTML for you.

Pro Tip: If your Gravity Forms or WPForms plugin already lives on the site, skip Web-to-Lead and connect Gravity Forms to Salesforce directly. You keep your existing design system and get richer field mapping.

Web-to-Case: The Public Support Intake

Same pattern, different object. Web-to-Case turns visitor submissions into Case records — up to 5,000 cases per day. Add reCAPTCHA v2 to stop the junk.

Best for: help-center contact forms, bug reports, support requests, warranty claims.

Limits: same as Web-to-Lead — one object, one form, no branching.

See the complete Web-to-Case walkthrough for setup, auto-response rules, and assignment logic.

Dynamic Forms: Smart Internal Record Pages

Dynamic Forms is a Lightning App Builder feature that lets admins drag fields onto a record page and apply visibility rules — so reps only see the fields that matter right now.

Best for: internal record edit pages where different teams need different fields on the same object (a “Business” account vs. an “Individual” account, for example).

The 2024–2025 updates made Dynamic Forms work on all standard objects and support related list filtering. If you’re still using classic page layouts, you’re leaving conditional UX on the table.

Full Dynamic Forms walkthrough with the Winter ’25 updates →

Screen Flow: Multi-Step Guided Forms

Screen Flow is the Swiss Army knife. It’s the form builder for Salesforce that most admins underuse. Build a multi-screen wizard — “Personal Info → Details → Payment → Review” — with real branching, input validation, and the ability to create multiple records in a single submission.

Best for:

• Sales reps entering new leads with qualifying questions
• Customer onboarding that creates a Contact + Account + Opportunity in one shot
• Support agents running a diagnostic script
• Public forms hosted on an Experience Cloud site (yes — Screen Flows work on public pages)

New in 2024–2025:

• Reactive Components — fields update in real time based on other field values (pick a country, state list refreshes instantly)
• Action Buttons — fire automations without leaving the screen
• HTTP Callouts — pull data from external APIs mid-flow

Screen Flow is where salesforce lightning form builder queries live. If Web-to-Lead feels too rigid and Dynamic Forms feels too “record page,” Screen Flow is the answer.

OmniScripts: Industry-Specific Guided Flows

OmniScript is part of OmniStudio (formerly Vlocity). Think of it as Screen Flow’s cousin for regulated industries — insurance quotes, healthcare intake, government license applications.

Best for: industries with structured multi-step applications where calculations, document generation, and conditional branching all need to happen in one guided experience.

Reality check: OmniStudio is a separate license for most orgs. Don’t jump to OmniScripts if Screen Flow can do the job.

Real Talk: OmniScripts get pitched as “the advanced option” but for 80% of admins, Screen Flow is more flexible, better documented, and cheaper. Only reach for OmniStudio if you’re already in Industries Cloud or you need its specific form-to-document pipeline.

Pro-Code Form Options

When the native Salesforce form builder options can’t do it, developers step in. These are for custom forms with code.

Lightning Web Components (LWC)

LWC is the current standard. Custom HTML + modern JavaScript elements that run anywhere Lightning runs — record pages, Experience sites, Flows, mobile.

The handy starter components:

• lightning-record-form — quick create/view/edit for any object
• lightning-record-edit-form — full control over layout and styling while still respecting field-level security
• lightning-record-view-form — read-only display

LWC is where you go when you need a form the native builders can’t make — external auth, complex branded UX, a single-page app embedded in a portal, or a form that talks to an external API before saving to Salesforce.

Aura Components

Older UI framework. Still supported, but new projects should pick LWC unless you’re extending existing Aura code.

Visualforce (Legacy)

Classic server-rendered pages with <apex:form> and <apex:inputField>. Mostly seen in orgs that haven’t migrated yet.

<apex:page standardController="Case">
  <apex:form>
    <apex:pageBlock>
      <apex:pageMessages/>
      <apex:inputField value="{!Case.Subject}"/>
      <apex:inputField value="{!Case.Status}"/>
      <apex:commandButton value="Save" action="{!save}"/>
    </apex:pageBlock>
  </apex:form>
</apex:page>

If you’re starting a new project in 2026, skip it. Use LWC.

Key Takeaway: Pro-code is for the 5% of requirements native tools can’t hit. If you can describe the form in admin-speak, don’t open the IDE.

Third-Party Form Builders for Salesforce

Sometimes the right answer isn’t native at all — it’s an external form tool with a Salesforce connector. These shine when you need a public-facing form with design freedom, complex logic, file uploads, payments, or e-signatures.

• FormAssembly — enterprise-grade, HIPAA & GDPR compliant, prefills from Salesforce, robust connector.
• Formstack — the AppExchange staple; strong admin UX, templates, payments.
• Gravity Forms — if your stack is WordPress, this is usually the best move.
• JotForm / 123FormBuilder / Cognito Forms — lighter-weight drag-and-drop options with Salesforce connectors.
• Google Forms — free and fast, integrated via Apps Script or Zapier.

We cover these in detail in our 10 forms that integrate with Salesforce roundup. For specific tutorials:

• JotForm Salesforce integration →
• Google Forms to Salesforce →
• Gravity Forms to Salesforce →
• 6 WordPress forms compatible with Salesforce →

Comparison Matrix: All Options Side-by-Side

Option	Audience	Code?	Conditional Logic	Multi-Step	File Uploads	Best Use
Web-to-Lead	Public	No	No	No	No	Marketing lead capture
Web-to-Case	Public	No	No	No	Yes (limited)	Support intake
Dynamic Forms	Internal	No	Yes	No	Via related files	Smart record edit pages
Screen Flow	Both	No	Yes	Yes	Yes	Guided processes, wizards, portal forms
OmniScripts	Both	No	Yes	Yes	Yes	Regulated industry applications
LWC	Both	Yes	Yes	Yes	Yes	Custom UX, external APIs, SPA forms
Visualforce	Both	Yes	Yes	Limited	Yes	Legacy maintenance only
FormAssembly / Formstack	Public	No	Yes	Yes	Yes	Enterprise public forms with compliance
Gravity / JotForm / Google	Public	No	Yes	Varies	Yes	Lighter public forms, existing non-SF stack

How to Pick the Right One

Four tests, in order:

1. Can a native no-code tool do it? If yes, use it. Web-to-Lead, Web-to-Case, Dynamic Forms, and Screen Flow cover 80% of real-world requests.
2. Is this for internal users on a record page? → Dynamic Forms, always. Nothing else beats it on that surface.
3. Is this a public-facing form with real complexity — conditional logic, payments, prefill, e-sign? → Third-party (FormAssembly, Formstack, Gravity Forms). Skip the months it’d take to build it in LWC.
4. Do you need a level of customization no admin tool can provide? → That’s when LWC earns its keep.

Pro Tip: When an AppExchange demo sells you on a shiny drag-and-drop builder, ask the rep: “What can this do that Screen Flow can’t?” If they hesitate, you don’t need the plugin.

Security, Compliance, and Pricing

The one thing every Salesforce form option gets right: data governance. Field-level security, sharing rules, validation rules, audit trails — they all apply automatically. You don’t bolt compliance on. It’s there because the form writes to the same objects as everything else in your org.

What’s included out of the box:

• SOC 2, ISO 27001, and GDPR handling
• HIPAA compliance (with the right license) for healthcare orgs
• Multi-factor auth and role-based access
• Salesforce Shield for encryption at rest and advanced audit trails

Pricing, ballpark:

• Starter Suite — from $25/user/month — enough for Web-to-Lead, Web-to-Case, basic Dynamic Forms
• Professional — from $80/user/month — adds automation, Flow, better admin tools
• Enterprise — from $165/user/month — full Screen Flow, Apex, LWC, Experience Cloud

Third-party tools are on top. FormAssembly starts around $89/month, Formstack around $99, Gravity Forms is a WordPress-side $259/year license plus their Salesforce add-on.

Real Talk: Free Salesforce form generators exist. They mostly work. But the second you need field mapping, audit logs, or HIPAA compliance, they fall apart — and the rebuild usually costs more than just picking the right tool on day one.

FAQs

Still not sure which option fits? We review your existing process, map it to the right Salesforce form type, and build it — native, LWC, or integrated third-party. Tell us what you’re trying to capture and we’ll point you to the shortest path.