# Forms Expert — Full Content
> Forms Expert is a form delivery engine — build a form once and ship it as a hosted page, an embeddable widget, and a REST API, with AI, translation, consent, and analytics built in.
---
# About — Forms Expert · The Form Delivery Engine
Source: https://forms.expert/about
Forms Expert turns one form definition into a hosted page, an embeddable widget, and a REST API. Translation, consent, and analytics are already inside. We build it the way we’d want to buy it: specific, flat-priced, and honest about scope.
## Four Principles We Won’t Compromise
They shape every feature we ship and every line of copy on this site, including what we refuse to claim.
- **Honesty is the product** — We never claim a capability we don’t ship. GDPR is the only compliance acronym we use — no badge walls, no invented testimonials.
- **One definition, not five rebuilds** — A form should ship as a page, a widget, and an API from a single source. Change the channel with a type field. Never rebuild.
- **Flat pricing, stated limits** — $0 to $99 a month with clear per-tier numbers and no per-response cliff. You always know exactly what you’re paying for.
- **Batteries included** — Translation, consent, analytics, and anti-spam belong inside one product — not stitched together from five separate invoices.
## Sign In Your Way, Secure Your Account
How you and your team get into the dashboard — passwordless by default, with social sign-in and authenticator-app two-factor.
- **Passwordless login** — Sign in with a 6-digit code sent to your email — no password to remember or leak.
- **Social sign-in** — Use Google, GitHub, Microsoft, or Apple to sign in; a social account links to a matching email automatically.
- **Authenticator-app 2FA** — Turn on TOTP two-factor with any authenticator app for a second layer of protection on your account.
---
# AI Form Builder — Generate a Form From a Prompt
Source: https://forms.expert/ai-form-builder
Write a plain-English prompt and Forms Expert drafts the fields, logic, and label copy for you. Keep refining with natural-language edits, then ship it as a hosted page, a widget, or a REST endpoint. AI assistance is on Starter and up.
## From a Sentence to a Working Form
Type what you want to collect. The AI builder drafts a structured form — fields, input types, and validation — that you can edit by hand or keep shaping with follow-up prompts.
- Generate from a prompt: describe the form and get a full first draft instantly.
- Edit with AI. Ask for changes in natural language, or tweak fields directly.
- From there it ships straight into triple delivery: page · widget · API.
## What the AI Form Builder Generates
The prompt is the start. Everything the AI drafts is fully editable and connects to the rest of Forms Expert.
- **Smart field selection** — The builder picks input types — rating, email, choice, long text — from your description, not a blank canvas.
- **Conversational edits** — “Add a phone field,” “make email required,” “shorten the intro” — refine without touching the editor.
- **Validation included** — Required fields and basic format checks are drafted right alongside the form.
- **Conditional fields** — Show or hide fields based on earlier answers. The AI can scaffold the rules, and you fine-tune them.
- **Into triple delivery** — The generated form is a normal Forms Expert form. Ship it as a hosted page, a widget, or a REST endpoint.
- **Consent built in** — GDPR cookie consent is part of every form on every plan, generated forms included.
## Prompt, Refine, Ship
1. **Describe it** — Write a sentence or two about what the form should collect and who it’s for.
2. **Refine with AI** — Generate, then adjust fields, logic, and copy by prompting or editing directly.
3. **Publish anywhere** — Ship the finished form as a page, an embedded widget, or a REST endpoint.
**AI generation is on Starter and up.** AI form generation and editing are paid features — they’re off on the Free plan. Every other part of a generated form works on all plans.
Plan availability: Free not included, Starter included, Pro included, Business included.
## AI Form Builder Questions
### Is the AI builder free?
No — AI generation and editing are part of the paid plans (Starter and up). You can build forms manually on the Free plan; the AI assistance turns on once you’re on Starter.
### Can I edit what the AI generates?
Yes. Everything it drafts is a normal, fully editable form — change fields by hand, or keep prompting the AI to adjust it for you.
### What can I do with the form once it’s generated?
The same things as any Forms Expert form: publish it as a hosted page, embed it as an auto-resizing widget, or post to it via the REST API — from one definition.
### Does a generated form include consent and analytics?
GDPR cookie consent is built into every form on every plan. A basic analytics overview is available on all plans, with the view-to-submit funnel, per-field response stats, and NPS on Pro and up.
---
# Contact Forms Expert — Questions, Support & Feedback
Source: https://forms.expert/contact
Questions about delivery channels, webhooks, or pricing? Send a note and we’ll get back to you. The form below is the proof. It’s a real Forms Expert form.
---
# Embeddable Form Builder — Widget, SDK, Auto-Resizing
Source: https://forms.expert/embeddable-forms
The published @forms.expert/sdk renders your form inline in React, Vue, or plain JavaScript and resizes itself to fit. Prefer the raw iframe? That works too. It's the embed half of triple delivery, from the same form definition as your page and API.
## Paste a Snippet, Get a Live Form
Add a target element and one script tag. The widget loads your form, matches your page, grows or shrinks as fields appear, and reports submissions back to your code.
- Published SDK — @forms.expert/sdk ships React, Vue, and vanilla-JS bindings; the recommended way to embed.
- Auto-resizing: the widget fits its content, no fixed iframe height.
- Framework-agnostic plain JavaScript runs inside React, Vue, plain HTML, or a CMS.
- Respond to submission callbacks via postMessage from any framework.
## What an Embeddable Form Adds
The widget is one channel of triple delivery: the same form definition you publish as a page and post to via the API.
- **One-line include** — A target and one script tag. No build step, no package to add.
- **Auto-resizing** — The widget reports its height and grows as conditional fields show or hide — never a clipped iframe.
- **Published SDK for every stack** — @forms.expert/sdk ships React (FormsProvider + FormsExpertForm), Vue, and vanilla-JS bindings — install from npm or unpkg. Prefer no dependency? The raw iframe still works anywhere.
- **Submission callbacks** — Listen for submit events via postMessage to show a thank-you state or fire analytics.
- **Consent & anti-spam** — GDPR consent rides along, with honeypot, rate-limiting, and CAPTCHA to keep junk out.
- **One definition, three surfaces** — The embed shares its definition with the hosted page and the REST API. Change it once and it ships everywhere.
## Copy, Paste, Collect
1. **Copy the snippet** — Grab the one-line embed code from your form's Embed tab.
2. **Paste it in** — Drop it anywhere on your site — a page, a CMS block, a landing template.
3. **Receive submissions** — Responses flow to email, Telegram, and signed webhooks — and your funnel.
**Embedding is on every plan.** The widget works on all plans, including Free. What changes by tier is the monthly submission limit: Free 100, Starter 1,000, Pro 10,000, Business 100,000.
Plan availability: Free · 100/mo included, Starter · 1k included, Pro · 10k included, Business · 100k included.
## Embedding Questions
### Is there a React SDK?
Yes — and it's the recommended way to embed. Install the published @forms.expert/sdk package (npm install @forms.expert/sdk, or load it from unpkg) and import @forms.expert/sdk/react for a FormsProvider and a FormsExpertForm component that renders your form inline. It supports theming, language, available-themes/setTheme, and onSuccess/onError callbacks. Vue and vanilla-JS builds ship in the same package, and the raw iframe embed or the REST submit endpoint remain available if you'd rather skip the dependency.
### Will it match my site's height and layout?
Yes — the widget auto-resizes to its content, so it grows and shrinks as fields show or hide based on earlier answers instead of sitting in a fixed-height iframe.
### How do I know when someone submits?
The widget emits a submit event via postMessage, so you can show a thank-you state or fire analytics. For server-side certainty, verify a signed webhook.
### Is it the same form as my hosted page and API?
Yes. The embed is one surface of triple delivery — it shares a single form definition with the hosted page and the REST endpoint, so edits apply everywhere at once.
---
# Form Analytics — Completion Funnel & NPS Built In
Source: https://forms.expert/form-analytics
Form analytics built into the product, not bolted on: a view-to-submit funnel, per-field response and completion stats, NPS scoring, geo breakdown, and device split. A basic submissions overview is on every plan; the deeper metrics are on Pro and up.
## From Views to Submissions, in One View
Watch the drop-off between views and submissions, read per-field response and completion stats, and track sentiment with NPS — without exporting anything to another tool.
- The view-to-submit funnel shows how many views turn into submissions: viewed → started → submitted.
- Fill rate and average length per field, plus NPS scoring for overall sentiment, without a separate survey tool.
- Geo & device breakdowns map reach and surface, with no separate analytics vendor.
## The Metrics Behind Each Submission
Form analytics is built in, so your form conversion rate and field-level stats live next to the form.
- **View-to-submit funnel** — See how views turn into submissions across viewed, started, and submitted, then spot the leak.
- **Per-field response stats** — How each field performs: fill rate, average length, and common answers, so you know what to tighten.
- **NPS scoring** — Run an NPS question and read the score over time, without wiring up a separate survey tool.
- **Geo breakdown** — See where submissions come from to understand reach and tailor your follow-up.
- **Device split** — Desktop vs. mobile completion, so the weaker surface is easy to spot.
- **Basic overview on all plans** — Every plan sees a simple submissions overview; the deep breakdowns above unlock on Pro and up.
- **Export every submission** — Download responses as CSV, JSON, or Excel on every plan, including Free. Compound fields like name and address flatten into clean, labelled columns.
## It's On the Moment You Publish
1. **Publish the form** — Analytics start collecting as soon as your form is live. Nothing to install.
2. **Watch the funnel** — See views, starts, and submissions in your dashboard, with per-field response stats alongside. New submissions appear live the moment they land, no refresh.
3. **Fix the leak** — Spot the field with the weakest response stats, change it, and watch completion respond.
**Basic Overview Everywhere, Deep Analytics on Pro+.** Every plan gets a basic submissions overview. Per-field response stats, the view-to-submit funnel, NPS, geo, and device analytics turn on at Pro and above.
Plan availability: Free not included, Starter not included, Pro included, Business included.
## Analytics Questions
### Do I get analytics on the Free plan?
Every plan gets a basic submissions overview. The deeper analytics (completion funnel, per-field response and completion stats, NPS, geo, and device) are available on Pro and up.
### Do I need a separate analytics tool?
No. Analytics are built into Forms Expert and tied to your form — there's no tag to add and no third-party dashboard to maintain.
### Can I measure NPS?
Yes — add an NPS question and Forms Expert scores it for you and tracks it over time, alongside the rest of the form's analytics (Pro and up).
### Does analytics work with embedded and API forms?
Analytics follow the form definition, so submissions from the hosted page, the embedded widget, and the REST API all roll up into the same view-to-submit funnel.
---
# Multilingual Form Builder — Translate One Form 30 Ways
Source: https://forms.expert/form-translation
Translate a form's content into 30 languages with built-in, in-product machine translation. Respondents pick a language and the whole form follows. Available on the Business plan.
## Translate the Whole Form in a Click
Labels, help text, options, and buttons translate together — in the product, not through a third-party overlay. Switch languages from the form itself and every string keeps up.
- 30 languages from one source form. No duplicate forms to maintain.
- In-product machine translation, not a Weglot-style external bolt-on.
- Respondents pick their language right on the hosted page or inside the embeddable widget page · widget.
## Every String, One Multilingual Form
Translation works on the whole form definition, so you maintain one form and serve many languages from it.
- **30 languages** — A fixed set of 30 supported languages, generated from your source form's content.
- **Labels & help text** — Field labels, descriptions, placeholders, and option text are all translated, not just titles.
- **Consent text too** — The built-in GDPR consent copy travels with the translation so the legal text isn't left in English.
- **Respondent switcher** — People choose their language right on the form — on the hosted page and inside the embedded widget.
- **One definition** — No cloned forms per locale — translations attach to the single source form you already manage.
- **Re-translate on edit** — Change the source copy and refresh the translations — you're not hand-syncing 30 copies.
## Build Once, Translate, Publish
1. **Build your form** — Create the form in your source language as you normally would.
2. **Add languages** — Pick from the 30 supported languages and generate translations of every string.
3. **Publish multilingual** — Ship one form; respondents switch language on the page or in the widget.
**Translation is a Business-plan feature.** 30-language translation is on the Business plan. Lower tiers can build a form in any single language; the multilingual switcher and translate-form capability are Business-only.
Plan availability: Free not included, Starter not included, Pro not included, Business included.
## Translation Questions
### How many languages are supported?
30 languages, generated from your source form. Translation is a built-in, in-product feature — there's no external service to connect.
### Which plan includes translation?
Translation is on the Business plan. On lower tiers you can build a form in any one language, but the 30-language switcher and machine translation are Business-only.
### Is the translation a third-party overlay?
No. It's in-product machine translation built into Forms Expert — not a Weglot-style external script layered over your form.
### Can respondents choose their language?
Yes — a language switcher appears on the hosted form page and inside the embeddable widget, so people answer in whichever supported language they prefer.
---
# Online Form Builder — Page, Widget & API | Forms Expert
Source: https://forms.expert/
An online form builder where one definition ships three ways: a hosted page, an auto-resizing embed, and a REST endpoint. No rebuilding.
## Everything in One Product, Not Five Subscriptions
Rivals scatter these across add-ons and higher tiers. Translation, consent, analytics, and a real API all live inside Forms Expert.
- **One form, three channels** — A single type field ships the form as a hosted page, an embeddable widget, and an API. No rebuilding.
- **AI form generation** — Our AI form builder generates and edits a form from a plain-English prompt with Anthropic Claude. Off on the Free plan.
- **30-language translation** — Native DeepL translation into 30 languages, built into the form. No separate vendor.
- **GDPR consent built in** — Cookie consent with per-modal analytics and full customization: position, layout, trigger, and categories.
- **Analytics beyond counts** — A completion funnel, per-field stats, NPS, and device breakdowns in form analytics. Basic overview on every plan; depth on Pro+.
- **Developer API & webhooks** — A real REST endpoint with publishable & secret keys and signed webhooks that retry up to 5× with exponential backoff.
## One Form Definition. No Rebuilds, Ever.
The trade-offs you escape by building on one form definition with batteries already included.
- **Never rebuild a form** — One no-code definition ships every way. Change the channel, leave the form alone. Set type and you’re done.
- **Flat, predictable pricing** — $0, $9, $29, $99 with stated per-tier limits and no per-response cliff. 100 to 100,000 submissions a month.
- **Batteries included** — Consent, analytics, anti-spam, and file handling all come in the box.
- **Built for teams** — A workspace per client site with real role-based collaboration. SMB prices, not an enterprise quote.
## How Does One Form Become Three Channels?
Build or generate the form once, choose how it ships, then collect and analyze. Everything stays in one product.
1. **Build or Generate** — Drag and drop 35 field types, generate an editable draft from a plain-English prompt with Claude, or start from a template.
2. **Choose How It Ships** — Set one type field: hosted page, embed, API, or all at once. No rebuilding, ever.
3. **Collect & Analyze** — Route submissions to email, Telegram, and signed webhooks, then read the completion funnel.
## Questions, Answered Plainly
### How does one form become three channels?
A single type field — api, hosted, embed, or both — selects how each form ships: a hosted page at /h/{slug}, an auto-resizing widget at /e/{slug}, and a REST endpoint. One definition, no rebuilding.
### Do you scan uploads for malware?
No. Uploads are validated with MIME presets, schema checks, and SHA-256 checksums on S3, and forms are protected by honeypot, rate limiting, and CAPTCHA. We don’t claim antivirus scanning we don’t run.
### Is the pricing really flat?
Yes — $0, $9, $29, and $99 per month with stated per-tier limits and no per-response cliff. Submissions per month run 100 / 1,000 / 10,000 / 100,000 across Free, Starter, Pro, and Business.
### Is there a published React SDK?
Yes — and it's the recommended way to embed. Install the published @forms.expert/sdk (npm install @forms.expert/sdk, or load it from unpkg), which ships React, Vue, and vanilla-JS bindings. The React binding renders the form inline and supports theme, language, available-themes/setTheme, and onSuccess/onError callbacks. Prefer no dependency? The one-line auto-resizing iframe widget and the REST submit endpoint are still there, with copy-paste fetch and cURL examples.
### Which features are paid?
AI generation is bundled from the paid $9 Starter tier (off on Free). 30-language translation is a Business-plan feature. Basic analytics is on every plan; per-field and NPS analytics are Pro and up.
---
# Lead Capture Forms — Embed Anywhere, Fire to Your Stack
Source: https://forms.expert/lead-capture-forms
On-brand lead capture forms that embed on any page and send every submission to your stack. Signed webhooks, a REST API, email and Telegram alerts, with GDPR consent built in from the first field.
## A Lead Form That Reaches Your Tools Instantly
Lead capture is mostly what happens after submit. Forms Expert embeds the form anywhere and routes each lead to the systems you already run, the moment it lands.
- Embed anywhere via the @forms.expert/sdk (React, Vue, or vanilla JS) or a plain iframe.
- Fire to your stack via signed webhooks and a REST API, with email or Telegram alerts.
- Consent & anti-spam, built in: GDPR opt-in, honeypot, rate-limit, and CAPTCHA.
- Qualify on the way in. Show or hide fields based on earlier answers, captured as page · widget · API.
## Everything a Lead Form Needs
The pieces that turn a form into a lead pipeline, all from one definition, no add-ons.
- **Embed on any page** — The @forms.expert/sdk works in React, Vue, or vanilla JS. A plain iframe is available for zero-dependency installs.
- **Signed webhooks** — Push each lead to your CRM or backend with verifiable, retrying webhooks — up to 5× with exponential backoff.
- **Email & Telegram alerts** — Get notified the instant a lead arrives, by email or Telegram, with no extra tool to wire up. There’s no Slack notification today.
- **Conditional fields** — Qualify on the way in: show or hide a follow-up field based on an earlier answer.
- **Consent built in** — GDPR cookie consent ships with every form on every plan, so opt-in is captured from the start.
- **Anti-spam** — Honeypot, rate-limiting, and CAPTCHA keep junk leads out. Real people barely notice them.
- **Control what happens next** — After submit, show a custom thank-you message, redirect to any URL, or render your own success HTML — fire a conversion pixel or send the lead to the next step.
## From Visitor to Lead in Your CRM
1. **Build & embed** — Design the lead form and drop the one-line widget onto your highest-intent pages.
2. **Connect your stack** — Point a signed webhook at your CRM, or read leads from the REST API on your schedule.
3. **Act on every lead** — Get instant email and Telegram alerts, and watch conversion in the view-to-submit funnel.
## What We Can Actually Promise
We’re early, so we won’t show logos we don’t have. Here’s what the product guarantees instead.
- **5× Webhook retries** — Failed deliveries retry up to five times with exponential backoff, so leads aren’t silently lost.
- **GDPR Consent built in** — Cookie consent is part of every form on every plan, so opt-in lands with the lead itself.
- **3 Ways to deliver** — The same lead form ships as a hosted page, an embeddable widget, and a REST endpoint.
## Lead Capture Questions
### Can I send leads to my CRM?
Yes. A lead capture form collects visitor details and routes them to your CRM via a signed webhook or the REST API. Webhooks retry up to 5× with exponential backoff, so deliveries aren’t lost.
### How do I get notified of new leads?
Forms Expert can notify you by email and Telegram the moment a lead submits, alongside the webhook and API. There’s no Slack notification today.
### How do you keep spam out?
Anti-spam is built in: a honeypot field, rate-limiting, and CAPTCHA. Together they cut junk submissions without adding friction for genuine leads.
### Is consent handled for me?
GDPR cookie consent is built into every form on every plan, so you capture opt-in as part of the lead rather than wiring up a separate consent tool.
### Can you email a confirmation to each respondent?
Yes — auto-send a confirmation email to the person who submitted, with a custom subject and message (Starter and up).
---
# Online Survey Builder — Multi-Step, NPS & Analytics
Source: https://forms.expert/online-surveys
Build multi-step surveys with conditional logic and NPS, then read real completion analytics to see where respondents drop off. Pricing is flat, no per-response cliff, so a busy survey won’t inflate your bill.
## Ask the Right Question Next
Forms Expert runs multi-step flows with conditional fields, so respondents only see follow-up questions that are relevant. That means cleaner data and less drop-off.
- Multi-step with progress: break a long survey into steps with a progress indicator so respondents see how far they’ve come.
- Conditional fields & NPS: show or hide fields based on earlier answers, and score sentiment over time.
- No per-response cliff. Flat pricing with stated monthly limits, not metered overages.
- One definition, two surfaces — run the same survey as a hosted page or an embeddable widget.
## Everything a Survey Needs
Conditional logic, NPS scoring, and a view-to-submit funnel in one product. The same survey runs as a hosted page, an embeddable widget, or a REST endpoint.
- **Multi-step flows** — Break long surveys into steps with a progress indicator to keep completion high.
- **Conditional fields** — Show or hide fields based on earlier answers, so people only see follow-up questions that matter.
- **NPS & rating scales** — Drop in an NPS or rating question and let Forms Expert score it for you over time.
- **Completion analytics** — Read a view-to-submit funnel and per-field response and completion stats. The deep funnel and NPS analytics are on Pro and up.
- **Flat pricing** — Stated monthly limits — Free 100, Starter 1,000, Pro 10,000, Business 100,000 — no per-response overage.
- **Share or embed** — Run the survey as a hosted page or embed it on your site — same definition, your choice.
## Build, Branch, and Measure
1. **Build the flow** — Add questions across steps and set the conditional fields that decide what each respondent sees next.
2. **Share it** — Publish as a hosted page or embed the survey anywhere you reach your audience.
3. **Read the results** — Track completion, the view-to-submit funnel, and NPS in the built-in analytics.
## What the Survey Engine Guarantees
No invented response counts or logos, just the capabilities you can rely on.
- **100k Submissions / month** — The Business tier handles up to 100,000 submissions a month — flat price, no per-response cliff.
- **NPS Scored for you** — Run an NPS question and read the score over time in the built-in analytics — no extra tool.
- **Logic Conditional fields built in** — Show or hide fields based on earlier answers, so surveys adapt to each respondent without add-ons.
## Survey Questions
### Will I get charged more if responses spike?
No. Pricing is flat with stated monthly submission limits — Free 100, Starter 1,000, Pro 10,000, Business 100,000 — so a busy survey won’t trigger a per-response overage.
### Can the survey adapt based on answers?
Yes — conditional logic lets you show or hide fields based on earlier answers, so respondents only see follow-up questions that are relevant across a multi-step flow.
### Do I get analytics on responses?
A basic overview is on every plan. The view-to-submit funnel, per-field response and completion stats, and NPS scoring are part of the deeper analytics on Pro and up.
### Can I embed the survey or just share a link?
Both. The same survey ships as a hosted page you can link to and as an auto-resizing embeddable widget — from one definition.
---
# Pricing — Forms Expert · Flat Plans from $0 to $99/mo
Source: https://forms.expert/pricing
### Free — $0/mo ($0/yr)
For trying it out and shipping your first forms.
Includes:
- 100 submissions / mo
- All 3 delivery channels
- All 35 field types
- Basic analytics
- GDPR consent
- Data export (CSV/JSON/XLSX)
### Starter — $9/mo ($90/yr)
AI generation bundled in — from here up.
Everything in Free, plus:
- 1,000 submissions / mo
- AI form generation
- 1 custom domain
- Signed webhooks
- Email support
### Pro — $29/mo ($290/yr)
For growing teams and deeper analytics.
Everything in Starter, plus:
- 10,000 submissions / mo
- Per-field analytics & NPS
- Completion funnel
- 5 custom domains
- Priority support
### Business — $99/mo ($990/yr)
Translation, scale, and real team roles.
Everything in Pro, plus:
- 100,000 submissions / mo
- 30-language translation
- 20 custom domains
- Role-based team access
## Every Capability, Side by Side
### Core
| Feature | Free | Starter | Pro | Business |
| --- | --- | --- | --- | --- |
| Submissions / month | 100 | 1,000 | 10,000 | 100,000 |
| Field types | 35 | 35 | 35 | 35 |
| Multi-step & conditional logic | Yes | Yes | Yes | Yes |
| File uploads | Yes | Yes | Yes | Yes |
### Delivery & developer
| Feature | Free | Starter | Pro | Business |
| --- | --- | --- | --- | --- |
| Hosted page, widget & REST API | Yes | Yes | Yes | Yes |
| Data export | Yes | Yes | Yes | Yes |
| Signed, retrying webhooks | — | Yes | Yes | Yes |
| Custom domains | — | 1 | 5 | 20 |
### AI & content
| Feature | Free | Starter | Pro | Business |
| --- | --- | --- | --- | --- |
| AI form generation | — | Yes | Yes | Yes |
| 30-language translation | — | — | — | Yes |
### Analytics
| Feature | Free | Starter | Pro | Business |
| --- | --- | --- | --- | --- |
| Basic analytics overview | Yes | Yes | Yes | Yes |
| Per-field stats, NPS & funnel | — | — | Yes | Yes |
### Compliance, team & support
| Feature | Free | Starter | Pro | Business |
| --- | --- | --- | --- | --- |
| GDPR consent & anti-spam | Yes | Yes | Yes | Yes |
| Password / domain / invitation access | — | Yes | Yes | Yes |
| Role-based team access | — | — | — | Yes |
| Support | Community | Email | Priority | Priority |
## Pricing, Answered Plainly
### What happens if I hit my submission limit?
Your monthly submissions are capped at the plan’s stated number — 100 / 1,000 / 10,000 / 100,000. There is no per-response overage billing: instead of a surprise charge, you’re prompted to upgrade. That’s what “no per-response cliff” means.
### Is there a free trial?
Yes. All paid plans include a 14-day trial. The Free plan is free forever with a 100-submission monthly limit — no credit card required to start.
### Which features are paid?
AI form generation is bundled from the $9 Starter tier (off on Free). 30-language translation is a Business-plan feature. Basic analytics is on every plan; per-field stats, NPS, and the completion funnel are Pro and up.
### What does yearly billing save me?
Paying yearly bills 10 months instead of 12 — effectively 2 months free. Toggle “Yearly” above to see each plan’s annual rate.
### Can I switch plans or cancel anytime?
Yes. Upgrade, downgrade, or cancel from your dashboard at any time. Changes take effect immediately and billing is prorated.
---
# Event Registration Form Builder — Uploads & Steps
Source: https://forms.expert/registration-forms
Build an event registration form that takes file uploads without requiring a respondent account. Split long signups into steps, let people save and continue later, and embed it anywhere with consent built in.
## Let People Register Without Friction
Event registration forms often need a document and more than one screen. Start from a registration form template, collect uploads with no respondent sign-in, and pace it across steps with progress saved.
- Collect IDs, CVs, or tickets via file upload. Respondents don't need to create an account.
- Long forms that don't lose people halfway through, with save-and-continue on Starter and up.
- Conditional fields show or hide fields based on earlier answers, like ticket type or role.
- Drop the signup on your event page or share a link. Inline code as page · widget · API.
## Everything a Signup Needs
From the upload to the confirmation — and the same form can be a page, a widget, or an API.
- **File uploads** — Collect IDs, CVs, photos, or tickets directly in the form. Respondents never have to sign in.
- **Multi-step** — Pace a long registration across clear steps, with a progress indicator as people go.
- **Save & continue** — Let people pause and return without losing progress, which means fewer abandoned signups.
- **Conditional fields** — Show or hide fields based on earlier answers — like ticket type or role — so each registrant sees only the right fields.
- **Consent & anti-spam** — GDPR consent is built in, with honeypot, rate-limiting, and CAPTCHA to block junk signups.
- **Access control** — Password-protect a registration, restrict it to a domain, make it invitation-only, cap the number of signups, or close it on a deadline.
- **Notify & sync** — Send each registration to email, Telegram, and signed webhooks, or read it from the REST API. Set up recipients once per workspace and reuse them across forms.
- **After-submit control** — Show a custom thank-you message, redirect to a confirmation or payment page, or render your own success HTML — so registration flows into your next step.
## Open Registration in Minutes
1. **Build the signup** — Add your fields, an upload or two, and split it across steps if it's long.
2. **Publish or embed** — Share a hosted registration page or embed the form on your event site.
3. **Manage signups** — Get notified, sync to your systems, and watch completion in the view-to-submit funnel.
## What the Registration Engine Promises
No invented attendee counts, just what the registration engine does.
- **No login Uploads without accounts** — Respondents attach files without creating an account, so fewer drop off before they finish.
- **Resume Save & continue** — People can pause a long registration and pick it back up where they left off.
- **3× Ways to deliver** — One registration form ships as a hosted page, an embeddable widget, and a REST endpoint.
## Registration Questions
### Can registrants upload files?
Yes — add file-upload fields for IDs, CVs, photos, or tickets, and respondents attach them without creating an account or signing in.
### Can people finish a long form later?
Yes — save-and-continue is available on the Starter plan and up. It lets registrants pause a multi-step form and return to where they left off, which cuts abandonment on longer signups. (Multi-step forms themselves are on every plan, including Free.)
### Does it handle payments for paid events?
No — Forms Expert does not collect payments. It handles the registration, uploads, and routing; you would pair it with a separate payment tool if you need to charge.
### Where do registrations go?
Each registration can notify you by email and Telegram, fire a signed webhook to your systems, and be read from the REST API — and it rolls up into the view-to-submit funnel. Inline as email · webhook · REST.
### Can registrants get a confirmation email?
Yes — automatically email each registrant a confirmation with a custom subject and message after they sign up (Starter and up).
---
# Bug Report Form Template — Repro Steps, Severity & API
Source: https://forms.expert/templates/bug-report-form
Capture reproducible bug reports — severity, steps to reproduce, expected vs actual, and a screenshot. Embed it in your app, host it as a page, or POST issues straight to your tracker via API.
## Ten Fields, Fully Reproducible
Everything a developer needs to triage a bug — and nothing they don't. Edit, reorder, or remove any field in the builder.
- Your Name (required) — text
- Email Address (required) — email
- Bug Title (required) — text
- Severity (required) — choice
- Description (required) — long text
- Steps to Reproduce (required) — long text
- Expected Behavior (required) — long text
- Actual Behavior (required) — long text
- Screenshot / Recording — file
- Page URL where bug occurred — url
Ships three ways from one definition: a hosted page (/h/{slug}), an embeddable widget (/e/{slug}), and a REST API.
## Live in Three Steps
1. **Start from this template** — It opens in the builder pre-filled, free on every plan, no credit card.
2. **Make it yours** — Adjust severity levels, add fields for your stack, and restyle it to match your product.
3. **Publish & route** — Ship it as a page, a widget, or an API — embed it in-app via embeddable forms and route issues to your tracker.
## Bug Report Questions
### Is the bug report form template free?
Yes, browsing and using it is free on every plan, with no credit card required.
### Can testers attach screenshots?
Yes — the template includes an optional screenshot/recording file field with MIME and size validation. No account needed to submit.
### Can I send bugs straight to my issue tracker?
Yes — route submissions to email, Telegram, or signed webhooks that retry, or pull them from the REST API into your tracker.
---
# Contact Form Template — Free, Embeddable & API-Ready
Source: https://forms.expert/templates/contact-form
A clean contact form your visitors actually finish — name, email, subject and message. Embed it as a widget on any page, host it as its own link, or post submissions straight to your API.
## Five Fields, Zero Clutter
Everything a visitor needs to reach you — and nothing they don't. Edit, reorder, or remove any field in the builder.
- Your Name (required) — text
- Email Address (required) — email
- Phone Number — phone
- Subject (required) — choice
- Message (required) — long text
Ships three ways from one definition: a hosted page (/h/{slug}), an embeddable widget (/e/{slug}), and a REST API.
## Live in Three Steps
1. **Start from this template** — It opens in the builder pre-filled, free on every plan, no credit card.
2. **Make it yours** — Rename the subject options, add fields, and match the accent to your brand.
3. **Publish & route** — Ship it as a page, a widget, or an API, then send submissions to email, Telegram or a webhook — or grow it into a full lead-capture flow.
## Contact Template Questions
### Is the contact form template free?
Yes, browsing and using it is free on every plan, with no credit card. Paid plans add extras like AI generation and 30-language translation, not template access.
### Can I embed the contact form on my website?
Yes. Ship it as an auto-resizing widget with a one-line script, host it as its own page, or POST to it via the REST API — all from one definition. See embeddable forms.
### Where do contact submissions go?
Route them to email, Telegram, or signed webhooks that retry — or pull them from the REST API into your CRM.
---
# Contact Form Templates — Page, Widget & API
Source: https://forms.expert/templates/contact
Two ways to open a clean line back to you — a focused contact form and a structured support ticket that captures the details you actually need to reply. Each one hosts as a standalone page, embeds as a widget on any site, or posts submissions to your own systems over the REST API. Both are free on every plan, and new submissions show up instantly so nothing slips through.
## Capturing leads, not just messages?
## Contact Template Questions
### Are the contact form templates free?
Yes, browsing and using every template is free on every plan, with no credit card required.
### Can I embed a contact form on my site?
Yes — each ships as an auto-resizing widget, a hosted page, and a REST API from one definition.
### Where do submissions go?
Route them to email, Telegram, or signed webhooks that retry, or pull them from the REST API into your CRM.
---
# Course Evaluation Form Template — Ratings & Feedback
Source: https://forms.expert/templates/course-evaluation-form
Gather end-of-course feedback that's actually useful — content and instructor ratings, plus open comments. Host it, embed it in your LMS, or pull responses via API.
## Eight Fields, Real Signal
Ratings for content and instructor, plus space for open feedback and a recommendation. Edit, reorder, or remove any field in the builder.
- Course Name (required) — text
- Instructor Name (required) — text
- Overall Course Rating (required) — rating
- Content Quality (required) — scale
- Instructor Effectiveness (required) — rating
- What did you like about the course? — long text
- Suggestions for improvement — long text
- Would you recommend this course? — yes/no
Ships three ways from one definition: a hosted page (/h/{slug}), an embeddable widget (/e/{slug}), and a REST API.
## Live in Three Steps
1. **Start from this template** — It opens in the builder pre-filled, free on every plan, no credit card.
2. **Make it yours** — Tune the rating scales, add questions, and restyle it to match your program.
3. **Publish & collect** — Ship it as a page, a widget, or an API — or run it as a recurring online survey across cohorts.
## Course Evaluation Questions
### Is the course evaluation form template free?
Yes, browsing and using it is free on every plan, with no credit card required.
### Can I see per-question rating stats?
A basic analytics overview is on every plan; per-field response stats and rating breakdowns are available on Pro and up.
### Can I embed it in my LMS?
Yes — embed it as an auto-resizing widget, host it as its own page, or POST to it via the REST API.
---
# Customer Feedback Form Template — NPS & Satisfaction
Source: https://forms.expert/templates/customer-feedback-survey
Measure satisfaction and capture the comments behind the score. An NPS question, a satisfaction rating, and open feedback — ready to host, embed, or call by API.
## Six Fields, Real Signal
An NPS recommend question, an overall satisfaction rating, and two open-comment prompts. Edit, reorder, or remove any field in the builder.
- Full Name (required) — text
- Email Address (required) — email
- How likely are you to recommend us? (required) — scale
- Overall Satisfaction (required) — rating
- What did you like most? — long text
- What could we improve? — long text
Ships three ways from one definition: a hosted page (/h/{slug}), an embeddable widget (/e/{slug}), and a REST API.
## Live in Three Steps
1. **Start from this template** — It opens in the builder pre-filled, free on every plan, no credit card.
2. **Make it yours** — Tune the NPS and rating scales, add questions, and restyle it to match your brand.
3. **Publish & collect** — Ship it as a page, a widget, or an API, then route responses anywhere — or run it as a recurring online survey.
## Feedback Survey Questions
### Is the customer feedback survey template free?
Yes, browsing and using it is free on every plan, with no credit card required.
### Does it calculate an NPS score?
The template includes the NPS recommend-likelihood question. A basic analytics overview is on every plan; per-field response stats and the NPS breakdown are available on Pro and up.
### Can I embed the survey or call it via API?
Yes — the same definition ships as a hosted page, an auto-resizing embed, and a REST endpoint. See form analytics for how responses are reported.
---
# Education Form Templates — Evaluations & Quizzes
Source: https://forms.expert/templates/education
Evaluations, quizzes and assessments for classrooms and training teams — collect answers, ratings and structured responses without spreadsheet wrangling. Each template hosts as its own page, embeds inside your LMS or course site, or runs over the REST API, and every one is free on every plan. Need something specific? Start from a template or generate a fresh form from a prompt.
## Surveying a whole cohort?
## Education Template Questions
### Are the education form templates free?
Yes, browsing and using every template is free on every plan, with no credit card required.
### Do the quizzes auto-grade?
Not automatically — Forms Expert collects the answers; tools like Google Forms offer built-in auto-grading. Use these when you want a multi-step quiz that also ships as a page, a widget, and an API, and score it with your own logic.
### Can I embed them in my LMS?
Yes — each ships as an auto-resizing widget, a hosted page, and a REST API from one definition.
---
# Employee Onboarding Form Template — Page, Widget & API
Source: https://forms.expert/templates/employee-onboarding-form
Gather new-hire details, emergency contacts and work setup step by step — without the back-and-forth email chain. Host it, share it, or post onboarding data to your HR system via API.
## Eleven Fields, Three Steps
Everything HR needs to set up a new hire — and nothing they don't. Edit, reorder, or remove any field in the builder.
- Full Name (required) — name
- Personal Email (required) — email
- Phone Number (required) — phone
- Date of Birth (required) — date
- Home Address (required) — address
- Emergency Contact Name (required) — text
- Emergency Contact Phone (required) — phone
- Start Date (required) — date
- Department (required) — select
- T-Shirt Size — choice
- Dietary Restrictions — multi-select
1. **Personal Information** — Name, email, phone, date of birth and home address.
2. **Emergency Contact** — Who to reach in an emergency, and how.
3. **Work Details** — Start date, department, and a couple of welcome details.
Ships three ways from one definition: a hosted page (/h/{slug}), an embeddable widget (/e/{slug}), and a REST API.
## Live in Three Steps
1. **Start from this template** — It opens in the builder pre-filled, free on every plan, no credit card.
2. **Make it yours** — Set departments, add policy acknowledgements, and restyle it to match your brand.
3. **Publish & route** — Ship it as a page, a widget, or an API — and pair it with other registration forms.
## Onboarding Questions
### Is the employee onboarding form template free?
Yes, browsing and using it is free on every plan, with no credit card required.
### Do multi-step forms work on mobile?
Yes — steps stack to a single column, the progress bar stays visible, and the form scrolls comfortably on a narrow screen.
### Where does onboarding data go?
Route it to email, Telegram, or signed webhooks, or pull it from the REST API into your HR system.
---
# Event Registration Form Template — Page, Widget & API
Source: https://forms.expert/templates/event-registration-form
Collect attendees, ticket types, headcount and dietary needs in a few clear fields. Host it as a page, embed it on your event site, or post registrations straight to your API.
## Seven Fields, Ready to Register
Everything you need to take a registration — and nothing you don't. Edit, reorder, or remove any field in the builder.
- Full Name (required) — text
- Email Address (required) — email
- Company / Organization — text
- Ticket Type (required) — choice
- Number of Attendees (required) — number
- Dietary Requirements — multi-select
- Special Requests — long text
Ships three ways from one definition: a hosted page (/h/{slug}), an embeddable widget (/e/{slug}), and a REST API.
## Live in Three Steps
1. **Start from this template** — It opens in the builder pre-filled, free on every plan, no credit card.
2. **Make it yours** — Set ticket types and limits, add custom questions, and restyle it to match your event.
3. **Publish & share** — Ship it as a page, a widget, or an API — or build it out into a fuller registration form for bigger events.
## Event Registration Questions
### Is the event registration form template free?
Yes, browsing and using it is free on every plan, with no credit card required.
### Can I embed it on my event website?
Yes — embed it as an auto-resizing widget with a one-line script, host it as its own page, or POST to it via the REST API.
### Does it collect payments?
Forms Expert does not process payments itself. The template collects registrations and ticket choices; pair it with your payment tool of choice at checkout.
---
# Event Form Templates — Registration & RSVP
Source: https://forms.expert/templates/event
Registrations and RSVPs without the back-and-forth — collect attendees, ticket choices, guest details and dietary needs in one structured submission. Each template hosts as a page you can share, embeds on your event site, or posts entries to your own tools over the REST API. All are free on every plan, and multi-step versions keep longer forms from feeling like a wall of fields.
## Need full event registration?
## Event Template Questions
### Are the event form templates free?
Yes, browsing and using every template is free on every plan, with no credit card required.
### Can I embed an event form on my site?
Yes — each ships as an auto-resizing widget, a hosted page, and a REST API from one definition.
### Do they collect payments?
Forms Expert does not process payments. The templates collect registrations and ticket choices; pair them with your payment tool of choice.
---
# Exit Interview Form Template — Structured Offboarding
Source: https://forms.expert/templates/exit-interview-form
Understand why people leave with honest, structured offboarding questions — reason, experience ratings and open feedback. Host it, share the link, or pull responses via API.
## Eight Fields, Honest Signal
Enough structure to compare across leavers, with room for candid feedback. Edit, reorder, or remove any field in the builder.
- Your Name (required) — text
- Department (required) — select
- Years at Company (required) — select
- Primary Reason for Leaving (required) — select
- Overall Experience (required) — select
- What did you enjoy about working here? — long text
- What could be improved? — long text
- Would you recommend this company to others? — yes/no
Ships three ways from one definition: a hosted page (/h/{slug}), an embeddable widget (/e/{slug}), and a REST API.
## Live in Three Steps
1. **Start from this template** — It opens in the builder pre-filled, free on every plan, no credit card.
2. **Make it yours** — Adjust the reason and experience options, drop the name field for anonymity, and restyle it.
3. **Publish & collect** — Share the hosted link or embed it — or run it as a standing online survey across departures.
## Exit Interview Questions
### Is the exit interview form template free?
Yes, browsing and using it is free on every plan, with no credit card required.
### Can responses be anonymous?
You can drop the name field in the builder to collect anonymous feedback — keep only the questions you want.
### Where do responses go?
Route them to email, Telegram, or signed webhooks, or pull them from the REST API into your HR system.
---
# Feedback Form Templates — Surveys & Bug Reports
Source: https://forms.expert/templates/feedback
Measure satisfaction and surface the comments behind the score — a customer feedback survey with rating scales and a reproducible bug report that captures the steps you need to fix it. Each template hosts as a page, embeds as a widget, or posts to your stack over the REST API, free on every plan. Export every response as CSV, JSON or XLSX when you are ready to dig in.
## Running a bigger survey?
## Feedback Template Questions
### Are the feedback form templates free?
Yes, browsing and using every template is free on every plan, with no credit card required.
### Can I see response stats?
A basic analytics overview is on every plan; per-field response stats and NPS breakdowns are available on Pro and up.
### Can I embed a feedback form?
Yes — each ships as an auto-resizing widget, a hosted page, and a REST API from one definition.
---
# HR Form Templates — Applications, Onboarding & Offboarding
Source: https://forms.expert/templates/hr
Hiring and people forms that handle resumes, multi-step flows and the details HR actually tracks — without bolting on a separate ATS. From job applications to onboarding and exit interviews, each template ships as a hosted page, an embeddable widget, and a REST API, and stays free on every plan. Collect file uploads, branch questions with conditional logic, and post submissions straight to the system you already use.
## Registering people at scale?
## HR Template Questions
### Are the HR form templates free?
Yes, browsing and using every template is free on every plan, with no credit card required.
### Can a job application accept resume uploads?
Yes — the job application template includes a required resume file field with MIME and size validation. Applicants can upload without an account.
### Do multi-step forms work on mobile?
Yes — steps stack to a single column, the progress bar stays visible, and the form scrolls comfortably on a narrow screen.
---
# Form Templates — Page, Widget & API · Forms Expert
Source: https://forms.expert/templates
## Start From a Template. Ship It as a Page, a Widget, and an API.
Every template is a real, working Forms Expert form — open it, fill it in, and make it yours. The same definition becomes a hosted page, an auto-resizing embed, and a REST endpoint.
## Every Template, Ready to Ship
Every form we offer in one place — filter by category, open any template to fill in the live preview, then launch it as a hosted page, an embeddable widget, and a REST API. Free on every plan.
## From Template to Live in Three Steps
Pick a template, make it yours, then choose how it ships — no rebuilding between channels.
1. **Pick & Preview** — Open any template and fill in the live preview — it is the real form, not a screenshot.
2. **Make It Yours** — Edit fields, logic and theme in the builder. The template keeps its own saved styling.
3. **Choose How It Ships** — Set one type field — page, embed, API, or all at once.
## Template Questions, Answered
### Do templates cost anything?
No. Browsing and using every template is free on every plan, including Free — no credit card required. Paid plans add things like AI generation and 30-language translation, not template access.
### Is the preview a real form?
Yes — each preview is the actual Forms Expert form, rendered live with its own saved theme. You can fill it in to see exactly how it behaves, including multi-step flows and validation.
### Can one template ship as a page, a widget, and an API?
That is the whole point. A single type field selects how each form ships: a hosted page at /h/{slug}, an auto-resizing widget at /e/{slug}, and a REST endpoint — from one definition, no rebuilding.
### Can I edit a template after I start from it?
Completely. Add or remove fields, change labels and validation, wire conditional logic, and restyle it. Templates are a starting point, not a lock-in.
---
# Job Application Form Template — Page, Widget & API
Source: https://forms.expert/templates/job-application-form
A guided, multi-step application that collects contact details, the role, experience, a resume upload, and screening answers — then ships as a careers-page embed, a hosted link, and a REST API into your systems.
## Thirteen Fields, Three Steps
Everything a hiring team needs to screen a candidate — and nothing it doesn't. Edit, reorder, or remove any field in the builder.
- Full Name (required) — name
- Email Address (required) — email
- Phone Number — phone
- Portfolio / LinkedIn URL — url
- Position Applied For (required) — text
- Years of Experience (required) — select
- Highest Education (required) — choice
- Upload Resume (required) — file
- Cover Letter — long text
- Available Start Date — date
- Salary Expectation — amount
- How did you hear about us? — choice
- Data Processing Consent (required) — consent
1. **Personal Information** — Name, email, phone and a portfolio or LinkedIn link — the basics, kept short to start strong.
2. **Professional Background** — The role, years of experience, education and a required resume upload.
3. **Additional Details** — Cover letter, start date, salary expectation, referral source, and GDPR consent before submit.
Ships three ways from one definition: a hosted page (/h/{slug}), an embeddable widget (/e/{slug}), and a REST API.
## Live in Three Steps
1. **Start from this template** — It opens in the builder pre-filled, free on every plan, no credit card.
2. **Adjust fields & theme** — Rename roles, add screening questions, and tweak the accent to match your brand.
3. **Publish & route** — Choose page, embed, or API, then send applications to email, Telegram, or a webhook — or pair it with other registration forms.
## Job Application Questions
### Can the job application accept resume uploads?
Yes — the template includes a required resume/CV file field with MIME and size validation. Applicants can upload without creating an account.
### Is the job application form template free?
Yes, browsing and using it is free on every plan, with no credit card required.
### Do multi-step forms work on mobile?
Yes — steps stack to a single column, the progress bar stays visible, and the form scrolls comfortably on a narrow screen.
### Where do applications go?
Route them to email, Telegram, and signed webhooks that retry — or pull them from the REST API into your ATS. See embeddable forms to add it to a careers page.
---
# Newsletter Signup Form Template — Embeddable Widget
Source: https://forms.expert/templates/newsletter-signup-form
The smallest form that earns its place — email, an optional first name, and an interest. Built to embed: drop the auto-resizing widget on any page, host it, or POST signups to your list via API.
## Three Fields, Built to Embed
Just enough to start a list, and nothing that adds friction. Edit, reorder, or remove any field in the builder.
- Email Address (required) — email
- First Name — text
- Primary Interest — select
Ships three ways from one definition: a hosted page (/h/{slug}), an embeddable widget (/e/{slug}), and a REST API.
## Live in Three Steps
1. **Start from this template** — It opens in the builder pre-filled, free on every plan, no credit card.
2. **Make it yours** — Add interest options, tweak the copy, and restyle it to match your brand.
3. **Embed it anywhere** — Drop the one-line auto-resizing widget on any page with embeddable forms — or host it, or POST signups via API.
## Newsletter Signup Questions
### Is the newsletter signup form template free?
Yes, browsing and using it is free on every plan, with no credit card required.
### How do I embed it on my site?
Paste a one-line script and it renders as an auto-resizing widget inside your page — no iframe wrangling. See embeddable forms.
### Does it include GDPR consent?
GDPR cookie consent is built into every Forms Expert form on every plan; add a consent field for explicit opt-in if you need one.
---
# Order Form Templates — Product Orders & Quote Requests
Source: https://forms.expert/templates/order
Take orders and quote requests, structured and ready to route — capture products, quantities, options and shipping in one clean submission. Each template hosts as a page, embeds as a widget, or posts entries to your system over the REST API, free on every plan. Payments stay with your own tool: these forms collect the order details and hand them off, so you keep your existing checkout.
## Capturing sales leads?
## Order Template Questions
### Are the order form templates free?
Yes, browsing and using every template is free on every plan, with no credit card required.
### Do they process payments?
No — Forms Expert does not handle payments. These forms collect order and quote details; pair them with your own payment tool at checkout.
### Can orders route into my system?
Yes — send them to email, Telegram, or signed webhooks, or pull them from the REST API into your order system.
---
# Patient Intake Form Template — Page, Widget & API
Source: https://forms.expert/templates/patient-intake-form
Structure a new-patient intake — personal details, insurance and medical history — across three clear steps, collected before the visit. Share the link, embed it, or pull responses via API.
## Twelve Fields, Three Steps
A standard intake structure you can shape to your practice. Edit, reorder, or remove any field in the builder.
- First Name (required) — text
- Last Name (required) — text
- Date of Birth (required) — date
- Email Address (required) — email
- Phone Number (required) — phone
- Home Address (required) — long text
- Insurance Provider — text
- Insurance ID — text
- Known Allergies — long text
- Current Medications — long text
- Existing Medical Conditions — long text
- Reason for Visit (required) — long text
1. **Personal Information** — Name, date of birth, and contact details.
2. **Insurance** — Provider and member ID, if you collect them.
3. **Medical History** — Allergies, medications, conditions, and the reason for the visit.
Ships three ways from one definition: a hosted page (/h/{slug}), an embeddable widget (/e/{slug}), and a REST API.
## Live in Three Steps
1. **Start from this template** — It opens in the builder pre-filled, free on every plan, no credit card.
2. **Make it yours** — Adjust the insurance and history fields, add questions, and restyle it to match your practice.
3. **Publish & collect** — Share the hosted link before a visit, or embed it — and pair it with other registration forms.
## Patient Intake Questions
### Is the patient intake form template free?
Yes, browsing and using it is free on every plan, with no credit card required.
### Is it HIPAA compliant?
No. Forms Expert is not a HIPAA or BAA provider, so do not use it for protected health information that requires HIPAA compliance. The template structures standard new-patient intake and includes GDPR cookie consent on every plan.
### Can patients fill it in before a visit?
Yes — share the hosted link or embed it on your site so patients complete intake ahead of time, on any device.
---
# Product Order Form Template — Multi-Step, Page, Widget & API
Source: https://forms.expert/templates/product-order-form
Take product orders with quantities, options and delivery details across two clear steps. Host it, embed it on your store, or POST orders to your system via API — pair it with your own payment tool.
## Eight Fields, Two Steps
Order details first, shipping second — kept short so buyers finish. Edit, reorder, or remove any field in the builder.
- Select Product (required) — select
- Quantity (required) — number
- Color — select
- Special Instructions — long text
- Full Name (required) — text
- Email Address (required) — email
- Shipping Address (required) — long text
- Phone Number (required) — phone
1. **Order Details** — Product, quantity, options and any special instructions.
2. **Shipping Information** — Where it's going and how to reach the buyer.
Ships three ways from one definition: a hosted page (/h/{slug}), an embeddable widget (/e/{slug}), and a REST API.
## Live in Three Steps
1. **Start from this template** — It opens in the builder pre-filled, free on every plan, no credit card.
2. **Make it yours** — Set products, options and shipping fields, and restyle it to match your store.
3. **Publish & route** — Ship it as a page, a widget, or an API, take payment with your own tool, and grow it into a full lead-capture flow.
## Product Order Questions
### Is the product order form template free?
Yes, browsing and using it is free on every plan, with no credit card required.
### Does it take payment?
No — Forms Expert does not process payments. This form collects the order and shipping details; pair it with your payment tool of choice at checkout.
### Can orders route into my system?
Yes — send them to email, Telegram, or signed webhooks, or pull them from the REST API into your order system.
---
# Quiz Template — Multi-Step Online Quiz & Assessment
Source: https://forms.expert/templates/quiz-assessment-template
Build a multi-step quiz or assessment — collect the taker's details, then ask your questions across clean steps. Host it, embed it, or call it via API, and score responses your own way.
## Seven Fields, Two Steps
Taker details first, then five sample multiple-choice questions to replace with your own. Edit, reorder, or remove any field in the builder.
- Your Name (required) — text
- Email Address (required) — email
- Question 1 (multiple choice) (required) — choice
- Question 2 (multiple choice) (required) — choice
- Question 3 (multiple choice) (required) — choice
- Question 4 (multiple choice) (required) — choice
- Question 5 (multiple choice) (required) — choice
1. **Student Information** — Who's taking the quiz.
2. **Questions** — Five multiple-choice questions — swap in your own.
Ships three ways from one definition: a hosted page (/h/{slug}), an embeddable widget (/e/{slug}), and a REST API.
## Live in Three Steps
1. **Start from this template** — It opens in the builder pre-filled, free on every plan, no credit card.
2. **Make it yours** — Swap in your own questions and options, add steps, and restyle it to match your brand.
3. **Publish & collect** — Ship it as a page, a widget, or an API — or run it as a recurring online survey or assessment.
## Quiz Template Questions
### Is the quiz template free?
Yes, browsing and using it is free on every plan, with no credit card required.
### Does it auto-grade answers?
Not automatically — Forms Expert collects the answers; tools like Google Forms offer built-in auto-grading. Use this template when you want a multi-step quiz that also ships as a page, a widget, and an API, and score it with your own logic.
### Can I add more questions or steps?
Yes — add or remove questions, split them across more steps, and restyle the whole thing in the builder.
---
# Quote Request Form Template — Lead-Gen, Page, Widget & API
Source: https://forms.expert/templates/quote-request-form
Let prospects describe what they need and request a tailored quote — service type, budget, timeline and project details. Host it, embed it, or post leads to your CRM via API.
## Eight Fields, Quote-Ready
Everything you need to scope a quote — and nothing that scares a lead off. Edit, reorder, or remove any field in the builder.
- Full Name (required) — text
- Email Address (required) — email
- Company — text
- Phone Number — phone
- Service Type (required) — select
- Budget Range (required) — select
- Timeline (required) — select
- Project Description (required) — long text
Ships three ways from one definition: a hosted page (/h/{slug}), an embeddable widget (/e/{slug}), and a REST API.
## Live in Three Steps
1. **Start from this template** — It opens in the builder pre-filled, free on every plan, no credit card.
2. **Make it yours** — Set service types, budget and timeline options, and restyle it to match your brand.
3. **Publish & route** — Ship it as a page, a widget, or an API — and grow it into a full lead-capture flow.
## Quote Request Questions
### Is the quote request form template free?
Yes, browsing and using it is free on every plan, with no credit card required.
### Does it process payments?
No — Forms Expert does not handle payments. This form collects the details you need to prepare a quote; you send the quote and take payment with your own tools.
### Can leads route into my CRM?
Yes — send them to email, Telegram, or signed webhooks that retry, or pull them from the REST API into your CRM.
---
# Support Ticket Form Template — Category, Priority & API
Source: https://forms.expert/templates/support-ticket-form
Capture support requests with the detail your team needs — category, priority, subject and an attachment. Embed it in your help center, host it, or POST tickets straight to your desk via API.
## Seven Fields, Triage-Ready
Everything an agent needs to pick up a ticket fast — and nothing they don't. Edit, reorder, or remove any field in the builder.
- Your Name (required) — text
- Email Address (required) — email
- Category (required) — select
- Priority (required) — select
- Subject (required) — text
- Description (required) — long text
- Attachment — file
Ships three ways from one definition: a hosted page (/h/{slug}), an embeddable widget (/e/{slug}), and a REST API.
## Live in Three Steps
1. **Start from this template** — It opens in the builder pre-filled, free on every plan, no credit card.
2. **Make it yours** — Set categories and priorities, add fields, and restyle it to match your brand.
3. **Publish & route** — Ship it as a page, a widget, or an API, then send tickets to your desk — or build a full lead-capture flow for pre-sales.
## Support Ticket Questions
### Is the support ticket form template free?
Yes, browsing and using it is free on every plan, with no credit card required.
### Can users attach files to a ticket?
Yes — the template includes an optional attachment file field with MIME and size validation.
### Can tickets route into my help desk?
Yes — send them to email, Telegram, or signed webhooks that retry, or pull them from the REST API into your help-desk tool.
---
# Wedding RSVP Form Template — Free & Shareable
Source: https://forms.expert/templates/wedding-rsvp-form
A quick yes or no with guest count, meal choice and a song request. Share the hosted link, embed it on your wedding site, or pull responses via API.
## Eight Fields, Effortless to Fill
Everything you need from a guest — and nothing that slows them down. Edit, reorder, or remove any field in the builder.
- Full Name (required) — text
- Email Address (required) — email
- Will you be attending? (required) — select
- Bringing a guest? — select
- Guest Name — text
- Meal Preference — select
- Dietary Restrictions — text
- Song Request — text
Ships three ways from one definition: a hosted page (/h/{slug}), an embeddable widget (/e/{slug}), and a REST API.
## Live in Three Steps
1. **Start from this template** — It opens in the builder pre-filled, free on every plan, no credit card.
2. **Make it yours** — Set meal options and guest rules, add questions, and restyle it to match your theme.
3. **Share it** — Send the hosted link or embed it on your site — or build a fuller registration form for the whole event.
## Wedding RSVP Questions
### Is the wedding RSVP form template free?
Yes, browsing and using it is free on every plan, with no credit card required.
### Can guests RSVP without an account?
Yes — anyone with the link can fill it in. No sign-up or app required to respond.
### Can I embed it on my wedding website?
Yes — embed it as an auto-resizing widget, host it as its own page, or POST to it via the REST API.
---
# Cognito Forms Alternative — API, AI & Translation
Source: https://forms.expert/alternatives/cognito-forms-alternative
Cognito wins on price-per-capability and a generous free tier, and we're not going to pretend otherwise. Forms Expert leads with the three things its pricing page doesn't advertise: a real REST API, prompt-to-form AI, and built-in translation — all from one definition that ships as a page, an embed, and an API.
## Forms Expert vs Cognito Forms, Feature by Feature
A side-by-side read, including the rows where Cognito genuinely comes out ahead. Competitor details are approximate (2026) — check them before you rely on them.
## Where Forms Expert Pulls Ahead of Cognito Forms
The reasons teams move off Cognito Forms, and what they get the day they switch.
- **A real REST API and signed webhooks** — A first-class endpoint with pk_/sk_ keys and signed webhooks that retry up to 5 times. Cognito doesn't lead with an API on its pricing page, so headless and product-embedded forms are where we pull ahead.
- **AI that builds and edits the form** — Type what you want, get a full editable form, then keep refining it by prompt (Claude, on paid plans). It's a workflow Cognito's pricing page doesn't advertise. See the AI form builder for what that looks like.
- **Translation inside the product** — Built-in DeepL across 30 languages with per-language publishing, on the $99 Business plan. Not advertised on Cognito's pricing page, and not a separate vendor here — more in form translation.
- **One definition, three channels** — The same form ships as a hosted page, an auto-resizing widget, and a REST endpoint — flip a type field, never rebuild it. Cognito covers the page and embed; the API is the part it doesn't.
- **HIPAA-ready from $9** — A signed BAA and HIPAA-ready forms come with every paid plan from $9. Cognito keeps HIPAA on its top Enterprise tier, so regulated intake starts a lot cheaper here. One honest caveat: it's on the paid plans, not the Free one.
- **Funnel analytics in the product** — A completion funnel, NPS, per-field stats, and geo and device breakdowns land on Pro and up. Cognito is strong on structured data and calculations; this adds the reporting layer that shows where a form loses people, without a separate tool.
## How to Switch From Cognito Forms in Four Steps
There's no automated importer, so you rebuild the form once — then it ships three ways from a single definition.
1. **Rebuild the form** — Recreate your Cognito form in the builder with 35 field types, conditional logic, and multi-step flows. Most forms take minutes, not an afternoon.
2. **Choose how it ships** — Set the type field — hosted page, embed, API, or all three at once. No separate build per channel, which is the whole point.
3. **Drop it into your product** — Install @forms.expert/sdk for React, Vue, or vanilla, or POST to the REST endpoint with a pk_ key. Wire signed webhooks for downstream events. Skip this step if you only need the hosted page.
4. **Turn on the extras** — Enable the GDPR consent module, per-field analytics on Pro, and 30-language translation on Business — all from the same dashboard. Mind the tiers: translation is Business-only, so plan around it.
## Switching From Cognito Forms
### Does Forms Expert have a developer API and webhooks?
Yes. There's a first-class REST endpoint with publishable (pk_) and secret (sk_) keys, plus signed webhooks that retry up to 5 times with exponential backoff. The same form definition also ships as a hosted page and an embed, controlled by one type field. Cognito Forms doesn't lead with an API on its pricing page, so if you're wiring forms into your own code, that's the clearest reason to look at us.
### Can Forms Expert generate a form with AI?
It can. Describe the form in plain English and you get a full, editable form back, then keep editing it by prompt (it runs on Claude). AI generation is on the paid plans, not the free tier. Cognito's pricing page doesn't advertise AI generation, so this is a workflow you'd be adding by switching, not replacing.
### Does Forms Expert support multiple languages?
Yes, with built-in DeepL translation across 30 languages and per-language publishing — on the $99 Business plan, not the cheaper tiers. Cognito doesn't advertise multi-language on its pricing page. So if a multilingual form is a hard requirement, check which tier you'd land on before you commit, because ours is gated to Business.
### What does triple delivery mean here?
One form definition ships three ways at once: a hosted page, an auto-resizing embed, and a REST API. You flip a type field instead of rebuilding the form per channel. Cognito gives you a hosted page and an embed, which covers most marketing use, but not the headless API path. That last channel is the wedge.
### Is Cognito Forms' free tier better than yours?
On raw allowance, probably. Cognito's free tier is genuinely generous, with a large entry allowance, and it's a big reason people like it. Forms Expert's free plan caps at 100 submissions a month. If a roomy free tier is the deciding factor, Cognito is a fair pick. We'd argue the trade is worth it once you need the API, AI, or translation, but the free-tier point goes to them.
### What about calculations, payments, and approvals?
Cognito is strong here. Its calculations, payment collection, and approval workflows are real strengths and show up even on its lower tiers, which is why structured-data and nonprofit teams reach for it. Forms Expert isn't built around heavy calculations or approval routing. If that's the center of your form, Cognito has the better price-per-capability — no contest.
### How do I switch from Cognito Forms to Forms Expert?
Rebuild the form once in the builder (35 field types with conditional logic), pick how it ships — hosted page, embed, API, or all three — then drop in the SDK or point your backend at the REST endpoint. Turn on consent and, on the right tiers, analytics and translation from the same dashboard. There's no automated Cognito importer, so you recreate the form, not migrate it.
---
# Fillout Alternative — Built-In Translation & Consent
Source: https://forms.expert/alternatives/fillout-alternative
Fillout wires forms into your CRM and hands you a roomy free tier, and we like it for that. Forms Expert leans somewhere else: built-in 30-language translation, a GDPR consent module, and one definition that ships as a page, an embed, and a REST API together.
## Forms Expert vs Fillout, Feature by Feature
A straight side-by-side, including the rows where Fillout comes out ahead. Competitor details are approximate (2026), so verify them before you rely on them.
## Where Forms Expert Pulls Ahead of Fillout
The practical reasons developer and growth teams move off Fillout, and what they get on day one.
- **Translation built into the form** — DeepL translation across 30 languages on the Business plan, published per language from the same dashboard. Fillout has no built-in translation, so multilingual there means a separate tool.
- **Consent that ships with the form** — A GDPR consent module with categories, stored consent records, and Google Consent Mode lives in the product. Fillout has no consent module, so you'd add a third-party banner or roll your own.
- **One definition, three channels** — The same form ships as a hosted page, an auto-resizing embed, and a REST endpoint with signed webhooks. Flip a type field, no rebuild per channel.
- **Analytics in the box** — Per-field stats, a completion funnel, NPS, and geo and device breakdowns land on Pro and up, in the same product. You see where responses drop off without wiring a separate analytics tool onto the form.
## How to Switch From Fillout in Four Steps
There's no automated importer, so you rebuild each form once. After that it ships three ways from a single definition.
1. **Rebuild the form** — Recreate your Fillout form with 35 field types, conditional logic, and multi-step flows. Most forms take minutes, not an afternoon.
2. **Choose how it ships** — Set the type field — hosted page, embed, API, or all three at once. One definition covers every channel.
3. **Drop it into your stack** — Install @forms.expert/sdk for React, Vue, or vanilla, or POST to the REST endpoint with a pk_ key. Wire signed webhooks for anything downstream, including the CRM you used Fillout for.
4. **Turn on the extras** — Enable the GDPR consent module, 30-language translation on Business, and per-field analytics on Pro, all from one dashboard.
## Switching From Fillout
### Does Forms Expert translate forms? Fillout doesn't.
Yes. Forms Expert ships built-in DeepL translation across 30 languages, with per-language publishing, on the $99 Business plan. Fillout has no built-in translation at all, so multilingual forms there mean a separate vendor or manual duplication. If you collect responses in more than one language, this is the cleanest reason to switch.
### Can I capture GDPR consent inside the form?
Yes — there's a built-in consent module with consent categories, stored consent records, and Google Consent Mode. Fillout has no consent module, so you'd bolt on a third-party banner or build it yourself. Having consent live in the same form you're already publishing saves a real integration.
### Does Fillout have an API? What's the actual difference?
Fillout does have a REST API, on every tier including free, so this isn't about who has an API. The difference is how it's framed. With Forms Expert, one form definition ships as a hosted page, an embed, and a REST endpoint together, set by a single type field, with signed webhooks that retry up to 5 times. Fillout's hosted, embed, and API are all there too, just less unified around one definition.
### Is Fillout's free plan more generous?
On raw volume, yes. Fillout's free plan allows 1,000 responses a month; Forms Expert's free tier is 100. If a roomy free allowance is your priority, Fillout wins that line outright. Our paid tiers move up fast (Starter 1,000, Pro 10,000, Business 100,000 a month) on flat pricing, but we won't pretend the free numbers are even.
### Does Forms Expert have as many field types as Fillout?
No. Fillout advertises 50+ field types; Forms Expert has 35, with conditional logic and multi-step flows. For most lead, signup, and feedback forms that's plenty, but if you lean on a long tail of specialized inputs, Fillout covers more ground there.
### What about native Airtable, Notion, and CRM integrations?
This is Fillout's home turf. Its native CRM, Airtable, and Notion connections are deeper than ours, and that's the whole reason a lot of teams pick it. Forms Expert reaches those tools through the REST API and signed webhooks rather than pre-built native blocks. If wiring straight into Airtable or Notion with no code is the job, Fillout is the better fit.
### How do I move my forms off Fillout?
Rebuild the form in Forms Expert (35 field types, conditional logic), pick how it ships, then embed it with the published @forms.expert/sdk or POST to the REST endpoint with a pk_ key. Switch on the consent module, 30-language translation, and per-field analytics from the same dashboard. There's no automated Fillout importer, so plan to recreate each form once.
---
# Forms.app Alternative — AI & Triple Delivery From $9
Source: https://forms.expert/alternatives/forms-app-alternative
Forms.app is a polished, fairly priced builder with credible AI and a deep template library — we won't pretend otherwise. Forms Expert competes on price and reach: the same AI generation and editing come bundled from our first paid tier, and one form definition ships three ways, as a page, a widget, and a REST API.
## Forms Expert vs Forms.app, Feature by Feature
A side-by-side read, including the two rows where Forms.app genuinely wins. Competitor figures are approximate (2026) — check them before you rely on them.
## Where Forms Expert Pulls Ahead of Forms.app
The reasons teams move over from Forms.app, and what lands the day you switch.
- **Same AI, lower entry price** — AI building and editing are bundled into the Starter plan at $9, our first paid tier, rather than waiting for a higher one. Forms.app's AI is genuinely good; the difference is that you hit the same prompt-to-form workflow sooner, for less.
- **One definition, three channels** — The same form ships as a hosted page, an auto-resizing widget, and a REST endpoint with signed webhooks. Flip a type field — you never rebuild it per channel. Forms.app stays hosted-and-embed.
- **Consent in the box, translation when you grow** — The GDPR consent module ships with the product, and Forms.app doesn't offer one at all. Add 30-language DeepL translation on Business and deeper per-field analytics on Pro and up. One product, no separate vendor, no bolted-on add-on.
- **HIPAA-ready forms from $9** — A signed BAA and HIPAA-ready forms come with every paid plan from $9, not a separate enterprise contract. If your intake touches patient or client health data, the compliant path sits on the same flat pricing. Plainly: it's on the paid plans, not Free.
## How to Switch From Forms.app in Four Steps
There's no automated importer, so you recreate the form once. After that, it ships three ways from a single definition.
1. **Rebuild or generate the form** — Recreate your Forms.app form with 35 field types and conditional logic, or describe it to the AI and edit from there. Most forms take minutes.
2. **Choose how it ships** — Set the type field — hosted page, embed, API, or all three at once. One build covers every channel, so there's no separate version to maintain.
3. **Drop it into your product** — Install @forms.expert/sdk for React, Vue, or vanilla, or POST to the REST endpoint with a pk_ key. Wire signed webhooks for downstream events.
4. **Turn on the extras** — Enable the GDPR consent module, then add 30-language translation on Business and per-field analytics on Pro. A common slip is expecting translation at Starter — it's a Business feature.
## Coming From Forms.app
### How much does AI form building cost on Forms Expert?
AI generation and editing come bundled into the Starter plan at $9 a month, which is our first paid tier. Forms.app's AI is well-integrated and credible, and it also lives on a paid tier that starts around $15. So the gap here is the entry price, not the capability — you reach the same prompt-to-form workflow for less.
### Does Forms Expert have a real API and webhooks?
Yes. There's a REST endpoint with publishable (pk_) and secret (sk_) keys and signed webhooks that retry up to 5 times with exponential backoff. The same form also ships as a hosted page and an auto-resizing embed through the published @forms.expert/sdk for React, Vue, or vanilla JS, all set by one type field. Forms.app stays hosted-and-embed, without that API channel.
### Can I translate my Forms Expert forms into other languages?
Yes, with built-in DeepL translation across 30 languages and per-language publishing — but that lives on the $99 Business plan, not on the $9 Starter tier. If you just need AI building and triple delivery, Starter covers it. Multilingual forms step up to Business, where the GDPR consent module also helps you keep records straight across markets.
### What does Forms.app do better than Forms Expert?
Templates and breadth, plainly. Forms.app ships 5,000+ templates and built-in PDF generation, and it's a reliable, well-rounded builder with a longer track record. Our starter set is curated rather than vast. If a huge template library or native PDF output is central to your work, Forms.app is a fair, well-priced choice and we'd say so.
### How do I switch from Forms.app to Forms Expert?
Rebuild the form once in our builder (35 field types with conditional logic), or describe it to the AI and edit from there. Pick how it ships — hosted page, embed, API, or all at once — then drop in the SDK or point your backend at the REST endpoint. There's no automated Forms.app importer, so plan to recreate the form rather than migrate it.
---
# Formstack Alternative — Developer Delivery, 1/10 Cost
Source: https://forms.expert/alternatives/formstack-alternative
Formstack is an enterprise compliance platform, and a real one — native Salesforce, document generation, eSignature. If what you actually need is form delivery your code can drive, Forms Expert gives you the same HIPAA + signed BAA (on every paid plan) plus a REST API, signed webhooks, and a published SDK on flat $0–$99 pricing instead of $113–225 per user a month.
## Forms Expert vs Formstack, Where Each One Wins
An honest side-by-side, including the rows where Formstack is clearly ahead. Competitor details are approximate (2026) — verify Formstack's pricing and compliance before you rely on them.
## Where Forms Expert Pulls Ahead of Formstack
Why teams leave Formstack, and what flat, self-serve delivery gives them on day one.
- **Flat pricing instead of per-seat** — Formstack bills per user per month; we don't. $0 / $9 / $29 / $99 covers the whole account. For a small team that adopted Formstack mainly for its API, that's roughly a tenth of the spend.
- **Delivery your code can drive, self-serve** — A first-class REST API, signed webhooks that retry up to five times, and the published @forms.expert/sdk (React, Vue, vanilla). No demo call, no enterprise contract — the keys are in your dashboard the moment you sign up.
- **One definition, three channels** — The same form ships as a hosted page, an auto-resizing widget, and a REST endpoint — flip a type field, never rebuild it. Translation across 30 languages and a GDPR consent module ride along in the same product.
- **Analytics without a second tool** — A completion funnel, NPS, per-field stats, and geo and device breakdowns arrive on Pro and up, in the same product. The numbers that show where a form stalls sit next to the responses, not behind a paid add-on.
## Moving From Formstack in Four Steps
There's no automated importer, so you rebuild each form once. Worth saying up front: this covers data collection and delivery, not Formstack's document, eSignature, or Salesforce workflows.
1. **Rebuild the form** — Recreate your Formstack form with 35 field types, conditional logic, and multi-step flows. A straightforward intake form takes minutes; a long workflow form takes a bit longer.
2. **Choose how it ships** — Set the type field — hosted page, embed, API, or all three at once. One definition, no separate build per channel.
3. **Wire it into your stack** — Install @forms.expert/sdk for React, Vue, or vanilla, or POST to the REST endpoint with a pk_ key. Point signed webhooks at your backend, or at Zapier if you're routing into Salesforce yourself.
4. **Turn on the extras** — Enable the GDPR consent module, 30-language translation on Business, and per-field analytics on Pro, all from one dashboard. Just remember the eSign and document pieces stay with a separate tool.
## Switching From Formstack
### How much cheaper is Forms Expert than Formstack?
A lot, and the reason is the billing model. Formstack charges roughly $113 to $225 per user per month, plus modular add-ons for the documents and signature pieces. Forms Expert is flat: $0, $9, $29, or $99 a month for the whole account, not per seat. So a small team that's deep into a Formstack contract on the developer-API story is often looking at close to a tenth of the cost on us. Run your real seat count against our pricing before you assume.
### Does Forms Expert have HIPAA compliance or a BAA?
Yes — Forms Expert is HIPAA compliant and signs a BAA on any paid plan (Starter and up), not on Free. Formstack also offers real HIPAA and BAAs, but on its enterprise per-seat plans ($113–225/user/mo); you get the same compliance from our $9 Starter plan.
### Can Forms Expert connect to Salesforce like Formstack does?
Not natively. Formstack ships a native Salesforce integration; we don't. What you get instead is a real REST API and signed webhooks, so you (or a tool like Zapier) can push submissions into Salesforce yourself. That's more wiring on your end. If a turnkey, native Salesforce connector is the thing you're buying for, Formstack is the honest answer.
### Does Forms Expert do document generation and eSignature?
No. Document generation, eSignature, and audit trails are Formstack's territory, and Forms Expert offers none of them. We collect and deliver form data — as a hosted page, an embed, and an API — but we don't produce signed PDFs or merge documents. If your workflow ends in a countersigned contract, Formstack (or a dedicated eSign tool) is the right call, not us.
### Is the Forms Expert API self-serve, or do I have to talk to sales?
Self-serve. Sign up, generate a publishable (pk_) and secret (sk_) key, and you're posting to the REST endpoint the same afternoon — no demo call, no enterprise contract. Webhooks are signed and retry up to five times with exponential backoff. The same form definition also ships as a hosted page and an embed, switched with one type field. Formstack's developer story sits behind a sales-led, enterprise motion; ours is just there when you sign up.
### What do I give up by leaving Formstack?
Less than you'd think on compliance. HIPAA and BAAs you keep — Forms Expert is HIPAA compliant and signs a BAA on every paid plan. What you actually lose is the native Salesforce connector, document generation, eSignature, and audit trails — Forms Expert matches none of those four. You also trade a sales-led platform for a self-serve one. What you gain is flat $0–$99 pricing instead of per-seat fees, and developer-grade delivery (REST API, signed webhooks, the published SDK) without an enterprise contract.
### How do I migrate from Formstack to Forms Expert?
Rebuild the form in our builder (35 field types with conditional logic), pick how it ships — page, embed, API, or all three — then drop in the SDK or point your backend at the REST endpoint. Turn on the GDPR consent module and per-field analytics from the same dashboard. HIPAA and a signed BAA come standard on any paid plan, so health-data intake moves over too. There's no automated Formstack importer, so plan to recreate each form once. For the document, eSignature, and Salesforce workflows, you'll need a separate plan; we don't replace those.
---
# Google Forms Alternative — A Real API & Branded Embeds
Source: https://forms.expert/alternatives/google-forms-alternative
Google Forms is free, fast, and sitting in an account you already have. We're not here to argue with that. Forms Expert is for the moment Google runs out of room: a real REST API, an auto-resizing branded widget, deeper logic, consent, and analytics, from one form definition.
## Forms Expert vs Google Forms, Feature by Feature
A side-by-side read, including the rows where Google Forms genuinely wins. Competitor details are approximate (2026), so check them before you rely on them.
## Where Forms Expert Pulls Ahead of Google Forms
The reasons teams outgrow Google Forms, and what they gain the day they switch.
- **A real API, not Apps Script** — Forms Expert ships a first-class REST API with pk_/sk_ keys and signed webhooks that retry up to 5 times. Google Forms has no first-class form API, so anything headless or product-embedded means gluing together Apps Script and add-ons.
- **An embed that actually fits** — Drop the form into your site with the published @forms.expert/sdk (React, Vue, vanilla). It auto-resizes and wears your branding, unlike Google's fixed iframe that leaves dead space or an inner scrollbar.
- **Uploads without a sign-in wall** — Forms Expert accepts file uploads to S3 from anyone, no account required. Google Forms makes respondents log into Google before they can attach a file, which quietly loses you submissions on any public form.
- **Depth Google leaves out** — 35 field types and real conditional logic, plus a GDPR consent module and per-field, geo, and device analytics on Pro and up. See the analytics and the embed options in detail.
- **Real multilingual, not browser translate** — DeepL translation across 30 languages is built into the form on Business, published per language. Google Forms leaves it to the respondent's browser or a copy duplicated per language, so real multilingual means maintaining several. Here it's one form, many languages.
- **AI that drafts the form** — Type a prompt and get a full, editable form, then keep refining it by prompt on the paid plans. Google Forms has no AI builder, so each form still starts from the blank editor or an old copy. See the AI form builder for how prompt-to-form works.
## How to Switch From Google Forms in Four Steps
There's no automated importer, so you rebuild each form once. After that it ships three ways from a single definition.
1. **Rebuild the form** — Recreate your Google Form with 35 field types, multi-step flows, and conditional logic. Most simple forms take only a few minutes, and you'll likely add depth Google couldn't reach.
2. **Choose how it ships** — Set the type field to hosted page, embed, API, or all at once. No separate build per channel, which is exactly what Google's single hosted view can't give you.
3. **Embed or call it** — To embed a Google Form replacement on your site, install @forms.expert/sdk for React, Vue, or vanilla. Prefer code? POST to the REST endpoint with a pk_ key and wire signed webhooks.
4. **Turn on the extras** — Switch on the GDPR consent module and per-field analytics on Pro, and serve the page from your own domain via CNAME or TXT. Heads up: custom-domain SSL isn't automated yet, so handle certs yourself.
## Switching From Google Forms
### Does Forms Expert have a real API? Google Forms doesn't.
Yes, and this is the cleanest reason to switch. Forms Expert ships a first-class REST API with publishable (pk_) and secret (sk_) keys plus signed webhooks that retry up to 5 times with backoff. Google Forms has no first-class form API at all; you're stuck wiring Apps Script or third-party add-ons. If you need to create forms, read responses, or fire events from your own code, Google leaves you improvising and we don't.
### Can I embed a Google Form on my website with my own branding?
You can embed a Google Form, but only as a plain iframe that won't resize to its content, so it leaves dead space or an inner scrollbar and keeps Google's generic look. Forms Expert gives you an auto-resizing branded widget through the published @forms.expert/sdk (React, Vue, vanilla, plus a CDN build). It grows with the form and matches your site, no clunky frame.
### Are responses and file uploads anonymous, with no sign-in?
Forms Expert accepts file uploads (stored on S3) without forcing anyone to sign in, which matters a lot for public intake. Google Forms makes respondents log into a Google account before they can attach a file, and that single requirement quietly kills a chunk of your submissions. For text answers Google can be set not to collect emails too, but the upload wall is the real gap, and we don't have one.
### Is Forms Expert free like Google Forms?
Not in the same way, and I won't pretend otherwise. Google Forms is genuinely free with no submission caps, bundled into an account most people already have. Forms Expert has a free plan too, but it's capped at 100 submissions a month, and the paid tiers run $9, $29, and $99. If your only need is a quick, no-cost survey, Google wins on price. You're paying us for the API, branding, logic, consent, and analytics Google doesn't do.
### Does Forms Expert support conditional logic and more field types?
Yes. You get 35 field types with multi-step forms and real conditional logic that branches on any answer. Google Forms gives you roughly a dozen basic types and section-only branching that fires off multiple-choice or dropdown questions. For anything past a simple quiz or a one-page survey, Google's logic runs out of room fast.
### What will I give up by moving off Google Forms?
A few real things. You lose the genuinely free, uncapped pricing, the zero-signup reach of a tool everyone already has a login for, and the native real-time Sheets, Drive, and Docs integration that Google does better than anyone. Forms Expert exports and integrates, but it isn't living inside your spreadsheet the way Google is. If those three are what you care about most, stay on Google Forms with a clear conscience.
### Does Forms Expert give me branded pages and a custom domain?
Yes. Hosted Forms Expert pages carry your branding instead of Google's generic, hard-to-restyle look, and you can serve them from your own domain via CNAME or TXT verification. One honest caveat: we don't issue automated SSL certificates for custom domains yet, so plan your certs accordingly. Google Forms has no real branding or custom-domain story to begin with. Want the full setup? See our embeddable forms.
### How do I move my forms off Google Forms?
Rebuild the form in Forms Expert with the field types and logic you actually want, then pick how it ships: a hosted page, an embed, the API, or all three from one definition. Point your backend at the REST endpoint or drop in the SDK, switch on the consent module and analytics, and you're live. There's no automated Google Forms importer, so you recreate each form once. Weighing other tools too? The Microsoft Forms comparison covers the other big free default.
---
# Form Builder Comparisons — Forms Expert vs 11 Tools
Source: https://forms.expert/alternatives
Finding the best form builder means knowing what each tool gets right. How Forms Expert compares to eleven popular tools: flat pricing, triple delivery, consent, and a real API. Pick the head-to-head you need.
## Eleven Honest Comparisons
Each comparison names the genuine strengths on both sides — no invented weaknesses. Find the tool you are weighing and see exactly where each one wins.
- **Typeform** — Flat $0–$99 pricing and triple delivery — where Typeform leads on conversational survey UX. [See the comparison →](https://forms.expert/alternatives/typeform-alternative)
- **Jotform** — Role-based team access below an enterprise tier, plus a first-class REST API. [See the comparison →](https://forms.expert/alternatives/jotform-alternative)
- **Google Forms** — A real REST API and an auto-resizing branded embed, beyond a shared link. [See the comparison →](https://forms.expert/alternatives/google-forms-alternative)
- **Tally** — In-app AI generation, 30-language translation, and built-in analytics. [See the comparison →](https://forms.expert/alternatives/tally-alternative)
- **SurveyMonkey** — No per-response overage, and first-party multilingual built into the product. [See the comparison →](https://forms.expert/alternatives/surveymonkey-alternative)
- **Formstack** — Self-serve flat pricing and a REST API — without an enterprise per-seat contract. [See the comparison →](https://forms.expert/alternatives/formstack-alternative)
- **Fillout** — Built-in translation and a GDPR consent module, first-party — Fillout ships neither. [See the comparison →](https://forms.expert/alternatives/fillout-alternative)
- **Microsoft Forms** — Public, embeddable, API-driven forms for work that lives beyond Microsoft 365. [See the comparison →](https://forms.expert/alternatives/microsoft-forms-alternative)
- **Paperform** — An embed that actually auto-resizes, plus a genuine $0 plan. [See the comparison →](https://forms.expert/alternatives/paperform-alternative)
- **Forms.app** — AI generation and editing bundled from $9, plus triple delivery. [See the comparison →](https://forms.expert/alternatives/forms-app-alternative)
- **Cognito Forms** — Triple delivery, a real REST API, and AI plus 30-language translation. [See the comparison →](https://forms.expert/alternatives/cognito-forms-alternative)
---
# Jotform Alternative — Real Teams, Triple Delivery
Source: https://forms.expert/alternatives/jotform-alternative
Jotform is a deep, mature builder with a huge template library, and we're not going to pretend otherwise. Forms Expert competes on two specific things: role-based teams that don't need an enterprise contract, and a real REST API, with one definition that ships as a page, a widget, and an API.
## Forms Expert vs Jotform, Row by Row
A side-by-side read, including the rows where Jotform clearly wins. Competitor figures are approximate (2026) and pulled from public sources, so check them before you rely on them.
## Where Forms Expert Pulls Ahead of Jotform
The concrete reasons teams move off Jotform, and what changes the day you switch.
- **Real teams below enterprise** — Invite teammates with owner, admin, editor, and viewer roles on the standard paid plans. Jotform walls real multi-user access behind a quote-only Enterprise tier, so growing teams get stuck on a single seat.
- **One definition, three channels** — The same form ships as a hosted page, an auto-resizing embed widget, and a REST endpoint with signed webhooks. Set a type field and you never rebuild it per channel.
- **Consent and analytics in the box** — A GDPR consent module lives inside the form, and a completion funnel, NPS, and per-field stats arrive with deeper analytics on Pro and up. One product, no separate vendor or paid add-on.
- **HIPAA without the enterprise tier** — A signed BAA and HIPAA-ready forms ship on every paid plan from $9. Jotform reserves HIPAA for its Gold and Enterprise tiers, so the same compliance costs more there. It's on the paid plans, not Free.
## How to Switch From Jotform in Four Steps
There's no automated importer, so you rebuild each form once. After that, it ships three ways from a single definition.
1. **Rebuild the form** — Recreate your Jotform with 35 field types, conditional logic, and multi-step flows. Most forms come together in a few minutes.
2. **Choose how it ships** — Set the type field to hosted page, embed, API, or all three at once. One build covers every channel, so skip this and you'll be rebuilding later.
3. **Bring your team in** — Add teammates as owner, admin, editor, or viewer on a paid plan. No enterprise quote, no waiting on a sales rep to unlock seats.
4. **Drop it into your product** — Install @forms.expert/sdk for React, Vue, or vanilla, or POST to the REST endpoint with a pk_ key. Wire signed webhooks, then turn on consent and analytics from the same dashboard.
## Switching From Jotform
### Is Forms Expert cheaper than Jotform?
Often, yes, but the bigger difference is what each tier counts. Forms Expert is flat: $0, $9, $29, $99 a month, with stated submission limits of 100, 1,000, 10,000, and 100,000. Jotform caps hard per tier (100 free, 1,000 Bronze, 2,500 Silver), which is its most-repeated complaint and the thing that pushes people to upgrade early. You won't hit a forced jump with us.
### Is Jotform free, and how does the Forms Expert free tier compare?
Jotform has a free plan, capped at 100 submissions a month plus limits on forms and storage. Our free tier is also 100 submissions a month, and it ships the parts we care about: the hosted page, the embed widget, and the REST API. So the free comparison isn't really about the cap. It's that a Forms Expert free form can already live in your product and your code, not just behind a hosted link.
### Do I need an enterprise plan to add my team?
No. Owner, admin, editor, and viewer roles come with the standard paid plans. Jotform reserves real multi-user, role-based access for its custom-priced Enterprise tier, which is a hard single-user wall that growing teams hit fast. You get teammates with the right permissions without a sales call or a quote.
### Does Forms Expert have a real API and webhooks for developers?
Yes. There's a first-class REST endpoint with publishable (pk_) and secret (sk_) keys and signed webhooks that retry up to 5 times with exponential backoff. Jotform has a REST API and SDKs too, so this isn't us having one and them not. The difference is that the same form definition ships as a hosted page, an embed, and an API from one type field, instead of treating deep API use as a developer add-on.
### Is Forms Expert safe and secure for collecting data?
Submissions move over HTTPS, file uploads land in S3, webhooks are signed so you can verify they came from us, and a built-in GDPR consent module records what each respondent agreed to. On the compliance side, Forms Expert is HIPAA compliant and signs a BAA on any paid plan (Starter and up), not on Free. Jotform reserves HIPAA for its Gold and Enterprise plans, so ours is available much earlier.
### Can Forms Expert collect payments like Jotform?
Not the way Jotform does. Payments through 30-plus gateways, PDF generation, e-signatures, and approval workflows are genuine Jotform strengths, and we don't match them. Forms Expert is built around the delivery wedge: one form as a page, a widget, and an API. If a checkout or a signed PDF is the point of your form, Jotform is the better tool.
### What will I give up by switching from Jotform?
The big ones: Jotform's 10,000-plus templates and 600-plus widgets, its payment gateways, PDF and e-sign workflows, AI Agents, and broader integrations. Jotform also advertises 130-plus respondent languages against our built-in 30 on the Business plan. If template breadth or those built-in workflows are central, Jotform stays the safer pick.
### How do I move my forms off Jotform?
Rebuild the form in Forms Expert with 35 field types and conditional logic, then pick how it ships: hosted page, embed, API, or all at once. Drop in @forms.expert/sdk for React, Vue, or vanilla, or point your backend at the REST endpoint. Turn on consent and analytics from the same dashboard. There's no automated Jotform importer, so plan to recreate each form once.
---
# Microsoft Forms Alternative — A Real API & Branding
Source: https://forms.expert/alternatives/microsoft-forms-alternative
Microsoft Forms is great for a quick internal poll or quiz inside Microsoft 365, and we won't pretend otherwise. Forms Expert competes on the outside: fully branded, public forms from one definition that ships as a hosted page, an embeddable widget, and a real REST API.
## Forms Expert vs Microsoft Forms, Row by Row
A side-by-side read, including the rows where Microsoft Forms genuinely wins. Competitor details are approximate (2026) — check them before you rely on them.
## Where Forms Expert Pulls Ahead of Microsoft Forms
The reasons teams reach past M365 Forms for public, branded work, and what they gain.
- **A real API and signed webhooks** — Microsoft Forms has no native API and no webhooks, so wiring it into anything usually means Power Automate or a manual export. Forms Expert gives you a REST endpoint with publishable (pk_) and secret (sk_) keys and signed webhooks that retry up to 5 times, so responses land in your own systems on their own.
- **Branding, embedding, no ~200-response wall** — Build fully branded public forms and drop them anywhere with the auto-resizing embed via @forms.expert/sdk (React, Vue, vanilla). Flat pricing runs 100 submissions on Free, then 1,000 / 10,000 / 100,000 — no ~200-response cap mid-campaign. Per-field and funnel analytics arrive on Pro and up.
- **Microsoft Forms vs Google Forms, and where we fit** — Searching "Microsoft Forms vs Google Forms" usually means you want a public, shareable form. Here's the catch: both are built for their own ecosystem, neither ships a first-class API, and both embed through a plain non-resizing iframe. Microsoft wins internal M365 work; Google wins zero-signup reach. For branded, embedded, API-driven forms, that's our lane — and we break down the Google side on our Google Forms alternative page.
- **Analytics past a summary chart** — Microsoft Forms gives you a response summary and a spreadsheet, fine for a quick internal poll. For forms that drive a funnel, Forms Expert adds per-field completion stats, an NPS view, drop-off analysis, and geo and device breakdowns on Pro and up. You see which question loses people and on what device, then fix it — a read a summary chart and an Excel export can't give you on a public, higher-volume form.
## How to Move From Microsoft Forms in Four Steps
There's no automated importer, so you rebuild the form once — then it ships three ways from a single definition.
1. **Rebuild the form** — Recreate your Microsoft Forms survey or quiz in the builder with 35 field types, conditional logic, and multi-step flows. Most forms take only a few minutes.
2. **Choose how it ships** — Set the type field — hosted page, embed, API, or all three at once. One definition, no separate build per channel.
3. **Wire it into your stack** — This is the part M365 Forms can't do. Install @forms.expert/sdk for React, Vue, or vanilla, or POST to the REST endpoint with a pk_ key, then point signed webhooks at your downstream systems.
4. **Turn on consent and analytics** — Switch on the GDPR consent module, and on Pro and up, per-field and funnel analytics — all from the same dashboard. A common slip: leaving consent off on a public form, so set it before you share the link.
## Moving Beyond Microsoft Forms
### Does Microsoft Forms have an API?
No. Microsoft Forms has no native API and no webhooks, so anything programmatic usually routes through Power Automate or a manual Excel export. Forms Expert is the opposite: a first-class REST endpoint with publishable (pk_) and secret (sk_) keys and signed webhooks that retry up to 5 times with exponential backoff. If you need form data flowing into your own systems automatically, that's the wedge.
### Microsoft Forms vs Google Forms — which is better for public forms?
For public, embedded, or developer-facing work, neither is a great fit, and they fall short for the same reasons: no first-class API, generic branding, and a plain non-resizing iframe. Microsoft Forms is the better internal pick if you live in M365; Google Forms wins on zero-signup reach. If the form has to be branded, embedded, and wired into your stack, that's where Forms Expert comes in. We wrote up the Google side separately on our Google Forms alternative page.
### Can I brand a form and embed it on my own website?
Yes. Microsoft Forms gives you minimal branding and a basic iframe. Forms Expert ships fully branded public forms, and the same definition renders as an auto-resizing embed through @forms.expert/sdk (React, Vue, or vanilla JS) plus a hosted page on its own URL. Respondents never need a Microsoft 365 login to open it.
### Will I hit a ~200-response cap like Microsoft Forms?
No. The Microsoft Forms free tier caps at around 200 responses, which is easy to hit on a public form. Forms Expert is flat-priced with stated monthly limits — 100 on Free, then 1,000, 10,000, and 100,000 on Business. No cliff drops on you halfway through a collection.
### Is Forms Expert free like Microsoft Forms?
Not in the same way, and that's a fair concession. Microsoft Forms is genuinely free if you already pay for Microsoft 365. Forms Expert has a free plan too, but it's capped at 100 submissions a month, then paid tiers run $9, $29, and $99. You're paying for the API, branding, embedding, and higher limits — not a copy of the M365 polling tool.
### Does Forms Expert connect to Excel, Teams, and SharePoint?
Not natively. This is where Microsoft Forms is plainly stronger: its native Excel, Teams, and SharePoint links are excellent for internal surveys and quizzes, and we don't match that. Forms Expert reaches your tools through the REST API, signed webhooks, and data export instead. For work that stays inside Microsoft 365, Microsoft Forms is the better tool.
### How do I switch from Microsoft Forms to Forms Expert?
Rebuild the form in the builder (35 field types with conditional logic and multi-step flows), pick how it ships, then either drop in the SDK or point your backend at the REST endpoint. Turn on GDPR consent and, on Pro and up, per-field analytics from the same dashboard. There's no automated importer, so you recreate the form once — most are quick.
---
# Paperform Alternative — Embeds That Auto-Resize
Source: https://forms.expert/alternatives/paperform-alternative
Paperform builds gorgeous document-style forms that read like a landing page, and that's a real strength. Forms Expert plays a tighter game: an embed that auto-resizes as the form grows, a genuine $0 plan instead of a trial, and one definition that ships as a page, a widget, and an API.
## Forms Expert vs Paperform, Row by Row
A side-by-side read, including the two rows where Paperform genuinely wins. Competitor details are approximate (2026), so check them before you rely on them.
## Where Forms Expert Pulls Ahead of Paperform
The practical reasons teams move off Paperform, and what changes the day you switch.
- **Embeds that auto-resize** — The @forms.expert/sdk widget grows and shrinks with the form, so a long or multi-page form sits cleanly inside your page. Paperform's iframe can't do that, and the scrollbars show. See how the embeddable widget handles it.
- **A real free tier, not a countdown** — Start at $0 with 100 submissions a month and stay there. Paperform gives you a trial, then asks for ~$24–29+. Our pricing is flat at $0/$9/$29/$99 with stated monthly limits and no per-response cliff.
- **One definition, three channels** — Write the form once. A single type field ships it as a hosted page, an auto-resizing widget, and a REST endpoint with signed webhooks, no rebuild per channel. Paperform's API is limited, so headless use cases stall.
- **HIPAA-ready from $9** — A signed BAA and HIPAA-ready forms ship on every paid plan from $9, so patient or client intake has a compliant home. Paperform isn't built around HIPAA, so for regulated work this is a real gap we close. One caveat: it's on the paid plans, not the Free one.
## How to Switch From Paperform in Four Steps
There's no automated importer, so you rebuild each form once. After that, one definition feeds the page, the embed, and the API.
1. **Rebuild the form** — Recreate your Paperform in the builder with 35 field types, conditional logic, and multi-step flows. Short forms take only a few minutes.
2. **Choose how it ships** — Set the type field to hosted page, embed, API, or all three at once. One build covers every channel, unlike maintaining a separate embed.
3. **Drop it into your page** — Add the @forms.expert/sdk widget for React, Vue, or vanilla, and it auto-resizes inside your layout. Prefer code? POST to the REST endpoint with a pk_ key and wire signed webhooks.
4. **Turn on the extras** — Switch on the GDPR consent module, 30-language translation on Business, and per-field analytics on Pro from the same dashboard. A quick heads-up: translation lives on the Business plan, not the entry tier.
## Coming From Paperform
### Does the Forms Expert embed resize automatically?
Yes. The widget grows and shrinks with the form, so adding a page or tripping a long validation message never leaves you with an inner scrollbar or a clipped field. Paperform's iframe embed doesn't auto-resize that way, which gets awkward on long or multi-page forms sitting inside your own page. That single behavior is the main reason people land on this comparison.
### Is there a real free plan, or just a trial like Paperform?
A real Free plan at $0, no card, with 100 submissions a month. Paperform is trial-only, then roughly $24 to $29 and up once the trial ends. Our paid tiers stay flat at $9, $29, and $99 with stated monthly limits, so the price you pick is the price you pay.
### Can one Forms Expert form be a page, an embed, and an API at once?
Yes, and that's the part Paperform doesn't do. You write the form once, then a single type field decides whether it ships as a hosted page, an embedded widget, a REST endpoint, or all of them together. Paperform covers the hosted page and the embed well; its API is limited, so headless or product-embedded use cases run into a wall.
### Does Forms Expert match Paperform on design and custom CSS?
Not fully, and I'd rather say so. Paperform's design freedom runs deeper. Its document-style canvas with custom HTML and CSS is built for forms that read like a polished landing page, and it supports multiple custom domains. Forms Expert gives you theming and custom CSS on Pro, which covers most brand needs, but if pixel-level page design is the whole point, Paperform stays ahead.
### Can I put a Forms Expert form on my own domain?
You can connect a custom domain through CNAME or TXT verification. Be clear on the limit, though: we don't issue the SSL certificate for you automatically, and Paperform supports more custom domains than we do. If running many branded domains matters, that's a point for Paperform.
### How do I move my forms off Paperform?
Rebuild the form in our builder using 35 field types with conditional logic, pick how it ships, then drop in the @forms.expert/sdk widget or point your backend at the REST endpoint. There's no automated importer, so you recreate each form once. After that it's a single definition feeding the page, the embed, and the API, so you're not maintaining three versions.
---
# SurveyMonkey Alternative — No Per-Response Overage
Source: https://forms.expert/alternatives/surveymonkey-alternative
SurveyMonkey is the survey brand people know, with real research depth, and we're not pretending otherwise. Forms Expert plays a different game: flat pricing with no per-response overage, multilingual built into the product, and one form definition that ships as a hosted page, an embed, and a REST API.
## Forms Expert vs SurveyMonkey, Row by Row
A side-by-side read, including the rows where SurveyMonkey genuinely wins. Competitor details are approximate (2026) — check them before you rely on them.
## Where Forms Expert Pulls Ahead of SurveyMonkey
The concrete reasons teams move off SurveyMonkey, and what changes once you switch.
- **No per-response overage** — Pricing is flat: $0 / $9 / $29 / $99 with stated submission limits from 100 to 100,000 a month. SurveyMonkey's metered plans tack on roughly $0.15 a response past the cap. Here, a survey that goes viral doesn't end the month with a surprise bill.
- **Multilingual without a second vendor** — DeepL translation across 30 languages is built into the product on the Business plan, with per-language publishing. It's first-party and in the product, not a translation service you bolt on. Worth being clear: this lives on Business, not on every tier.
- **One definition, three channels** — The same survey ships as a hosted page, an auto-resizing embed, and a REST endpoint with signed webhooks. Flip a type field instead of rebuilding it. A built-in GDPR consent module rides along, so consent lives in the form rather than a separate tool.
- **HIPAA-ready intake from $9** — A signed BAA comes with every paid plan from $9, so patient, client, or research intake has a compliant home. SurveyMonkey keeps HIPAA on its higher tiers, where the bill climbs well past that. Worth stating: it's on the paid plans here, not the Free one, and a template isn't medical certification.
## How to Switch From SurveyMonkey in Four Steps
There's no automated importer, so you rebuild each survey once — then it ships three ways from a single definition.
1. **Rebuild the survey** — Recreate your SurveyMonkey survey in the builder with 35 field types, conditional logic, and multi-step flows. Most surveys take minutes, not an afternoon.
2. **Choose how it ships** — Set the type field — hosted page, embed, API, or all three at once. One survey, no separate build per channel.
3. **Drop it where it's needed** — Install @forms.expert/sdk for React, Vue, or vanilla, or POST to the REST endpoint with a pk_ key. Skip this step if you're only running a hosted survey link.
4. **Turn on the extras** — Switch on the GDPR consent module, 30-language translation on Business, and per-field analytics on Pro — all from one dashboard. Anonymous collection works out of the box.
## Switching From SurveyMonkey
### Is there a per-response charge on Forms Expert?
No. There's no per-response overage at all. Pricing is flat — $0, $9, $29, $99 a month — with stated submission limits of 100, 1,000, 10,000, and 100,000. SurveyMonkey's metered plans add roughly $0.15 per response once you pass the cap, so a survey that suddenly takes off can quietly run up your bill. With us, a spike just means more responses, not a surprise invoice.
### Are responses anonymous, the way SurveyMonkey surveys can be?
Yes. Both tools support anonymous responses, so this isn't where they differ. You can collect submissions without asking respondents to sign in or identify themselves, and you decide what to capture. If anonymity is the whole reason you're shopping, either product covers it — the real gap is pricing and feature gating, not whether a survey can stay anonymous.
### Is Forms Expert free, and is it more usable than SurveyMonkey's free plan?
There's a free tier — 100 submissions a month with a fuller set of features. SurveyMonkey's free plan caps each survey at around 10 questions and 40 responses, which runs out fast for anything real. So yes, free exists on both sides; ours just lets you build something closer to a finished survey before you have to pay.
### Can I run multilingual surveys without paying a separate translation vendor?
Yes, on the $99 Business plan. DeepL translation across 30 languages is built in, with per-language publishing, so it's first-party and lives inside the product rather than a tool you wire up on the side. SurveyMonkey gates multilingual surveys to its higher tiers too. The honest framing: this is a Business-plan feature on our end, not something included on every tier. More on form translation.
### Can I embed a survey or pull responses through an API?
Yes. The same form ships as an embed through @forms.expert/sdk (React, Vue, vanilla JS) or a raw iframe, and as a REST endpoint with publishable (pk_) and secret (sk_) keys plus signed webhooks that retry up to 5 times. One type field controls how it ships — you don't rebuild per channel. SurveyMonkey is survey-centric with a thin embed and API story, so this is a real wedge if the survey has to live inside your product or your code.
### Is Forms Expert HIPAA compliant like SurveyMonkey?
Yes — Forms Expert is HIPAA compliant and signs a BAA on any paid plan (Starter and up); it isn't offered on the Free plan. SurveyMonkey offers HIPAA only on higher-tier plans, so ours is available earlier and on flat pricing.
### What will I give up by switching from SurveyMonkey?
Honestly, two things: brand trust and survey-research depth. SurveyMonkey is the name people recognize, and its question bank plus research-grade analytics go deeper than ours for serious methodology work. If validated survey design is your core job, that's a fair reason to stay. If predictable pricing, in-product translation, and embed-plus-API are what you're after, that's our lane.
### How do I move my surveys off SurveyMonkey?
Rebuild the survey in Forms Expert with 35 field types and conditional logic, pick how it ships — hosted page, embed, API, or all at once — then drop in the SDK or point your backend at the REST endpoint. Turn on the consent module, translation, and analytics from the same dashboard. There's no automated SurveyMonkey importer, so plan to recreate each survey once.
---
# Tally Alternative — Native AI & In-Product Translation
Source: https://forms.expert/alternatives/tally-alternative
Tally's free tier is hard to beat, and we won't pretend otherwise. Forms Expert plays a different angle: AI form generation and editing you run in-product, content translation across 30 languages, and a consent module in the form — with the same definition shipping as a page, an embed, and an API.
## Forms Expert vs Tally, Feature by Feature
A straight side-by-side, including the rows where Tally wins outright. Competitor details are approximate (2026) — check them before you rely on them.
## Where Forms Expert Pulls Ahead of Tally
The reasons teams move off Tally, and what lands the day they switch.
- **AI that lives in the builder** — Type a prompt, get a full editable form, then keep refining with AI without leaving the tool. Tally's AI runs through an external MCP server. See the AI form builder for how in-product generation works.
- **Translate the form, not just the chrome** — Built-in DeepL translation of your form content across 30 languages on Business, with per-language publishing — no Weglot bolt-on. Details on the form translation page.
- **Consent and analytics in the box** — A GDPR consent module sits in the form, and per-field stats, NPS, geo, and a completion funnel land on Pro. Tally is privacy-friendly already; this adds the consent record and the deeper numbers without a second tool.
- **One definition, three channels** — The same form ships as a hosted page, an auto-resizing widget, and a REST endpoint with signed webhooks — flip a type field, never rebuild it. Tally has an API too; here it's the frame, not an add-on.
- **HIPAA-ready from $9** — A signed BAA and HIPAA-ready forms ship on every paid plan from $9, so patient, client, or HR intake has a compliant home — the kind of regulated coverage a lean indie builder like Tally doesn't take on. It's on the paid plans, not Free.
- **Roles for a real team** — Invite teammates as owner, admin, editor, or viewer on the paid plans, each with the access their role needs. Tally keeps collaboration lighter, so for a team that needs real permission levels on shared forms, the structure is here.
## How to Switch From Tally in Four Steps
There's no automated importer, so you rebuild the form once — then it ships three ways from a single definition.
1. **Rebuild the form** — Recreate your Tally form in the builder with 35 field types, conditional logic, and multi-step flows. Most forms take only a few minutes.
2. **Generate or edit with AI** — Stuck on structure? Describe the form in plain English and let AI draft it, then tweak fields with AI in the same screen. A quick prompt often beats rebuilding by hand.
3. **Choose how it ships** — Set the type field — hosted page, embed, API, or all three at once. Drop in @forms.expert/sdk for React, Vue, or vanilla, or POST to the REST endpoint.
4. **Turn on the extras** — Enable the GDPR consent module, 30-language translation on Business, and per-field analytics on Pro — all from the same dashboard.
## Switching From Tally
### Does Forms Expert have AI form generation built in?
Yes, and that's the main reason teams move. You type a plain-English prompt and get a full, editable form back, then keep editing with AI right inside the builder (Claude, on paid plans). Tally's AI lives outside the tool — you drive a Tally MCP server from Claude, ChatGPT, or Cursor. There's no built-in prompt-to-form generator in Tally itself. If you want AI in the product instead of a separate window, that's the difference.
### Can I run a multilingual form without Weglot?
Yes. Forms Expert ships built-in DeepL translation of the form content across 30 languages, on the $99 Business plan, with per-language publishing. Tally translates its default UI text into 50+ languages, but full multilingual content usually means wiring in third-party Weglot on its Pro plan. So both can go multilingual — ours just doesn't hand the content layer to another vendor.
### Is Tally's free plan better than Forms Expert's?
On raw generosity, yes — and we'll say so plainly. Tally gives you unlimited forms and unlimited submissions for free (fair use), with logic, uploads, and payments at $0. Forms Expert's free tier caps you at 100 submissions a month. If a no-cost, no-limit form is all you need, Tally is the better free deal. We make our case on what's in the paid product: native in-app AI, content translation, a consent module, and the API.
### Does Tally have an API, or only Forms Expert?
Tally has a real REST API and webhooks, free even on the free plan — anyone telling you otherwise is wrong. Our edge isn't having an API; it's how the form ships. One Forms Expert definition goes out at once as a hosted page, an auto-resizing embed, and a REST endpoint, set by a single type field, with signed webhooks that retry up to 5 times. It's triple delivery as the frame of the product, not an API tacked onto a hosted-first tool.
### Does Forms Expert include consent and analytics?
Yes. There's a GDPR consent module built into the form — categories, consent records, and Google Consent Mode — plus per-field stats, NPS, geo, device, and a completion funnel on Pro and up. Tally is genuinely privacy-friendly (EU-hosted, no cookie tracking), so this isn't about Tally ignoring privacy. The difference is the consent module living in the form, and analytics that don't lean on a separate tool.
### How do I switch from Tally to Forms Expert?
Rebuild the form in Forms Expert (35 field types, conditional logic, multi-step), pick how it ships, then drop in the SDK or point your backend at the REST endpoint. Turn on consent, translation, and analytics from the same dashboard. There's no automated Tally importer, so you'll recreate the form once — most take only a few minutes.
---
# Typeform Alternative — Flat Pricing, Triple Delivery
Source: https://forms.expert/alternatives/typeform-alternative
Typeform owns the conversational survey, and we're not pretending otherwise. Forms Expert plays a different game: one form definition that ships three ways, with consent and analytics in the box, on flat $0–$99 pricing and no per-response cliff.
## Forms Expert vs Typeform, Feature by Feature
A side-by-side read, including the rows where Typeform genuinely wins. Competitor details are approximate (2026) — check them before you rely on them.
## Where Forms Expert Pulls Ahead of Typeform
The reasons teams move off Typeform, and what changes the day they switch.
- **Flat pricing, no per-response cliff** — $0 / $9 / $29 / $99 with stated submission limits, 100 to 100,000 a month. No surprise overage when a campaign takes off and the responses spike.
- **One definition, three channels** — The same form ships as a hosted page, an auto-resizing widget, and a REST endpoint with signed webhooks — flip a type field, never rebuild it.
- **Consent and analytics in the box** — A GDPR consent module and per-field analytics live in one product, not a separate vendor or paid add-on. The completion funnel, NPS, and per-field stats land on Pro and up.
- **Built for your code** — Embed with the published @forms.expert/sdk (React, Vue, vanilla) or call the API directly. The form lives inside your product, not behind a shared link.
- **HIPAA from $9, not enterprise** — A signed BAA ships from the $9 plan. Typeform keeps HIPAA on its enterprise tier, so regulated intake starts far cheaper here. It's on the paid plans, not Free.
- **Roles without an enterprise plan** — Owner, admin, editor, and viewer roles come on the standard paid plans. Typeform pushes granular access and SSO toward enterprise, so a small team gets real permissions sooner.
## How to Switch From Typeform in Four Steps
There's no automated importer, so you rebuild the form once — then it ships three ways from a single definition.
1. **Rebuild the form** — Recreate your Typeform in the builder with 35 field types, conditional logic, and multi-step flows. Most forms take minutes.
2. **Choose how it ships** — Set the type field — hosted page, embed, API, or all three at once. No separate build per channel.
3. **Drop it into your product** — Install @forms.expert/sdk for React, Vue, or vanilla, or POST to the REST endpoint with a pk_ key. Wire signed webhooks for downstream events.
4. **Turn on the extras** — Enable the GDPR consent module, 30-language translation on Business, and per-field analytics on Pro — all from the same dashboard.
## Switching From Typeform
### Is Forms Expert cheaper than Typeform?
It depends on your volume, but the pricing model is the real difference. Forms Expert is flat — $0, $9, $29, $99 a month, with stated submission limits (100 to 100,000). Typeform meters by volume and counts partial completions, which is what pushes heavy users toward its $199+ Growth tiers. You won't get a spike-driven overage bill from us.
### Can I embed a Forms Expert form the way I embed Typeform?
Yes. The recommended path is our published SDK, @forms.expert/sdk, with React, Vue, and vanilla-JS bindings from npm or a CDN. It renders the form inline and exposes theme, language, and onSuccess/onError callbacks. Prefer no dependency? The raw iframe embed (/e/{slug}) auto-resizes too. Both products ship a React SDK, so embedding is at parity.
### Does Forms Expert have a real API and webhooks?
Yes — a first-class REST endpoint with publishable (pk_) and secret (sk_) keys and signed webhooks that retry up to 5 times with exponential backoff. The same form definition also ships as a hosted page and an embed, set by one type field. Typeform has an API, but it's bolted onto a hosted-first product rather than the frame of it.
### Is Forms Expert HIPAA compliant like Typeform?
Yes — Forms Expert is HIPAA compliant and will sign a BAA on any paid plan (Starter and up); it isn't offered on the Free plan. Typeform reserves HIPAA for its enterprise tier, so with us HIPAA is available far earlier, from $9. If you're collecting protected health information, sign the BAA, stay off Free, and you're covered on the same flat pricing as everything else.
### What will I give up by switching from Typeform?
Honestly: Typeform's polished one-question-at-a-time conversational flow and its documented completion-rate lift, its broader AI and enrichment layer, a larger template gallery, and enterprise trust like SSO and a dedicated CSM. HIPAA isn't one of them — we're HIPAA compliant and sign a BAA from $9, earlier than Typeform's enterprise-only HIPAA. If a brand-led survey experience is the whole point, Typeform is a fair choice. If the form has to live inside your product and your code on predictable pricing, that's our lane.
### Can Forms Expert handle multiple languages?
Yes, with built-in DeepL translation across 30 languages and per-language publishing — on the $99 Business plan. Typeform also gates multi-language to its Business tier. So it's roughly even on availability; the difference is that ours is first-party and in the product, with a GDPR consent module included rather than handed to a separate vendor.
### How do I move my forms off Typeform?
Rebuild the form in Forms Expert (35 field types with conditional logic), choose how it ships — hosted page, embed, API, or all at once — then drop in the SDK or point your backend at the REST endpoint. Turn on consent, translation, and analytics from the same dashboard. There's no automated Typeform importer, so plan to recreate the form once.
---
# Blog — Forms Expert
Source: https://forms.expert/blog
## Articles
- [How to Write Good Survey Questions (40+ Examples and Rules)](https://forms.expert/md/en/blog/good-survey-questions.md): Good survey questions explained: 5 rules for clear, unbiased wording plus 40+ examples by use case, and the bad questions to avoid.
- [Types of Survey Questions: 12 Formats and When to Use Each](https://forms.expert/md/en/blog/survey-question-types.md): Types of survey questions explained: 12 formats from multiple choice to Likert, ranking, and open-ended, with an example and when to use each.
- [How to Build a Multilingual Form (Methods, Pitfalls, and Examples)](https://forms.expert/md/en/blog/multilingual-forms.md): What a multilingual form is, the four ways to build one, how to translate a Google Form, and the encoding and RTL pitfalls to avoid.
- [Translate a Form Into 30 Languages Without a Separate Vendor](https://forms.expert/md/en/blog/translate-a-form-into-30-languages.md): A multilingual form builder with one-click DeepL translation into 30 languages, per-language publish control, and an optional public language switcher. Business plan.
- [File Upload Forms: How to Let People Send You Files (2026 Guide)](https://forms.expert/md/en/blog/file-upload-forms.md): How to make a file upload form: how the file field works, the Google Forms and WordPress routes, file-type and size limits, and security explained.
- [Save and Continue Forms: Let Respondents Finish Later (2026 Guide)](https://forms.expert/md/en/blog/save-and-continue-forms.md): What a save and continue form is, why it cuts abandonment on long forms, how saving progress works, and how to add it with a return link.
- [Multi-Step Forms: How to Build Them and Why They Convert (2026)](https://forms.expert/md/en/blog/multi-step-forms.md): What a multi-step form is, why splitting a long form lifts completion, how to build one (no-code or in code), best practices, and real examples.
- [Conditional Logic and Multi-Step Forms, Explained](https://forms.expert/md/en/blog/conditional-logic-and-multi-step-forms.md): How multi-step layouts, branching form logic, and save-and-continue drafts work in Forms Expert — plus practical UX guidance for building forms people finish.
- [How to Create a Consent Form (Required Elements and How to Build One)](https://forms.expert/md/en/blog/how-to-create-a-consent-form.md): How to create a consent form: the required elements a valid one needs, the types, a 5-step digital build, and how it stores a timestamped record.
- [Client Intake Form: What to Include and How to Build One](https://forms.expert/md/en/blog/client-intake-form-guide.md): Client intake form guide: what to include, fields by profession, a 5-step build, best practices, and a free intake template to start from.
- [How to Create a Job Application Form (Fields, Steps, and a Free Template)](https://forms.expert/md/en/blog/how-to-create-a-job-application-form.md): How to create a job application form: the fields to include, a 5-step build with resume upload, what you legally can't ask, and a free template.
- [How to Create an Order Form (Fields, Steps, and a Free Template)](https://forms.expert/md/en/blog/how-to-create-an-order-form.md): How to create an order form: the fields to include, a 5-step build, how to route orders, the honest truth on payments, and a free template.
- [How to Make a Feedback Form (Questions, Steps, and a Free Template)](https://forms.expert/md/en/blog/how-to-make-a-feedback-form.md): How to make a feedback form: the questions to ask, a 4-step build, rating scales, response routing, and a free template to start from.
- [How to Make a Registration Form (Fields, Steps, and a Free Template)](https://forms.expert/md/en/blog/how-to-make-a-registration-form.md): How to make a registration form: the fields to include, a 5-step build, no-account uploads, capping sign-ups, and a free event template.
- [Generating a Form From a Prompt With Claude](https://forms.expert/md/en/blog/generate-a-form-from-a-prompt-with-claude.md): Describe a form in plain English and Forms Expert drafts an editable form with Claude. AI Edit reworks it by instruction. Paid, bundled from the $9 Starter tier.
- [How to Create a Form With AI (From a Plain-English Prompt)](https://forms.expert/md/en/blog/create-a-form-with-ai.md): How to create a form with AI in five steps: open a generator, write a good prompt, generate, review, and edit. With a copyable prompt example.
- [AI Form Builder: How AI Generates an Editable Form From a Prompt](https://forms.expert/md/en/blog/ai-form-builder.md): What an AI form builder is, how prompt-to-form works step by step, how to write a good prompt, editing the draft, and what AI generation costs.
- [One Form, Three Channels: How the type Field Works](https://forms.expert/md/en/blog/one-form-three-channels.md): A single type field ships a form as a hosted page, an embeddable widget, or both — and every published form is also a REST endpoint.
- [Why We Don't Bill Per Response (and What "No Per-Response Cliff" Means)](https://forms.expert/md/en/blog/why-we-dont-bill-per-response.md): Forms Expert uses flat pricing — $0/$9/$29/$99 with stated monthly submission limits. Hit the cap and you're prompted to upgrade, not hit with a surprise overage.
- [The Best Survey Tools in 2026 (Free and Paid, Compared)](https://forms.expert/md/en/blog/best-survey-tools.md): The best survey tools compared: a fair shortlist with each tool's best-for, free plan, standout, and price, plus the best pick by survey type.
- [Typeform vs Google Forms: A Neutral, Side-by-Side Comparison (2026)](https://forms.expert/md/en/blog/typeform-vs-google-forms.md): Typeform vs Google Forms compared dimension by dimension — price, design, embedding, API, and analytics — with a clear verdict on which to choose.
- [Best Online Form Builder in 2026: How to Choose (Buyer's Guide)](https://forms.expert/md/en/blog/best-online-form-builder.md): How to choose the best online form builder: the six factors that matter (pricing model, embed/API, data ownership, free tiers) plus a shortlist.
- [The Best Form Builders in 2026 (Tested and Compared by Use Case)](https://forms.expert/md/en/blog/best-form-builders.md): The best form builders compared: a use-case shortlist with each tool's best-for, free plan, standout, and price, so you can pick the right one.
---
# How to Write Good Survey Questions (40+ Examples and Rules)
Source: https://forms.expert/blog/good-survey-questions
**On this page:** What Makes a Good Survey Question · 5 Rules for Writing Good Survey Questions · Good Survey Questions Examples by Use Case · Open-Ended vs Closed-Ended Survey Questions · Bad Survey Questions to Avoid · How Long Should a Survey Be · Turn Good Questions Into a Live Survey
A survey is only as good as its questions, and most surveys quietly lose before they're sent. A vague phrase here, a leading word there, two ideas crammed into one line, and the answers come back impossible to trust. The fix isn't complicated, but it is specific. This guide covers what separates a good survey question from a bad one, the five rules that catch most mistakes, a bank of 40+ examples you can copy by use case, and the loaded and double-barrelled questions to stop asking.
## What Makes a Good Survey Question
A good survey question is one that every respondent reads the same way and can answer honestly. That's the whole test. If two people could reasonably interpret the wording differently, or if the phrasing nudges them toward a particular answer, the data is broken before anyone opens a chart. Good questions are clear, neutral, and focused on a single idea, which sounds obvious until you start writing them and notice how easily all three slip.
Think of it as protecting the answer. Every choice you make (the words, the scale, the order) either keeps the respondent's honest opinion intact or distorts it. A question like "how satisfied were you with our fast, friendly support?" has already decided the support was fast and friendly, so a dissatisfied customer has to argue with your premise before they can answer. Strip the adjectives and the same question becomes usable. The [Pew Research Center's work on writing survey questions](https://www.pewresearch.org/writing-survey-questions/) is the definitive deep dive if you want the research behind why small wording changes move results so much.
It helps to remember what a bad question actually costs. It doesn't just produce one weak data point, it quietly corrupts the average, because the people who misread it answer a slightly different question than the people who read it as intended. You can't see that damage in the results, which is what makes it dangerous. A clean question fails loudly (people skip it); a subtly biased one fails silently and still gives you a number that looks trustworthy.
One more thing worth saying up front: a good question is also one you'll actually use. If the answer can't change a decision you're going to make, it isn't a good question for this survey, no matter how cleanly it's written. Clarity and neutrality keep the data honest. Relevance keeps the survey short enough that people finish it.
## 5 Rules for Writing Good Survey Questions
Five rules catch the large majority of survey mistakes. Run every question past them before it goes out.
**1. One idea per question.** The most common mistake is the double-barrelled question: "how would you rate our speed and pricing?" If someone loves your speed and hates your price, they can't answer truthfully, so they pick something in the middle and you learn nothing. Split anything with an "and" or an "or" into separate questions.
**2. Keep the wording neutral.** A question shouldn't reveal the answer you're hoping for. Drop praise words ("our excellent support"), drop assumptions ("how much did you enjoy..."), and don't bundle a justification into the question. Neutral phrasing feels almost too plain when you write it, and that flatness is the point.
**3. Use plain, accessible language.** Write for the least specialist person who'll answer. Cut jargon, acronyms, and internal product names that respondents won't recognize. "How long did it take to get your first result?" beats "how would you rate your time-to-value?" every time. The University of Pittsburgh's [tips for writing good survey questions](https://teaching.pitt.edu/resources/tips-for-writing-good-survey-questions/) is a tidy reference on accessible wording.
**4. Pretest before you send.** Show the draft to three or four people who resemble your audience and watch where they hesitate. A question that makes sense in your head but trips up every tester is a question that'll trip up a thousand respondents. Pretesting is the cheapest quality step in the whole process, and the one people skip most.
**5. Match the question type to the goal.** A number you'll track over time wants a rating or a scale. A list of known options wants multiple choice. A reason you can't predict wants an open box. Picking the wrong format is its own kind of bad question, and our guide to the [types of survey questions](https://forms.expert/blog/survey-question-types) walks through which format fits which goal.
If you only remember one thing, make it this: a good question gives away nothing about the answer you want. Clarity, neutrality, plain language, and pretesting are all really in service of that single idea. Write the question so that a happy customer and an unhappy one can both answer it without arguing with the wording first, and most of the other rules take care of themselves.
> **note:** A fast neutrality check: read your question and try to guess the answer the writer is hoping for. If you can guess it, so can your respondents, and they'll drift toward it. Good questions give away nothing about the "right" answer, which is why genuinely neutral wording often feels almost boringly plain.
## Good Survey Questions Examples by Use Case
Here's the bank. These are written to be copied and adapted, grouped by the survey you're most likely running. Swap in your product or context and keep the neutral phrasing.
**Customer satisfaction questions:**
- How satisfied are you with your purchase overall?
- How easy was it to get the help you needed?
- How well does the product meet your needs?
- How likely are you to buy from us again?
- What almost stopped you from completing your order?
- How did we compare to what you expected before buying?
- What is one thing we could do better?
- How likely are you to recommend us to a friend or colleague?
**Product feedback questions:**
- How often do you use the product?
- Which feature do you rely on most?
- Which feature do you wish worked differently?
- How easy was it to get started?
- When something goes wrong, how easy is it to recover?
- What were you trying to do the last time you got stuck?
- How well does the product fit into your existing workflow?
- If the product disappeared tomorrow, what would you miss most?
**Employee and team questions:**
- How clear are you on what's expected of you in your role?
- How supported do you feel by your manager?
- How comfortable are you raising concerns with leadership?
- How well do the tools you're given fit the job?
- How manageable is your current workload?
- What would make the biggest difference to your day-to-day?
- How connected do you feel to the team's goals?
**Post-event questions:**
- How would you rate the event overall?
- Which session was the most useful to you, and why?
- How well did the event match what was advertised?
- How likely are you to attend again?
- What topic would you want covered next time?
- How was the pace, too slow, about right, or too fast?
- What's one thing we should change for next time?
**Website and UX questions:**
- Were you able to find what you came for today?
- What almost made you leave the page?
- How easy was it to understand what we offer?
- Was anything confusing or missing?
- How would you rate the speed of the site?
- What were you hoping to do that you couldn't?
- How did you first hear about us?
**Market and pricing research questions:**
- How much would you expect to pay for something like this?
- At what price would this start to feel too expensive?
- At what price would it feel so cheap you'd question the quality?
- Which of these options would you choose, and why?
- What would you most likely use instead of us?
- How important is price next to the other things you weigh?
- What would make this an easy yes for you?
That's 40-plus to start from. Notice how few of them carry an opinion: most ask "how" or "what" and leave the verdict entirely to the respondent.
## Open-Ended vs Closed-Ended Survey Questions
Good questions come in two shapes, and knowing when to use each is half the craft. A closed-ended question gives a fixed set of options, so it's quick to answer and easy to count. An open-ended question leaves a blank box, so it's slower but catches things you didn't think to ask.
Closed-ended questions do the measuring. Multiple choice, rating scales, and [Likert scales](https://forms.expert/blog/likert-scale-survey-questions) all let you put a number on opinion and watch it move over time. Open-ended questions do the discovering. "What almost stopped you from signing up?" surfaces objections in the customer's own words, often the exact phrasing your marketing should be using. The catch is effort: open questions cost the respondent more, and they cost you reading time, so they earn their place near the end of a survey and in small numbers.
The honest answer to "which should I use?" is usually both. Lean on closed questions for the bulk of the survey so you get clean numbers, then add one or two open questions for the surprises. If you want the full breakdown of every format and when it fits, the [types of survey questions](https://forms.expert/blog/survey-question-types) guide is the companion to this one. The short version: close the question when you know the possible answers, open it when you don't.
A rough ratio helps in practice: aim for most of the survey to be closed questions and reserve one or two open ones, usually near the end. Too many open questions and your completion rate falls off a cliff, since typing is real work. Too few and you only ever hear back about the things you already knew to ask. One well-placed open question, like "what almost stopped you?", often earns more than five extra rating scales.
## Bad Survey Questions to Avoid
Bad questions usually fail in one of a few predictable ways. Each has a quick fix once you can name it. The table pairs the common problems with a bad example and a better version you can borrow.
The pattern underneath all of them is the same: a bad question does some of the answering for the respondent, or asks for more than one thing at once, or assumes a fact that might not be true. Read each of your questions out loud and ask whether a person who disagrees with you could still answer it comfortably. If they can't, you've found a leading or loaded question. The UK Government's [questionnaire design guidance](https://analysisfunction.civilservice.gov.uk/policy-store/questionnaire-design-guidance/) catalogues these failure modes in more detail if you want a formal checklist to test against.
| Problem | Bad question | Better version |
| --- | --- | --- |
| Double-barrelled | Was our staff friendly and knowledgeable? | Split it: "Was our staff friendly?" and "Was our staff knowledgeable?" |
| Leading | How great was our award-winning support? | How would you rate your experience with our support? |
| Loaded (built-in assumption) | Where do you skip the docs before asking support? | When you have a question, where do you look first? |
| Absolutes | Do you always read our release notes? | How often do you read our release notes? Never to always |
| Vague | Do you use the product often? | How many times did you use the product last week? |
| Jargon | How would you rate your onboarding TTV? | How long did it take to get your first result? |
## How Long Should a Survey Be
Shorter than you want it to be. Every question you add costs completions, and the drop gets steeper the longer the form feels. There's no magic number, but a focused survey of five to ten good questions almost always beats a sprawling one of thirty, because the people who would have quit at question twenty-two actually finish.
The useful discipline is to start from the decision, not the question list. Write down what you'll do differently depending on the answers, then keep only the questions that feed those decisions. If an answer wouldn't change anything, the question is costing you completions for nothing. Order matters too: open with easy, low-stakes questions to build momentum, put the effortful ones (ranking, long open text, sensitive demographics) near the end once people are invested, and never lead with "what's your income?"
There's a real trade-off here worth naming. More questions feel like more insight, and it's tempting to ask everything while you have someone's attention. But a half-finished survey teaches you less than a short one that people complete, so the restraint pays off twice: better completion rates and cleaner data from respondents who weren't rushing to escape.
A practical way to find your length: build the survey, then cut it by a third before sending. Almost every draft has questions that felt essential while writing and turn out to be curiosity rather than need. The third you remove is rarely missed, and the completion rate you gain from the shorter form usually tells you more than the questions you dropped ever would have.
> **important:** Before you send, run the cut test: go through every question and ask "what will I do differently based on the answer?" If you can't answer that, delete the question. A survey people finish is worth more than a thorough one they abandon, and ruthless trimming is the single biggest lever on your response rate.
## Turn Good Questions Into a Live Survey
Once the questions are written, building the survey is the easy part. In [Forms Expert](https://forms.expert/online-surveys), every question type in this guide (multiple choice, rating, Likert, open text, ranking, and demographic fields) is available on every plan, including Free, so you can mix the formats your questions actually call for. Group related questions, keep the form short, and use [conditional logic](https://forms.expert/blog/conditional-logic-and-multi-step-forms) to show follow-ups only when they're relevant, which keeps a survey feeling shorter than it is.
When you publish, the same survey ships as a hosted page, an embeddable widget, or a REST endpoint, so it meets people wherever they already are, on a site, in an email, or inside your own app. If you'd rather not start from a blank page, the [survey templates](https://forms.expert/templates) come with sensible questions already laid out, and a [customer feedback survey](https://forms.expert/blog/customer-feedback-survey) is one of the most common places to start.
The honest note on analysis: collecting responses and reading a basic results overview is all-plans, while per-field breakdowns and trend tracking are part of the Pro analytics. So you can run a full survey on Free and upgrade only when you want the deeper reporting. Write clear, neutral, single-focus questions, keep the list short, and the survey will mostly take care of itself from there. Start from the [home page](https://forms.expert/) when you're ready to build.
## Frequently Asked Questions
### What makes a good survey question?
A good survey question is one that every respondent reads the same way and can answer honestly. In practice that means three things: it's clear (no ambiguous wording), it's neutral (it doesn't reveal the answer you're hoping for), and it's focused on a single idea rather than two crammed together. A useful test is to imagine someone who disagrees with you reading it. If they can still answer comfortably, the question is probably fine. If the wording argues with them first, it's leading or loaded and needs a rewrite. The last quiet rule is relevance: a good question is one whose answer will actually change a decision you're going to make.
### What are examples of good survey questions to ask?
Good questions usually ask "how" or "what" and leave the verdict to the respondent. For customers: "How easy was it to get the help you needed?" and "What almost stopped you from completing your order?" For products: "Which feature do you rely on most?" and "What were you trying to do the last time you got stuck?" For employees: "How clear are you on what's expected of you?" For events: "Which session was the most useful, and why?" Notice none of them carry an opinion or a compliment that would nudge the answer.
### What's the difference between open-ended and closed-ended survey questions?
A closed-ended question gives a fixed set of options, so it's fast to answer and easy to count, like multiple choice or a rating scale. An open-ended question leaves a blank box for a written answer, which is richer but slower to analyze. Use closed questions for the measuring work and the numbers you'll track, and save a small number of open questions for discovering things you didn't think to ask. Most good surveys mix both, leaning on closed questions and adding one or two open ones near the end.
### What are examples of bad survey questions to avoid?
The usual offenders are leading, loaded, and double-barrelled questions. Leading: "How great was our award-winning support?" assumes the support was great. Double-barrelled: "Was our staff friendly and knowledgeable?" asks two things at once, so someone who felt one but not the other can't answer. Loaded: "Where do you skip the docs before asking support?" smuggles in an assumption. Absolutes like "do you always..." force a yes/no where a frequency scale belongs. The fix is the same each time: remove the opinion, split the question, or replace the absolute with a scale.
### How many questions should a survey have?
Fewer than you'll be tempted to include. There's no perfect number, but a focused survey of five to ten well-chosen questions usually beats a long one, because more people finish it. The deciding rule is whether each answer will change a decision you're going to make. If it won't, the question is costing you completions for nothing. Put the easy questions first to build momentum and the effortful ones near the end, and cut anything you can't tie to an actual decision.
### How do you write neutral, unbiased survey questions?
Strip out anything that reveals or assumes an answer. Remove praise words like "excellent" or "award-winning," drop assumptions baked into the phrasing ("how much did you enjoy..." assumes enjoyment), and don't attach a justification to the question. Balance any scale so the positive and negative ends mirror each other. Then pretest it: show the draft to a few people who resemble your audience and watch for hesitation, since a question that trips up testers will trip up respondents. Neutral questions often feel almost too plain, and that plainness is exactly what keeps the data honest.
---
# Types of Survey Questions: 12 Formats and When to Use Each
Source: https://forms.expert/blog/survey-question-types
**On this page:** What Are the Types of Survey Questions · Closed-Ended Survey Question Types · Scaled Survey Question Types · Ranking and Order Survey Question Types · Open-Ended Survey Question Types · Demographic Survey Questions · How to Choose the Right Survey Question Type · Build Any of These Question Types in Forms Expert
The question type you pick decides what you can do with the answer. Ask "how was support?" as an open text box and you get stories you have to read one by one. Ask it as a 1-to-5 rating and you get a number you can chart by Tuesday. Neither is wrong, but they answer different questions, and choosing the wrong format is the quietest way to waste a survey. This guide is a labeled catalogue of the 12 survey question types worth knowing, each with a one-line example and a plain note on when to reach for it.
## What Are the Types of Survey Questions
Every survey question is either closed-ended or open-ended, and that split is the most useful way to think about all the types of survey questions. A **closed-ended** question gives people a fixed set of options to choose from, so the answers come back countable and comparable. An **open-ended** question leaves a blank box, so the answers come back rich but messy. Most of the named formats (multiple choice, Likert, rating, ranking, dropdown) are just flavors of closed-ended, tuned for different kinds of decisions.
The choice between them isn't only stylistic, it changes what you can do with the data and how many people finish. Closed questions are quick to answer and quick to analyze, so they protect your completion rate and hand you charts on day one. Open questions cost the respondent effort and cost you reading time, which is why a survey that's all open boxes gets abandoned and a survey that's all closed boxes misses the things you didn't think to ask. The skill is knowing which job each question is doing before you pick its format.
The practical version: closed-ended questions are for measuring, open-ended questions are for discovering. If you already know the possible answers and want to count them, close the question. If you don't know what people will say and want to find out, leave it open. A good survey usually mixes both, leaning heavily on closed questions for the numbers and saving one or two open ones for the surprises. The UK Government's [questionnaire design guidance](https://analysisfunction.civilservice.gov.uk/policy-store/questionnaire-design-guidance/) is a solid, neutral reference if you want the formal version of this split.
The table below is the whole catalogue at a glance. The sections after it walk through each group with examples.
| Question type | Example | Use it when | Family |
| --- | --- | --- | --- |
| Dichotomous (yes/no) | Did you find what you needed today? | A clean either/or with no middle ground | Closed |
| Multiple choice (single) | Which plan are you on? Free / Starter / Pro | One answer from a known list | Closed |
| Checkbox (multiple-answer) | Which features do you use? Select all that apply | Several answers can be true at once | Closed |
| Dropdown | What country are you in? | A long single-select list you want to keep compact | Closed |
| Likert scale | Setup was easy: strongly disagree to strongly agree | Measuring agreement or an attitude | Scaled |
| Rating scale | Rate our support from 1 to 5 stars | A quick quality or satisfaction score | Scaled |
| NPS (0 to 10) | How likely are you to recommend us? | Tracking loyalty as a trend over time | Scaled |
| Matrix | Rate speed, design, and price on the same scale | Several items sharing one scale | Scaled |
| Slider | Set your ideal monthly budget | A feel for magnitude on a continuous range | Scaled |
| Rank order | Drag these five features into priority order | Forcing trade-offs between options | Ranking |
| Open-ended (text) | What almost stopped you from signing up? | Catching reasons you didn't predict | Open |
| Demographic | What is your age range? | Segmenting results by who answered | Closed |
## Closed-Ended Survey Question Types
Closed-ended questions are the backbone of any survey you plan to analyze. Four formats cover most of what you'll need.
**Dichotomous questions** offer exactly two options, usually yes/no or true/false. They're fast and unambiguous, which makes them great as a gate ("Have you used the API?") that routes people to the right follow-up. The catch is that real opinions rarely fit in two boxes, so don't use them where a scale belongs.
**Multiple choice** questions let people pick one option from a list. They're the most common closed format for a reason: easy to answer, easy to count. The work is all in the options. Make them cover every likely answer, keep them from overlapping, and add an "Other" field when you're not sure you've caught everything. These are what most people mean by [multiple choice survey questions](https://forms.expert/online-surveys), and they're the default for anything with a known set of answers.
**Checkbox questions**, also called multiple-answer, look like multiple choice but let people select more than one option. Use them when several answers can be true at once ("Which of these do you use?"). One honest warning: because respondents can pick many or none, you can't read the percentages the same way as single-select, since they won't add up to 100.
**Dropdowns** are single-select questions that hide their options until clicked. They earn their place for long lists, like country or job title, where showing every option would swamp the page. For three or four options, plain radio buttons are friendlier than making people open a menu.
Across all four, the quality lives in the options, not the question stem. Three rules carry most of the weight: make the options mutually exclusive so no answer fits two boxes, make them collectively exhaustive so everyone has a home (an "Other" field covers the gaps), and keep the list short enough to read without scrolling. A multiple choice question with overlapping or missing options doesn't just lose data, it quietly pushes people toward whichever answer happens to sit at the top.
## Scaled Survey Question Types
Scaled questions measure intensity, not just choice. They turn "how much" into a number, which is exactly what you want when you're tracking something over time.
**Likert scales** measure agreement along an ordered range, usually five or seven points from strongly disagree to strongly agree. They're the workhorse of attitude measurement. There's enough to say about them that they have their own guide: see [Likert scale examples and how to use them](https://forms.expert/blog/likert-scale-survey-questions) for ready-to-copy anchor sets.
**Rating scales** ask for a score, often 1 to 5 stars or 1 to 10. They feel natural to respondents and read instantly on a dashboard. The thing to nail down is what the endpoints mean, because "3 out of 5" is useless if nobody knows whether 5 is best or worst.
**NPS** is a specific 0-to-10 rating ("how likely are you to recommend us?") rolled into a single loyalty score and tracked as a trend. It's worth its own treatment too: our [NPS survey guide](https://forms.expert/blog/nps-survey-guide) covers how the scoring works and how to read the movement.
**Matrix questions** stack several items on one shared scale, like rating speed, design, and price all from 1 to 5 in a single grid. They save space and feel efficient, but they tire people out fast, so keep the rows few. **Sliders** let people drag along a continuous range, which suits questions about magnitude (a budget, a percentage) where exact buckets would feel arbitrary.
When should you reach for a scale instead of a plain choice? When the answer has a direction and a degree. "Did support help?" is a yes/no. "How helpful was support?" is a scale, and the gap between them is everything you learn from the people who'd technically say yes but only barely. Scales also let you track movement: a number you measure this month and again next month tells a story a one-time choice can't.
> **note:** A rating scale and a Likert scale look similar but answer different questions. A rating scale asks for a score on one thing ("rate this 1 to 5"). A Likert scale asks how much you agree with a statement ("setup was easy: agree or disagree"). If you want a number, rate. If you want an attitude, use Likert.
## Ranking and Order Survey Question Types
Ranking questions ask people to put options in order rather than score each one on its own. They're the right tool when you need priorities, not ratings.
**Rank-order questions** ask respondents to sort a list from most to least important. The payoff is that they force trade-offs: when someone has to choose, you learn what actually matters, instead of getting a survey where every feature is rated "very important." The cost is effort, so keep the list short, ideally five items or fewer, because ranking ten things is a chore most people quit.
**This-or-that questions** (forced-choice pairs) are ranking stripped to two options at a time: "which matters more, speed or price?" Asked in a series, they reveal preferences more honestly than a grid of ratings, because there's nowhere to hide. If you want the full breakdown of when to rank versus rate, our guide to [ranking survey questions](https://forms.expert/blog/ranking-survey-questions) goes deeper. The short version: rate when you want each item's standalone score, rank when you want their order.
One practical caution: ranking questions are harder on a phone, where dragging items is fiddlier than tapping. If most of your audience answers on mobile, test the ranking question on a real device before you ship it, or fall back to a short series of this-or-that pairs that only ask for a tap.
## Open-Ended Survey Question Types
Open-ended questions hand people a blank box. They're slower to analyze and you can't average them, but they're the only format that tells you things you didn't think to ask.
**Short-text questions** suit answers that are open but bounded, like "what's your role?" or "what almost stopped you from signing up?" That second one is worth stealing: a single open question about hesitation often surfaces the objection your whole funnel is built to handle, in the customer's own words. **Long-text or comment fields** give room for a real explanation ("tell us about your experience"), which is where you find the quotes that make a case to your team.
Here's the honest tension. Open-ended questions get you the richest material and the worst response rates, because typing is work. The fix isn't to avoid them, it's to ration them. One sharp open question near the end of a survey, placed after people are already invested, earns far more than three scattered through the middle. For more on phrasing them well, our piece on [good survey questions](https://forms.expert/blog/good-survey-questions) covers the wording that gets useful answers instead of one-word shrugs.
There's a cost on your end too, not just the respondent's. Open answers have to be read and grouped before they mean anything, which is fine for a hundred replies and painful for ten thousand. A common middle path: run an open question on an early batch, spot the recurring themes, then turn those themes into a closed multiple choice question for the full audience. You get the discovery of open text and the countability of closed options, in that order.
## Demographic Survey Questions
Demographic questions ask who the respondent is: age range, location, role, company size, income band. Mechanically they're usually multiple choice or dropdowns, but they get their own category because of how you use them. Their job isn't to be interesting on their own, it's to let you slice every other answer by segment, so you can see that mobile users are the unhappy ones or that enterprise accounts want a different feature than startups do.
Two habits keep them from backfiring. Put them at the end, not the start, because leading with "what's your income?" makes people bail before they've answered anything useful. And ask only for the segments you'll actually analyze. Every extra demographic question costs you completions and, for sensitive fields, trust, so if you won't split the data by it, cut it. When you do ask, an "prefer not to say" option is both kinder and more honest than forcing an answer. Kantar's rundown of [essential survey question types](https://www.kantar.com/north-america/inspiration/research-services/5-essential-survey-question-types-explained-pf) is a good reference on matching format to purpose here.
A note on the categories themselves: write them the way respondents think, not the way your database stores them. Age ranges beat asking for a birth year, role buckets beat a free-text job title, and offering bands for income or company size gets far more answers than an open number. The looser category is easier to answer and still slices the data the way you need.
## How to Choose the Right Survey Question Type
Forget the formats for a second and start with the decision you're trying to make. The question type should fall out of that, not the other way around.
Work backward from the answer you need. If you need a number to track over time, use a rating, Likert, or NPS question. If you need to know what people prefer when they can't have everything, rank or use forced pairs. If you need to count how many fall into known buckets, use multiple choice or checkboxes. If you genuinely don't know what people will say, leave it open and read the replies. The [Pew Research Center's guidance on writing survey questions](https://www.pewresearch.org/writing-survey-questions/) is the gold standard if you want to go deeper on how format and wording shape answers.
Three rules of thumb save most surveys. Lead with the easy closed questions and save effortful ones (ranking, open text, sensitive demographics) for the end. Don't mix two question types in one item, the way "rate and explain" secretly does. And match the format to how you'll report it, because a question you can't summarize the way you need is a question you shouldn't have asked. Pick the format from the decision, and the survey mostly writes itself.
A quick worked example. Say you want to know why people downgrade. Start closed to size the problem: a multiple choice "what's the main reason?" with the four or five reasons you already suspect, plus "Other." Add one open question for the people who pick Other, so you catch the reason you didn't list. Finish with a demographic question or two if you'll want to see whether smaller accounts churn for different reasons than larger ones. Three question types, each pulling its weight, none of them doing another's job.
> **important:** A survey's worst enemy is its own length. Every question you add costs completions, and the drop gets steeper once people sense the form dragging. Before you ship, cut every question you won't act on. The honest test: if the answer can't change a decision, it doesn't belong in the survey.
## Build Any of These Question Types in Forms Expert
Every format in this guide is buildable in [Forms Expert](https://forms.expert/online-surveys), and all of them are available on every plan, including Free. Multiple choice, checkbox, dropdown, Likert, rating, NPS-style 0-to-10, ranking, open text, and demographic fields are all standard, so you can mix the types your survey actually needs instead of bending one format to do another's job.
A couple of things that help once you're building. Group related questions so respondents settle into a rhythm, and use [conditional logic](https://forms.expert/blog/conditional-logic-and-multi-step-forms) to show follow-ups only when they're relevant, which keeps long surveys from feeling long. When you publish, the same survey ships as a hosted page, an embeddable widget, or a REST endpoint, so it goes wherever your audience already is. If you'd rather start from something pre-built, the [survey templates](https://forms.expert/templates) come with the common question types already laid out.
The honest line on analysis: collecting any of these question types and reading a basic results overview is all-plans, while per-field breakdowns and trend tracking are part of the Pro analytics. So you can run a full mixed-format survey on Free and upgrade only when you want the deeper reporting. Start from the decision you're making, pick the format that answers it, and the rest is just asking clearly.
## Frequently Asked Questions
### What are the main types of survey questions?
They fall into two big groups. Closed-ended questions give a fixed set of options and come back countable: multiple choice, checkbox (multiple-answer), dropdown, dichotomous yes/no, and the scaled formats like Likert, rating, and NPS. Open-ended questions leave a blank box for a written answer. Ranking questions are a third practical group, where people put options in order rather than scoring them, and demographic questions are closed-format questions used to segment the rest of your results. Most surveys mix several types, leaning on closed questions for the numbers and a few open ones for the surprises.
### What is the difference between open-ended and closed-ended questions?
A closed-ended question gives people a fixed set of options to choose from, so the answers are easy to count and compare. An open-ended question leaves a blank box, so the answers are richer but have to be read one by one. The rule of thumb: closed questions are for measuring things you already know the shape of, and open questions are for discovering things you don't. Good surveys use closed questions for most of the work and save a couple of open ones for what you couldn't predict.
### What is the difference between multiple choice and checkbox questions?
Multiple choice lets people pick one option from the list. Checkbox, also called multiple-answer, lets them pick several. Use multiple choice when only one answer can be true, like which plan someone is on. Use checkbox when more than one can apply, like which features they use. One thing to watch: because checkbox answers can select many options or none, the percentages won't add up to 100, so you read them as "share of people who picked this" rather than as a split of the whole.
### What is the difference between a rating scale and a Likert scale?
A rating scale asks for a score on a single thing, like rating support from 1 to 5. A Likert scale asks how much you agree with a statement, from strongly disagree to strongly agree. They look similar but answer different questions: use a rating when you want a number, and a Likert scale when you want to measure an attitude or opinion.
### When should you use a ranking question instead of a rating question?
Use a ranking question when you need to know what people prefer once they can't have everything. Rating each item separately often produces a survey where everything scores "very important," which tells you nothing about priorities. Ranking forces trade-offs, so you learn the actual order. The downside is effort, so keep the list to five items or fewer. Use a rating instead when you want each item's standalone score rather than its position relative to the others.
### What are demographic survey questions?
Demographic questions ask who the respondent is: age range, location, role, company size, and similar. They're usually multiple choice or dropdowns, but their purpose is segmentation, letting you break every other answer down by group. Put them at the end of the survey so they don't scare people off early, ask only for the segments you'll actually analyze, and offer a "prefer not to say" option on sensitive fields. Asked well, they turn a single average into a story about which groups feel differently.
---
# How to Build a Multilingual Form (Methods, Pitfalls, and Examples)
Source: https://forms.expert/blog/multilingual-forms
**On this page:** What Is a Multilingual Form · Ways to Build a Multilingual Form · How to Translate a Google Form · Machine vs Manual Translation for Forms · The Hard Parts of Multilingual Forms · Letting Respondents Pick a Language · Build a Multilingual Form in Forms Expert
A multilingual form is one form your respondents can read and complete in their own language, with a switcher that lets them choose. Same questions, same logic, same results table, just rendered in Spanish, Arabic, or Japanese depending on who shows up. Simple in theory. Then you try to build one and find there are four different ways to do it, each with a catch. You can duplicate the form once per language and maintain five copies by hand, lean on a WordPress plugin, paste your fields through Google Translate, or use a tool that translates and serves the languages for you. This guide covers all four, walks the most-searched DIY route (translating a Google Form), and stays honest about the parts that quietly break: character encoding, right-to-left scripts, and dates that read differently from one country to the next.
## What Is a Multilingual Form
A multilingual form is a single form published in more than one language, where the labels, help text, answer options, and buttons all appear in the respondent's language while the form underneath stays identical. One definition, several presentations. Someone in Berlin sees German, someone in São Paulo sees Portuguese, and both sets of answers land in the same place for you to read.
That shared results table is what separates a real multilingual form from a pile of look-alike forms. Build five unrelated forms, one per language, and you also get five response tables, five sets of analytics, and five things to fix every time a single question changes. Keep the structure unified instead and the math gets a lot kinder: edit a field once, re-check its translations, and every submission still flows into one dataset no matter which language it came from. You analyze the results as one population, not as five spreadsheets you have to stitch together by hand.
Here's a distinction people trip over constantly. Translating the form is not the same as translating your website, and neither is the same as the language your admin dashboard runs in. Your site can sit in English while the form embedded on it offers six languages, and your back office can stay in whatever you and your team read. So when someone asks for a multilingual form, it's worth asking back: do they mean the public questions, the confirmation email, the validation messages, or all of it? Almost always they mean the questions and buttons the respondent sees. That's where most of the effort goes, and it's the part this guide focuses on.
## Ways to Build a Multilingual Form
There are four common ways to build a multilingual form, and they run from free-but-tedious to paid-but-painless. The honest trade-offs first, then the detail.
Duplicating forms is the route that needs the least thinking and the most repetition. You rebuild the whole form for each language, translate the strings as you go, and link the versions together somehow (a menu, separate URLs). It works fine for one or two languages on a form you'll rarely touch. The moment you're maintaining four copies and someone asks to add a question, you feel the cost: that edit now happens four times, and miss one and that language quietly drifts out of sync with the rest.
If your site already runs on WordPress, a multilingual plugin like WPML or Polylang can translate form strings alongside the rest of your content. Sensible if you're committed to that stack. Less sensible if you aren't, because you inherit the setup overhead, the plugin-conflict roulette, and a translation workflow bolted to your CMS rather than to the form itself. It also doesn't help at all if your form lives somewhere other than WordPress.
The copy-paste Google Translate route is the fast, rough-draft option. You run each label through Google Translate and paste the result into a duplicated field. Good enough for an internal poll. Risky for anything customer-facing, because machine output dropped straight into a form goes out unreviewed, and a mistranslated consent line or a garbled payment label is a real problem, not a typo. There's also no switcher, so you're back to managing separate forms anyway.
Built-in translation is when the form tool does the work. You write the form once, the tool machine-translates it into the languages you pick, you edit anything that reads wrong, and it serves each language behind a [built-in form translation](https://forms.expert/form-translation) switcher. Least ongoing effort, cleanest result, single response table. The catch is that this usually sits on a paid plan, which is the trade you're making for not hand-maintaining copies forever.
| Method | How it works | Best for | Drawback |
| --- | --- | --- | --- |
| Duplicate forms | Rebuild the form once per language, link them manually | One or two languages, rarely edited | Every edit repeated N times; split results |
| WordPress plugin | A plugin (WPML, Polylang) translates form strings | Sites already on WordPress | Setup overhead; tied to the CMS; conflicts |
| Copy-paste Google Translate | Translate strings by hand, paste into new fields | A quick, internal rough draft | Unreviewed errors; no switcher; manual upkeep |
| Built-in translation | The tool translates and serves languages with a switcher | Ongoing or customer-facing forms | Usually a paid plan |
## How to Translate a Google Form
This is the single most-searched version of the question, so let's answer it straight. Google Forms doesn't have a built-in button that translates a form and hands respondents a live language switcher. So can you translate a Google Form? Sort of, with workarounds, and it helps to know their limits before you commit to one.
The manual route is the duplicate-and-translate one. Make a copy of the form, then go field by field translating the title, the questions, the descriptions, and the answer options into the target language. Say you want to translate a Google Form to Spanish: you'd retype each string in Spanish, or paste it in from Google Translate, then publish that copy as a separate form and point Spanish-speaking respondents at its link. Repeat for every language you need. It's the same duplicate-forms pattern from the previous section, just living inside Google Forms, with the same upkeep tax every time a question changes.
The browser route leans on the respondent's own tools instead of yours. Chrome and most browsers can auto-translate a page, so a respondent can right-click and pick Translate, or run the form's URL through Google Translate. This needs nothing from you, which is the appeal, but you don't control the result: translation quality varies, it can mangle option labels, it sometimes breaks the layout, and plenty of people never turn it on. Treat it as a fallback, not a feature you can rely on.
What you don't get from Google Forms either way is one unified form with a proper switcher and a single response sheet across languages. You get either several separate forms or a respondent-side auto-translation you can't see or fix. For a quick internal survey that's usually fine. For anything that represents your brand or collects sensitive answers, the gaps start to matter, and that's the point where people go looking for a tool that treats translation as a first-class part of the form rather than an afterthought.
> **note:** Honest limit: Google Forms has no native, respondent-facing language switcher and no shared cross-language response table. Your options are duplicating the form per language (which you maintain by hand) or relying on the visitor's browser to auto-translate (which you can't control or correct). That's fine for an internal poll. It's thin for a public, branded, or compliance-sensitive form.
## Machine vs Manual Translation for Forms
Every route above eventually forces the same decision: do you trust machine translation, or do you write the translations by hand? The honest answer is that you want both, in that order.
Machine translation (DeepL, Google Translate, and the rest) is genuinely good now, and for the bulk of a form, the plain field labels, the help text, the generic options, it gets you most of the way in seconds. Starting from scratch in six languages by hand is a waste of time when a machine can draft the whole thing and you can correct it.
But forms have a handful of strings where most of the way isn't good enough. Consent and legal text has to say exactly the right thing in every language, and a machine doesn't know your jurisdiction or your intent. Answer options sometimes carry meaning a literal translation loses, like a satisfaction scale, a job title, or a regional term that has no clean equivalent. Anything with a number, a currency, or a date needs a human eye for local convention. And short button text like "Submit" or "Next" occasionally comes back oddly formal, or just wrong, in a way that's obvious to a native speaker and invisible to you.
So the workflow that actually holds up is simple to say: machine-translate first to get a complete draft, then have a human (ideally a native speaker) review the labels respondents will read most and the strings where a mistake costs you something. If you're running a [multi-language survey](https://forms.expert/online-surveys) where wording shifts the results, that review isn't optional, because a leading or confusing question in translation quietly biases everything you collect from that language group. Machines draft. People sign off. Skip the second step only on throwaway forms where nobody important is reading the answers.
## The Hard Parts of Multilingual Forms
Translation is the obvious work. The pitfalls below are the ones that surprise people, and they're where a multilingual form goes from translated to actually working.
Encoding is the classic one. If any layer in the chain, the page, the form handler, the database, the export, isn't using UTF-8, your accented French and your Japanese and your emoji turn into garbage somewhere along the way. The fix is boring and absolute: use UTF-8 everywhere, declare it in your page, and store it that way end to end. The W3C's guidance on [handling form data in UTF-8](https://www.w3.org/International/questions/qa-forms-utf-8) is the reference worth bookmarking, because encoding bugs are miserable to track down after the data is already corrupted.
Right-to-left languages are the pitfall people forget until an Arabic-speaking respondent sends a screenshot. Arabic, Hebrew, Persian, and Urdu read right to left, and a form laid out for English doesn't just need translated words, it needs its direction flipped: labels on the right, inputs aligned correctly, the whole flow mirrored. That comes down to setting the page direction and language attributes, which the W3C covers in its notes on [language and direction declarations](https://www.w3.org/International/techniques/authoring-html). Translate the words without handling direction and the form reads, technically, but it feels broken to the very people it's meant for.
Then there's locale formatting, the quiet one. 03/04/2026 is March 4th to an American and the 3rd of April to almost everyone else. Decimal separators flip between commas and periods. Currency symbols sit on different sides of the number. None of this is translation, it's localization, and it's governed by per-locale data like the [Unicode CLDR](https://cldr.unicode.org/) that powers date and number formatting across the web. For a form, the safe moves are to localize formats per language where you can, and to remove ambiguity where you can't: an ISO date, a clearly labeled currency, an example next to the field. Get this wrong and you don't get garbled text, you get clean-looking data that's silently incorrect, which is the worse failure because nobody notices until it matters.
| Pitfall | What breaks | How to handle it |
| --- | --- | --- |
| Character encoding | Accented and non-Latin characters show as garbled boxes | Use and store UTF-8 end to end; declare it in the page |
| Right-to-left scripts | Arabic and Hebrew misalign; layout reads backwards | Set the direction and lang attributes; test the layout |
| Locale formats | Dates, numbers, and currency are misread (03/04 differs) | Localize formats per language; use ISO dates and labels |
## Letting Respondents Pick a Language
A multilingual form is only useful if respondents land in the right language without thinking about it. That's the job of two things working together: a switcher they can use, and a sensible default so most people never need to use it.
The switcher is the visible part, usually a small globe icon or a dropdown listing the published languages. A respondent picks theirs and the form re-renders, ideally without losing anything they've already typed. Keep it where people expect it, near the top, and only list languages you've actually finished translating, because a switcher offering a half-translated language is worse than not offering it at all.
The default is the smart part. A good multilingual form resolves the starting language in a sensible order: an explicit choice in the URL first (a query like "?lang=es" or a localized path, handy when you share a link to a specific audience), then the visitor's browser language, then a remembered choice from a previous visit stored in their browser, falling back to your form's base language if none of those apply. Done well, a French speaker who clicks your link sees French immediately and never touches the switcher, while a Polish speaker who manually picked Polish last week sees Polish again. The switcher is the safety net, not the main event.
If you're embedding the form on a page rather than sending people to a hosted link, the switcher rides along inside the widget, so the form's language stays independent of whatever language the surrounding site happens to be in. That interaction with embedding is its own small topic, covered in how to [embed a form that auto-resizes](https://forms.expert/blog/embed-a-form-that-auto-resizes) without scrollbars or clipped content.
## Build a Multilingual Form in Forms Expert
Forms Expert handles multilingual forms in the product, not as a separate translation service layered over the page. You build the form once, send it through machine translation, edit anything that reads wrong, and publish each language behind its own switcher. Here's the honest shape of it, including what it doesn't do.
Translation runs on DeepL into 30 specific languages (English, Spanish, French, German, Arabic, Japanese, Chinese, Ukrainian, and 22 others). That's a fixed list, not any language on earth, so check yours is on it before you plan around it. Each language gets manual per-string editing, so you can fix the machine's draft, and an independent publish state, so a language goes live only when its copy is ready rather than the moment it's generated. The public globe switcher resolves the starting language from the URL, then the browser, then a remembered choice, the same order described in the previous section. The full walkthrough of that flow lives in the companion guide on how to [translate a form into 30 languages](https://forms.expert/blog/translate-a-form-into-30-languages) without a separate vendor.
Two honest caveats, because this is exactly where marketing copy tends to overreach. First, multi-language forms are a Business-plan feature, so this isn't a free capability and shouldn't be sold as one. If you only ever need a single language, you don't need any of this. Second, the 30-language form translation is a separate thing from the language the Forms Expert dashboard itself runs in: the admin interface is available in English and Ukrainian only. Translating your form into Japanese doesn't put your control panel in Japanese, and the two aren't connected. You can see where the multilingual feature sits across the tiers on the [pricing page](https://forms.expert/pricing).
Once a form is translated, it ships like any other Forms Expert form: a hosted page, an embedded widget, or a REST endpoint, all from the one definition, which is the subject of [one form, three channels](https://forms.expert/blog/one-form-three-channels). The translation travels with it. So a single multilingual form can be a public link for one audience, an embed on your site for another, and an API-fed form for a third, without rebuilding anything per language. That's the whole point of keeping translation inside the form instead of bolting it on afterwards.
> **note:** The honest version: Forms Expert's multilingual forms are a Business-plan feature, powered by DeepL into 30 fixed languages, with per-language editing, independent publish control, and a public language switcher. It's built into the product, not a Weglot-style bolt-on, and it isn't free. The 30-language form translation is also separate from the dashboard's own interface language, which is English or Ukrainian only.
## Frequently Asked Questions
### What is a multilingual form?
A multilingual form is one form published in several languages, where respondents read and answer in their own language while every submission lands in a single shared results table. The questions, logic, and data stay unified; only the displayed language changes. A language switcher lets people pick, and a sensible default picks for them when they don't.
### How do you create a multilingual form?
You have four practical options. Duplicate the form once per language and maintain each copy by hand; use a WordPress plugin like WPML or Polylang if your site already runs on WordPress; copy-paste each string through Google Translate for a rough draft; or use a tool with built-in translation that generates the languages, lets you edit them, and serves a switcher. For anything ongoing or customer-facing, built-in translation saves the most time, because the other routes leave you re-doing every edit in every language.
### How do you translate a Google Form, and can you?
You can, but only with workarounds, because Google Forms has no native one-click translation or respondent-facing switcher. The manual way is to duplicate the form and retype each question, description, and option in the target language (translating a Google Form to Spanish, for instance, means re-entering every string in Spanish), then share that copy as a separate form. The other way is to let respondents auto-translate the page in their browser, which needs nothing from you but gives you no control over quality or layout. Neither approach gives you one unified form with a shared response sheet across languages.
### Should I use machine translation or translate forms manually?
Use machine translation to draft, then a human to review. Tools like DeepL translate the bulk of a form, the plain labels and help text, quickly and well. But consent and legal text, answer options that carry nuance, anything with dates or currency, and short button labels all deserve a native-speaker check, because a small error in those spots is the kind respondents notice or that quietly biases a survey. Machines get you most of the way; people catch what actually matters.
### How do respondents switch languages on a form?
Through a language switcher, usually a globe icon or dropdown that lists the published languages and re-renders the form when someone chooses. Most respondents never need it, though: a well-built form sets the starting language automatically from the URL first, then the browser's language, then any choice remembered from a past visit, falling back to the base language.
### What breaks in multilingual forms?
Three things, mostly, and none of them are translation itself. Character encoding is the first: if any layer in the chain isn't UTF-8, accented and non-Latin characters turn into garbage, so use UTF-8 from the page through to the export. Right-to-left scripts are the second: Arabic, Hebrew, Persian, and Urdu need the layout's direction flipped, not just the words translated, or the form looks broken to the people it's for. Locale formatting is the third and quietest: dates like 03/04 mean different days in different countries, separators and currency symbols differ, and getting it wrong produces clean-looking data that's silently incorrect.
### How many languages can one multilingual form support?
It depends on the tool. A hand-maintained approach (duplicate forms or copy-paste) has no hard limit but a steep practical one, since you maintain every language yourself. Built-in tools usually translate into a fixed set: Forms Expert, for example, covers 30 specific languages through DeepL rather than any language you name. So the honest question isn't how many, it's whether the one you need is on the list, which is worth checking before you commit.
---
# Translate a Form Into 30 Languages Without a Separate Vendor
Source: https://forms.expert/blog/translate-a-form-into-30-languages
**On this page:** Two Common Approaches, Both Expensive · How One-Click Translation Works · Per-Language Publish Control · The Public Language Switcher · Where Translation Fits the Product · Which Plan You Need
Forms Expert translates a single form definition into 30 languages through DeepL, in one action. There is no second toolchain to wire up: no exporting copy to a translation service, no pasting results back, and no separate form to maintain per language. A **multilingual form builder** should treat translation as one attribute of one form, and that is what this does.
## Two Common Approaches, Both Expensive
Most teams approach localized forms one of two ways, and both are expensive in the long run.
- **Duplicate the form per language.** Now a single label change means editing it in every copy, and the copies drift apart the moment someone forgets one.
- Bolt on an external translation service, and you pay a second vendor, manage a second set of credentials, and own the glue code that shuttles strings back and forth.
Either way, the form definition stops being a single source of truth. *Form translation* works better as an attribute of one form than as a fleet of near-identical clones you maintain by hand.
## How One-Click Translation Works
In Forms Expert, translation runs against the form you already built — its labels, help text, options, button copy, and validation messages. You pick the target languages and trigger the translation, and the platform sends the source strings to **DeepL**, the engine behind the feature, which returns up to 30 languages. The structure does not change: the same field schema, conditional logic, and [consent settings](https://forms.expert/blog/gdpr-cookie-consent-built-in) apply to every language, because there is still only one form underneath. You are translating the content while the definition stays put. When you later edit the source copy, you re-translate the affected strings rather than rebuilding anything.
> **note:** Machine translation is a strong first draft, not a final sign-off. DeepL handles the bulk of the work in seconds, but a native reviewer should still read the legally and tonally sensitive strings — consent language, pricing, and calls to action — before that language goes live. Per-language publish control exists precisely so the machine draft and the human review can happen on different days without holding up the languages that are already correct.
## Per-Language Publish Control
Translation and publication are separate steps on purpose. A freshly translated language sits as a draft you can edit, so a reviewer can correct the DeepL output before any respondent sees it. Each language is then published on its own schedule: French and German can go live this week while Japanese waits for a native check next week. The source language keeps running the entire time. This is what keeps *multilingual forms* honest — nothing reaches the public until a human has decided it is ready, and an unfinished translation can never block the languages that are already good to go.
## The Public Language Switcher
Once more than one language is published, you can optionally expose a language switcher on the hosted page and the embeddable widget. Respondents pick their own language, and the form re-renders in that locale while still writing back to the same underlying form. It is optional because not every deployment wants it — a campaign that already routes German traffic to a German page may prefer to skip the control and serve that language directly. Either way, every translation answers to one definition, so a submission in Polish lands in the same place as a submission in English, with the same validation and the same delivery.
## Where Translation Fits the Product
Translation is one attribute of the form, so the surfaces you already rely on keep working in every language. The same form can ship as a hosted page at `/h/{slug}`, an auto-resizing embedded widget at `/e/{slug}`, and a REST endpoint — and the localized versions inherit all three. A programmatic submission goes to the same endpoint regardless of language:
```
POST /f/{resourceId}/{slug}?token=pk_…
Content-Type: application/json
{ "email": "sofia@empresa.es", "plan": "pro" }
```
Because the localized copies share one definition, your delivery and analytics stay unified too. Submissions still route to email, Telegram, and signed webhooks, and on the [Pro plan and up](https://forms.expert/pricing) the [completion funnel, per-field stats, and NPS](https://forms.expert/blog/form-analytics-beyond-counts) aggregate across languages instead of scattering across a dozen duplicate forms. A drop in Spanish completions, for instance, shows up in the same funnel as the English one rather than in a separate report you have to remember to open.
| Capability | Forms Expert | Duplicate-per-language | External translation vendor |
| --- | --- | --- | --- |
| Single source of truth | Yes — one definition | No — N copies drift | Partial — glue code in between |
| Translate in one action | Yes, via DeepL | No — manual per copy | No — export and re-import |
| Review before publish | Per-language drafts | Manual and ad hoc | Depends on the vendor |
| Unified analytics and delivery | Yes | No — split per copy | No — split per copy |
| Second vendor to manage | None | None | Yes |
## Which Plan You Need
Thirty-language DeepL translation is a **Business plan** feature — it is not available on Free, Starter, or Pro, and it is not framed as a free add-on. Business sits at the top of flat, predictable pricing: Free at $0, Starter at $9, Pro at $29, and Business at $99 per month, billed monthly or yearly at ten times the monthly rate, which works out to two months free. Paid plans include a 14-day trial, so a team can confirm that one-click *DeepL form translation* fits their workflow before committing. The full breakdown of limits and what each tier unlocks lives on the [pricing page](https://forms.expert/pricing).
## Frequently Asked Questions
### How many languages can a form be translated into?
A form can be translated into up to 30 languages. Forms Expert sends the form's source strings — labels, help text, answer options, button copy, and validation messages — to DeepL, which returns translations for the languages you select. The form's structure is unchanged across every language: the same field schema, conditional logic, and consent settings apply, because all the translations share a single form definition rather than becoming separate copies. That shared definition is what keeps the experience consistent, so editing the source copy later means re-translating the affected strings rather than rebuilding anything. Thirty-language translation is available on the Business plan.
### What translation engine does Forms Expert use?
Forms Expert uses DeepL as the translation engine. When you choose target languages and trigger a translation, the platform passes the source strings to DeepL and applies the returned translations to the corresponding language version of the form. There is no separate translation vendor to sign up for, no second set of credentials to manage, and no glue code to maintain; the translation step is built into the form builder itself. DeepL produces a strong first draft quickly, and because each language can be reviewed as a draft before it is published, a native speaker can refine the output before any respondent sees it.
### Do I have to publish every language at once?
No. Translation and publication are deliberately separate steps. A newly translated language starts as an editable draft, so a reviewer can correct the machine output before it goes live. Each language is then published on its own schedule — French and German can launch this week while a language awaiting a native check waits until next week — and the original source language keeps running throughout. This per-language publish control means an unfinished translation never blocks the languages that are already correct, and nothing reaches the public until a human has decided that version is ready. It is the safeguard that lets a machine-translation first draft and human review happen on different days.
### Can respondents choose their own language?
Yes, optionally. Once more than one language is published, a language switcher can be exposed on the hosted page and the embeddable widget, letting respondents pick their preferred language while the form re-renders in that locale. It is optional because some deployments already route traffic to the right language at the campaign level and prefer to serve a single language directly. Whether respondents switch languages themselves or arrive on a pre-selected version, every translation answers to the same underlying form definition, so a submission in one language lands in the same place as any other, with identical validation, delivery, and analytics. There is no separate inbox per language to reconcile.
### Which plan includes multilingual form translation?
Thirty-language DeepL translation is included on the Business plan, which is $99 per month. It is not part of the Free, Starter, or Pro tiers, and it is not offered as a free add-on. Pricing is flat across all plans — Free at $0, Starter at $9, Pro at $29, and Business at $99 monthly — with yearly billing priced at ten times the monthly rate, equivalent to two months free. Paid plans include a 14-day trial, so a team that needs multilingual forms can verify the translation workflow before committing to Business. A full comparison of submission limits, custom domains, and the features each tier unlocks is on the pricing page.
### Is the translated content reviewed by a human or fully automatic?
The translation itself is automatic — DeepL generates each language version in seconds — but publication is not. Every translated language arrives as an editable draft rather than going live immediately, which gives a reviewer the chance to refine machine output before respondents encounter it. This matters most for strings where nuance carries weight: consent language, pricing, and calls to action benefit from a native speaker's read even when the literal translation is accurate. Treating DeepL output as a strong first draft, then publishing each language only after review, combines the speed of machine translation with the accuracy of human oversight, and per-language publish control is what makes that two-step workflow practical.
---
# File Upload Forms: How to Let People Send You Files (2026 Guide)
Source: https://forms.expert/blog/file-upload-forms
**On this page:** What Is a File Upload Form · How a File Upload Form Works · Build a File Upload Form in Plain HTML · Add File Upload to a Google Form · Add a File Upload Form in WordPress · File Types, Size Limits, and Security · Build One with Forms Expert
Sometimes a form needs more than typed answers, it needs a file: a resume attached to a job application, a photo with a support ticket, a signed PDF on an intake form, a logo on a design brief. A file upload form is how you let people send you those files without email back-and-forth. This guide explains how file upload forms work, walks through the plain-HTML, Google Forms, and WordPress routes, covers the file-type and size limits that matter, and is honest about what upload security does and doesn't mean. By the end you'll know which approach fits your situation and how to ship one quickly.
## What Is a File Upload Form
A file upload form is a form with a file field, a control that lets respondents attach one or more files (documents, images, PDFs) along with their other answers. When someone submits, the files are uploaded and stored somewhere the form owner can retrieve them, usually a dashboard, a cloud folder, or a notification with download links.
It solves a specific, common problem: collecting files from people who aren't in your systems. Instead of asking applicants to email a resume or customers to message you a screenshot, you give them one form that captures both their information and their files in a single, organised submission. The result is less back-and-forth, files tied to the right record, and a consistent place to find everything. The rest of this guide is about the different ways to build one, from raw HTML to a hosted form builder, and the trade-offs of each.
## How a File Upload Form Works
Under the hood, a file upload form relies on a single HTML element and a specific way of sending data. The file field is ``, which renders the familiar choose-a-file control (and, with the `multiple` attribute, lets people pick several at once). The important detail is the form's encoding: to send files, the form must use `enctype="multipart/form-data"`, which packages each file as a separate part of the request rather than trying to cram it into a normal text submission.
When the form is submitted, the browser sends that multipart request to a server, which receives the file, writes it to storage (a disk, or more commonly cloud storage like an S3-compatible bucket), and records a reference to it alongside the rest of the submission. The form owner then retrieves the files, by downloading them from a dashboard, getting them in a notification, or syncing them to a folder. Every file upload form, however it's built, follows this same shape: a file field, multipart encoding, server-side storage, and a way to retrieve. The differences between approaches are who handles the storage, validation, and retrieval, you, or the tool. The canonical technical references are MDN's pages on [the file input](https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Elements/input/file) and [sending form data](https://developer.mozilla.org/en-US/docs/Learn_web_development/Extensions/Forms/Sending_and_retrieving_form_data).
It's worth understanding why the encoding matters, because it's the part people miss. A normal form submission sends text as key-value pairs, which works for names and emails but can't carry the raw bytes of a file. The multipart encoding solves this by splitting the request into parts, one per field, so a file travels as its own binary chunk with its filename and type attached. Get the encoding wrong, by leaving it as the default, and the file simply won't arrive: the server sees only the filename as text. That single attribute is the difference between an upload that works and one that silently fails.
## How to Build a File Upload Form in Plain HTML
If you control a web page and a backend, the markup for a file upload form is short. Here's a minimal example that accepts a single PDF:
```
```
Three things make this work: `enctype="multipart/form-data"` (so the file is sent correctly), `type="file"` (the upload control), and the `accept` attribute (a hint that nudges the file picker toward PDFs). Add `multiple` to allow several files.
The catch is everything the markup doesn't do. The HTML only collects the file in the browser, you still need a backend at `/upload` to receive the multipart request, write the file to storage, validate it (type and size), guard against abuse, and give you a way to download it later. That's real work: you're responsible for storage costs, security, virus considerations, size limits, and retrieval. Note too that the `accept` attribute is only a convenience, it does not enforce the file type, so a determined user can still submit something else; real validation must happen on your server. For a one-off on a site you already run, raw HTML is fine. For anything you don't want to build and maintain, a hosted form handles the storage, validation, and retrieval for you, which is the trade-off the rest of this guide weighs.
It's also worth knowing the browser-side niceties you get for free and the ones you don't. You get the native file picker and, with the multiple attribute, multi-file selection; you don't get progress bars, drag-and-drop, image previews, or client-side size checks unless you add JavaScript for them. Those touches matter for a polished public form, which is another reason teams reach for a tool once the upload is more than a quick internal utility.
## How to Add File Upload to a Google Form
Google Forms supports file uploads with one significant catch. To add it, edit your form, add a question, and choose the **File upload** question type; you can set the allowed file types, the maximum number of files, and a size cap. Uploaded files land in a folder in the form owner's Google Drive, which is convenient if you already live in Google Workspace.
The catch is the sign-in requirement: **respondents must be signed in to a Google account to upload a file.** This is a frequent frustration, it's the reason people search for ways to accept Google Forms uploads without sign-in, because requiring a Google login adds friction and excludes anyone who doesn't have (or doesn't want to use) a Google account. For an internal form where everyone's on Workspace, it's a non-issue. For a public form, a job application, a customer request, a lead magnet, it can cost you submissions, and there's no native way around it in Google Forms itself. That single limitation is what pushes many public-facing file upload forms to other tools.
A couple of other Google Forms limits are worth noting. Uploads count against the form owner's Google Drive storage, so high-volume file collection can eat into your quota, and the file-type and size controls are basic compared with a dedicated tool. None of these is a dealbreaker for internal use; together with the sign-in requirement, they're why Google Forms is best for internal file collection and weaker for public-facing uploads.
## How to Add a File Upload Form in WordPress
On WordPress, file uploads come via a form plugin. Most of the popular form plugins (the well-known ones in the WordPress ecosystem) offer a file-upload field, sometimes on paid tiers, that stores uploads in your WordPress media library or a designated folder and attaches them to the form entry. The setup is generally: install the plugin, add a form, drag in a file-upload field, configure allowed types and size, and place the form on a page.
The trade-offs are worth knowing. A plugin keeps everything inside WordPress, which is tidy if that's your stack, but uploads then consume your hosting storage and the file-size ceiling is bound by your server's PHP upload limits (which you may need to raise). You're also responsible for keeping the plugin updated and for the security of files sitting on your host. For a WordPress-centric site this is the natural route; if you'd rather not store files on your own hosting or wrestle with PHP limits, a hosted form embedded into the WordPress page keeps the files (and the size limits) off your server.
## File Types, Size Limits, and Security
Three practical questions decide whether a file upload form is safe and usable: what types you accept, how big files can be, and what security actually covers.
**File types.** Restrict uploads to the types you actually need with a MIME allow-list, accept PDFs for a resume, images for a photo upload, rather than allowing anything. An allow-list is both a usability nudge and a security measure, since it narrows what can be sent. Remember that the browser's `accept` attribute is only a hint; enforcement has to happen server-side.
**Size limits.** Every upload form needs a per-file size cap, both to control storage costs and to stop oversized uploads. Sensible defaults are a few megabytes per file for documents and images, with a higher ceiling only where you genuinely need it (high-resolution images, large PDFs).
**Security, honestly.** This is where it pays to be precise rather than reassuring. Good upload hygiene means storing files safely, sanitising filenames (so a crafted name can't cause problems), recording a checksum to detect corruption or tampering, and limiting abuse with measures like a honeypot, rate limiting, and a CAPTCHA. What it does **not** automatically mean is antivirus scanning. Many hosted form tools, ours included, do not run a malware scanner on every upload, so you should not assume an uploaded file is malware-free just because it came through a form. If you accept executables or Office files from the public and need scanning, run uploaded files through a dedicated malware scanner in your own pipeline before opening them. OWASP's [File Upload Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/File_Upload_Cheat_Sheet.html) is the reference for doing uploads safely.
One more practical point: communicate the limits to respondents. A form that silently rejects a 12 MB file, or a .docx when you only accept PDF, just frustrates people and loses you the submission. State the accepted types and the size cap near the field, and show a clear error when something is out of bounds. Good upload UX is as much about telling people the rules up front as it is about enforcing them.
> **warning:** Be clear-eyed about scanning: storing, checksumming, and sanitising filenames is not the same as antivirus scanning. Forms Expert does not run a malware scanner at upload time, so treat files from public forms as untrusted and scan them yourself before opening if that's a risk for you.
## Build a File Upload Form with Forms Expert
If you'd rather not build and maintain the storage, validation, and retrieval yourself, a hosted form builder handles them. Here's how it works in Forms Expert, with the real defaults and limits so you can judge the fit, and the one genuine advantage over Google Forms.
The differentiator is that **respondents don't need to sign in** to upload a file, which removes the friction that costs Google Forms public submissions. You add a file field, pick a MIME preset (Documents, Images, PDF only, or Any), and the field accepts up to **5 files of 5 MB each by default**. The maximum single-file size is tier-bound, and so is total storage and your monthly submission count:
| Plan | Max file size | Total storage | Submissions / mo |
| --- | --- | --- | --- |
| Free | 5 MB | 100 MB | 100 |
| Starter | 10 MB | 1 GB | 1,000 |
| Pro | 25 MB | 10 GB | 10,000 |
| Business | 100 MB | 100 GB | 100,000 |
Uploaded files are stored in S3-compatible storage, SHA-256 checksummed (to detect corruption or tampering), and filename-sanitised; you retrieve them from the submissions dashboard. To be straight about it, as covered above, there's no antivirus scan at intake, and anti-abuse is a honeypot, IP rate limiting, and CAPTCHA rather than malware detection. Over-limit submissions are rejected at submit time rather than silently dropped, so you'll know.
If you outgrow a plan's storage or file-size ceiling, the fix is moving up a tier rather than paying per upload, the same flat, predictable model as the rest of the product. For most intake and application forms, the default of 5 files at 5 MB comfortably covers resumes, PDFs, and photos without any configuration.
Where a hosted upload field shines is on forms that already do other work, an application that also collects a resume, an intake form that needs a document, a support request with a screenshot. File uploads pair naturally with [conditional logic and multi-step forms](https://forms.expert/blog/conditional-logic-and-multi-step-forms) (show the upload field only on a relevant branch), with [multi-step forms](https://forms.expert/blog/multi-step-forms) (put the upload on its own step), and with [save and continue](https://forms.expert/blog/save-and-continue-forms) for longer forms where people gather documents over time. For intake and [lead capture forms](https://forms.expert/lead-capture-forms) specifically, collecting the file with the rest of the submission is the whole point. Start from the [home page](https://forms.expert/) to build one.
## Frequently Asked Questions
### What is a file upload form?
A file upload form is a form that includes a file field, letting respondents attach one or more files, such as documents, images, or PDFs, along with their other answers. When someone submits, the files are uploaded and stored where the form owner can retrieve them, typically a dashboard, a cloud folder, or a notification with download links. It solves the common problem of collecting files from people who aren't in your systems: instead of asking for files by email, you capture a person's information and their files together in one organised submission. Job applications with resumes, support tickets with screenshots, and intake forms with documents are all classic file upload forms.
### How do I create a form that lets people upload files?
You have three main routes. In plain HTML, add an input of type file inside a form with enctype set to multipart/form-data, then build a backend to receive, validate, store, and let you download the files, full control, but you handle the infrastructure and security. In Google Forms, add a File upload question, though respondents must sign in to a Google account. Or use a hosted form builder, which gives you a file field with built-in storage, type and size limits, and a dashboard to retrieve uploads, with no backend to maintain. Choose raw HTML for a one-off on a site you run, Google Forms for internal Workspace forms, and a hosted builder for public-facing forms you don't want to maintain.
### How do I add file upload to a Google Form?
In the Google Forms editor, add a question and choose the File upload question type. You can then set which file types are allowed, the maximum number of files, and a size limit, and uploaded files are saved to a folder in the form owner's Google Drive. The important limitation is that respondents must be signed in to a Google account to upload, which is fine for internal forms where everyone uses Google Workspace but adds friction for public forms. If you need to collect files from people who may not have a Google account, a hosted form builder that doesn't require respondent sign-in is usually a better fit.
### Can people upload files to a Google Form without signing in?
Not in Google Forms itself, file upload questions require respondents to be signed in to a Google account, and there's no native setting to turn that off. This is a common frustration for public-facing forms, because requiring a Google login adds friction and excludes anyone without an account. The usual workarounds involve third-party tools or add-ons, but the cleaner solution is to use a form builder whose file uploads don't require any respondent sign-in. Forms Expert, for example, lets anyone upload a file without logging in, which removes exactly the barrier that costs public Google Forms their submissions.
### What file types and sizes can a file upload form accept?
That depends on how you configure it, and you should configure it deliberately. Restrict file types to what you actually need using a MIME allow-list (for example, PDFs for a resume or images for a photo upload) rather than accepting anything, which is both more usable and more secure. For size, set a per-file cap to control storage and block oversized uploads, a few megabytes per file is sensible for documents and images, with a higher ceiling only where you genuinely need it. In Forms Expert, the default is up to 5 files of 5 MB each, with the maximum single-file size depending on plan (from 5 MB on Free up to 100 MB on Business). Always enforce type and size on the server, since the browser's accept attribute is only a hint.
### Are file upload forms secure?
They can be, but be precise about what secure means. Good practice covers storing files safely, sanitising filenames so a crafted name can't cause problems, recording a checksum to detect tampering or corruption, and limiting abuse with a honeypot, rate limiting, and a CAPTCHA. What it does not automatically include is antivirus scanning: many hosted form tools, including Forms Expert, do not run a malware scanner on every upload, so you should not assume a file is malware-free just because it arrived through a form. Forms Expert stores uploads in S3-compatible storage, SHA-256 checksums them, and sanitises filenames, but does not scan for malware. If you accept files from the public and that's a risk, run them through a dedicated scanner in your own pipeline before opening.
### How do I receive the files people upload?
It depends on the tool. With a plain HTML form, your backend receives the multipart request and you store and retrieve the files however you've built it. With Google Forms, uploads go to a folder in the form owner's Google Drive. With a hosted form builder like Forms Expert, uploaded files appear in the submissions dashboard alongside the rest of each response, where you can download them, and you're notified of new submissions. The practical advantage of a hosted tool is that the files are automatically tied to the right submission and kept in one place, so you're not matching loose email attachments to the right person by hand.
---
# Save and Continue Forms: Let Respondents Finish Later (2026 Guide)
Source: https://forms.expert/blog/save-and-continue-forms
**On this page:** What Is a Save and Continue Form · Why It Matters: Form Abandonment · How a Save and Continue Form Works · Partial Submissions vs Save and Continue · Best Practices · Add It with Forms Expert
Long forms ask a lot in one sitting. An application, a detailed intake, a multi-section registration, these often can't be finished in a single uninterrupted go, and when someone is forced to, many simply give up partway and never return. A save and continue form solves this by letting respondents save their progress and come back later to finish, instead of losing everything when they close the tab. This is a focused guide to that capability: what it is, why it matters for abandonment on long forms, how saving and resuming actually works, how it differs from a partial submission, and how to add it, with an honest account of the limits.
If your forms are short, you can skip this one: it's specifically for the long, interruptible forms where a saved draft is the difference between a finished application and a lost one.
## What Is a Save and Continue Form
A save and continue form (often called save and continue later) is a form that lets a respondent save their progress partway through and return later to complete it, usually via a link, rather than having to finish in one sitting. Their answers so far are stored, and when they come back, the form is repopulated where they left off.
The point is to remove the all-or-nothing pressure of a long form. Without it, someone who has to stop, to find a document, take a call, or simply think, loses everything and often doesn't bother starting again. With it, they save, deal with whatever interrupted them, and pick up where they were. It's a capability that matters most on exactly the forms that are hardest to finish in one go: applications, onboarding, intake, and any form long enough that an interruption is likely. The rest of this guide covers why that reduces abandonment, how it works under the hood, and how to set it up.
It helps to be clear about what save and continue is not. It isn't the same as autosave in a document, where every keystroke is persisted silently; it's a deliberate save action the respondent takes, producing a draft they can return to. It's also not a way for you to harvest half-finished responses, the data stays the respondent's draft until they choose to submit. Keeping those boundaries clear avoids both technical confusion and the privacy missteps that come from treating an unfinished draft as a submission.
The terminology varies by tool, save and continue, save and resume, save for later, save progress, but the idea is the same: a respondent-controlled pause-and-resume for a form that's too long to finish in one go. Throughout this guide, save and continue means exactly that, and where a specific tool's behaviour differs (especially on how long a draft lasts), it's worth checking the details rather than assuming.
## Why Save and Continue Matters: Form Abandonment
Form abandonment is when someone starts a form and leaves before submitting, and it rises sharply with length and effort. Rather than quote an invented percentage, here's the honest mechanism: every additional field, step, and moment of required effort is a chance for someone to stop, and the longer the form, the more chances there are. When stopping means losing all their progress, a single interruption can cost you the whole submission.
Save and continue attacks the most avoidable cause of abandonment, the interruption. A respondent who needs to find a reference number, check with someone, or upload a document they don't have to hand can save and return, instead of abandoning. The UX research is clear on the principle: long forms should reduce the cost of interaction and let people recover from interruptions, as Nielsen Norman Group covers in its [form design guidance](https://www.nngroup.com/articles/web-form-design/), and government services structure lengthy forms into small, manageable pages so progress is easy to make and to recover, as set out in the [GOV.UK Service Manual](https://www.gov.uk/service-manual/design/form-structure). The takeaway isn't a magic number; it's that for any form long enough to be interrupted, the ability to save progress directly protects completions you would otherwise lose.
It's worth being concrete about when this bites. Picture a job application that asks for employment history, references, and a document upload. A candidate starts at lunch, realises they need a former manager's email, and closes the tab meaning to come back. Without save and continue, returning means starting over, and many won't. With it, they reopen their draft that evening and finish. The longer and more document-dependent the form, the more of these everyday interruptions stand between a starter and a completed submission, and the more a save option recovers.
## How a Save and Continue Form Works
Mechanically, save and continue has a few moving parts. When a respondent saves, the form stores what they've entered so far, their answers, and usually the current step or last field, as a draft. To let them get back to it, the form issues a return mechanism: commonly a unique link (backed by a token) and/or a cookie in their browser, so reopening the form restores the draft. Some implementations email that return link to the respondent, which is why saving often asks for an email address, both to send the link and to identify the draft.
Two details matter for expectations. First, drafts don't last forever: there's an expiry window after which an unfinished draft is cleared, so save and continue is for finishing soon, not months later. Second, what counts as finished: a saved draft is not a submission, you only receive the response when the respondent returns and actually submits. Until then it's their in-progress draft, not your data. Understanding both, the expiry and the draft-versus-submission distinction, is the key to using the feature well and setting honest expectations with respondents.
It's also worth knowing how the return link relates to privacy. Because anyone with the link can open the draft, the link is effectively a key to the partially-entered data, so it should be treated like one: sent to the respondent's own email, not shared, and invalidated once the form is submitted. Tools that auto-delete the draft on submission and expire it after a set window are limiting how long that key stays useful, which is good practice. If a form collects sensitive information, this link-as-key behaviour is something to be deliberate about rather than an afterthought.
## Partial Submissions vs Save and Continue
These two terms get used interchangeably, but they're different ideas. A **partial submission** is incomplete form data captured by the form owner, often automatically, when someone abandons a form; the owner gets whatever was entered so far, even though the respondent never submitted. **Save and continue** is respondent-driven: the person deliberately saves their own progress to finish later. One is mainly a lead-recovery tool for the owner; the other is a convenience for the respondent. They can overlap, but the intent and the data flow differ.
| Aspect | Partial submission | Save and continue later |
| --- | --- | --- |
| Driven by | The form owner (often auto-captured) | The respondent, deliberately |
| What's kept | Whatever was entered before abandoning | The respondent's draft, to resume |
| How it resumes | Owner may follow up; respondent may not return | Respondent returns via a saved link |
| Main purpose | Recovering leads from abandoned forms | Letting people finish a long form later |
Which you want depends on your goal. If you're trying to recover leads who drop off, partial submissions (capturing what they entered) is the relevant idea, though it carries its own consent considerations, since you're storing data someone didn't submit. If you're trying to help genuine applicants finish a long form, save and continue is the respondent-friendly choice. This guide is about the latter, but it's worth knowing the distinction so you ask for the right feature.
There's also a compliance angle worth flagging. Because a partial submission stores data the person never chose to submit, it can raise consent and data-minimisation questions under regimes like GDPR: you're keeping personal data from someone who didn't complete the action. Save and continue is cleaner on this front, since the respondent deliberately saves their own draft and controls whether to come back. If you're in a regulated context, that difference is worth weighing before enabling automatic partial-submission capture.
## Best Practices for Save and Continue Forms
A few practices make save and continue genuinely useful rather than confusing.
**Make the save option visible up front.** People decide whether to start a long form partly on whether they can pause it. Showing a Save and continue later option early reassures them it's safe to begin. **Set expectations about expiry.** Tell respondents how long their draft will be kept and, if you email a return link, that they should use it within that window, surprise expiry is worse than no save feature at all. **Be clear about what saving needs.** If saving requires an email (to send the return link), say so, and explain it's used to let them resume. **Combine it with multi-step.** Save and continue and [multi-step forms](https://forms.expert/blog/multi-step-forms) are natural partners: long forms benefit from both being broken into steps and being resumable, so a saved draft returns the person to the right step. **Confirm the save.** When someone saves, show a clear confirmation (and the return link), so they trust their progress is safe.
Accessibility matters here too: the W3C WAI [multi-page forms guidance](https://www.w3.org/WAI/tutorials/forms/multi-page/) warns against time limits that could cut people off, an expiry window should be generous and clearly communicated, never a silent cutoff mid-task.
A couple more worth doing. Don't force a save to finish, make it optional, since most people will complete in one go and only some need to pause; a mandatory save step adds friction for everyone. And test the resume flow yourself, save a draft, close the browser, and return via the link, because a save feature that doesn't reliably restore the right state is worse than none: it promises safety and then loses work. The whole value is trust that progress is genuinely safe, so the resume path has to be solid.
One placement tip: put the save control where the effort is. On a multi-step form, a save option at each step boundary matches where people naturally pause; on a single long page, keep it visible as they scroll. The goal is that the moment someone feels the urge to stop, the save option is right there, not buried, so a pause becomes a save rather than an abandonment.
## How to Add Save and Continue Later in Forms Expert
Forms Expert offers save and continue later as a capability you can enable on a form, here's exactly what it does, stated precisely so you know what you're getting. When enabled, the form shows a **Save and continue later** option. Saving stores the respondent's data, their current step, and last field as a **draft kept for 7 days**, resumable via a **token-based return link (and a cookie)**. You can optionally **require an email** at save time, used to send the return link. When the respondent comes back and submits, the draft is converted to a real submission and **auto-deleted**, drafts don't pile up, and unfinished ones are cleared after the 7-day window.
> **note:** Be precise about the limits: saved drafts are kept for 7 days, not indefinitely, and a draft is not a submission until the respondent returns and submits. Save and continue is a feature you enable on a form rather than something on by default, so check it's available on your plan and turn it on where a form is long enough to need it.
Because of the 7-day window, the feature is designed for finishing soon after an interruption, not for saving a form for weeks. That's the honest framing: it protects the common case (someone gets interrupted and comes back the same day or that week) rather than promising indefinite storage. It pairs naturally with the rest of the long-form toolkit, [multi-step forms](https://forms.expert/blog/multi-step-forms) to break the form up, [file uploads](https://forms.expert/blog/file-upload-forms) for the documents a long application needs, and [conditional logic](https://forms.expert/blog/conditional-logic-and-multi-step-forms) to keep it relevant, and it fits the prime use cases of [registration and intake forms](https://forms.expert/registration-forms) where applications are genuinely long. If your forms are short enough to finish in one go, you don't need it; if they're not, it's the difference between a saved draft and a lost applicant. Start from the [home page](https://forms.expert/) to set it up.
One last honest note on fit: save and continue is a targeted feature, not a headline one. It quietly protects completions on your longest forms and does nothing for your short ones, which is exactly as it should be. Enable it where a form is genuinely long or document-dependent, communicate the 7-day window, and leave it off elsewhere, that's the whole job, done well.
## Frequently Asked Questions
### What is a save and continue later form?
A save and continue later form is a form that lets a respondent save their progress partway through and return later to finish it, usually via a link, instead of having to complete it in one sitting. Their answers so far are stored as a draft, and when they come back, the form is repopulated where they left off. The purpose is to remove the all-or-nothing pressure of a long form: someone who has to stop to find a document or take a call can save and resume rather than lose everything. It's most valuable on long forms, applications, onboarding, and detailed intake, where an interruption is likely and abandonment is costly.
### What is a partial submission?
A partial submission is incomplete form data that the form owner captures when someone starts a form but abandons it before submitting, so you receive whatever was entered up to that point even though the respondent never finished. It's primarily a lead-recovery idea: it lets the owner follow up with people who dropped off. This is different from save and continue, which is respondent-driven, the person deliberately saves their own progress to finish later. One captures abandoned data for the owner; the other lets the respondent resume. Note that capturing partial submissions carries consent considerations, since you're storing data the person didn't choose to submit, so handle it carefully and transparently.
### How do respondents resume a saved form?
Through a return mechanism the form issues when they save, most commonly a unique link backed by a token, and often a cookie in their browser so reopening the form restores the draft. Many implementations email that return link to the respondent, which is why saving frequently asks for an email address: it's used both to send the link and to identify the draft. When the respondent follows the link (or returns in the same browser), their saved answers are repopulated and they continue from where they left off. The practical advice is to keep that return link safe and use it before the draft expires.
### How long is a saved form kept before it expires?
It depends on the tool, and you should always check the specific window rather than assume drafts last forever, because they don't. In Forms Expert, a saved draft is kept for 7 days, after which an unfinished draft is cleared. That window is deliberately designed for finishing soon after an interruption, returning the same day or that week, rather than for saving a form for months. The key point for setting expectations is to tell respondents how long they have, so a draft never expires as an unpleasant surprise. If your process genuinely needs people to return after weeks, save and continue with a short expiry isn't the right mechanism.
### Does saving progress require an account or an email?
Usually not a full account, but often an email. Save and continue typically works through a return link backed by a token and a browser cookie, so a respondent can resume without creating an account. Many tools, including Forms Expert, can optionally require an email at save time, which is used to send the return link so the person can get back to their draft even on another device. So the common pattern is: no account needed, but an email may be requested purely to deliver the resume link. If you enable an email requirement, tell respondents why, so it reads as helpful rather than as an unexpected ask.
### Which form builders offer save and continue later?
Several do, though it's often a feature you enable rather than a default, and availability varies by plan. Among WordPress plugins, Gravity Forms is well known for a save-and-continue option, and Jotform offers a save-and-continue-later feature as well; other builders provide partial-submission or save-progress capabilities under various names. Forms Expert offers save and continue later as an enableable capability, storing a draft for 7 days that's resumable via a return link. Because the naming and the exact behaviour (expiry window, whether an email is required, what's stored) differ between tools, the practical advice is to confirm the specifics, especially how long drafts are kept, on whichever builder you choose.
### How does save and continue reduce form abandonment?
It reduces abandonment by removing its most avoidable cause: the interruption that forces someone to start over. On a long form, the risk of abandonment rises with every field and every moment something might pull the person away, a call, a missing document, a detail to check. When stopping means losing all their progress, a single interruption can cost the whole submission. Letting people save and return turns that interruption from a dead end into a pause: they deal with whatever came up and finish later from where they left off. It doesn't fix abandonment caused by a form simply being too long or asking too much, those need fewer or better-grouped fields, but it directly recovers the completions lost purely to interruptions, which on long forms is a meaningful share.
---
# Multi-Step Forms: How to Build Them and Why They Convert (2026)
Source: https://forms.expert/blog/multi-step-forms
**On this page:** What Is a Multi-Step Form · Why Multi-Step Forms Convert Better · How to Build One (No-Code) · How to Build One in Code · Multi-Step Form Best Practices · Examples and Design Patterns · Build One with Forms Expert
A long form is intimidating. Faced with twenty fields on one screen, a lot of people take one look and leave. A multi-step form fixes that by showing the same questions a few at a time, across several steps with a progress indicator, so the form feels manageable instead of overwhelming. This guide covers what a multi-step form is, the honest reasons it tends to convert better, how to build one with no code or in code, the best practices (including accessibility), and a set of real-world examples you can borrow. The aim is a complete, practical reference, not a sales pitch.
## What Is a Multi-Step Form
A multi-step form (also called a multi-page or wizard form) is a single form split across multiple steps, with only a few related fields shown at a time and a progress indicator that tells people where they are. Instead of scrolling through one long page, the respondent answers a small group of questions, clicks next, and moves to the following step, often with the option to go back.
The key parts are a sequence of steps, a way to move forward and back, validation on each step (so errors are caught before moving on), and a visible progress cue such as Step 2 of 4 or a progress bar. It's worth distinguishing the layout from the logic: a multi-step form is about how a form is paginated, whereas conditional logic is about which fields or steps appear based on earlier answers. The two pair well but aren't the same thing, and we cover how they work together in our guide to [conditional logic and multi-step forms](https://forms.expert/blog/conditional-logic-and-multi-step-forms). This article focuses on the multi-step layout itself, why it helps, how to build it, and how to design it well.
One more clarification, since the terms get muddled: a multi-step form is still a single submission. The respondent moves through steps, but they're filling in one form, and you receive one complete record at the end, not separate submissions per step. The pagination is purely a presentation choice; the underlying form, and the data you get, is unified. That's what separates a multi-step form from a sequence of linked, separate forms.
## Why Multi-Step Forms Convert Better
It's tempting to quote a precise conversion-lift percentage here, but those numbers vary wildly by form, audience, and design, and a made-up figure helps no one. What's well understood is the mechanism, the reasons a multi-step form tends to outperform a long single page when it's done well.
**Reduced perceived effort.** A short first step looks easy, and easy invites a start. The same questions feel lighter spread across steps than stacked on one daunting page, even though the total work is identical. **Progress feedback.** A visible Step X of N or a progress bar gives a sense of momentum and a reason to finish, people don't like abandoning something they're most of the way through. **Early, easy wins build commitment.** Asking the simplest question first (an email, a name, a single choice) earns a small commitment that makes people more likely to continue, a well-documented effect in behavioural research. **Focus.** Fewer fields on screen means less cognitive load and fewer chances to get distracted or intimidated.
The honest caveat: multi-step isn't automatically better. Splitting a genuinely short form into steps just adds clicks for no benefit, and a clumsy implementation (no back button, lost data, unclear progress) can hurt. The lift comes from the design, not the format alone, which is what the best practices below are about.
It's also worth naming who benefits most. Multi-step pays off most clearly on longer or higher-friction forms, applications, detailed quote requests, registrations with payment, where a single page would be genuinely daunting. On a three-field newsletter signup it adds nothing and may even slow people down with an extra click. So the question isn't whether multi-step is better in the abstract, but whether your form is long or demanding enough to benefit from being broken up. The longer and more intimidating the form, the more the format helps.
## How to Build a Multi-Step Form (No-Code)
With a form builder, building a multi-step form is a matter of configuration, not coding. The general process is the same across tools.
First, **group your fields into logical steps**, related questions together, simplest first. A registration form might be: basic details, then preferences, then payment. Second, **add a step break** between each group (in a good builder this is a single action that turns a long form into a paged one). Third, **enable a progress indicator** so respondents see how many steps remain. Fourth, **turn on per-step validation** so required fields are checked before someone can advance, catching errors early rather than at the very end. Fifth, **allow back navigation** so people can fix an earlier answer without losing their place. Finally, **test the flow** end to end on mobile and desktop, the experience of moving between steps is where multi-step forms succeed or fail.
The whole point of the no-code route is that the builder handles the step state, validation, and progress UI for you, so you spend your time on the field grouping and wording rather than on the plumbing. If your form is long, also consider letting people save and return, covered below.
A practical tip on grouping: a good test is whether you can give each step a short, honest title, Your details, Your project, Payment. If a step resists a clean label, it's probably mixing unrelated questions and should be regrouped. Titles also double as the progress labels respondents see, so getting the grouping right improves both the structure and the experience at once. Spend your effort here; it's the decision that most affects how the finished form feels.
## How to Build a Multi-Step Form in Code
If you're building a form by hand, the core idea is simple: render all the steps, then show only one at a time and move between them. Here's the minimal pattern in plain JavaScript:
```
// Show one step at a time and move between them
const steps = document.querySelectorAll('.step')
let current = 0
function showStep(i) {
steps.forEach((step, n) => { step.hidden = n !== i })
}
function next() {
// validate the current step before advancing
if (current < steps.length - 1) showStep(++current)
}
function back() {
if (current > 0) showStep(--current)
}
showStep(current)
```
That's the skeleton: a set of step containers, an index for the current step, and next/back functions that move it. In a real build you'd add per-step validation inside `next()` (don't advance if required fields are empty), update a progress indicator, and persist answers so a refresh doesn't wipe them. Use semantic grouping, a `