How to add a short answer question in Google Forms

Last updated September 2026 · ~7 minute read

Short answer: add a question, then set its type to Short answer — the first entry in the type menu. Google describes it as an open question where “Responders can find one line to write their answer in a few words.” Two things beyond the box size are genuinely different from Paragraph: Short answer accepts four families of validation rule instead of two, and it is the only free-text type that can carry a quiz answer key.

The one-line box is the part everyone notices and the least consequential thing about this question type. Nothing in Google's documentation says the box refuses a long answer. What the type actually decides is how much the form can check, and whether a quiz can mark it for you.

Adding one

1. Open the form in the editor and add a question.
2. Open the question type control beside the question title and choose Short answer.
3. Type the prompt. There is nothing else to fill in — a Short answer question has no options, rows or columns, so the prompt and the optional description are the whole question.
4. If the answer has a shape — a number, an email address, a reference code — open the question's More menu and turn on Response validation.

Read the rules page, not the type blurb

Google's Choose a type of question for your form page gives Short answer one sentence of capability: “You can set rules such as maximum character count.” For Paragraph, the same page says “maximum or minimum character count.” Read only that, and you would conclude Short answer has no minimum.

It does. Google's How to set rules for your form page defines the Length rule identically for both — “select Maximum or Minimum character count, and the number” — and gives the Short answer section four rule families where Paragraph gets two. The type blurb is a summary written loosely; the rules page is the specification. Where the two disagree, the rules page is the one with the click-path in it.

The four rule families, and where we cover them

Google's rules page splits into sections by question type, and “Rules for short answer questions” lists Number, Text, Length and Regular expression. “Rules for Paragraph questions” lists Length and Regular expression, and stops. That asymmetry is the substantive functional difference between the two text types, and it runs against intuition: the smaller box is the more configurable one.

Each family already has a page here, so this one will not repeat them: data validation covers the categories across every question type, number validation lists all ten Number rules, regex validation covers pattern rules, and character limit covers Length — including the fact that Google publishes no platform maximum for the length of an answer, for either text type. Word count covers why none of these rules count words.

One type or two? Google's own APIs disagree

If you want to know whether the distinction is structural or presentational, the developer references are where the answer lives — and they do not give the same one.

The REST API treats them as one type with a switch. We pulled the live discovery document (forms.googleapis.com, version v1, revision 20260909) and the entire schema for a free-text question is:

• TextQuestion — “A text-based question.” One property, paragraph, a boolean, described as “Whether the question is a paragraph question or not. If not, the question is a short text question.”

That is the whole model. No length field, no validation field — the strings maxLength, maxItems and validation appear zero times in the document, which our word count guide goes into.

The Apps Script reference treats them as two separate types. ItemType defines TEXT as “a question item that allows the respondent to enter a single line of text” and PARAGRAPH_TEXT as “a question item that allows the respondent to enter a block of text”. They get different classes — TextItem and ParagraphTextItem — and, tellingly, different validation builders. TextValidationBuilder exposes eighteen require… methods; ParagraphTextValidationBuilder exposes six. The twelve Short answer has and Paragraph does not are the ten number rules plus requireTextIsEmail() and requireTextIsUrl().

So the difference is real and it is enforced — but it is enforced by the rules you attach, not by the height of the box. Neither API carries any statement that a one-line field rejects a long answer, and neither exposes a maximum you could read or set.

The thing only Short answer can do in a quiz

Google's Create & grade quizzes page names the types that can take an answer key: “Short answer, Multiple choice, Checkboxes, Dropdown, Multiple choice grid, Checkbox grid.” Paragraph is not among them. Of the two text types, only Short answer can be marked automatically.

The REST reference says how the marking works. CorrectAnswers.answers is a list, and “for single-valued questions, a response is marked correct if it matches any value in this list (in other words, multiple correct answers are possible).” So an answer key on a Short answer question is a set of exact strings, and a response is right if it equals one of them. Add every spelling you will accept — Paris, paris, PARIS — rather than assuming one covers the others.

We assume that because Google never defines what “matches” means. Nothing in the help centre, the Apps Script reference, the REST reference or the discovery document states whether the comparison is case-sensitive, whether leading and trailing spaces are trimmed, or how accents are handled. Google's own reference hints at how much it trusts the result: the description of Grading.generalFeedback says it is “commonly used for short answer questions when a quiz owner wants to quickly give respondents some sense of whether they answered the question correctly before they've had a chance to officially grade the response.” The API's model of a short-answer quiz is that a human grades it afterwards.

The practical rule: before a Short answer question carries marks that matter, submit two test responses that differ only in case and spacing, and look at what the grader did. That takes two minutes and is the only authority on the question.

When Short answer is the right choice

• The answer is a value you will sort, filter or check — a name, a postcode, an order number, an email address. Only Short answer can validate it.
• The answer is a number. Number rules exist on this type alone, so a question holding an age, a quantity or a price has to be a Short answer.
• It is a quiz question with one right answer. Paragraph cannot hold a key.
• You want people to be brief. A one-line box is a social signal, not a cap — it makes people write less without truncating anyone.

If the answer is prose you intend to read, use Paragraph instead; our paragraph question guide covers what that type can and cannot do. Switching between them later is one control, with consequences — changing a question type covers those.

On iPhone and iPad

Forms+ puts the same list behind the question type row, in the same order. The first group of the Question Type sheet is exactly two rows — Short answer, then Paragraph — above the choice types, and the same group appears whether you are adding a question or changing an existing one's type.

On a Short answer question, the question's overflow menu carries Response validation, and the category list behind it is the same four Google publishes: Number, Text, Length and Regular expression. Picking Number starts you on a “greater than” rule, which you then change. The app mirrors Google's rule set rather than inventing one.

Frequently asked questions

Is there a character limit on a Google Forms short answer question?

Not one Google publishes. There is no maximum stated on the help pages or anywhere in the Forms API, and the discovery document contains no length field at all. The only limit is the Length rule you set yourself — see Google Forms character limit.

What is the real difference between Short answer and Paragraph?

Two published ones. Short answer accepts four validation families (Number, Text, Length, Regular expression) where Paragraph accepts two, and Short answer can carry a quiz answer key where Paragraph cannot. The box size is presentational: nothing in either API encodes a length.

Can a short answer question be graded automatically?

Yes. It is one of six types that can take an answer key, and the key is a list of accepted values — a response is marked correct if it matches any one of them. Google does not document whether that match ignores case or spacing, so add every spelling you will accept and test before it counts.

How is a short answer question stored in the Forms API?

As a TextQuestion with paragraph set to false — the same schema a Paragraph question uses, with one boolean flipped. Apps Script models it differently, as its own TEXT item type with its own class and validation builder.