How to generate PDF from Google Form responses: what Forms does itself and three routes that work

What Google Forms does and does not do with responses

Google Forms does not create a designed PDF for each response by itself. Google's help pages on viewing and saving responses, read on 3 October 2026, describe four things: viewing answers in the form's Responses tab by summary, by question or by person; linking the form to a Google Sheet; downloading all responses as a CSV file; and turning on email notifications for new responses. None of those pages describes a PDF export.

So to get a PDF from a Google Form you add something on top. Google's own help points to the options: add-ons and Apps Script. A third route uses an automation tool to pass each response to a template API.

Google's own options: Sheets, add-ons and Apps Script

Add-ons. Google's help page gives the steps for Forms: open the form, click More at the top right, click Add-ons, pick one, then Install and Continue. The add-on will ask for access to the data it needs. We have not assessed individual add-ons, so check each one's permissions and pricing on its Google Workspace Marketplace listing.

Apps Script. Google's developer documentation describes an installable form submit trigger that runs when a user responds to a form. There are two versions: one for Google Forms itself, where the event object carries a response (a FormResponse), and one for the linked spreadsheet, where it carries namedValues, the question names and answers. A script can copy a Google Docs template, replace placeholders with those values and convert the result with the documented call doc.getAs('application/pdf'). Google also publishes a sample solution that generates and emails PDFs from Google Sheets data, a useful starting point.

To add the trigger by hand, open the Apps Script project, click Triggers, click Add Trigger, choose the form submit event and save.

Zapier with a template API: the steps from CraftMyPDF's tutorial

Prerequisites and plan. A Google Form, a Zapier account and a CraftMyPDF account. CraftMyPDF's pricing page lists Zapier on every plan including Free, which allows 50 PDFs a month and 3 templates (read 3 October 2026). You also need a template built in its editor and your API key from the API Integration tab.

1. In Zapier, create a Zap and choose Google Forms as the trigger app with the event New Form Response.
2. Connect your Google account, select the form and test the trigger so Zapier loads recent responses.
3. Add an action step, choose CraftMyPDF and the event Create PDF.
4. Authenticate with the CraftMyPDF API key.
5. Set the action fields: Region, Template, Version and the payload type. The tutorial uses the Dictionary payload type.
6. Enter one key per template placeholder and map each to a form answer.
7. Test the step, check the generated PDF, then turn the Zap on.

CraftMyPDF lists Make.com on every plan too. If you are weighing this against writing code, see no-code or API.

Worked example: an order form with three fields

CraftMyPDF's tutorial uses a form with three short-answer questions: Company Name, Email and Company Address, feeding its sample invoice template. In the Zap, three dictionary keys are mapped to those three answers. Each submission produces one PDF and uses one credit.

On the Free plan that covers 50 submissions a month. A form that receives 400 responses a month needs the Lite plan at $29 a month, which allows 1,200 PDFs (pricing page, 3 October 2026). Zapier's own plan limits apply on top; we did not verify them for this page. The CraftMyPDF pricing page has the full plan table.

Mistakes to avoid with Google Form PDFs

• Keys that do not match the template. A dictionary key spelled differently from the template's placeholder will not match it. Write the mapping down first in a field map.
• Renaming a form question after setup. In Apps Script, namedValues is keyed by question name, so a script that looks up the old name no longer finds the answer.
• Expecting script-submitted responses to fire the trigger. Google states that script executions and API requests do not cause triggers to run.
• Forgetting whose account runs it. Installable triggers always run as the person who created them and count against that account's Apps Script quotas.

Which route to choose for your form

If a plain document is acceptable and you already work in Google Workspace, Apps Script with a Google Docs template costs nothing extra and keeps the data inside Google. That is enough for internal confirmations, and you do not need CraftMyPDF for it.

Choose the Zapier and template API route when the PDF is customer-facing and needs a controlled layout, with tables, barcodes or QR codes, and when nobody wants to maintain a script. Choose an add-on when you want the least setup and its permissions are acceptable to you. Before paying for anything, check what your existing tools already do.