How to Create a QR Code for a Google Form (2026)
Making the code takes ten seconds. Making one that still works after it is printed, and telling which poster it came from, takes a little more — here is both.
The three steps
Google has never shipped a QR code feature inside Forms, so every route goes through the share link. There are Workspace Marketplace add-ons that bolt one on, but they want access to your forms to do a job a plain URL already does.
- 1. Get the link. Open the form, click Send, then the link icon. Tick Shorten URL to get a forms.gle address — shorter links make visually simpler codes, which scan faster and survive being printed small.
- 2. Generate the code. Paste the link into our Google Form QR code generator and pick a size. Nothing to install, and no add-on gets permission to read your Drive.
- 3. Test it before it goes anywhere. Scan it with a phone that is not signed into your Google account. This is the step that catches the single most common failure, below.
Check who is allowed to respond
If your form is restricted to your organisation, or has Collect email addresses set to verified, then every scan from a personal phone lands on a Google sign-in screen. The code is fine. The form is fine. The combination is useless on a public poster, and you will not discover it by testing on your own laptop, which is already signed in. Open the code in a private window or on a borrowed phone.
The code is permanent — the link is not
A QR code is not a redirect. It is the URL itself, encoded as squares. There is no dashboard where you later point it somewhere else. That has two consequences worth knowing before you print anything.
First, if you replace the form next term or next season, the old code keeps working and keeps sending people to last season's form — a quieter failure than a dead link, and a worse one, because the responses still arrive and land in the wrong sheet. Second, if you expect to change the destination, encode a link you control — a short link on your own domain, or any redirect service — and point that at the form. Then the printed code stays valid and you change where it goes.
Print size: the 10× rule
The working rule of thumb is that a QR code scans reliably from about ten times its own width. A 2 cm code wants a reader within roughly 20 cm — fine for a table tent or a handout, hopeless for a poster across a room. Size the code for the distance people will actually stand at:
- Table tent, flyer, receipt: 2–3 cm. Download at 512 px so the print does not soften the edges.
- A4 noticeboard poster: 4–5 cm, read from about half a metre.
- Roll-up banner or wall sign: 15 cm and up. This is where most codes fail — scaled down to look tidy in the layout, then unscannable from where anyone stands.
Leave a clear margin around it, keep it dark-on-light, and avoid glossy lamination under a spotlight — glare defeats a camera as effectively as bad contrast does.
Knowing which code produced which response
Print the same code on a poster, a receipt, and a table card, and Google Forms will tell you nothing about which one worked. It does not record UTM parameters — appending ?utm_source=poster to a Google Form link gets you nothing, which is the mistake most people make first.
What does work is a pre-filled link. Add a short-answer question called something like "Location", open the form's three-dot menu, choose Get pre-filled link, type the value for that one placement, and copy the generated URL. Make a separate QR code from each pre-filled link. Every response then arrives already stamped with where it came from. Hide the question from view if you like — the value still submits, and you finally know whether the receipts or the poster earned their space.
Try it live
The classic QR use case — a feedback form on a table card. This one asks one question at a time, which is what the scan-then-abandon problem below is really about.
When people scan and don't finish
A QR code solves distribution. It does not solve the form. Scans arrive almost entirely on phones, and a Google Form that looked reasonable on a laptop becomes a long grey column of fields on a small screen — every question visible at once, a scrollbar that never seems to end, and no sense of progress. People who scanned out of genuine interest leave at question four.
If your scan rate is healthy and your completion rate is not, the fix is on the form side, not the code side. Asking one question at a time is the single biggest change available, because it makes a twelve-question form feel like a conversation instead of a document — see how SiliForm compares to Google Forms for what that changes in practice.
Before you print a thousand of them
- Scanned the printed proof, not the file on screen.
- Tested on a phone signed out of your Google account.
- Confirmed the form is accepting responses and not closed.
- Sized the code for the distance people will stand at.
- Written a line of text beside it saying what it opens and how long it takes.
That last one is not decoration. An unlabelled square is ignored; "Scan to tell us how we did — 30 seconds" is the difference between a code that gets used and a code that gets printed.