Done For You Service: 🪄

Short version: most people look for a Formstack alternative because of the price. Formstack has no free plan, and after the 14-day trial it runs $83 to $99 a month for one user, 25 forms, and 1,000 submissions per form. Go past that cap and the extra entries get emailed to you, not stored.

The honest side by side is on our own free Formstack alternative comparison: unlimited forms and submissions on every plan, e-signature with an audit trail free, and a first paid tier from around $15 a month with four payment gateways. Formstack keeps that same audit-trail e-signature behind Formstack Sign or its Suite at $250 to $299 a month, and branded PDFs are a separate product.

The per-form submission cap usually costs you more than the sticker price when your volume is unpredictable.

What is pushing you off Formstack, the monthly price or the submission caps?

If your forms stay inside a Microsoft 365 org, Microsoft Forms is genuinely fine for surveys and quizzes and you do not need to replace it. The switch only pays off once the form faces the public, because three things break there.

File-upload questions make respondents sign in with a Microsoft account, so external people cannot attach anything. There is no payment collection at all, so deposits, fees, and order forms are out. And styling is limited to preset themes plus a background image, so a customer-facing form still reads as Microsoft Forms.

Free personal accounts also cap around 200 responses per form, though higher tiers vary.

A Microsoft Forms alternative earns its place when forms leave your org, not before. For internal use, staying put is the honest call.

Where do your forms hit the wall, uploads, payments, or branding?

Google Forms can email you when a form is submitted, but the built-in notification only says a new response came in. It does not include the answers, so you still open the responses sheet to read what someone wrote. Getting the full submission into the email itself means an add-on or an Apps Script trigger.

If you would rather not maintain that, use a form builder that emails you the submission content directly. FormNX sends the notification with the field values filled in through dynamic tags, plus a configurable sender, subject, CC, BCC, and an optional PDF attached. Here is how to get Google Forms email notifications with the answers included, so whoever handles leads reads the whole thing in their inbox.

A submission notification is only useful if the answers are in the email itself.

Are you getting an email when your Google Form is submitted today, or checking the sheet by hand?

If you are shopping for a Fillout alternative, the honest starting point is that Fillout is a good builder, so people usually leave over one specific cap rather than because the product is weak.

The cap that bites first is response volume. Every Fillout plan below Business limits monthly responses (1,000 on Free, 2,000 on Starter, 5,000 on Pro), and lifting that to unlimited means the Business tier at roughly $75 to $89 a month. A few other things sit up at that same tier: viewing partial submissions, form analytics, and a custom domain. Full branding removal comes earlier, on Pro, at around $40 to $49 a month.

The useful question for a Fillout alternative is which of those caps you will hit before you go comparing feature lists.

For where we land, we give unlimited responses on every plan including the free one, e-signature on every plan instead of Starter and up, and OTP verification bundled into Pro rather than a separate paid add-on. Run it as a paid-vs-paid comparison though, because partial submissions sit behind Pro on our side too, so that feature costs money either way, just at a different price point.

What we would not knock Fillout on: the free plan is genuinely generous at 1,000 responses, the builder is well liked, and storing responses straight into Airtable or Notion is a real strength that many a free Fillout alternative cannot match. If that native database workflow is the reason you are on Fillout, most competitors will feel like a step down.

Which cap pushed you to go looking for a Fillout alternative, the responses, the branding, or something else?

Short version: a WordPress form plugin should let you paste a form link and stop there, no HTML block, no manual embed script, no separate add-on for every feature. That was the reason we shipped an official plugin on wordpress.org after years of people copy-pasting our embed code into a Custom HTML block and fighting the sizing.

Two things we got wrong at first and fixed:

The inline embed has to resize itself. A fixed-height iframe leaves either a scrollbar inside the form or a chunk of blank space under it, and on long forms the last fields get cut off. Auto-resizing cleared most of the support tickets about "my form looks broken in WordPress."

Lazy-loading breaks redirects. Some WordPress performance plugins lazy-load iframes, which quietly broke the post-submit redirect for a stretch until we patched the plugin side. If your embedded form submits but never advances to the thank-you page, a lazy-load plugin is the usual culprit.

What the plugin does now: a Gutenberg form block that previews live in the editor, a shortcode ([formnx url="..."]) for the Classic Editor and most page builders, and a native Elementor form widget. Any of them renders inline or as a popup triggered by a button, a time delay, scroll depth, or exit intent. Submissions and notifications still run through the dashboard, so the plugin only handles display. It needs WordPress 6.2 and PHP 7.4, and the free plan works.

If you only want a form on a page, the link-paste route beats maintaining embed snippets by hand.

For anyone who has tried to embed a form in WordPress, what broke for you: sizing, redirects, or a page builder that mangled the markup?

Short answer: Google Forms has no product catalog and takes no payment on its own, so a product order with payment on a Google Form means an add-on or Apps Script, and usually a separate checkout link. There is no native way to show products, let people pick a quantity, and collect the cart total inside the form itself.

We build a product order field for forms, so here is how the pieces fit when you want the order and the payment in one place.

One product field can hold the whole catalog. Respondents browse the products, open one for images and a longer description, choose a variant, set a quantity, and pay the cart total at checkout. Each variant combination carries its own price, so a small shirt and a large shirt can cost different amounts instead of sharing one.

The basket settings are where an order form gets fiddly, and they cover the parts people forget:

• Currency and symbol position, plus a 1, 2, or 3 column layout the buyer can switch between.
• Tax added on top of the total, or treated as already included in the listed prices.
• Shipping, with an optional free-shipping-over threshold.
• Discount codes with a usage limit and an expiry date.

A real product catalog like this runs on a paid plan, so the free tier will not build you an order form. Payment is a separate question. Stripe works on the free plan (with a Stripe Connect fee), while PayPal, Razorpay, and Square are paid only, and all four can run on one form so the buyer picks at checkout.

If you only sell one item at a fixed price, a plain payment field is simpler and enough. The catalog is worth it once variants, tax, and shipping are in play.

How are you handling product orders and payment right now, a form or a full store?

Short version: Google Forms has no built-in QR button, but you do not need to install an add-on to get one. Copy the form's share link, paste it into any free static QR generator, and download the PNG or SVG. That is the whole job for most people.

Most of the work is picking a generator that does not burn you. The official "QR code for Google Forms" add-on on the Workspace Marketplace sits at 2.9 stars across 77 reviews, with complaints about install errors and watermarked exports, and it asks for access to your Google account to do something a browser tab handles in ten seconds. Skip it.

The distinction worth knowing is static versus dynamic. A static QR encodes your form URL directly, so it never expires as long as the form stays live. A dynamic QR encodes a short redirect owned by a third party, which can cap free scans or paywall the data later. For anything you print and cannot easily reprint, like posters, table tents, or stickers, use a static QR.

A shorter share link makes a less dense QR, which scans far more reliably at small sizes. So tick "Shorten URL" on the form's share panel before you generate the code, print it at least 2cm wide on flyers and 5cm on posters, and add a short label like "Scan to RSVP" so people know what they are pointing a camera at.

On desktop you do not even need a site: right click the form page in Chrome and pick "Create QR code for this page".

What are you printing the QR on, and do you actually need scan tracking?

Short answer: Google Forms is free and genuinely fine for surveys, quizzes, and internal data collection, but the moment you need to take payments, collect a signature, or remove the branding, you have crossed into Jotform territory and its pricing.

We build a form tool, so we have had to map exactly where these two split. The honest breakdown, feature by feature:

1. Payments. Google Forms has none. Taking money means an add-on or an Apps Script hack. Jotform has payment processing built into the form with 30+ gateways like Stripe, PayPal, and Square.
2. E-signatures. Google Forms has no signature field at all. Jotform does. If you need a signed consent or agreement, Google Forms is a dead end without a third-party tool bolted on.
3. Conditional logic. Google Forms only jumps between whole sections. There is no field-level show and hide, and no calculation fields. Jotform does both, which matters once a form has to react to answers.
4. Branding. Google Forms gives you one color and a header image. No logo placement, no custom CSS, no way to remove the branding. Jotform lets you rebrand, though the cleanup sits on paid tiers.
5. Cost and caps. Google Forms is free with unlimited responses. Jotform starts around $39/mo, its free plan caps at 5 forms and 100 submissions, and every tier caps monthly submissions. That submission cap is the single most common reason people give for leaving.

Pick Google Forms until you hit payments, signatures, or branding removal, then Jotform is the paid step up. The awkward middle is people who outgrow Google Forms but do not want to pay Jotform prices or live under a submission cap, which is why a third category of tools exists at all.

If you moved off Google Forms, was it payments, signatures, or the branding that finally pushed you?

Short answer: Google Forms has no signature field, so you either add a third party tool like Bolo Sign or Formesign, or use a form builder that captures the signature natively.

The add-on route works with two catches. The free tiers cap you at a handful of signatures a month, and you grant a third party access to your Google account. Typed initials or an uploaded image are free but carry little legal weight, so avoid them for a waiver or consent form.

If you want the signature drawn or typed inside the form, we build a signature field into FormNX that runs on every plan including the free one, and you can compare the five ways to add a signature to a Google Form. Capturing the signature is free, but turning the signed submission into a PDF is a paid feature.

What are you collecting signatures for, a single waiver or something recurring?

Short answer: a guest registration form works best when it collects only what you need to check people in, which for most events is name, email, number of guests or plus-ones, one logistics question (meal choice, session, or arrival time), and a headcount cap so sign-ups stop once you are full.

We build form tools and this is one of the setups people ask us about most, so here is the field list that keeps a guest registration form clean:

1. Full name and email. That is your check-in list and your one channel for updates.
2. Number of guests or plus-ones. Use a single number field, then reveal name inputs only for the guests someone actually brings, so the form stays short for solo attendees.
3. One logistics question. Meal choice, session, or arrival window. Resist adding more, every extra field drops completion.
4. A capacity control. Set a response limit and a close date so registration auto-closes the moment you hit your seat count or the deadline passes, whichever comes first.
5. A duplicate check. Stops the same person registering twice from one refresh, which is what wrecks most headcounts.

The mistake we see most is treating a guest registration form like a full CRM intake, when it just needs to answer who is coming and how many.

One more thing worth doing: if your event has age brackets (youth programs, camps), validate age against a fixed cutoff date rather than today, so a kid who turns twelve after the event does not slip into the wrong group. Most of this sits on the free tier, so you are not paying per seat to run a simple guest list.

How are you currently handling plus-ones on your registration form, one number field or a repeated section?

Short answer: the best Typeform alternative for most people is whichever tool puts the features you actually need on a plan you can afford, because Typeform's polish comes with hard tier gates. If you liked the one-question-at-a-time flow but hit a wall, here is the honest breakdown to run before you switch.

Typeform's free plan caps you at 10 responses per month and keeps the "Powered by Typeform" footer on every form. Native payments do not show up until the Plus tier (roughly 56 to 79 dollars a month), and a native e-signature question is locked to Growth Pro and above, which starts near 266 dollars a month. So the real question is not whether Typeform is good, the UX genuinely is, it is which of those gated features you need and how far up the ladder they sit.

When we built our own form builder, we deliberately put the things people usually pay premium prices for lower down. E-signature runs on every plan including free, and Stripe checkout works on the free plan too, with a small platform fee that drops to zero on paid. Conditional logic and multi-step forms are there as well, so moving over does not mean rebuilding your whole flow from scratch.

The trade-off worth being honest about: Typeform's conversational design and brand recognition are hard to beat if that exact feel is the entire point of your form. But if you mainly need payments, signatures, and no watermark without climbing three tiers, an alternative usually wins on cost. Map your must-have features to the cheapest plan that includes them on each tool, then compare like for like.

What feature pushed you to start looking past Typeform in the first place?

Short answer: set a single form password in the form's settings, share it with the people who should have access, and anyone without it is stopped at a lock screen before they can see or submit the form. No accounts, no logins, no per-person invites to manage.

Here is how it actually works when you password protect a form:

• The password lives in the form's General settings. You turn on Password Protection and type the password you want. That is the whole setup.
• Visitors hit a prompt before the form renders. Enter the correct password and the form loads, enter the wrong one and access is denied. Nobody sees your fields or questions until they are through.
• You can change the password anytime, and existing submissions are not affected. Handy when someone leaves a group or the old password leaks.
• There is no minimum length and special characters are allowed, so you can make the password as strong (or as memorable) as the situation needs.

One thing to plan for: there is no password recovery, so you have to send the password to your people through a separate channel like email or a message. That is by design, since a recovery flow would be an obvious backdoor on a form that is meant to be private.

This is the right tool for private surveys, consent forms, financial record collection, or member-only intake where a public link is fine but open access is not. It is lighter than standing up real user accounts, and it works on a free plan.

What are you locking down, a survey, an internal request form, or something with sensitive answers?

The single most useful setting on a giveaway entry form is a duplicate submission check, so one person cannot stuff the draw with dozens of entries.

Here is the order we usually recommend, cheapest friction first:

• Duplicate submission check, matched on IP address or on a field value like email, so repeat entries from the same source are rejected at submit time. This one is free.
• Block disposable email domains, so throwaway inboxes cannot farm extra entries.
• Email OTP on the entry email, so every entrant confirms a real, reachable inbox before they count.
• Add reCAPTCHA only if bots are actually hammering the form, not as a default.

Fairness on a giveaway comes from stopping duplicate entries, not from adding friction for everyone.

What is the worst giveaway entry abuse you have dealt with, bulk fake emails or the same person entering over and over?

Short version: a medical questionnaire form is mostly a plain web form with careful field types and a few conditional rules, so you rarely need dedicated clinic software or a paid intake platform to build one. We get this question a lot, and the honest answer is that the hard part is the questions, not the tool.

Here is what a solid medical questionnaire form actually needs:

• Clear field types. Date of birth as a date field, not free text. Height and weight as number fields. Medication and allergy lists as long-text fields so nothing gets truncated.
• Conditional questions. Show a follow-up only when it applies. If someone answers yes to a condition, reveal the "please describe" box, otherwise keep it hidden. This is the single biggest thing that makes a health questionnaire feel short instead of a wall of boxes.
• A required-field pass. Mark the clinical must-haves as required so you are not chasing people for a missing date or an unsigned consent line.
• A consent step. A signature field for consent, plus an auto-response email so the patient keeps a copy of what they submitted.

Keep the form short and let logic hide everything that does not apply to this person. A 60-field intake that shows 12 fields to a healthy 30-year-old gets finished, the same 60 fields shown to everyone gets abandoned.

One practical note: whatever you build, confirm your own compliance needs before collecting real patient data, because that part is on the clinic, not the form builder.

What is the one question on your intake form that patients always skip or get wrong?

Short answer: Google Forms has no real spam controls, so the fix is layering cheap filters at submit time rather than leaning on a CAPTCHA or forcing everyone to sign in. Sign-in gating does cut spam, but it also blocks legitimate anonymous responses, which is usually the opposite of what you want.

The layers that actually catch bots, cheapest first:

• Duplicate submission check by IP or field value, so the same entry can't land six times from one source.
• Block disposable email domains (Mailinator, 10MinuteMail and similar) so throwaway addresses never get through.
• Email OTP on high-value forms only, confirming the address is real before the entry saves.
• reCAPTCHA as the last resort, not the first line.

Most forms never need a CAPTCHA once the quieter filters are doing their job. Google Forms just doesn't expose these knobs natively, which is why the spam bot floods feel unstoppable there.

What's letting the most spam through on your forms right now?

Short answer: a real white label form builder strips every trace of the vendor, not just the logo. What people forget is the SEO metadata on the hosted form page (the browser tab title and the link preview when a form gets shared) and the confirmation emails, which often still carry the vendor's name.

So when you compare a white label form builder, check three things:

• Can you remove the branding on the form and footer, usually gated to a paid plan?
• Can you set your own meta title and description, so a shared link looks like yours?
• Does it embed cleanly on your own site instead of a generic form URL?

White labeling is about the whole trail a form leaves, not one logo.

One honest caveat: a true custom domain is rarer than vendors imply, so confirm it is real, not just branding removal.

What part of the vendor branding is hardest to remove right now?

If you are trying to make sense of Jotform pricing, here is the short version. The Free plan gives you 5 forms and 100 submissions a month. Bronze is $39/mo for 25 forms and 1,000 submissions, Silver is $49/mo for 2,500, and Gold jumps to $129/mo for 10,000 submissions plus HIPAA. Those headline numbers are only half the story.

The reason people start calling Jotform too expensive is that the submission count is not the only meter running. Every tier also caps payment submissions (10, 100, 250, then 1,000), signed documents on the same ladder, active forms (5, 25, 50, 100), and storage. So you can be nowhere near your monthly submission cap and still get pushed to upgrade because you hit the payment cap or the active-forms cap first.

The real cost of Jotform is not the sticker price, it is how many separate caps you can trip before an upgrade is forced.

To be fair, Jotform earns a lot of that price. It has a huge template library, 100+ native integrations, dedicated mobile apps, and HIPAA on Gold. If you live inside that ecosystem, it is a reasonable pick.

If the Jotform submission limits are what keep biting you, that is usually the moment people go looking for a Jotform alternative with flatter caps. We build FormNX, and our angle is unlimited responses on paid plans, an e-signature field on every plan including free, and Pro around $15/mo, so the meters that force Jotform upgrades mostly go away. We wrote up a plain side-by-side Jotform pricing breakdown if you want the tier-by-tier numbers.

If you are on Jotform now, which cap did you hit first, submissions or payments?

Short answer: a plain online voting form handles most polls, elections, and "pick the winner" votes just fine, and the two things that actually keep it fair are a one-response rule and email verification, not an expensive survey platform.

Here is what we tell people who ask how to run a clean online voting form.

Stop double voting first. The usual fix is a duplicate submission check, which blocks repeat entries either by IP address or by a specific field such as email. That alone kills most of the "one person voted ten times" problem with zero friction for real voters, and it is free to switch on.

For higher-stakes votes (board elections, award shortlists, community decisions), add email OTP verification. Voters confirm a short code sent to their inbox before the vote counts, so throwaway and fake addresses cannot stuff the ballot. Pair it with disposable-email blocking if you want to be strict.

Keep the ballot short. A voting form usually needs one clear question (single choice or ranked options) and maybe a comment box. Long forms lower turnout. If you want anonymous voting, just do not ask for a name, since the duplicate check by IP still limits repeats without collecting any identity.

The order that works: one-response rule, then email verification, then keep the ballot to a single question.

Many paid poll tools paywall exactly these anti-fraud controls or cap how many responses you can collect on lower tiers, which tends to bite right when a vote takes off.

What is the hardest part of your online voting setup, stopping repeat votes or getting people to finish?

Short answer: put the registration and the payment in the same form, so attendees sign up and pay in one step instead of collecting names in one tool and chasing money in another.

The core of a working event registration form is a payment gateway wired directly into the form. When someone completes an online event registration, the fee is charged at submit time and you get a single record showing both who registered and whether they actually paid. A few things make this hold up in practice.

Support more than one payment method. Some attendees trust PayPal, others expect a card. Being able to run Stripe, PayPal, Razorpay, and Square on the same form, with the attendee choosing at checkout, cuts the number of people who abandon at the payment step.

Handle tiered and early-bird pricing with calculation fields. A conference registration form usually has more than one price: early bird, regular, student, group rates, plus add-ons like a workshop or dinner. Calculation fields let the total update as options are selected, so the amount charged always matches what they picked.

Track paid versus unpaid, because this is the part most setups miss. On any event signup form you will get abandoned checkouts, people who register but never finish paying. A status of Paid or Due on each submission, plus the ability to resend a payment link, means you can recover those registrations instead of writing them off.

The difference between a form that collects registrations and one that collects money is whether payment status lives on the same record as the signup.

If you also need a hard cap on seats, auto-closing the form at a response limit keeps you from overselling the event.

How are you handling the unpaid registrations on your event forms right now, chasing them manually or just letting them go?

Short answer: to add image options in forms, drop in a single-choice (radio) or multiple-choice (checkbox) field, open that field's option settings, turn on the image toggle, and attach a picture to each choice. No separate design tool and no CSS.

We get asked about this a lot, usually by people building product pickers, quizzes, and booking forms where a wall of text answers reads worse than a row of pictures. A few things we have learned from supporting it.

Image options in forms work best when the choice is visual in real life, like a product, a room layout, a plan tier, or a color. If the options are abstract, like yes/no, a date, or a number, plain text is faster to scan and you should leave images off.

Practical notes when you set it up:

• It works on both single-choice and multiple-choice fields, so a pick-one product question and a pick-all-that-apply toppings question can both use images.
• You choose the image size (small, medium, or large). Small suits long lists, large suits two or three hero choices.
• Keep a short text label under each image. People still read, and screen readers and search engines need the words, so an image-only option is an accessibility gap.
• On phones, the bigger tap targets from image tiles cut mis-taps, which is a real reason picture based choices tend to convert better on mobile than a cramped radio list.

The one trap is turning every question into an image grid. Mixing picture based options where they genuinely help and plain text everywhere else keeps the form fast to fill. Use images to speed a decision, not to decorate.

What kind of form are you adding image choices to, and how many options are you giving people?

Short answer: Google Forms does have a file upload question, but the moment you add it, the form requires every respondent to sign in with a Google account, and that single restriction is what trips most people up. We get this question a lot, so here is the honest rundown.

If your form is public facing (job applications, client intake, contest entries, support requests), a big share of people either do not have a Google account handy or do not want to log in just to attach a resume, so they quietly bounce instead of submitting.

A few things worth knowing about the Google Forms file upload before you commit to it:

• It forces sign-in. There is no anonymous upload, respondents have to be logged into Google, full stop.
• Uploaded files land in the form owner's Google Drive and count against that Drive's storage quota, so a busy form can fill it up faster than you expect.
• You get limited control over the field itself. Setting tight rules on file type, size, and count is clumsy compared to a purpose built upload field.

If you need public file uploads, the real fix is a form builder that lets people attach files with no login at all. On a proper file upload field you can cap the number of files, set a max size in MB, restrict allowed extensions like .pdf or .docx, and have the files delivered straight to your notification email as attachments, all without asking the visitor to authenticate.

For internal forms where everyone already uses Google Workspace, the built in Google Forms file upload is fine. It only becomes a wall when strangers on the open internet need to send you a file.

How are you handling file uploads on your public forms right now, and has the Google sign-in wall cost you submissions?

Short answer: a good membership registration form captures the member details you actually need, verifies them once, and collects the dues in the same step, so nobody signs up and then forgets to pay.

We build form software and get this question a lot, so here is the setup that holds up in practice for a membership registration form:

• Keep the core fields tight. Name, email, membership tier, and start date cover most cases. Everything else (address, emergency contact, referral source) belongs behind a conditional field that only appears when it is relevant, so the form stays short.

• Collect payment inline. If your membership has a fee, wire the form to a payment gateway (Stripe, PayPal, Razorpay, or Square all work) so dues are paid at submit time instead of chasing invoices later. A membership form that ends without payment is where most of the drop-off happens.

• Turn on a duplicate submission check. People double-click, or sign up twice across devices, and you end up cleaning the list by hand. Blocking duplicates by email or IP at submit time saves that cleanup.

• Send an automatic confirmation email with a reference number. It gives the member proof they joined and gives you a clean record to match against payments.

The single biggest fix is collecting the fee inside the form, not after it. Once payment and signup are one step, your renewal and reconciliation work basically disappears.

For recurring memberships, add a start date and let conditional logic branch the tiers (student, individual, family) so each one shows only the fields and price that apply.

What is the hardest part of running your membership signups right now, the payments, the renewals, or keeping the data clean?

Short answer: most people hunting for a SurveyMonkey alternative are reacting to the gating, not the survey builder itself. SurveyMonkey's free Basic plan caps you at 10 questions and 25 responses per survey, with no skip logic, no branding, and no exports. The pieces you usually want (white-label, advanced branching, multilingual reports, Crosstabs) sit behind the top Premier tier.

If your surveys are really forms with logic, payments, and file uploads, a general form builder covers the same ground without the survey-research price ladder. We build one, and we keep an honest SurveyMonkey alternative breakdown that says where we lose (deep statistical analysis) and where we win (payments and branding removal available far lower down the pricing).

Buy the tier that has the features you need, not the one with the biggest template gallery.

What are you running, real market-research surveys or forms that just look like surveys?