QR code for Google Forms: create one that still works next year

A QR code for Google Forms is one of the quickest ways to collect feedback on paper: a poster in a waiting area, a card on a counter, a bookmark in a returned book. The catch is that Google Forms does not make the code for you. Its help page on sharing a form lists a responder link, a shortened URL, an email option and embed code, and nothing about QR codes (checked 28 October 2026). So the code has to come from somewhere else, and where it comes from decides whether it still works when the form changes.

This guide walks through the steps first. After that it explains why a dynamic code is worth the small extra effort for anything you print.

Why a QR code for Google Forms has to come from outside the form

Google's help article Publish & share your form with responders describes how a form becomes reachable. Once you publish it, responders can open it. Under "General access" you can give access to anyone with a link. You can then choose "Copy responder link", tick "Shorten URL" for a shorter version, send the form by email, or select "Embed HTML" to place it on a website.

That gives you a URL. Any QR code generator can turn that URL into a pattern, and so can a browser: our article on Chrome's built-in QR tool covers that route. The choice that matters is what the code contains. A static code stores the Google link itself. A dynamic code stores a short link that you control and that forwards to Google. Only the second one can be pointed at a different form later.

Step by step: from published form to printed code

The whole process takes a few minutes once the form is ready.

1. Publish the form and check access. Make sure responders can open it. If people outside your organisation must answer, look at the "anyone with a link" setting under General access.
2. Copy the responder link. Use "Copy responder link". The shortened URL works too, but you do not need it, because the dynamic code will be short anyway.
3. Create a dynamic code. Paste the link as the destination of a new code in EUQR's dynamic QR codes. Give the code a name that says where it will hang, for example "Library North, entrance poster".
4. Repeat per placement. Make one code per poster, card or bookmark, all pointing at the same form. This is what lets you compare placements later.
5. Download the right file. Use PNG for screens and slides and SVG for anything a printer handles, because SVG stays sharp at any size. EPS and PDF are available from Pro.
6. Test before printing. Scan the proof with two different phones, one iPhone and one Android, in the light where it will hang. The 10-point test checklist lists what else to check.
7. Print and put it up. Add one line of text next to the code that says what the form is about and how long it takes. People scan more readily when they know what they will get.

An example: three library branches, one form, nine codes

Take a city library with three branches that wants reader feedback for a full year. The team builds one Google Form with six questions and creates nine dynamic codes. Each branch gets a poster at the entrance, a card at the loan desk and a bookmark that staff hand out with returned books.

All nine codes open the same form. After a month the counts show that bookmarks in the central branch bring the most scans, while the posters in the north branch barely get noticed because they hang behind the door when it is open. The team moves the posters and leaves the form alone.

In spring the questions change for a new survey about opening hours. A new form is made, the nine codes are edited to point at it, and not one bookmark has to be reprinted. The form still tells the team how many responses arrived. The codes tell them where people came from. Together they show which placement deserves the print budget next year.

Why the raw form link makes a poor printed code

Encoding the Google link directly in a static code works on the day you make it. Over a year, three problems tend to appear.

• The link is long. A full responder link contains a long form identifier. More characters mean more modules in the pattern, so the code has to be printed larger to scan reliably from a distance. A short redirect link keeps the pattern simple. Our guide on minimum code size for print explains the trade-off.
• A new form means a new link. Copying a form or starting a fresh one for next term gives it a new address. A static code keeps sending people to the old form, which may be closed or, worse, still open and collecting answers nobody reads.
• You cannot tell placements apart. Google Forms counts responses. It does not tell you whether a respondent came from the poster, the bookmark or a newsletter. With one static code everywhere, every source looks the same.

A dynamic code removes all three problems. The printed pattern holds a short qreu.eu link, the destination can be changed at any time, and every code has its own count.

What you see per code, and what stays with Google

EUQR counts each scan before it forwards the visitor. In scan analytics you see, per code, how many scans arrived over time, broken down by country, device, browser and phone language. These are aggregate counts. EUQR never stores raw IP addresses and sets no tracking cookies, so the redirect itself needs no cookie banner.

What happens after the redirect is a separate matter. The respondent lands on Google's form, and the answers are collected and stored by Google under its own terms. EUQR does not see the answers and cannot tell you who filled in the form. If your survey asks for personal data, the privacy notice belongs in the form, and your organisation decides whether Google Forms is the right tool for that data. This is not legal advice.

The split also keeps your numbers honest. A scan is a scan, and a response is a response. Comparing scans per code with responses in the form shows where people open the form and then give up, which usually means the form is too long.

Microsoft Forms has its own QR download

If your organisation works in Microsoft 365, the comparison is useful. Microsoft's help article Send a form and collect responses lists a QR option among the ways to send a form: select the QR icon, then Download, and you get a .png to insert wherever your audience can scan it (checked 28 October 2026).

That is handy for a slide or a one-off handout. The article does not describe changing where that image points or counting scans per image. For a printed poster that will hang for months, the same reasoning applies as with Google Forms: put a dynamic code in front of the form link, so you can change the destination and compare placements.

Keeping the code working next year

The title of this guide promises a code that still works next year. Three habits make that true.

First, edit the destination instead of printing a new code. When a survey ends, point the code at the next form, or at a short thank-you page if there is no next form. A code that leads to a closed form frustrates people and teaches them to ignore your posters.

Second, keep the account in the organisation's name. Codes created on a volunteer's personal account leave with that volunteer. Use extra seats so more than one person can edit the destinations; Pro includes four seats.

Third, know what happens if the subscription stops. On EUQR, dynamic codes then show your branded Recovery Page for 90 days and afterwards a generic EUQR page, never a dead error. Static codes keep working forever because they hold the link itself. Plans start at €0.99 per month for ten dynamic codes, and the pricing page lists the rest.

If a survey must stop on a fixed date, put an expiry date or a click limit on a qreu.eu short link and let the code point at that link. In EUQR those settings live on links.

A five-minute check before the posters go up

• The form is published and opens on a phone that is not logged in to your Google account.
• Each code has a name that says where it hangs.
• The printed file is SVG or a high-resolution PNG, with a clear white margin around the code.
• Two different phones open the form from the printed proof.
• A line of text tells people what the form is for and how long it takes.
• Someone owns the account and knows when the survey ends.