How to Import Questions into Google Forms from a CSV

How to import questions into Google Forms from a CSV

Google Forms cannot import questions from a CSV on its own. Its built in "Import questions" button only pulls questions from another Google Form. To get a spreadsheet of questions into a Form you need one of three routes: a Google Workspace add-on such as Form Builder, a short Apps Script that reads the sheet and creates the questions, or a third party importer. This guide covers all three, when each is worth it, and the CSV layout that makes any of them work.

Why the native import does not do what you expect

The button exists, which is what makes this confusing. Open a Form, look at the right hand toolbar, and there is an "Import questions" icon. Click it and you get a file picker showing your existing Google Forms. That is the whole feature. It is a Form to Form copier, useful when you keep a question bank in one Form and assemble tests from it, and useless when your questions live in Sheets, Excel, or a CSV export from somewhere else.

This trips people up every year, and the reason is worth knowing. A Form question is not a row of text. It is a typed object: a stem, a question type, an ordered option list, a correct answer key, a point value, and optional feedback shown when someone answers wrong. A CSV row is flat text. Something has to decide which column is the key and which are distractors, and Google has never shipped that mapping step. So the work does not disappear. It moves to an add-on, a script, or you.

Get the CSV layout right first

Every method below works better with the same shape, and a badly shaped file is the usual reason an import "fails" when the tool is fine. One question per row, one concept per column:

• Question. The full stem, readable on its own without the options.
• Option 1 to Option 4. One option per column. Do not cram four options into one cell separated by semicolons.
• Correct answer. Either the exact text of the right option or its number. Pick one convention and keep it for the whole file.
• Points. A number. Blank is not zero to every importer, so fill it in.
• Feedback. The line shown when someone gets it wrong. Optional, and the column most worth having.

Two details save the most rework. Keep the correct answer text character for character identical to the option text, because most importers match on exact string and a trailing space is enough to break the key. And save as UTF-8, or curly quotes and accented characters arrive as mojibake in your Form.

Method 1: a Google Forms add-on

This is the right default for most people. Form Builder is the add-on most teams land on: install it from Google Workspace Marketplace, open your sheet, point it at the range that holds your questions, map each column to its role, and it creates the Form questions for you. Jotform's AI Form Builder does a similar job and tries to infer question patterns from your content rather than asking you to map columns by hand.

The tradeoffs are honest ones. Add-ons need permission to read your Sheets and edit your Forms, which some IT departments will not approve without review, and that is a reasonable thing for them to check. Free tiers tend to cap how many questions you can push per import. But for a fifty question bank you already have in a spreadsheet, this is fifteen minutes of work rather than an afternoon.

Method 2: Apps Script

If add-ons are blocked, or you are doing this every week, a script is more durable. Apps Script runs inside your own Workspace account, needs no third party permission, and turns the import into something you can rerun. The shape of it is short: open the sheet with SpreadsheetApp, read the rows, then for each row call form.addMultipleChoiceItem(), set the choices, mark the key with createChoice(text, true), set the points, and attach feedback with FormResponse feedback builders.

Two things to know before you start. The Form must already be a quiz, which you switch on in Settings, or points and answer keys silently do nothing. And scripts hit quota limits on large runs, so a thousand question import wants batching and a pause rather than one long loop.

Method 3: skip the CSV and generate the questions where they belong

Worth asking: why is there a CSV at all? Usually because someone typed a question bank into a spreadsheet, since typing in Sheets beats typing in the Forms editor. The spreadsheet is a workaround for the Forms editor being slow, and the import is a workaround for the workaround.

If the quiz is about a video, a course module, a recorded training session, a webinar, or a lecture, the writing step is the one worth removing. An online quiz maker that generates the questions reads the source and produces the stems, options, marked answer key, points, and feedback in one pass, laid out in the column order Forms importers expect. Our Google Forms quiz maker exports exactly that CSV: paste a video link, review the draft, cut what does not fit, then run it through the add-on or script above. You still grade and collect responses in Forms, which is the part Forms is genuinely good at.

The questions are generated from your own video and you edit them before anyone sees them, so the review pass still matters. It is just review instead of authorship.

Which method should you pick?

A rough rule from watching people do this: importing once, under a hundred questions, add-ons already approved, use the add-on. Importing on a schedule, or your admin blocks add-ons, write the script once. Questions do not exist yet and the material is a video, generate them and import the export. Under ten questions, honestly, just type them into Forms. The setup costs more than the typing.

Common errors and what they actually mean

• Questions import but no answer key. The Form is not in quiz mode. Settings, then "Make this a quiz", then reimport.
• Every question comes in as short answer. The importer could not find your option columns, usually because options are stuffed in one cell or the header row is missing.
• The key is wrong on some rows. Whitespace or punctuation mismatch between the correct answer column and the option text. Run a trim over both columns.
• Half the file imported. A free tier cap or a script quota, not a corrupt file. Split and rerun.
• Strange characters. The file was not saved as UTF-8.

Does any of this survive a real training program?

Forms is a fine place to run a quiz and a poor place to run a curriculum. It does not track who completed which module, it does not remind people, and it does not issue a record anyone can audit later. Teams usually notice this at the point compliance asks who has been trained. If your quizzes are one step inside a program where you need to onboard people, track completion and certify them, that record keeping belongs in a system built for it, and the quiz becomes one graded step inside the course rather than a standalone link.

For a class quiz, a hiring screen, or a knowledge check after a training video, Forms plus a clean import is genuinely enough, and the CSV route above will keep working.

The short version

Google Forms imports questions only from other Google Forms, so a CSV needs an add-on, an Apps Script, or a third party importer. Shape the file with one question per row and one option per column, keep the correct answer text identical to the option text, save as UTF-8, and turn on quiz mode before you import or the answer key will not stick. And if the questions have not been written yet, generating them from the source beats typing them into a spreadsheet so you can type them into a Form.