There is no Export to Excel button in Google Forms. That is the whole reason this search exists. Google's own spreadsheet is one click away, an .xlsx file is not, and the gap has to be crossed by a route that nobody signposts.
There are three routes, and they are not interchangeable. One produces a file you can email to a colleague. One produces something that keeps updating as new responses arrive. One produces a mess if the form has a lot of responses. Knowing which is which takes about four minutes, and choosing wrong costs an afternoon of rebuilding a pivot table on stale data.
The three routes, side by side
| Route | What you get | Keeps updating | Best for |
|---|---|---|---|
| Download responses (.csv), open in Excel | One file, one sheet, plain text | No | A one off handover, or feeding another system |
| Link to Sheets, then File, Download, Microsoft Excel (.xlsx) | A real workbook with formatting intact | No, the download is a snapshot | Reporting that goes to someone who works in Excel |
| Link to Sheets and leave it linked | A spreadsheet that appends a row per response | Yes, inside Google Sheets only | Anything where the numbers are checked more than once |
The third row is the one people skip past, and it is usually the right answer. Excel files do not refresh themselves. If the report is going to be looked at again next week, the question is not how to get the data into Excel but whether it needs to be in Excel at all.
Route one, the CSV download
Open the form, click Responses at the top, then More, then Download responses (.csv). The file lands in your downloads folder.
Opening that file by double clicking it works, and sometimes produces text that looks wrong: accented characters replaced by symbols, or every field crammed into column A. Both are the same class of problem, and both are fixed by importing rather than opening. In Excel, on the Data tab, in the Get & Transform Data group, choose From Text/CSV, pick the file, then set the File Origin and the Delimiter in the preview before clicking Load. Microsoft documents that the preview updates immediately, so the right combination is the one where the columns line up on screen.
One detail matters for big forms. Google documents that if you download responses as a CSV and the rows are not sorted by the timestamp of submission, it can be because the form has more than 10,000 responses. Nothing is missing, but the order is no longer chronological, so any analysis that assumes row order is reading a shuffled deck. Sort on the Timestamp column before doing anything else.
A CSV also carries no formatting, no formulas and no second sheet. If your report has three tabs and a chart, this route throws all of that away every time you run it.
Route two, through Google Sheets to .xlsx
At the top right of the Responses tab, click Link to Sheets. Google offers a choice through More, Select destination for responses: create a new spreadsheet, or select an existing one. Every response becomes a row, with Timestamp first and one column per question.
From there, in Google Sheets, click File, then Download, then Microsoft Excel (.xlsx). This is the route worth using for anything that a person will read, because the workbook arrives with the header row, the column widths and any number formatting you applied, rather than as raw text.
Two permission facts to hold onto. Google notes that when a new response spreadsheet is created, form collaborators automatically get access to it, and that later changes to the form's permissions do not synchronise: access has to be updated on the form and the sheet separately. A colleague removed from the form keeps the spreadsheet unless somebody removes them there too.
If the sheet should stop receiving new rows, Unlink form under More on the Responses tab stops the flow while leaving existing data intact, and Select destination for responses reconnects a spreadsheet later.
The limits that decide the route for you
These are published numbers, and they arrive without warning.
Past 10,000 responses, Google documents that the question view and the individual view can stop being offered inside Forms, and that a downloaded CSV may no longer be sorted by timestamp.
Past 50,000 responses, the response summary can go missing.
Past 100,000 responses, Google documents that a form's responses may not sync with Sheets. That is the one to watch on this route, because a linked spreadsheet that has quietly stopped receiving rows looks exactly like a spreadsheet that is up to date.
Google Sheets holds up to 20 million cells or 100MB for spreadsheets created in or converted to Sheets. Forty questions across 100,000 responses is four million cells, so the cell ceiling is rarely the binding constraint, but a sheet that has grown extra tabs of formulas can reach it.
Excel holds 1,048,576 rows by 16,384 columns per worksheet, which no form response set is likely to trouble. The direction that does bite is conversion in the other way: Google notes that when a document is converted from Excel to Google Sheets, any cell with more than 50,000 characters is removed. A long paragraph answer survives comfortably. A pasted document does not.
When the form changes, the export changes shape
A form is rarely finished. Someone adds a question in March, and from that point the response set has one more column than the reports built against it.
Google allows up to 300 pieces of content in a single form and up to 75 sections, so there is plenty of room for a form to drift a long way from the shape it had when the first pivot table was built. The practical consequence is narrow but sharp: anything downstream that refers to a column by its letter will eventually point at the wrong question.
The defence is to reference by header rather than by position. In Excel, load the CSV or the workbook as a table, then use structured references or an INDEX and MATCH pair keyed on the header text. Rebuilding a report because column L became column M is the single most common reason people say the export is fragile, and it is entirely avoidable.
The same caution applies to the header row itself. Question text becomes the column name, so long questions produce unwieldy headers, and two questions worded similarly produce two headers that are hard to tell apart at a glance. Short, distinct question wording is worth the effort before the responses start arriving rather than after.
Doing it without Excel on the machine in front of you
The route through Google Sheets needs nothing installed. Google Drive previews Excel files in both .XLS and .XLSX form, so a workbook someone sends you can be read without a licence, and a personal Google account comes with 15 GB of storage shared across Drive, Gmail and Photos, which is more than enough for response data.
On a phone, the Google Sheets app opens the linked spreadsheet directly. Downloading an .xlsx on a phone and finding something that opens it is the harder path, so for a quick check on the way to a meeting the linked sheet wins outright.
If nobody should have to run the export at all
Every route described so far is a person clicking things. That is fine monthly and tiresome weekly.
Two ways out exist. The first is to stop downloading and read the linked spreadsheet, which updates itself. The second is to let the response arrive where it is needed in the first place. Some form tools publish an API, appear in the Zapier app directory, or ship a community node for n8n, with triggers that fire the moment a response arrives. Chat notifications into Teams, Slack, Discord or Chatwork cover the simpler case where somebody just needs to know that something came in.
None of that removes the need for a spreadsheet. It removes the need for the spreadsheet to be assembled by hand.
What the export does not bring with it
This is the part that turns a five minute job into a recurring one.
A file upload answer is a pointer, not a file. Google stores uploaded files in a folder on the form owner's Drive. The spreadsheet column holds a link, so the person who opens your .xlsx sees an address they may have no permission to follow. Any handover that includes attachments needs the Drive folder shared as a separate step.
Checkbox answers land in one cell. Multiple selections arrive comma joined in a single column, which Excel treats as one string. Counting them means splitting the column first, every time you re export.
There is no owner, no status and no reply. Google Forms holds none of these, so the export cannot carry them. Whatever your team knows about a submission lives in the columns somebody added by hand.
That last point is why the export becomes a habit rather than a task. The loop runs like this: export to Excel, add columns for who is handling it and what was said, work from that file for a week, then find that twelve new responses arrived and the annotated file is now the stale one. Re export, and the annotations are lost. Copy them across by hand, and the errors start.
Getting off the export loop
The loop is not caused by Excel and it is not caused by Google Forms. It is caused by keeping the answers in one place and the work about the answers in another.
A form tool with response management closes that gap by putting both in the same record. Each response carries an owner and a stage. The fields your team fills in after the submission arrives are defined once and appear as columns in the list and in the CSV, in the same order, so an export is a report rather than a rebuild. Replies go out from the response itself and stay on its history. The Features page covers what that includes, and the demo shows a populated workspace rather than an empty one.
Where a live spreadsheet genuinely is the destination, it is worth checking whether your tool appends rather than replaces. A row per new response, with a stage change updating that same row, means the spreadsheet stays current without anybody running an export at all.
What to change first
If the export exists so that somebody can read the numbers, keep the spreadsheet linked and stop producing .xlsx files: the link updates itself and the file never will. If the export exists so that your team can track who is handling what, the columns you keep adding by hand are the actual requirement, and no export route will make them survive the next refresh.
Decide which of those two it is before touching the form again. If it is the second, move the intake somewhere that holds the owner and the status on the response, and keep the export for reporting only. Halict is free for one person with unlimited forms and unlimited responses, which is enough to test the idea against a real intake before changing anything.
Q1. Is there a direct Export to Excel option in Google Forms?
No. The two built in exits are Download responses (.csv) under More on the Responses tab, and Link to Sheets. An .xlsx file comes from the linked Google Sheet through File, then Download, then Microsoft Excel (.xlsx).
Q2. Will the Excel file update when new responses come in?
No. Both the CSV and the .xlsx are snapshots taken at the moment you download them. Only the linked Google Sheet keeps appending rows, so anything that needs to stay current has to be read there rather than in a downloaded file.
Q3. Why does my downloaded CSV show strange characters in Excel?
That is usually a character encoding mismatch from opening the file directly. Import it instead: on the Data tab, in Get & Transform Data, choose From Text/CSV, then set File Origin and Delimiter in the preview until the columns and the text look right, and click Load.
Q4. My linked spreadsheet stopped getting new rows. Why?
Check two things. The form may have been unlinked, in which case Select destination for responses under More reconnects it. Google also documents that a form's responses may not sync with Sheets once it has more than 100,000 responses, which looks identical to a sheet that is simply up to date.
Q5. Do uploaded files come across in the export?
No. Google stores uploaded files in a folder on the form owner's Drive, and the export carries a link to each one rather than the file itself. Anyone who needs the actual documents also needs access to that Drive folder, which has to be granted separately.