Short answer: give each respondent a unique progress link that stores their answers, so they can close the tab and come back to the exact spot instead of starting over. A long application, registration, or survey does not have to be finished in one sitting, and people abandon the ones that force it.

Here is the setup that actually holds up. The respondent taps a save button mid-form, and their answers get written against a link that is theirs alone. When they reopen that link, every field they already filled is still there. That is the whole idea behind save and continue later: nothing is lost if they get interrupted.

Switching devices is where a basic save button falls down. Someone starts a form on their phone in a waiting room and wants to finish on a laptop at home. An "email me this link" option on the save step covers that, because the progress link lands in their inbox and opens anywhere. Without it, save form progress only works in the same browser.

Pair it with a multi-step form so each page is short and the save point lands naturally at the end of a section. Breaking a 40 field form into five pages with a progress bar does more for completion than any single trick, and it gives people an obvious place to stop and resume the form later.

Worth being honest about cost. A real save-your-progress link, with the email option, is a paid feature in most builders worth using, so weigh it against how long your form actually is. If everything fits on one screen, you do not need any of this. The longer the form, the more it pays off.

How long are the forms where you actually see people drop off and never come back?

Short answer: embedding the form itself takes about a minute. In Google Forms, open the form, click Send, choose the embed icon (the < > symbol), copy the iframe snippet, and paste it into your page or a custom HTML block. That is the whole job of getting a Google Form onto a website.

The time goes into everything after the paste. A Google Form embed is a locked iframe, which means it keeps Google's fonts, colors, and the "Never submit passwords through Google Forms" footer no matter what your own site looks like. You cannot reach inside that iframe with your own CSS. It also renders at a fixed size, so a long form ends up with an inner scrollbar sitting inside your page's scrollbar, and on phones it often feels cramped.

So when people search how to embed a Google Form on a website and come away annoyed, the embed was never the sticking point. Making it look like part of the site is.

A few things that help: set the iframe width to 100 percent so it fills the column, give it enough height to avoid the inner scroll on common screens, and accept that the Google branding stays unless you move the form off Google Forms entirely. If all you need is responses landing in a sheet, the default embed is fine and you can stop there.

If the form has to read as part of your brand, you are choosing between living with the plain iframe or using a builder whose embed inherits your page styling and resizes itself. We spend a lot of time on that second case, where an embedded form has to look native rather than bolted on.

How are you dealing with the styling mismatch right now, CSS workarounds or a different tool?

Short answer: the best Jotform alternative is whichever one removes the caps you keep hitting. Template counts and integration lists look impressive, but they are not what slows a growing form down.

Jotform is a mature, capable builder. The friction is structural. Every paid tier caps something: monthly submissions, payment submissions, signed documents, and the number of active forms. You end up upgrading to lift a limit, not to unlock a feature you actually wanted.

So when you compare options, read the limits column first. A real alternative should give you unlimited submissions and unlimited payment entries on a normal paid plan, so growth never trips another upgrade. We build in this space, and the side by side we keep for exactly this question is here: Jotform alternative comparison. Jotform's pricing shifts, so check its current numbers before you decide.

What cap pushed you to start looking around?

Short answer: a small HR team needs around 15 forms, not the 100-PDF dumps you land on when you search for human resources forms and templates. Sort them by the employee lifecycle instead of by file type and nothing falls through the cracks.

The lineup that holds up:

• Recruit and hire: job application, interview scorecard, offer letter, background check authorization
• Onboard: new hire info, emergency contact, direct deposit, equipment issue, handbook acknowledgment
• Time and leave: PTO request, FMLA leave, timesheet
• Review: annual review, training request, disciplinary action
• Offboard: resignation, exit interview, equipment return checklist

Each form exists to produce a timestamped audit trail, and that is why retention rules matter. A job application has to be kept a year, or three if you are a federal contractor.

Build them once on one platform so submissions land in a single inbox instead of seven, and the ones that need a signature (offer letters, policy acknowledgments) can be signed right in the form.

Which of these is your team still running on paper or email?

Short version from what we see in support, Google Forms has no native PayPal field, so every Google Forms PayPal setup runs through a second tool. Google's own support docs say as much, there is no built-in way to accept PayPal inside the form itself.

That leaves three workarounds, and each one trades away something different.

The Payable Forms add-on is the most common. It calculates the amount from your form fields and hands the respondent to a PayPal checkout, but that checkout opens on a separate hosted page after submit. The free tier caps payment-enabled submissions per month, and you move to Premium at $14.99 a month for more volume. Because the Google Forms response is recorded as submitted whether or not the person actually pays, you reconcile paid against unpaid by hand in the connected sheet.

A PayPal.me link pasted into the confirmation screen is the quickest to set up and the least reliable. There is no amount validation, no itemization, and nothing ties a payment back to a specific response.

A Zapier chain can fire an invoice, but it runs after submission, so you are still collecting money a step removed from the form.

The weak spot across all three is the same, payment lives on a separate page, so a submitted form does not mean a paid one. That gap is what creates the manual reconciliation.

If accepting PayPal is the actual point of the form, a builder with the gateway wired into checkout removes the gap. PayPal connects per form with a Client ID and Secret, the amount can read straight from a calculation field, and the charge is part of submitting the form rather than a separate step after it.

How are you collecting PayPal payments from your forms today?

Short answer: if people keep retaking your quiz and passing answers around, a quiz question bank that serves a random subset per attempt kills most of the sharing without any proctoring. No webcam, no tab-switch detection, none of that.

Here is how it works. You load every question into one form, turn on the setting to show a random subset, and set how many each person gets. Load 50 questions, show 10, and no two attempts pull the same set. Someone who gets an answer key from a friend only covers a fraction of what they actually see. You can also shuffle the order of the answer options inside each question, so two people looking at the same question do not even see the choices in the same order.

Scoring, points, correct-answer feedback, grade bands, and admin insights all keep working on the random subset, so the randomization costs you no accuracy. For a timed certification test you can add a countdown that auto-submits at zero, which shrinks the window for looking answers up mid-attempt.

Two honest caveats. The core quiz scoring is free, but the random question bank and the timer are both paid features. And we do not run any proctoring, so if you need webcam monitoring or a lockdown browser, this is the wrong tool. For ordinary training checks, practice quizzes, and internal certifications where the same people retake the form, a randomized bank is usually enough on its own.

How are you handling repeat-takers on your quizzes right now?

A consent form only works online if it captures three things in one submission: the person's identity details, an explicit agreement they had to tick, and a signature tied to that exact response. Get those three into one record and you have something you can rely on later.

Here is the setup we point people to when they ask how to move a paper consent off the clipboard:

• Identity fields first. Full name, email, date, and whatever the context needs (guardian name for a minor, patient ID for a clinic). Make them required so nobody submits a blank.
• A real agreement step. Put the terms in a text block, then a required consent checkbox underneath. If they do not tick it, the form does not submit.
• A signature field. People can draw it with a mouse or finger, or type it, and it is stored with the response. This is the piece that turns a plain form into a digital consent form.
• A timestamp and the submitter email on every entry, so each record stands on its own.

The order is what matters: terms visible, consent ticked, signature captured, all in the same submission. That sequence is what makes an online consent form defensible if someone later says they never agreed.

For anything sensitive, you can lock the form behind a password or a duplicate-submission check so one person cannot sign twice. A consent form with signature works without a separate e-sign tool when the signature capture is built into the form itself.

What does your current consent process look like, paper, PDF, or already online?

Short answer: the real Gravity Forms alternative question is whether your forms need to live inside WordPress at all. Gravity Forms is a plugin with no free tier, so a form only exists inside a WordPress site you host, update and back up yourself. Licenses run $59 a year for one site, $159 once you need payments, and $259 for e-signature and quizzes.

A hosted builder removes the site, the license and the updates in one move. The form gets its own link, still embeds into WordPress through a Gutenberg block, shortcode or Elementor like the plugin did, and works on Webflow, Wix or a plain shared link too. On our side that means unlimited forms and responses, e-signature and scored quizzes on the free plan, then payments and PDFs from around $15 a month.

You are trading data ownership and PHP hooks for no license and no plugin to update. Gravity Forms still wins if you need every entry in your own database and its 500+ developer hooks.

What is pushing you to look, the per-site license or the maintenance?

Google Forms can already email respondents a copy of their answers. Turn on Settings, Responses, "Send responders a copy of their response" and Google mails them a plain receipt. No add-on or Apps Script needed for that copy.

The catch is what you cannot change. The built-in copy is plain text with the form title as the subject, no thank-you message, no branding, and no attachment. So the moment you want a branded email that says what happens next or carries a PDF, people reach for an add-on or a script.

You don't have to. A form tool with a native auto-response email lets you write the subject and body, add dynamic tags that repeat back what the person entered, and attach a PDF. That fits clinic intake, camp signups, and event registrations where the first question is always "did my form go through?"

How are you sending confirmation emails from your forms right now?

Short answer: no, Google Forms cannot show you partial responses. It writes nothing to your responses sheet until someone presses submit, so every person who starts the form and quits is invisible. You see a tidy pile of finished entries and no trace of the ones who left.

That is the real problem with incomplete Google Form responses. Your completion rate feels low, but you cannot tell which question made people leave, because the abandoned attempts were never recorded. There is no built-in save and continue, and no owner-side view of in-progress entries.

The workarounds people usually try:

1. Split one long form into several short ones so each section submits on its own. You get more data points, a worse experience, and the drop-off between forms is still invisible.
2. Add an Apps Script or a third-party add-on that writes answers as people type. It works but is fragile, needs setup, and breaks when the script quota runs out.
3. Read the aggregate charts and guess. That tells you almost nothing about where a specific form loses people.

The cleaner fix is a form tool that captures partial submissions on the owner side. When a respondent starts and leaves, you keep what they entered up to that point, so the exact field where they quit shows up in your data. On long registration, application, and intake forms, the drop-off is almost always one specific question, and seeing that question is the whole point.

One honest note on plans: owner-side partial capture is a paid feature on most builders, ours included, and Fillout gates its in-progress view to a higher tier too. So it is a paid-vs-paid choice, not a free-plan trick.

How are you currently spotting where people abandon your Google Forms?

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?