Fillout Review

Fillout: Forms, Payments And Signatures

• Six products in one: forms, scheduling, PDF generation, payments, workflows and signatures.
• White-label to the favicon, served from your own custom domain with custom social share previews.
• Respondents can edit their own submissions through login forms — the feature that saves the most support time.
• Four embed modes — popup, slider, side tab and full screen — rather than one iframe.
• SOC 2 Type 2 with 256-bit encryption, and 100,000-plus organisations claimed.

Fillout: Products And Security

Why Do Form Builders Keep Adding Products?

Fillout describes itself as the all-in-one form solution, and lists scheduling, PDF, payments, workflows and signatures alongside forms themselves.

That expansion is not feature creep. It follows the shape of what actually happens after a form is submitted.

Consider an event registration. Someone fills in a form, pays, picks a time slot, receives a confirmation document, and possibly signs a waiver. Five products, one process, and historically five subscriptions plus an automation service holding them together.

Every join in that chain is a place where data goes missing, a webhook fails silently, or a person ends up registered but unpaid. Collapsing the chain removes the joins rather than automating them.

The trade is the usual one. A specialist scheduling tool will out-feature this, and so will a dedicated e-signature platform. What you buy instead is one place where the record is complete — which is the same argument that makes a consolidated knowledge base like Document360 beat five well-integrated wikis.

Five products, one process, and five places where someone ends up registered but unpaid. Collapsing the chain removes the joins.

Letting Respondents Edit Their Own Answers

Buried in the feature list is something more valuable than its placement suggests: login forms that let respondents update their existing submissions, with the option to make forms internal-only.

Anyone who has run an intake process knows what this replaces.

Somebody enters the wrong email address, or their availability changes, or they need to correct a dietary requirement. Without self-service the only route is an email to whoever owns the form, a manual database edit, and a reply — several minutes of someone's time, multiplied by the number of respondents.

Self-service editing turns that into nothing. It also improves data quality, because people will correct their own record when it is easy and will not when it requires asking a stranger for a favour.

The reason it is rarely advertised is that it is unglamorous and requires real work — identity, permissions and versioning on a form submission. Its presence is a better signal of product maturity than any AI feature on the page.

White Labelling Down To The Favicon

The branding claim is unusually specific: pre-built themes or your own fonts, logo, colours and custom CSS, control over social share previews, full white-labelling down to the favicon, and sharing from your own custom domain.

Naming the favicon is the detail that shows someone has actually thought about this.

White-label is a term applied loosely. Most tools mean the vendor's logo is hidden from the page, while the browser tab still shows their icon, the share preview still carries their branding, and the URL still says their domain. Each of those leaks the vendor at a moment the respondent is deciding whether to trust the form.

That matters because forms are where people hand over personal data, and an unfamiliar domain is exactly the signal security training teaches them to distrust.

So a form on your own domain, with your favicon and your share preview, is a conversion feature rather than a vanity one. The four embed modes serve the same end — a popup or side tab keeps the respondent on your site entirely, which is better again. Referral and affiliate intake is a specific version of the same problem, handled end to end by Partnero.

Conditional Logic And Where It Breaks

Fillout describes smart forms that reduce manual work with intelligent routing, plus workflows as a distinct product surface.

Conditional logic is where every form builder is genuinely tested, and where most of them quietly fail.

The simple case is easy and every tool handles it: if the answer is yes, show the next question. The difficulty is compounding — a form where the fourth question depends on the first and second, the routing depends on the fourth, and someone changes their answer to the first after reaching question six.

That is where builders break, either by showing a question that no longer applies or by silently keeping an answer that is now orphaned. Both produce data that looks clean and is wrong.

The practical test during evaluation is to build your ugliest real form rather than a demo one, then go back and change an early answer. Whether the tool recovers gracefully tells you more than any feature list, and it is the single thing worth spending an hour on.

• Build your ugliest real form, not a demo one, during evaluation.
• Change an early answer after reaching the end and see what happens.
• Set up the custom domain before sharing anything externally.
• Enable respondent editing if the same data ever needs correcting.
• Check the integration to your CRM before the first live submission.

Reading The Ratings And The Customers

Fillout displays an average of 4.8 out of 5 from hundreds of reviews, broken into 5 out of 5 on business reviews and 4.7 on Product Hunt, alongside a claim of 100,000-plus organisations.

A perfect 5 out of 5 on any platform with a meaningful sample is worth reading carefully rather than as a straightforward endorsement, since averages that clean usually indicate a small or recent review base.

The customer names carry more weight. A county election manager and a giving programme at a consumer brand are both organisations with real data-intake requirements and, in the first case, unusual scrutiny.

The election manager's quote is the most useful thing on the page — describing trying many form builders over the years and finding this one more robust and more flexible. That is a comparison from someone with a professional reason to be careful.

The published comparison pages against six named competitors point the same way. A company that invites direct comparison with Jotform, Typeform and Formstack is confident about where it lands, and those pages are a reasonable place to start your own evaluation. What happens to the responses afterwards is a separate question, and where a tool like Quadratic takes over.

Building A Form That Actually Converts

Form abandonment is a design problem rather than a tooling one, and the most common cause is asking for things you do not yet need.

This sequence uses the platform's strengths and avoids the mistakes that lose respondents.

1. Cut every field you will not act on — each one costs completions.
2. Set up the custom domain and branding before sharing anything.
3. Use conditional logic so nobody sees a question that does not apply.
4. Embed as a popup or side tab rather than sending people away.
5. Enable respondent editing so corrections do not become support tickets.
6. Watch the analytics for the field where people stop, and remove it.