Google Forms has no signature field
There is no signature question type in Google Forms, on any account type. What people do instead is one of four things: a Marketplace add-on that generates a signable document, a file upload where the respondent attaches a signed page, a typed full name paired with an agreement checkbox, or a link out to a dedicated e-signature tool. Which one is right depends entirely on what the signature is for.
The short answer
Google Forms cannot capture a drawn or typed signature natively. Nothing in the question list draws on a canvas, and paid Workspace does not add one. Every approach below is a workaround, and the cheapest of them — typed name plus a consent checkbox — is genuinely sufficient for a lot of everyday agreements.
The four workarounds
Ordered from least to most setup. Start at the top and stop as soon as one is good enough for what you are collecting.
Typed full name plus an agreement checkbox
A required short-answer question labelled "Type your full legal name to sign", immediately after a required checkbox that restates what they are agreeing to, with the agreement text in full above it. Free, takes two minutes, and gives you a record of who agreed to what and when. This is the right answer for internal policy acknowledgements, event waivers with low stakes, and photo consent at a school event.
A file upload of a signed page
Add a file upload question and ask the respondent to attach a photo or scan of a signed document. It produces something that looks like a traditional signature. Two real costs: file upload questions force respondents to sign in to a Google account, which kills completion on public forms, and the uploaded files consume the form owner's Drive storage.
A Marketplace add-on
Add-ons in the Google Workspace Marketplace can merge responses into a document template and send it out for signature, or insert a signature step after submission. This is the closest you get to a real flow inside Google's ecosystem. Expect a separate subscription, and check the permissions it requests, because it needs access to your responses and usually to Drive.
Hand off to a dedicated e-signature tool
Use the form to collect the data, then trigger a signature request from a dedicated e-sign product using the response. Legally the strongest option and the most expensive, both in subscription cost and in the number of moving parts. Worth it for contracts with money attached; overkill for a field trip permission slip.
The free version, set up properly
If you go with typed name plus checkbox — and most people should — these three details are what make the record actually worth having.
Put the full agreement text in the form
Not a link to it. Use a section header or a description block containing the complete text the person is agreeing to, immediately above the checkbox. A record that says somebody ticked a box next to a hyperlink is weak; a record that shows exactly what was on screen is not.
Version the agreement and turn on email collection
Add a hidden-in-plain-sight version marker to the section heading ("Waiver v3, updated August 2026") so that every response carries the wording it was signed against. Enable "Collect email addresses" in settings so the response has an identity attached, and keep the automatic timestamp column in the linked Sheet.
Lock the form once it is live
Editing the agreement text after responses arrive silently changes what your records appear to say. When you need new wording, copy the form, edit the copy, bump the version marker, and retire the old one. Keep the old responses and the old wording together.
What you're actually missing
A typed name in a text box captures intent, which is the part that matters most in practice. What it does not capture is the evidence trail that makes a signature defensible later: the signature image itself, a record of what document version was displayed, and a tamper-evident link between the two. In Google Forms those live in three different places if they exist at all — the response row, your memory of when you last edited the form, and nothing.
The other missing piece is that the signature is not a field. It is a short-answer question you have agreed to treat as a signature. Nothing validates that the name matches anything, nothing stops the respondent typing "n/a", and nothing distinguishes a signature question from any other text question when the data lands in Sheets.
This is worth being honest about in both directions. For a book club liability waiver, none of that matters and you should use the free workaround. For a client contract, a rental agreement, or a medical consent form, it matters a lot, and it is the reason e-signature exists as a distinct question type in tools that have one.
In Zunoform, e-signature is one of the 24 question types. The respondent signs in the form, the signature is stored on the response next to everything else they answered, and the form can carry the agreement text, the consent checkbox, and the signature as one flow rather than three improvised parts. It is one of three question types — alongside NPS and payment — that need the Pro plan at $14.99/month to publish; building and previewing a form with one is free. This is general information about how the tools work, not legal advice about whether a particular signature meets a particular requirement.
Forms that usually need a signature
Start from one of these rather than building the consent section from scratch.
Assumption of risk, emergency contact, and a legally-signed release.
Permission to use photos and video, with a guardian path for minors.
Study overview, acknowledgments, recording consent, and a signature.
Video-visit disclosures, acknowledgments, and a binding signature.
Questions people ask
Is there a signature add-on for Google Forms?
Yes, several exist in the Google Workspace Marketplace, typically working by merging responses into a document and routing it for signature after submission. They generally carry their own subscription and require permission to read your form responses and access Drive, so review the requested scopes before installing.
Can I add a drawn signature box to a Google Form?
Not natively. No Google Forms question type renders a drawing canvas. The closest native approximation is a file upload question where the respondent attaches a photo of a signed page, which requires them to sign in to a Google account and consumes your Drive storage.
Is a typed name in a Google Form a valid signature?
That depends on the jurisdiction and on what is being signed, and it is a question for a lawyer rather than a form builder. Practically, what strengthens the record is capturing the full agreement text in the form itself, the respondent's identity, a timestamp, and a version marker for the wording they saw. Google Forms can do all four with care.
Why does the file upload question ask people to sign in?
Google requires respondents to be signed in to a Google account to upload files, because the files are written to the form owner's Drive. It is a hard requirement, not a setting, and it is the main reason file-upload signature workarounds perform badly on public-facing forms.
Keep reading
Better forms.
Better data.
Build your first form in under 60 seconds. Free forever for personal use, no credit card required.