Free Tool

4.9/5

Free Google Form Prefill Link Generator

Turn a one-off Google Forms pre-filled link into a reusable template. Every entry field becomes an editable input, and any value can become a merge token your email tool fills in per recipient.

Paste your Google Forms pre-filled link *

In Google Forms: three-dot menu, then "Get pre-filled link".

Everything runs in your browser. Your form link and the values you type never reach our servers, and the history above lives only in this browser's localStorage.

Google Forms counts submissions, not opens.

Wrap your prefilled URL in a Flyn short link and you see the other half of the funnel: opens versus responses, so you know whether the form is the problem or the invite is.

Open counts, free Country breakdown on Pro Branded domains on Pro

Shorten for free

How to Build a Prefilled Google Form Link in 3 Steps

Get the pre-filled link from Google Forms

Open your form in edit mode, click the three-dot menu at the top right, choose "Get pre-filled link", type a sample answer into every question you want to prefill, then click "Get link" and copy it. Your entry IDs come from Google, which is why the flow starts there.

Paste it and edit every field

We parse out every entry parameter, including the split date and time parts and the repeated IDs that checkbox questions produce. Each one becomes a labelled input pre-loaded with the sample answer, so you can rename it, rewrite it, or clear it entirely.

Swap values for merge tokens and copy

Replace any answer with a token such as {{first_name}} or *|FNAME|*. We encode the rest of the value but leave the token delimiters untouched, so your email tool or CRM still substitutes them. Copy the URL and the one-off link becomes a template.

What Is a Prefilled Google Form Link?

A prefilled link is an ordinary Google Forms view URL carrying extra query parameters that populate answers before the respondent sees the page. The shape looks like this:

https://docs.google.com/forms/d/e/1FAIpQLSc.../viewform?usp=pp_url&entry.1045781291=Ada+Lovelace&[email protected]

Each entry.NNNNNNNNN is one question, and the number is an internal ID assigned when the question was created, which is why it looks random and says nothing about the question itself. The usp=pp_url flag is not required. Checked against a live public form on 12 August 2026, the answer prefilled the same with the flag, without it, and with a bogus usp value; dropping the flag also prefilled the same when the request was sent with an Android Chrome user agent and with an iOS Safari user agent. This tool puts usp=pp_url at the front of every URL it builds. When a value is not landing, look at the entry ID, the encoding, and whether the value matches one of the form's options exactly.

Published forms use /forms/d/e/LONG_ID/viewform, which is the responder-facing address. Older or internally shared forms sometimes use /forms/d/DOC_ID/viewform, which is derived from the document ID. This tool accepts both shapes, rebuilds whichever one you pasted, and refuses an editor URL outright, so one does not go out by mistake.

Prefilling is a convenience layer, not a security layer. The respondent sees every value, can change all of it, and nothing is recorded until they press Submit. Use it to remove typing friction, and validate anything that matters again once the response lands in your sheet.

Turning a One-off Prefill Into a Reusable Template

Google gives you a link with your sample answers baked in. That is useful exactly once. The moment you want to send it to two hundred people with their own names in it, you need a template, and that is what merge tokens are for.

Replace the value of a field with your email platform's personalization token instead of a literal answer. Where you would have typed Ada Lovelace, type *|FNAME|*. When the campaign sends, the platform rewrites the token per recipient, so each person clicks a link that already knows who they are.

The catch that trips almost everybody up is encoding. A URL builder that naively percent-encodes the whole value turns {{first_name}} into %7B%7Bfirst_name%7D%7D, and the email platform no longer recognises the pattern it is supposed to substitute. Your recipients get the literal encoded string typed into the form. This tool encodes only the parts of a value that sit outside a token, so the delimiters survive and the substitution still fires.

Beyond email, the same template works anywhere a system does string substitution before a click: CRM workflows, help desk macros, spreadsheet formulas that build a per-row link, or an Apps Script that mails a personalised form invite to each row of a sheet.

Merge token syntax by platform

Platform	First name token	Notes
Mailchimp	\|FNAME\|	Merge tags. \|EMAIL\|, \|LNAME\|, and any custom audience field.
HubSpot	{{ contact.firstname }}	Personalization tokens, referenced by internal property name.
Klaviyo	{{ first_name }}	Django-style template tags with an optional default filter.
Brevo	{{ contact.FIRSTNAME }}	Contact attributes are upper-case by convention.
ActiveCampaign	%FIRSTNAME%	Percent-wrapped personalization tags, conventionally upper-case.
Salesforce Marketing Cloud	%%FirstName%%	Personalization strings resolved from the send data extension.

All six shapes are recognised and left unencoded by this tool. Check your own account for the exact field names, since custom properties differ per audience.

Which Question Types Can Be Prefilled

Most Google Forms question types can be prefilled. The differences are in how the value has to be formatted, and in file upload, which cannot work from a URL at all.

Question type	Prefill	How the value is sent
Short answer, paragraph	Yes	Any text. Spaces and punctuation are percent-encoded for you.
Multiple choice, dropdown	Yes	Value must match the option text exactly, including case.
Checkboxes	Yes	Repeat the same entry ID once per selected option.
Linear scale	Yes	Send the number you want selected, for example 4.
Multiple choice grid	Yes	One entry ID per row, value is the column label.
Date	Yes	Splits into entry.ID_year, entry.ID_month, entry.ID_day, or send one entry.ID=1998-03-07. Send the year as four digits: 98 is read as the year 0098, with no error.
Time, duration	Yes	Splits into entry.ID_hour and entry.ID_minute, plus entry.ID_second for a duration.
File upload	No	A URL cannot carry a file.

Prefill Mistakes That Break the Link Silently

A bad prefill usually fails quietly rather than erroring, leaving the field blank, which is why these are so easy to ship without noticing.

The option text does not match

Prefilling a dropdown with "yes" when the option reads "Yes" leaves the question blank with no error at all. Copy option labels out of the form rather than retyping them, and watch for trailing spaces that survived a paste.

You copied the share link, not the prefill link

The URL from the Send button and the forms.gle short link contain no entry parameters, so there is nothing to edit. The URL produced by "Get pre-filled link" is the one that carries the entry IDs this tool reads.

A question was deleted and recreated

Recreating a question mints a brand new entry ID, so an older link stops prefilling that field with no warning. Rewording a question is safe, rebuilding it is not. Regenerate the pre-filled link after any structural edit.

The merge token got percent-encoded

If the braces or pipes in your token are encoded, the email platform stops recognising it and your recipients see raw characters in the form. Keep the token option switched on here so only the surrounding text is encoded.

The multi-section page parameter was lost

Forms split into sections carry a pageHistory parameter that decides which page opens. Strip it and your respondent can land on the wrong section with the prefilled answers hidden behind a Next button. Any extra parameters in your pasted link are preserved.

Why Use Flyn's Prefill Link Generator?

Built for the part Google leaves out: making the link reusable, readable, and measurable once it goes out the door.

Token-safe encoding

Encodes the text around your merge tokens but leaves the tokens themselves as literal text, so your email tool or CRM can still substitute them.

100% in your browser

Your form link and every value you type stay on your device. No request carries them to us.

Handles the odd shapes

Split date and time parts, repeated checkbox IDs, sentinel markers, and the pageHistory parameter multi-section forms need are all preserved.

Measurable after the send

Google Forms reports submissions. Wrap the prefill URL in a Flyn short link and you see opens too, so you can tell a bad invite from a bad form.

Frequently Asked Questions

Where is "Get pre-filled link" in Google Forms?

Open your form in edit mode, click the three-dot overflow menu at the top right of the editor, and choose "Get pre-filled link". Google opens a preview of your form where you type a sample answer into each question you want to prefill. Scroll to the bottom, click "Get link", then click "Copy link" in the toast that appears. That copied URL is exactly what you paste into this tool.

Why do Google Form entry IDs look like random numbers?

Each question carries an internal numeric ID, and that ID becomes the query parameter name, for example entry.1045781291. The number does not describe the question, so a pasted link reads as a wall of digits. That is why this tool shows the sample answer from your link next to each field and lets you type your own label, so the wall of digits becomes a readable list.

What is a prefilled Google Form link?

It is a normal Google Forms view URL with extra query parameters that populate answers before the respondent sees the form. The shape is /forms/d/e/FORM_ID/viewform?usp=pp_url&entry.123456789=Value. When someone opens it, the matching questions already contain your values and the rest of the form is blank. Nothing is submitted until the respondent clicks Submit themselves.

Can I prefill checkboxes, dropdowns, and multiple choice?

Yes, but the value has to match the option text character for character, including capitalisation, punctuation, and any trailing spaces. If it does not match an existing option, the question is left blank with no error shown. For checkbox questions that accept several answers, repeat the same entry ID once per option. This tool keeps every repeat when it rebuilds the URL.

Can I prefill a date or a time question?

Yes, and Google splits them into separate parameters. A date question becomes entry.123_year, entry.123_month, and entry.123_day, while a time question becomes entry.123_hour and entry.123_minute. Send the year as four digits: a two-digit year like 98 is read literally as the year 0098, not 1998, and Google accepts it silently, so the form quietly carries a date in the year 0098. Leading zeros elsewhere are fine, so entry.123_month=03 and entry.123_month=3 both work. What does break is an incomplete value: a month and day with no year, or an hour with no minute, prefills nothing at all and raises no error. A date question also accepts a single combined parameter, entry.123=1998-03-07, instead of the three split ones. This tool labels each of those parts for you so you do not have to guess which number goes where.

Does the respondent see the prefilled values, and can they change them?

Yes to both. Prefilling is a convenience, not a lock. Prefilled values appear in the form as ordinary answers, and the respondent can edit or delete them before submitting. Treat prefilled values as a starting draft that saves typing, never as a field you control, and validate anything important again on your side after the response lands.

Is a prefilled link secure for sensitive data?

No. Everything you put in a prefilled link sits in plain text in the URL, which means it shows up in browser history, in the address bar, in referrer headers, in email client link previews, and in proxies or security appliances that log traffic. Never prefill passwords, national ID numbers, health details, or payment information. Prefill low-risk identifiers only, such as a first name, an order reference, or a campaign code.

How do I use merge tokens with Mailchimp?

Build the link here with the value set to a Mailchimp merge tag such as *|FNAME|* or *|EMAIL|*, keep the "keep merge tokens unencoded" option switched on, then paste the finished URL straight into your Mailchimp campaign as a link. Mailchimp substitutes the tag per recipient at send time, so each recipient gets a form link already carrying their own name and email. Any email tool that substitutes a merge tag at send time can be used the same way, with that tool's own token syntax in place of Mailchimp's.

Why do my merge tokens arrive as %7B%7Bname%7D%7D?

Because something percent-encoded the braces before your email tool got a chance to substitute them. Once the token is encoded it no longer matches the pattern the platform scans for, so it is passed through as literal text and your respondents see the encoded string in the form. This tool solves it by encoding only the parts of a value that are not merge tokens, leaving the token delimiters intact so the substitution still fires.

Is there a character limit on a prefilled URL?

We did not find a maximum documented on Google's Forms help pages, and its Forms API limits page lists rate limits rather than a URL length. Google's servers do turn away a long enough request URL. In a check on 12 August 2026, run with a made-up form ID so that no real form was involved, a request to docs.google.com whose total URL was 8,200 characters was routed and answered with an HTTP 404 for the missing form, while the same request at 8,201 characters came back as an HTTP 400 Bad Request page, so the longer URL was turned away before the form ID was looked up. None of that comes from your browser: Chromium's URL display guidelines say "Chrome limits URLs to a maximum length of 2MB". Very few prefills get anywhere near 8,200 characters. Email is the tighter constraint, since RFC 5322 says "Each line of characters MUST be no more than 998 characters", and a link longer than that cannot sit on one line of a conforming message, so mail software has to wrap or encode it somehow. This tool shows a live character count and flags a URL past 2,000 characters. Treat 2,000 as this tool's own cushion rather than a published threshold, and keep an emailed link as short as you can.

Why did my prefilled link stop working after I edited the form?

Deleting and recreating a question gives it a brand new entry ID, so the old parameter in your link no longer matches anything and the value is dropped without any warning. Renaming a question is safe because the ID is unchanged, but rewording a multiple-choice option is not, since prefill values are matched against the option text. After any structural edit, generate a fresh pre-filled link and re-paste it here.

Can I prefill a file upload, linear scale, or grid question?

File upload questions cannot be prefilled, because a URL cannot carry a file. Linear scale questions accept the numeric value you chose, and multiple choice grids use one parameter per row with the column label as the value. If a question type refuses to prefill, generate a pre-filled link from Google itself and check whether an entry parameter appears for it; if there is none, that question type is not supported.

Does a prefilled link submit the form automatically?

No. A prefilled link only populates the fields. The respondent still has to press Submit, and nothing is recorded until they do. We looked through Google's Forms help pages and did not find a URL parameter that submits a form on load. If you need a response recorded without a person clicking Submit, look at Apps Script instead: Google's FormResponse reference describes using "withItemResponse(response) and submit()" to programmatically submit a response to the form, and documents submit() as returning "A newly created response saved to the form's response store". The Google Forms REST API is a poor fit for this. Its forms.responses reference documents "get: Get one response from the form" and "list: List a form's responses", and we did not find a method there that creates a response. Either way, treat prefilling as a convenience layer and not a security layer: the respondent sees every value and can change all of it before submitting.

Can I shorten a prefilled Google Form link?

Yes, and it is usually worth it because prefilled URLs are long and ugly in an email or a printed handout. A short link also counts opens, so you can compare how many people opened the form against how many submitted it. Be aware that a shortened URL hides the merge tokens, so shorten the link after substitution or use a per-recipient link rather than one shared short link.

Does this tool send my form or my data anywhere?

No. The parsing and rebuilding happen entirely in your browser with client-side JavaScript, and no request carries your form link or your answers. Your form link, your entry values and your merge tokens are never sent to us, and the history lives only in this browser's localStorage.

Ready to see who actually opens the form?

Build the prefilled link here for free, then wrap it in a Flyn short link to count every open. Free click counts and QR codes, with country, device, and referrer breakdowns plus custom domains on Pro.

Start free, no credit card Read the API Docs