You create a form in Google Forms by opening forms.google.com, picking a blank template or one from the template gallery, and adding questions in the editor. Google saves every change automatically. You don't need a paid account: Google Forms is part of Google Workspace, and anyone with a personal Google Account gets it free. The whole build for a ten-question form takes most people under 15 minutes, though the settings that decide whether your data stays clean take another five.
The catch most first-timers hit: Google Forms has no Save button, so there's nothing to confirm your work is safe. It does save, but there's no visual cue except a small "Saved" note that fades. That missing button is why people close the tab too early and then wonder where their form went.
Opening Google Forms and choosing between blank and template
You have two doors into the editor, and they produce different starting points. Go to forms.google.com and click the "Blank" tile with the plus sign for an empty form. Or scroll the template gallery at the top of the same page to pick a pre-built layout β Google organizes these into Personal, Work, and Education rows.
The template gallery saves real time if your need is common. A "Contact Information" template already has name, email, and phone fields; an "Event Registration" template ships with attendance options. Templates arrive with conditional formatting and section breaks intact, so you edit wording rather than structure.
Pick blank when the form will feed a spreadsheet you already have column names for. A template you have to strip down often takes longer than starting from an empty canvas with three questions you actually need. My rule: borrow a template when the field types match, start blank when the questions are unusual.
The URL matters for a different reason. If you open forms.google.com and nothing loads, you're probably signed into a personal account on a browser profile that's also holding a work session. Google serves the wrong tenant and the gallery looks empty. Sign out fully or open a private window to isolate the account.
Naming the form, choosing a destination, and wiring responses to Sheets
Before you write a single question, set two things in the top area of the editor. The title field (currently "Untitled form") becomes the H1 of your live form; the description box beneath it is where you add instructions. Both are visible to respondents.
Response destination is the setting that saves people later. Click the "Responses" tab at the top of the editor, then the green Sheets icon, and choose "Create a new spreadsheet." Confirm the name Google suggests. Now every submission lands as a row, which means sorting, filtering, and formulas work from day one.
Skip that step and your responses live only inside the Forms interface. You can still view them under Responses β Summary or Individual, and you can download a CSV from the three-dot menu, but you lose the live view into aggregation. For anything over about twenty responses, Sheets is the difference between reading a list and understanding a trend.
One naming behavior catches teams: if you rename the form later, the linked spreadsheet keeps its original name. Rename the spreadsheet yourself from Drive, or the pair drifts apart in search results. Google's own Workspace help documentation confirms responses flow to the spreadsheet even after you edit the form, which is why consistent titles matter more than they seem to.
Adding questions and picking the right question type
Click the plus icon in the floating toolbar on the right to add a question. A small dialog appears with a dropdown. The dropdown is the whole game: each type determines what data you can cleanly analyze later.
| Question type | Use it for | What it stores in Sheets |
|---|---|---|
| Short answer | Names, emails, one-line facts | Plain text, unbounded length |
| Paragraph | Open feedback, addresses | Plain text, multi-line |
| Multiple choice | One answer from a fixed list | The chosen option text |
| Checkboxes | Several answers from a list | Comma-separated selections in one cell |
| Dropdown | Long option lists (states, years) | Chosen option text |
| Linear scale | Rating 1β5 or 1β10 | A single number |
| Multiple choice grid | Rating several items on one scale | One column per row item |
| Date | Deadlines, birth dates | Date-formatted cell |
| File upload | Documents, images | Drive link (requires sign-in) |
The type that trips people up is checkboxes. Respondents can select anything, including nothing, so add "Required" if a blank is unacceptable. Multiple choice can't be left blank once marked required, which makes it safer for branching.
Two types carry hidden costs. File upload forces respondents to sign into a Google account, which kills response rates from outside organizations β that's a real drawback worth knowing before you build a resume collection form. Grid questions produce one spreadsheet column per row, so a five-row grid becomes five columns and analysis gets wider fast.
Writing multiple-choice options, scales, and required questions
Enter your question in the text box, then fill the option fields below it. Press Enter after each option to add the next line automatically. For linear scale questions, set the start and end values in the dropdowns β 1 to 5 is the default, and the endpoints accept labels like "Poor" and "Excellent."
Marking a question required is a single toggle at the bottom right of its card, labeled "Required." A red asterisk then appears on the live form. Respondents cannot submit until they answer it, which is exactly what you want for email addresses and exactly what you don't want for optional comments.
Here's where design affects data quality more than people expect. Linear scale answers only make sense if respondents know what the middle means. Label the endpoints; label the midpoint too if your scale has one. Otherwise you get a pile of 3s and no way to interpret them, and your survey effort is wasted.
For multiple-choice questions with more than about eight options, switch to a dropdown. Dropdowns keep long lists scannable on phones, where a nineteen-item radio list pushes the submit button off screen. Google Forms does not limit option count β the limit is the respondent's patience.
Making questions required and setting response rules with data validation
Data validation is buried behind the three-dot "More" menu on each question card, then "Response validation." It's the single most underused feature in Google Forms, and it's what separates a form that returns clean data from one you spend an afternoon cleaning.
Validation options depend on question type. Short answer fields can require a number, text, length between X and Y characters, a regular expression, or a specific format like email or URL. Checkbox questions can require a minimum and maximum number of selections β set "at least 2, at most 4" and the form enforces it before submission.
A worked example shows why this matters. Suppose you collect employee IDs with a short answer field and no validation. You get "1042," "1042 " (trailing space), "ID1042," and "one thousand forty two." A regex validation set to a pattern like ^\d{4}$ accepts only four digits and rejects the other three variants. Ten seconds of setup prevents an hour of spreadsheet cleanup.
Validation has one failure mode worth understanding before you rely on it. If the pattern is wrong, correct respondents get blocked and you won't discover it until the first complaint arrives. Test every validation rule by submitting the form yourself with both a valid and an invalid entry. Google's Forms help center lists the available patterns; the default "Number" check is the safest place to start.
Branching with sections and skip logic for longer forms
Long forms lose respondents. Google Forms fixes that with sections and branching: you show people only the questions relevant to them. Click the "Add section" icon in the floating toolbar (it looks like an equals sign in a box) to split the form into pages.
Branching lives in the three-dot menu after each multiple-choice or dropdown question: "Go to section based on answer." Map each answer to the section it should jump to. Someone who answers "No" to "Do you own a car?" can skip straight to the final page; someone who answers "Yes" lands in the vehicle-details section.
The limit to know: branching works on multiple choice and dropdown only, not checkboxes or short answers. If you need branch logic off a checkbox list, restructure the question as multiple choice first. Designers often fight this for ten minutes before accepting it.
Sections also improve completion rates for a specific measurable reason. Every section change creates a progress indicator β the thin bar at the top of the live form. Respondents who can see progress complete longer forms at higher rates than those facing an undifferentiated scroll, which is why Google's own form-design guidance recommends splitting anything past ten questions.
Choosing settings: quiz mode, one response, and email collection
The Settings tab at the top of the editor holds four collapsible panels, and the defaults are not always what you want. Walk them in order before you share the link.
Under "Responses," toggle "Collect email addresses" if you need to know who answered. There are two modes: verified (respondents must sign in, and email is captured automatically) and responder input (they type it, and can lie). Verified mode is a hard requirement when the form asks for anything sensitive or when duplicate submissions matter.
The same panel contains "Limit to 1 response." Turn it on when each person should answer once. It requires sign-in, so it won't work for anonymous public forms β there the setting is unavailable entirely, not just ineffective. A brief edge case: if your audience uses shared devices, verified collection records the device's account, not the actual respondent.
Quiz mode lives under "Make this a quiz." Flip it on and each question gains a points value and an answer key, and the form returns scores. An important date for anyone using graded forms in education: Google rolled out the current quiz features over 2020, and the automatic feedback options now include per-question explanations, which schools rely on for asynchronous assessment. Test quiz mode with a dummy submission before assigning it to a class.
Formatting the theme and adding response validation on the live view
Customizing look and feel takes two minutes and is optional. Click the palette icon at the top to open the theme panel. There you can pick a header color, choose a font from the available set, and upload a header image. Upload is drag-and-drop, which makes testing take seconds.
Font choice has a practical dimension. The default font is legible on both desktop and phone; decorative fonts sometimes break line-height on smaller screens, which makes long-answer boxes hard to read. If your audience is mobile-heavy β most are, since Google Forms renders responsively β stick with the default stack and prove a custom font on a phone before shipping.
The theme panel also holds a background color. Respondents see it first, so it's your one branding impression before they start typing. If you're collecting anything health-related, sensitive, or confidential, add the note that data is collected via Google Forms and who can see responses, in the form's description field.
Preview the live view before you share. Click the eye icon in the top bar to open the "Preview" state, then fill it in exactly as a respondent would. This is where most duplicate-response mistakes get caught, and where you discover that your "Required" grid question is unanswerable on a phone.
Testing a broken validation rule before you share the link
Here's a failure case worth the five minutes. Suppose you build a short answer field for phone numbers and set response validation to "Number" with a maximum of 10 digits. A respondent enters "+1 555 010 0199" β fifteen characters including spaces and the country code. Validation rejects it. They retry twice, then abandon the form.
The fix is a regular expression, not a stricter number check. A pattern that permits optional country code, spaces, and parentheses accepts real-world inputs. The lesson generalizes: validation is only as good as your worst-case input, and your worst-case input comes from someone in a hurry on a phone.
A structured test protocol catches this before your respondents do. Submit the form three times from the preview: once with perfect data, once with the worst plausible input, once with everything blank. Any requirement that an empty form can pass isn't actually required, and any well-formed answer that gets blocked tells you the rule is too tight.
Then verify the response side. Open the linked spreadsheet and confirm three rows landed with the expected columns. Check that a checkbox selection shows as comma-separated text in a single cell, not three cells. If your analysis relies on counting selections, that storage format is the number you'll work from.
Choosing between personal and Workspace accounts: what changes
Sign-in type quietly changes what Google Forms will let you do, and the differences leave people stuck when they switch from a personal Gmail to a work account.
| Capability | Personal Google Account | Google Workspace account |
|---|---|---|
| Create and share forms | Yes, free | Yes, included in subscription |
| File upload question | Yes, requires respondent sign-in | Yes, with admin controls on Drive |
| Limit to 1 response | Yes, sign-in required | Yes, sign-in required |
| Domain-restricted sharing | No | Yes, admins can restrict to org |
| Response data retention | Stays in your Drive | Managed by admin retention rules |
| Email collection | Verified or manual | Verified or manual, plus audit logs |
The headline: you can do nearly everything on a free personal account. What you can't do is restrict who within an organization can respond, and you can't rely on an administrator's retention policy to protect the data.
Workspace adds one feature that matters to regulated teams β admins can review and, if needed, remove form data through the admin console. If your form collects anything that falls under a records policy, that oversight is the reason to build it inside an organizational unit rather than a personal Drive.
A version-specific note: Google renamed G Suite to Google Workspace in October 2020, and old tutorials referencing "G Suite" settings map to the same menus under new names. If a help article tells you to open a menu you can't find, the labeling probably predates the rename rather than describing a missing feature.
FAQ
How many responses can a Google Form collect?
There is no cap Google publishes on responses per form; limits show up on the spreadsheet side, set by Drive storage for Sheets. For scale reference, a form collecting a few thousand rows is routine and loads fine in the browser. Past roughly tens of thousands of rows, analysis slows and you should plan to export to CSV for heavier processing.
What happens if two people submit at the same time?
Both submissions are recorded; Google serializes them into the linked spreadsheet in arrival order. Timestamps in the Responses view serve as the arbitration record if someone disputes order. No response is lost from concurrency, and simultaneous entries appear as separate rows.
Can I edit a form after I've sent the link?
Yes, and changes apply to the live version immediately β respondents may see the new wording mid-session. To change a form without disturbing active respondents, make a copy from the three-dot menu ("Make a copy"), edit the duplicate, and share that link instead.
Does Google Forms cost anything?
The core product is free with any Google account and has been since it launched publicly in 2008. Formatting, branching, validation, quiz mode, and Sheets integration are all free. Paid Workspace tiers add org-level controls, admin oversight, and storage alongside the rest of the suite, not the form builder itself.
Why did my file upload question fail for a respondent?
File upload questions require respondents to sign in to a Google account, and the file lands in your Drive, counting against your storage quota. A respondent with no Google account, or one outside your organization on a restricted form, sees a sign-in gate and often abandons. Check Drive quota first when uploads suddenly fail for you too.
Can I force one response per person without sign-in?
No. Limiting to one response is enforced by account identity, so it requires sign-in by definition. For anonymous one-per-person forms, the common workaround is a hidden field populated with a unique code, but that approach is bypassable and shouldn't be treated as strict enforcement.
What's the fastest way to build a form with no idea where to start?
Copy a template from the gallery and edit it rather than building from blank β templates arrive with sections and question types already configured. If you're building for a team, check whether someone in your organization maintains a standard form template first, since consistency across submissions often matters more than layout polish.
How do I stop responses I already collected from being deleted by mistake?
Make a copy of the linked spreadsheet and keep editing only the copy, treating the original as a read-only archive. April 12, 2026 isn't a magic date for form data, so the archiving habit is the protection β not any automatic retention guarantee from Google.