Google Forms Character Limits: What You Need to Know

Updated July 2026 · 8 min read

"What's the character limit on Google Forms?" is a common search, and the honest answer is that there isn't one tidy number to give you. Google doesn't publish a single, universal character cap that applies across every question type, the title, the description, and every option label. What actually matters in practice is different for each part of the form, and for the one place you can genuinely control length — individual questions — there's a built-in tool for it. This guide breaks down what's actually true for each part of a Google Form.

Short Answer vs. Paragraph: it's a UI difference, not a length cap

This is the most common point of confusion. People assume "Short Answer" means Google enforces a short maximum length and "Paragraph" allows more characters. That's not how it works. Both question types accept long text by default — a Short Answer field will technically take a very long string typed or pasted into it. The difference between the two types is purely the input box: Short Answer renders as a single-line field, while Paragraph renders as a multi-line, resizable box meant for longer, open-ended responses.

In other words, choosing Short Answer doesn't protect you from a respondent pasting in three paragraphs of text — it just makes that text harder for them to review before submitting, since it scrolls horizontally in a one-line box. If you actually need to cap how much someone can type, neither question type does that on its own. You need Response Validation, covered below.

Where practical limits actually exist

While there's no single published character limit, a few places do have practical ceilings worth knowing about:

• Form title and description. Both accept a generous amount of text, but there's no reason to push them. A long title wraps across multiple lines and pushes your first question further down the page — especially costly on a phone screen where every scroll matters before someone even starts answering.
• Question text and option labels. Google Forms will let you type long question text or long answer options, but they wrap awkwardly once they exceed a line or two, particularly in Multiple Choice or Checkbox lists viewed on a small screen. See our guide on Google Forms on mobile for how the editor and live form behave differently on phone-sized viewports.
• Respondent answers. As covered above, there's no default cap on Short Answer or Paragraph responses. Anyone can paste in a very long block of text unless you add validation.

The practical takeaway: don't design around a number Google hasn't published. Design around what's readable — short, scannable question text and option labels — and use validation for anything you genuinely need to enforce.

How to actually enforce a character limit

If you need respondents to stay under (or over) a specific character count — a tweet-length bio field, a "one sentence only" answer, a minimum-length essay response — Response Validation's Length rule is the real tool for the job. It's the only built-in way to make Google Forms reject an answer based on how many characters it contains.

1. Click the question you want to limit (Short Answer or Paragraph).
2. Click the three-dot menu at the bottom-right of the question and select Response validation.
3. In the dropdown, choose Length.
4. Pick Maximum character count or Minimum character count, then type your number.
5. Add a custom error message, like "Please limit your answer to 150 characters," so respondents understand why their submission was blocked.
6. Preview the form and test it with text both under and over your limit to confirm it behaves as expected.

For the full range of validation options — including number ranges, regular expressions, and email format checks — see our complete guide to Google Forms response validation. If you'd rather prevent an answer from being skipped entirely, that's a separate setting covered in our guide to making a question required.

What about total response size?

If your form has several Paragraph questions and expects a high volume of submissions, it's worth thinking about the connected Google Sheet rather than the form itself. Long text answers across many rows and columns make a spreadsheet heavier to work with — slower to filter, sort, or open — but this is a normal spreadsheet-scale consideration, not a form-breaking limit. If this matters for your use case, keep the number of open-ended, unrestricted Paragraph fields to what you actually need, and consider Length validation on any that don't need to be unlimited.

Practical guidelines to work by

• Use Short Answer for single facts — names, emails, short IDs — where a one-line box signals the expected length to respondents.
• Use Paragraph for genuinely open-ended feedback where you want people to write freely.
• Add Length validation whenever a specific limit actually matters to your use case, rather than assuming the question type enforces one.
• Keep question text and option labels short so they don't wrap awkwardly on a phone screen.
• Test on mobile before sending a form widely — long text wraps differently on a small screen than in the desktop editor.

FAQ

Related guides

• Google Forms response validation: the complete guide
• Google Forms on mobile: the complete guide
• How to make a question required in Google Forms