Loading...
Morgan Hopkins, Customer Success Manager
Last Updated: Mar 9, 2026
One of the most common questions about Google Forms is whether you can add a signature field. Whether you're collecting consent forms, contracts, policy acknowledgments, or approval sign-offs, a signature gives the submission formal weight. Google Forms doesn't have a native signature field, but there are practical workarounds — and for approval workflows, a better alternative altogether.
Google Forms is designed for structured data collection — text, multiple choice, checkboxes, dates, and file uploads. A freehand signature is inherently unstructured (it's an image drawn on a canvas), which doesn't fit the form-field model. Google has never added a native signature question type, and there's no indication it's on the roadmap.
The simplest approach is to add a short-answer question labeled "Signature" or "Full Name (as signature)" and include a note that typing their name constitutes an electronic signature. This is legally sufficient in many contexts:
This works well for internal processes like policy acknowledgments, training completion, and basic agreements.
If you specifically need a handwritten signature image, you can use Google Forms' file upload question type:
The downside is friction. Asking someone to create and upload a signature image is cumbersome, especially on mobile. It also requires respondents to have a Google account (file uploads are only available when "Restrict to users in your organization" is enabled or respondents sign in).
For many use cases, a simple checkbox is more practical than a signature:
In many cases, the reason people want a signature field is because they need someone to formally sign a submission — a manager signing off on a purchase order, a supervisor confirming a safety checklist, a client signing a contract or agreement. The workarounds above are clunky for this. What you actually need is a way to send the form submission to a signer and capture their real signature.
The Form Approvals add-on has a built-in "Needs to Sign" role type that does exactly this. When you add a recipient with the "Needs to Sign" role, here's what happens:
This gives you a real, drawn signature — not a typed name or a checkbox — without any of the friction of the file upload workaround. The signer doesn't need a Google account, doesn't need to download an app, and doesn't need to upload anything. They simply draw their signature in the email link they receive.
To add a signer to your workflow:
You can combine signers with approvers in the same workflow. For example, a purchase order could go to a manager for approval first, then to the vendor contact for signature. Learn more about role types.
Once a signature has been captured, Form Approvals can generate a PDF document that includes the form response data, the approval history, and the collected signature. This is ideal for creating signed records like:
You can export a PDF from the Form Approvals dashboard after a request has been completed, or set up a custom template (using Google Docs, Sheets, or Slides) that the add-on automatically populates with the form response, approval records, and signatures — then attaches as a PDF to your email notifications. Use the <<Recipient 1 Signature>> marker in your template to insert the captured signature. Learn more about generating PDFs.
If your signature need is really an approval need, try Form Approvals — free to start with 20 responses per month. View pricing or get started today.