You ask for a phone number and get a name. You ask for an email address and get one with a typo that bounces. Cleaning that up after a hundred submissions costs you an afternoon.
Response validation in Google Forms prevents it. It lets you set rules an answer must follow before the form can be submitted, so bad answers get rejected during filling instead of cleaned up in a spreadsheet later. This guide shows you how to set up Google Forms response validation, what each of the four rule types does, and copy-paste regex patterns for the formats people ask about most.
Quick answer
- Click a short answer, paragraph, or checkbox question (the only three types that support validation).
- Open the three-dot menu in the bottom-right corner of the question and choose Response validation.
- Pick a rule type: Number, Text, Length, or Regular expression.
- Set the condition and write a custom error message that tells people how to fix their answer.
- Preview the form and test it with wrong answers before you share it.
What is response validation in Google Forms?
Response validation is a rule you attach to a question. When someone submits an answer that breaks the rule, Google Forms shows them an error message and blocks the submission until they fix it. An age field can require a number between 18 and 100. An email field can require a valid email format. A feedback box can require at least 50 characters.
When an answer breaks the rule, your error message shows under the question in red, and Google Forms refuses to accept the form until the answer is fixed. If the answer passes, nothing happens and the respondent moves on.
One limit to know before you plan your form: full validation only works on three question types. Short answer questions get the full set of rules. Paragraph questions get length and regex rules only. Checkbox questions can only limit how many options someone selects. Grid questions get two narrow settings of their own (require a response in every row, limit to one response per column). Multiple choice and dropdown questions have no validation at all, because their answers are already restricted to the choices you provide.
How to add response validation in Google Forms
The setup takes under a minute per question. Here it is end to end:
-
Open your form and pick a question
Go to forms.google.com and open the form you're working on. Click the question you want to validate, and make sure its type is short answer, paragraph, or checkboxes. If the question is a dropdown or multiple choice, validation won't appear in the menu.
-
Turn on response validation
Click the three-dot menu in the bottom-right corner of the question card, then choose Response validation. A new row of dropdowns appears under the answer field.
-
Choose the rule
The first dropdown sets the rule category: Number, Text, Length, or Regular expression. The second dropdown sets the condition, like between, contains, or maximum character count. The field after it takes your value. For an age question, that's Number, then Between, then 18 and 100.
-
Write a custom error message
The last field holds the text people see when their answer fails. Google's default error is vague, so say exactly what to do: enter a number between 18 and 100, or enter your work email address. A clear error message is the difference between a fixed answer and an abandoned form.
-
Preview and test the form
Click the eye icon at the top to open the preview. Submit a wrong answer on purpose and confirm the error appears, then submit a correct one and confirm it goes through. Test the edge cases too: spaces before an email address, a number written with a comma, an empty field. Two minutes of testing here saves you from finding out through a hundred broken submissions.
Validation and the Required toggle work independently. A validated question that isn't required can simply be left blank, and the rule never runs. Mark the question required if the answer must be present and correct.
The 4 types of response validation (with examples)
Each rule type covers a different kind of answer. Pick based on what the question collects.
Number validation
Number rules keep answers numeric and inside a range you choose. The conditions are greater than, greater than or equal to, less than, less than or equal to, equal to, not equal to, between, not between, is number, and whole number.
Use it whenever the answer is a quantity: age, ticket count, hours worked, a rating you couldn't fit into a scale question. A quantity field with a between rule of 1 and 10 stops someone from ordering 1,000 t-shirts by accident. The whole number condition matters more than it looks, because without it 2.5 people can RSVP to your event.
Text validation for email and URL
Text rules check what the answer contains. The conditions are contains, doesn't contain, email address, and URL.
Email address is the one you'll use most. Set the dropdowns to Text and Email address, and Google Forms rejects anything that doesn't follow the name@domain shape, like an address missing the @ or ending in .con. If you collect emails for follow-up, this single rule filters out most unusable entries. The URL condition does the same for links, which helps when you ask for a portfolio or website.
The contains and doesn't contain conditions handle in-house formats. If every employee ID in your company starts with ACM, a contains rule for ACM catches everyone who typed only the digits.
Length validation
Length rules set a minimum or maximum character count. They work on both short answer and paragraph questions.
Use a minimum when you need substance: a feedback question with a 50-character minimum turns one-word answers into sentences. Use a maximum when the answer feeds a system with limits, like a display name capped at 20 characters. Don't set a minimum on every open question, though. Forced padding produces longer answers, not better ones.
Regular expression validation
Regex rules match answers against a pattern, character by character. The conditions are contains, doesn't contain, matches, and doesn't match. This is the rule you reach for when the built-in options can't describe your format: phone numbers, PIN codes, dates, order IDs.
A pattern reads like a recipe. In the phone pattern ^\d{3}-\d{3}-\d{4}$, the ^ means the answer starts here, \d{3} means exactly three digits, the - is a literal dash, and $ means the answer ends here. So only answers shaped like 555-123-4567 pass. You don't need to learn regex to use it. Copy a pattern from the table below.
Copy-paste regex patterns for Google Forms
For each of these, set the validation to Regular expression and the condition to Matches, unless the row says otherwise. Paste the pattern as-is.
| What you want | Pattern | Passes |
|---|---|---|
| US phone (dashes) | ^\d{3}-\d{3}-\d{4}$ | 555-123-4567 |
| 10-digit phone, digits only | ^\d{10}$ | 5551234567 |
| Indian mobile number | ^[6-9]\d{9}$ | 9812345678 |
| US ZIP code | ^\d{5}(-\d{4})?$ | 12345 or 12345-6789 |
| Indian PIN code | ^[1-9]\d{5}$ | 560001 |
| Date as MM/DD/YYYY | ^(0[1-9]|1[0-2])/(0[1-9]|[12]\d|3[01])/\d{4}$ | 03/28/2026 |
| Letters and spaces only (names) | ^[A-Za-z ]+$ | Priya Sharma |
| Block links in answers | https?://|www\. with condition Doesn't contain | any answer without a link |
Adjust the pieces to fit your format: change \d{3} to \d{4} for four digits, or swap the dash for a space. Google Forms uses RE2 regex syntax, which has no lookahead support, so very clever patterns from Stack Overflow may not work. The patterns above all do.
The blocked-links row solves a specific problem: spam bots paste URLs into open text fields. A doesn't-contain rule on your paragraph questions filters most of them without bothering real respondents. (Use doesn't contain, not doesn't match: the matches conditions test the whole answer against the pattern, so a spam message with extra words around the link would slip through.)
Limit how many checkboxes people can select
Checkbox questions get their own validation. The conditions are Select at least, Select at most, and Select exactly, each with a number.
Use it when a pick-your-top-3 question would otherwise collect seven answers from enthusiastic respondents. Open the three-dot menu on a checkbox question, choose Response validation, pick the condition, and set the count. The error message field works the same as everywhere else.
What response validation can't do
Validation solves formatting problems. It does not solve every data problem, and knowing the gaps saves you from trusting the tool too far.
One rule per question. You can't require both a minimum length and an email format on the same field. Combine the conditions into one regex, or split the question in two.
Full rules on three question types only. Short answer, paragraph, and checkboxes. Paragraph questions only get length and regex rules, and grids only get row and column limits, so you can't run a text or number check on either.
The email check is format-only. name@gmial.com passes, because it looks like an email. A fake address someone invented on the spot passes too. Format validation tells you the answer is shaped right, not that the inbox exists.
No cross-field rules. A rule can't compare two answers, so you can't require an end date later than a start date, or a shipping address only when a checkbox is ticked.
For most surveys and sign-ups, these gaps don't matter. For lead capture, registrations, and anything where the contact details are the whole point, they do. If you want more workarounds for the platform's edges, our collection of Google Forms tips and tricks covers the rest of the toolset.
Validation on every field, and verification where it counts
Formester treats validation as a property of every field, not a bolt-on for three question types. Phone, email, number, date, and file upload fields each carry their own rules, and the parts Google Forms can't check get verified for real:
Email verification that confirms the inbox. The email verification field sends a one-time code to the address the respondent entered. They type the code into the form, which proves the inbox exists and belongs to them. Typos and throwaway addresses stop there.
Phone verification over SMS. SMS verification does the same for phone numbers with an OTP, so a lead's number is dialable before it reaches your CRM.
Fields that react to other answers. Conditional logic shows and hides fields based on earlier answers, so a shipping address field can appear only when someone ticks the checkbox asking for delivery.
If your forms collect contact details you plan to act on, verification catches the bad entries that format checks let through. Here's the full case for Formester as a Google Forms alternative.
Collect contact details that actually work
Formester verifies emails and phone numbers with one-time codes at submission, so every lead in your list is reachable. Format rules are built into the fields themselves.
Try Formester freeFree forever · No credit card · 56,000+ teams
