Google Form QR Code Generator

In Google Forms, click Send, choose the link tab, and copy the URL — it will look like docs.google.com/forms/d/e/…/viewform. Optionally tick the shortened link option first.

Don't use the edit URL (the one ending in /edit). That link only works for people with edit access, and a poster full of permission errors is a bad afternoon.

Test the printed code with two different phones before you print a hundred of them.

No. Google Forms gives you a responder link, a shortened link, an embed code and email sharing, but its sharing help page has no QR code option. There are two free ways around that without an add-on.

The first is this page: paste the responder link, download the code. The second is Chrome itself. On a computer, open the live form (the responder view, not the editor), click the share icon at the right of the address bar and choose the QR code option; on Android and iPhone it is under Share in Chrome's menu. Chrome's version works, but it downloads a PNG only, with no size or color options, so for anything printed large, use a generator that also exports SVG.

The Google Workspace Marketplace also has third-party QR add-ons for Forms. They are not made by Google, and they ask for access to your forms, which a link-to-QR conversion does not need.

Yes, when you can. A QR code gets denser as the text inside it gets longer, and a denser code needs to be printed larger to scan from the same distance.

Worked example, using the same QR library this page uses: a typical full Google Form link is about 99 characters and produces a code 41 modules across (a module is one black or white square). The forms.gle short link is about 35 characters and produces a 29-module code. With the required four-module margin on each side, that is 49 versus 37 modules in total.

Printed 3 cm wide, each module of the long-link code is 30 ÷ 49 ≈ 0.61 mm; each module of the short-link code is 30 ÷ 37 ≈ 0.81 mm, about a third bigger. Bigger modules scan faster, from further away, and survive a cheap printer better.

QR codes carry spare data so they still scan when part of the code is smudged or covered. The standard has four levels; Denso Wave lists them as roughly 7% (L), 15% (M), 25% (Q) and 30% (H) of the code being recoverable, and notes that M is the most frequently chosen.

This generator uses level M. It is a sensible default for a form link on paper: higher levels make the code denser (the same full Google Form link needs 57 modules at level H instead of 41 at M), which works against you unless the code will get dirty or you plan to cover part of it with a logo. This generator does not add logos, so M is the right trade-off.

If the code scans and opens a page, the QR code is fine and the problem is the form's settings. Check these in order.

Unpublished forms are unreachable for responders. A published form with Accepting responses turned off, or one that hit a close date or response limit, shows its closed message instead of the questions.

A link ending in /edit opens the editor, which only works for people with edit access. Everyone else gets a permission request. Use the responder link (…/viewform or forms.gle).

Settings such as collecting verified email addresses, limiting to one response, or restricting to people in your organization make respondents sign in to a Google Account first. At an event where people scan on their own phones, that step loses people. Turn those settings off if you do not need them, or tell people up front that they will need to sign in.

Usually too small for the distance, too little contrast, a cropped margin, glare from a laminated or glossy surface, or printed on a curved cup or bottle. Reprint larger, dark on white, on matte stock.

Not with Google Forms alone. A static QR code has no counter, and Google Forms does not let you add a Google Analytics tag or store URL parameters with responses, so appending UTM parameters to a Google Form link records nothing.

What does work is a pre-filled link. Add a short-answer question such as Where did you find this form?, then use More → Get pre-filled link, type poster-library into that question, and copy the link. Build one link per placement (poster-library, poster-cafe, flyer), make a separate QR code from each, and the source is saved with every response. You count submissions, not scans, but submissions are the number you care about.

If you need scan-level source data and UTMs to flow into Sheets or a webhook automatically, that needs a form tool with hidden fields. Zunoform's hidden fields, for example, store utm_source and similar URL parameters with each response and add them as columns in Google Sheets.

A common use is a sign-in sheet: a code on the door or the first slide, and a form with name and email. Two cautions. Anyone can photograph the code and submit from elsewhere, so a static code proves someone had the code, not that they were in the room. And a single code for a recurring class collects every session into one sheet; add a Date question, or build one pre-filled link per session.