FRFormRanger
Google Forms + Sheets add-on

Sync Google Forms Dropdowns and Choices from Google Sheets

FormRanger maps a selected Google Sheets column into a Google Forms dropdown, multiple-choice, checkbox, or grid question. Auto-update choices without maintaining Apps Script: start with one question, run Preflight, update once, then check the public respondent preview.

Free during public launch. Tested on the real Google Forms add-on path: sidebar mapping, save, Preflight, Update now, and respondent preview.

If you are deciding whether to install, use the copied-form first-run test before touching a live form. The useful proof is simple: Preflight passes, Update now reports a changed question, and the public preview shows the expected Sheet values.

Dropdown Multiple choice Checkbox Grid choices Preflight Free launch
Install from Marketplace Run first-run test
First-run pathSheets to Forms
Google Sheetsource column
HeaderSession
Alpha, Beta, Workshop A
Google Formchoice question
QuestionChoose a session
Choices updated from the selected column
FormRangerWorkspace add-on

Link one question, run Preflight, update choices, and verify the respondent-facing form before launch.

Update verified
1. Select source2. Preflight3. Update4. Public preview
First successful update

Where are you now?

Choose the current state and continue with one safe next action. Troubleshooting users stay on the test path; the review path is never shown here.

Install FormRanger
Start from the problem

Pick the Google Forms choices issue you actually have.

External questions rarely start with a product name. They usually start with a dropdown, a Sheet source list, a stale form preview, or a dependent-dropdown expectation. Use the matching path before installing anything on a live form.

1

Dropdown from a Sheet

You have one Google Sheets column and want one Google Forms dropdown or multiple-choice question to use those values.

Open the dropdown sync guide

2

No Apps Script owner

You need a repeatable no-code path instead of maintaining triggers, form IDs, question IDs, and permissions yourself.

Open the no-code guide

4

Dependent dropdowns

You need to separate owner-controlled choice refresh from respondent-time filtering while someone is filling out the form.

Open the limits guide

5

Long dropdown list

The form editor is hard to manage because a dropdown has dozens or hundreds of options that should live in Sheets.

Open the long-list guide

Match the question type

Send each searcher to the exact choice-sync guide.

FormRanger traffic usually arrives with a question type, not the product name. Start with the matching guide, then run the copied-form first-run test before installing on a live form.

A

Import any choice list

Use this when the intent is broad: Google Forms choices from a Google Sheets source list.

Open the import guide

B

Multiple choice from Sheets

Map one Sheet column to one single-choice Google Forms question and verify the public preview.

Open the multiple-choice guide

C

Checkbox list from Sheets

Use a spreadsheet column as the source for a respondent-facing multi-select checkbox list.

Open the checkbox guide

D

Grid choices from Sheets

Refresh grid row or column labels from Sheets before respondents use the form.

Open the grid guide

Google Forms choices from Sheets, not a brand-name shortcut.

Use FormRanger when the real job is keeping Google Forms dropdown, multiple-choice, checkbox, or grid choices aligned with a Google Sheets source list. The search intent is the task: make the form show the current spreadsheet values before respondents use it.

1

Dropdown and multiple choice

Refresh sessions, departments, locations, products, or categories from one clean Google Sheets column.

2

Checkbox lists

Update multi-select choices before launch without maintaining Apps Script triggers, form IDs, or custom authorization.

3

Grid choices

Keep grid row or column labels aligned with the spreadsheet source before sharing the form link.

Failure causes

Why Google Forms choices from Sheets usually fail.

Most failed first runs are not mysterious. They come from a stale mapping, a changed Sheet column, a copied form, or checking the editor instead of the respondent-facing preview.

Source list

The Sheet column moved or changed.

A renamed header, inserted blank row, duplicate-only values, hidden cleanup column, or changed sheet tab can make the mapping point at the wrong data.

Question

The form question no longer matches.

If the dropdown was duplicated, deleted, renamed, or changed from dropdown to another question type, re-select the exact question before updating.

Action

A saved mapping is not an update.

The useful result is Update now reporting that a question changed. Saving configuration only proves the setup was stored.

Preview

The editor is not the final proof.

Always open the public respondent preview after Update now. That is the surface respondents will see.

Real setup screens

What the first-run path looks like.

These screenshots are from the FormRanger setup flow: open the add-on, select the Sheet source, map one question, run Preflight, and update the form choices.

FormRanger sidebar opened in Google Forms
Open the FormRanger sidebar from the Google Forms add-ons menu before editing a live workflow.
FormRanger maps a Google Forms question to a Google Sheets column
Map one supported question to one Google Sheets source column so the first test is easy to verify.
FormRanger Preflight check before updating choices
Run Preflight before changing choices. It should catch file, range, and mapping issues before the update.
FormRanger update success screen after syncing choices
After Update now, open the public preview and confirm the form shows the expected Sheet values.
Choose the path

Manual paste vs Apps Script vs FormRanger.

The right option depends on how often the list changes and who is responsible for maintaining the workflow.

PathGood whenMain risk
Manual pasteThe list changes rarely and one owner can update it before launch.Easy to forget, no repeatable check, and no source-of-truth proof.
Apps ScriptYou have someone who will own code, triggers, IDs, permissions, and errors.Breaks quietly when form IDs, question IDs, or authorization change.
FormRangerSheets is the source list and the owner wants a no-code update flow with Preflight.Still needs a copied-form first run and public preview check before launch.
First-run proof

Do one small update before trusting a live form.

Use a copied form, one supported choice question, and one Sheets column with Alpha and Beta. A successful first run means Preflight passes, Update now reports an updated question, and the public preview shows the expected values.

Install FormRanger Open first-run checklist
Install

Open the add-on inside the Google Form you want to update.

Preflight

Check file access, sheet tab, column, and question mapping before changing choices.

Preview

Open the respondent-facing preview after Update now, not only the editor.

Run the checklist Troubleshoot setup Read setup guide Watch demo
Install confidence

Answer the install questions before changing a live form.

Most Google Forms operators do not install another add-on until three questions are answered: will it touch the right file, will it actually update the public form, and what happens if the setup is wrong?

1

Selected-file access

FormRanger uses a user-selected spreadsheet flow for mappings, then reads that selected source when you update choices.

2

Preflight before update

Check the file, sheet tab, source column, and supported question type before changing the form choices.

3

Respondent preview proof

The useful success signal is not a saved mapping. It is the public preview showing the expected Sheet values after Update now.

Read permissions Run copied-form test Troubleshoot setup
Sheets dropdown guides

These pages separate four common searches: updating a dropdown from Sheets, avoiding Apps Script, troubleshooting stale choices, and understanding dependent dropdown limits.

1

Auto update from Sheets

Use when the Sheet is the source list and you want a repeatable owner-controlled refresh.

Open dropdown update guide

2

No Apps Script

Use when you want Sheets-backed choices without maintaining triggers, form IDs, or script permissions.

Open no-code guide

3

Not updating

Use when a saved mapping exists but the respondent-facing dropdown still shows old choices.

Open troubleshooting guide

4

Dependent dropdown limits

Use when you need to separate live respondent-time filtering from owner-controlled Sheets choice sync.

Open dependent dropdown guide

5

Long dropdown list

Use when the editor becomes hard to manage because the option list is large and better maintained in Sheets.

Open long-list guide

Boundary

Not a booking or inventory lock.

FormRanger updates Google Forms choices from selected spreadsheet data before respondents use the form. It does not reserve seats, process payments, lock inventory, or filter options while a respondent is already filling out the form. If you need live respondent-time logic, a Google Form is usually the wrong surface.

Fix dropdown not updating Read permissions

Frequently asked questions

Which question types work?

Dropdown, multiple choice, checkbox, multiple-choice grid, and checkbox grid choices.

What should I test first?

Use one copied form, one supported question, and one Sheets column with Alpha and Beta. Run Preflight, update, then check the public respondent preview.

Can it handle dependent dropdowns?

Use FormRanger for spreadsheet-backed choice refresh before respondents use the form. It is not respondent-time conditional filtering.

Why did the choices not change after setup?

Most often the mapping was saved but Update now was not run, the source column moved, the question was changed or duplicated, or the public preview was not refreshed after the update.

Should I use this on a live form first?

No. Use a copied form first so you can verify Preflight, Update now, and public preview without risking real respondents.

Install from Marketplace Setup support