Fillout Review

Fillout review verdict: choose Fillout when the form needs to update a database, qualify a lead, collect a payment or book a meeting. Its free plan includes 1,000 responses per month plus unlimited forms and seats, but a client portal, an unbranded form and a Salesforce workflow cross different upgrade gates.

Fillout is a form builder that can read existing information, collect new answers and send the result into the system where you manage the work. It makes surveys, quizzes, applications, registrations and booking flows as well as ordinary contact forms. That makes it useful as the front door to a business process; the database or customer relationship management system behind it still needs an owner. Fillout’s product overview, plan details.

Verified against live vendor pricing and documentation on November 1, 2026. This evaluation uses published capabilities, plan boundaries and workflow analysis, with no signed-in product test.

Fillout Review: Who Should Use It?

Fillout fits an operator whose next task begins with the submitted information. An agency needs the inquiry in its client database, a workshop organizer needs registration tied to payment, and a service business needs qualifying answers attached to the appointment. Its strongest advantage is reducing the gap between the form and that working record.

The buying criteria here are what happens after submission, what can be read or updated, which plan permits the complete flow, and what can fail silently. Visual polish matters, but a beautiful form that creates duplicate contacts or treats an unsettled payment as paid creates work elsewhere.

The capabilities behind these recommendations are documented by Fillout, Typeform and Google Forms. For a wider shortlist, see our best form builder comparison.

Fillout vs Typeform

Typeform remains a credible choice when the experience of answering the form is central to the product: a brand campaign, qualitative customer research or a survey that benefits from video and adaptive follow-up questions. Its current product includes those capabilities alongside its conversational form experience. If that is your brief, evaluate Typeform before switching solely for response capacity. Typeform’s product pages.

Fillout wins the free-plan argument on usable response capacity and payment collection, but free conditional logic is not an exclusive advantage. Typeform’s own Free documentation includes branching, calculations, scores and variables, plus an Airtable integration. Its payment question is paid. Fillout’s advantage is the combination of logic with a larger free allowance, native database-update workflows and included payment pages. Fillout plans.

Do not move a working Typeform funnel on an assumed conversion gain. Neither a feature list nor a pricing comparison proves that more people will finish your form. Compare the actual mobile journey and the destination data before changing an established campaign.

Fillout vs Google Forms

Google Forms is the sensible default for a staff questionnaire, a basic feedback survey or a quiz whose answers need to land in Google Sheets. Google documents answer-dependent flows, quiz support, collaborative analysis and response charts. If that completes the job, another platform adds configuration without a clear payoff. Google Forms features.

Fillout becomes more compelling when the requirement changes from collecting answers to updating a customer record, collecting a registration payment or joining intake to booking. Its integration catalog also includes importing an existing Google Form. Treat that as a migration starting point: review the mapped fields, branching and downstream behavior before replacing the old link. Fillout’s integrations.

Fillout Conditional Logic: Qualify the Lead Before the Handoff

Fillout can collect different information from different prospects without forcing everyone through the same questionnaire. Conditional logic means a prior answer determines which field or page appears next. Answer piping reuses an earlier answer in later text; calculations turn answers into a score or amount. These capabilities are included on Free. Logic overview, plan entitlements.

Consider a B2B agency taking both new-project inquiries and support requests. Asking an existing customer about budget and company background wastes their time. Sending a new prospect straight to the support queue wastes yours. Start with the reason for contacting you, branch to the relevant questions, and pass the useful answers into the destination record.

The same building blocks support a product-fit quiz or a customer survey. A quiz can calculate a score; a survey can skip questions about a service the respondent has never used. Fillout lists text, choice, dropdown, rating, ranking, matrix, date, upload and signature fields among its question types, with premium field entitlements depending on the plan. Field catalog.

1. 1

   Separate the decisions from the questions

   For an agency inquiry, decide where a new-project request, an existing-client request and an unsuitable inquiry should go. Then write only the questions needed for each destination. This is the workflow design; the builder cannot decide your qualification policy.

2. 2

   Connect the relevant pages

   In Fillout, open Logic, connect the pages, use Set condition, and add branches for the other paths. Keep a sensible route for answers that do not meet a special condition. These are the controls shown in Fillout’s page-logic guide.

3. 3

   Check both the form and the destination

   Walk through the branches before publishing. Confirm that each route asks the intended questions and maps the right answers into your business system. A branch that looks correct but loses the contact email is still a broken intake process.

The editor steps follow Fillout’s branching documentation. For a marketer, the payoff is more useful qualification data and less irrelevant questioning, not a promised increase in conversion rate.

The upgrade boundary is easy to miss: free branching does not mean every possible ending is free. Fillout places custom endings, multiple endings and completion redirects on Starter and above. A simple qualification flow may fit Free; a campaign that must redirect each segment to a different destination can require an upgrade. Pricing matrix.

Fillout Airtable Integration: Update the Record, Not Another Inbox

Fillout’s Airtable connection is its strongest reason to exist for many operators: an existing record can prefill a form, the respondent can correct it, and the submission can update that record. Airtable is a database presented in a spreadsheet-like interface. Fillout provides a more focused surface for someone who should complete a task without working inside the whole base. Airtable integration.

For an agency, that might mean asking a client to confirm project details already stored in Airtable. The useful comparison is between “send another questionnaire and reconcile the answer” and “edit the record the project already uses.” The second workflow removes a reconciliation step by design, although the amount of time saved depends on your process.

Fillout also supports picking, creating and filtering linked records, the relationships between entries such as a client and its projects. That matters when the answer must attach to an existing project instead of becoming an isolated submission. Airtable capabilities.

The documented update setup is specific: open Integrate, choose Airtable, switch to Update record, and copy Fillout’s generated formula into an Airtable formula field. Each record then has its own update link. Missing the record’s id in that URL changes the behavior: Fillout creates a new record instead. That is an important check before sending a client-update campaign. Update-record guide.

A simple client portal needs an access decision

Fillout login forms can verify a respondent’s email, restrict access by domain or a database user list, and let people return to edit previous submissions. That can cover a narrow client portal whose job is submitting or correcting information. Login forms begin on Fillout Starter; a Zite app plan with a similar tier name does not automatically include form login. Login documentation.

A login page and an update link solve different problems. The login establishes who is responding. The update link identifies the record. Neither removes the need to decide which fields that person may receive.

That warning and its workaround come directly from Fillout’s update-form documentation. A client record containing internal margin notes is a reason to design the data boundary before distributing links, not after.

For a portal needing broader account navigation, role-based screens and ongoing record management, scope an application separately. A form with a login is a good answer to a narrow task, but it should not become the accidental architecture for an entire customer workspace.

Native integrations are not all equivalent

Fillout connects directly to the main destinations in this review, but the supported operation and plan matter more than a logo in a directory.

• Notion: create or update database entries and map form questions to properties. Refresh the mapping after changing the database structure.
• HubSpot: create contacts or update an existing contact when the submitted email matches. Custom properties must be enabled for use in forms and bots.
• Salesforce: create or update records, but publishing that integration requires Team or Enterprise. Connecting it during setup on a lower plan does not remove that gate.
• Google Sheets: send submissions into a spreadsheet when the workflow only needs an accumulating response log.

These behaviors are documented in the Notion guide, HubSpot guide, Salesforce guide and integration catalog.

The catalog also lists native connections for work and messaging tools such as Slack, Microsoft Teams, Monday.com, ClickUp, SmartSuite and Pipedrive; file destinations include Google Drive, Dropbox, OneDrive and Amazon S3. Email and marketing connections include Mailchimp, Klaviyo, ActiveCampaign and Brevo. Availability still depends on the feature and plan.

By contrast, Fillout puts PostgreSQL, MySQL, MongoDB, Firebase and PayPal in its Partner integrations section, described as powered by Zapier. Do not budget those as direct database connections just because their names appear on the page. A webhook, a message sent to another service when a form is submitted, is another supported route if you have an endpoint to receive it. Native and partner catalog, webhook guide.

Fillout Payments: Good for Registrations, With a Settlement Caveat

Fillout includes Stripe payment pages on every plan and adds no platform transaction surcharge. Stripe’s ordinary fees still apply. It supports one-time charges, subscriptions and pay-what-you-want payments, with options including cards, US bank payments, Affirm and Stripe Link. Payment features, payment documentation.

For a paid workshop, collect the attendee’s details, calculate the selected option’s price, take payment, and send the registration information to the destination system. A service business can use the same structure for a paid consultation. This is a good fit when the form itself captures the information needed to deliver what was purchased.

The setup starts with Add page → Payment, a payment type and Connect to Stripe. The amount and product name can reference form answers or calculations. Keep the payment page on every route that should require payment, and give it a following page or ending. Otherwise, your branching design can undermine the purchase requirement. Payment-page setup.

A submitted form is not always a settled payment. Fillout blocks ordinary abandoned or declined payments from completing the form, but free checkouts, subscription trials and processing US bank payments are exceptions. Its documentation says bank payments can submit before the money arrives, and the payment status in Fillout is not updated later, even if the bank payment fails.

For automatic fulfillment, compare the status exactly with succeeded. A loose “contains succeeded” rule also matches succeeded_free. Bank payments need a separate settlement check in Stripe using the payment ID. The business consequence is concrete: do not issue a paid registration, release goods or grant membership merely because a row appeared in Airtable. Payment states and exceptions.

There are other boundaries. Fillout does not automatically add value-added tax (VAT) even if the Stripe setting is enabled; its documented workaround uses a calculated tax-inclusive amount. A subscription payment page uses a single Stripe price, so alternative subscription tiers need separate pages and branching. Form answers also cannot be passed directly into Stripe payment metadata. Keep the payment ID beside the registration, or add a separate automation when Stripe needs that metadata. Payment limitations.

The verdict for paid registrations is therefore positive for a defined intake-and-checkout flow. If the business depends on sophisticated tax handling, subscription management or asynchronous-payment fulfillment, specify those requirements before treating the form as the checkout system.

Booking and Documents: Finish the Intake Workflow

Fillout can carry the same answers into scheduling and document generation, which is valuable when the form initiates an appointment or an administrative handoff. The important design choice is what the customer should leave with: a booking, a completed document, or both.

Fillout Scheduling

Fillout Scheduling connects to Google Calendar and Microsoft Outlook, checks availability and can sit inside a longer form. Its public feature page lists round robin, collective and group meetings, reminders, minimum notice and buffer times. Native scheduling is included on Free; using Fillout’s Calendly integration is a separate Starter feature. Scheduling features, plan comparison.

A local service business could ask what work is needed before offering an appointment. A B2B sales team could collect qualification details before showing the relevant booking step. The benefit is keeping context attached to the meeting instead of asking the prospect to explain the same request again.

Set the connected calendars, working hours, location, minimum notice and buffers before distributing the link. Fillout’s guide also contains a consequential testing detail: a booking made in Preview is a real booking, with a calendar event, invitation and workflow execution. Cancel practice appointments afterward. Scheduling setup.

If your database must stay current when a customer reschedules or cancels, a webhook attached under Integrate is insufficient by itself: it runs for the original submission. Use a workflow for the later scheduling event. Otherwise, your calendar can be correct while the operational record still shows the old appointment. Scheduling webhook behavior.

Fillout PDF generation

Fillout can map answers into a PDF or document template, making it useful for a registration confirmation, intake sheet or customer document. In Integrate → Generate PDF, upload the template, map the fields, preview the result and publish. Completed documents can be downloaded, attached to emails or sent to supported destinations such as Airtable, Notion and Dropbox. The delivery method has its own plan requirements; free PDF generation does not make every email feature free. PDF guide, pricing.

For an operations manager, this removes the need to copy each answer into a standard document manually. Keep the template focused on the information the receiving person needs, and inspect longer answers before using the output for customers.

The storage behavior deserves more attention than the feature name. Fillout says generated documents are rebuilt from the template when their links open; they are not stored as independent files. Deleting the submission breaks its document link. An already downloaded or emailed copy cannot be recalled. If you need a durable completed record, save a copy to the chosen storage destination as part of the workflow. Google Sheets cannot receive generated PDFs. Document lifecycle and destinations.

Fillout Pricing: Choose the Feature Gate, Then Check Responses

Fillout Free is a usable operating plan, but Starter is the first serious upgrade for a business that needs CAPTCHA bot checks, login forms, signatures, respondent emails or a completion redirect. Pro buys brand control. Business buys the custom domain, deeper analytics, partial submissions and data prefetch, which loads information before the form opens. Choose the feature that completes your workflow before choosing by response volume alone.

The standard paid prices below are monthly equivalents billed annually, not month-to-month prices. They come from Fillout’s live pricing page. Team pricing comes from its Team documentation; Team and Enterprise response allowances are confirmed in the submission-limit documentation.

Free includes unlimited forms and seats, multi-page forms, conditional logic, calculations, answer piping, payment collection, scheduling, PDF generation, uploads, hidden fields and most integrations. It leaves the Fillout badge in place. Starter still has light branding; Pro removes it, but Pro does not include a custom domain. That belongs to Business. Feature matrix.

For a solo agency sharing unbranded forms, Pro is the natural evaluation point. For a growth marketer who needs drop-off analysis or partial submissions to diagnose a campaign, Business is the relevant comparison even if the response count would fit a smaller plan. Features such as abandonment recovery and enrichment are separately marked as Conversion kit capabilities, so do not assume Business includes the whole conversion toolkit.

Salesforce changes the recommendation more sharply. Its integration requires Team or Enterprise to publish. A Salesforce buyer should price the workflow against that gate from the beginning, rather than build around the Free allowance and discover the restriction at launch. Salesforce requirement.

Fillout Limitations That Matter After Launch

Fillout’s documented limits affect capacity, access and automation. These are the checks most likely to change an implementation decision after the feature checklist looks complete.

Unlimited responses still have fair-use boundaries

Fillout lists consistently exceeding 30,000 submissions per month or exceeding 250,000 submissions in total among its examples of excessive usage. Its file examples include over 50 GB uploaded monthly or 300 GB stored. These are fair-use examples, not new guaranteed plan allowances. A high-volume campaign should get its expected load agreed before relying on the Unlimited label. Fair-use policy.

File count and file size are also different limits: Free, Starter and Pro list a 20 MB maximum file size. An agency collecting large creative assets can reach that boundary while receiving relatively few responses. Upload limits.

The response allowance belongs to the organization

Fillout counts completed submissions across the organization’s forms, not a separate allowance for each form. Counts reset at the start of the calendar month in UTC, rather than on the subscription renewal date. Live-link test submissions count; Preview submissions and partial responses do not. Counting rules.

Forms continue collecting after a plan limit is exceeded, and the Results view remains available. Repeated overages can lead to an upgrade request and eventually feature restrictions. That is helpful continuity during a spike, not permission to run permanently above the purchased allowance.

Free workflows have limits and an email-verification gate

Fillout allows 5 workflows per form, increasing to 20 after organization verification, with 20 actions per workflow. Its docs say paying for a higher plan does not change those workflow-count limits. Workflow limits.

For organizations created on or after October 5, 2026 with no paid Fillout or Zite plan, workflows sending email from Fillout require verification or an upgrade. Connected Gmail or Outlook sending and non-email actions are treated differently. An operator can therefore have a working form and an email follow-up that still needs authorization. Also, published workflows run during Preview submissions and can send real messages. Email and Preview behavior.

A branded portal still sends login codes from Fillout

Fillout’s login-code sender is always notifications@fillout.com; the sender name cannot be changed or replaced with your own domain. That is a specific limit for an agency promising a fully branded client experience. Form branding removal does not remove every third-party touchpoint. Login email controls.

Simultaneous integrations cannot pass a newly created record ID between them

Fillout cannot send a just-created Airtable record ID through another webhook that fires on the same submission. Both integrations run at submission time, before that new ID is available to the webhook. If a downstream process needs the ID, sequence that process after creation instead of assuming all integrations form an ordered chain. Webhook limitation.

Notion Person properties are not ordinary text fields

Fillout cannot fill Notion’s Person or Last edited by properties. Its suggested Select-property workaround stores a name as text, not as a Notion user. For a task-intake form, that distinction can break the intended ownership workflow even though the row contains the right-looking name. Computed and system-managed properties also remain read-only. Notion property limitations.

Verdict: Choose by the Work After Submission

Fillout earns a recommendation when its native connection completes a defined business task. It earns a more conditional recommendation when you need a portal, a payment system or a chain of automations that goes beyond form submission.

For lead capture: choose Fillout when qualification and the CRM handoff matter most. Begin on Free if its presentation and controls fit, move to Starter for the relevant capture controls, and evaluate Business when conversion diagnostics or a custom domain are requirements. Keep Typeform on the shortlist when conversational presentation, video responses or research capabilities are central.

For internal operations: choose Fillout for structured intake that updates working data, produces a document or triggers an approval process. Keep Google Forms if a questionnaire and a Google Sheets response log already complete the task. Complexity should earn its place by removing a specific manual handoff.

For paid registrations: choose Fillout when Stripe checkout, attendee details and the destination record form a manageable flow. Make payment status part of fulfillment. Skip treating it as a complete commerce system when tax handling, subscription operations or delayed settlement are core requirements.

For an Airtable front end: this is the strongest fit. Record prefill, updates and linked-record handling address work that a basic collection form does not. Before sharing externally, define the permitted records and fields, restrict prefilled data where needed, and choose login protection when the workflow requires identity verification.

The decision rule is simple: pick Fillout when it completes the intake-to-record workflow on a plan you can justify; choose another tool when the missing piece is the respondent experience, a basic survey you already have, or a broader application.

For the next implementation, take an existing intake process and trace it from the respondent’s first answer to the final business record. Identify the create-or-update rule, payment requirement, document destination and access boundary before building. Then verify the successful path and the failure paths: wrong record link, declined payment, rescheduled booking and failed integration. That gives you a concrete acceptance checklist without assuming a feature label guarantees the outcome.

Frequently Asked Questions

Is Fillout free?

Yes. Free includes 1,000 responses per month, unlimited forms and seats, logic, payments, native scheduling and core integrations. Login forms, branding removal and a custom domain sit on different paid plans. Fillout pricing.

Does Fillout have conditional logic on the free plan?

Yes. Fillout lists conditional logic, calculations, scoring and answer piping on Free. Custom endings and completion redirects are separate paid features, so check the entire route through the form. Plan comparison.

Is Fillout better than Typeform?

For database-backed intake and a practical free operating allowance, Fillout is the stronger choice here. Typeform remains worth evaluating for conversational forms, video responses and research. Choose by the complete workflow rather than logic alone. Fillout capabilities, Typeform features.

How much does Fillout cost?

The standard paid ladder starts with Starter at $15 per month when billed annually, with an annual bill of $180. The plan table above distinguishes the other tiers and billing bases. Choose by the required feature gate as well as response volume. Current pricing.

Does Fillout replace a CRM?

For an ongoing sales process, keep a CRM such as HubSpot or Salesforce as the relationship system. Fillout can collect information and update records; ownership, sales stages and follow-up policy still need to be designed in the system that manages those relationships. HubSpot connection, Salesforce connection.

Get the AI Business Workflow Audit Checklist

Map the intake, data, permissions and handoffs before choosing your next business tool.