HomeGuides › Using Google Forms offline

Can you use Google Forms offline?

Last updated September 2026 · ~8 minute read

Short answer: no. Google Drive's offline mode covers Docs, Sheets and Slides — Forms is not on the list, on any platform. A respondent who loses signal mid-form stops being autosaved (Google's own words: “If you're offline, autosave doesn't work.”) and cannot submit. An editor cannot save a change to a form without a connection. The dependable field workaround is still paper.

This is one of the few Google Forms questions where the answer is a flat no rather than a “yes, but”. It is worth knowing exactly where the line falls, because the parts that do survive a dead connection are narrower than most people assume — and knowing them in advance is the difference between a lost afternoon of data and a stack of paper you type up later.

How we checked

Rather than assert it, we read Google's own documentation: the Drive help page Use Google Drive files offline, the editors page Work on Google Docs, Sheets, & Slides offline, the Forms page Autosave your response progress on a Google Form, and the Forms editing help. Quotes below are from those pages.

Which Google editors offline mode actually covers

Google's offline page states it plainly: “If you aren't connected to the internet, you can still create, view, and edit files on:”

  • Google Docs
  • Google Sheets
  • Google Slides

That is the whole list. Google Forms is not named on either offline page — not in the Drive version, not in the Docs editors version. The setup those pages describe is Chrome or Microsoft Edge plus the Google Docs Offline extension, and the checkbox you tick reads “Create, open, and edit your recent Google Docs, Sheets, and Slides files on this device while offline.” Forms is not in the sentence, so ticking it does nothing for a form.

Worth being precise about what that means: Google does not publish a page saying “Forms does not work offline”. What it publishes is a list of the editors that do, and Forms is absent from it. Absence from the supported list is the answer you get, and it matches what happens in practice — open a form with the network off and you get a browser error page, not an editor.

What happens to a half-filled response when the signal drops

Google does document draft saving for respondents, and it is easy to mistake it for offline support. It is not. The autosave page says: “When you fill out a Google Form in your Google account, your progress is automatically saved as a draft for 30 days.” Three limits matter:

  • It requires a Google Account. The draft is tied to the account you are signed in with. An anonymous respondent on a public link gets nothing.
  • It requires a connection. The same page states: “If you're offline, autosave doesn't work.” The draft is saved to Google, not to your device.
  • The form's creator can switch it off. If autosave has been disabled for a form, Google says a signed-in respondent sees “Saving disabled” at the top instead of “Draft saved”.

So the realistic sequence in a basement, a field or a tunnel is: the answers already synced before the signal went are held as a draft for 30 days; anything typed after that point lives only in the open browser tab; and pressing Submit does not queue anything for later — it simply fails. Close the tab and those last answers are gone. Google documents no send-when-reconnected behaviour for form responses anywhere.

What a form editor can and cannot do

Less, not more. Editing a form is a live operation against Google's servers, and Google publishes no offline mode for the Forms editor on the web, on Android or on iOS. In practice that means:

  • You cannot open the editor for a form you have not already got on screen.
  • You cannot create a form, add a question, or change a setting and have it sync later.
  • You cannot look at new responses, because fetching them is a network call.
  • There is no version of the form cached by the Docs Offline extension to fall back on — it does not cover Forms.

If a form will not load and you are not sure the connection is the cause, our Google Forms troubleshooting guide works through the symptoms one at a time.

If you genuinely have no signal

When the venue has no coverage and the answers still have to be collected, stop trying to make the software do it. The route that has never failed anyone is a printed blank form: collect on paper, type the answers in when you are back on a connection. Google Forms has a real Print command for exactly this, and our guide to printing a Google Form covers how to get a clean blank copy rather than a screenshot of the editor.

Two things make the typing-up half less painful. Print one copy per respondent rather than one master sheet, so each paper form maps to one submitted response with no transcription guesswork. And open the live form in a browser while you type, rather than the responses sheet, so validation and required-question rules catch mistakes as you go.

We deliberately do not recommend a third-party “offline forms” app here. Several exist, but an app that collects answers offline is collecting them into its own database — those submissions are not Google Forms responses, and unless a vendor documents a genuine sync back into your form, treating them as interchangeable will cost you a dataset.

What Forms+ does when the connection drops

Forms+ is a native iPhone and iPad client for your real Google Forms, and it is worth being exact about the difference between reading data offline and changing it offline. Forms+ does the first, within limits, and does not pretend to do the second.

What keeps working with no connection:

  • Responses you have already loaded. Forms+ keeps a local copy of the responses it has fetched for a form and re-shows them rather than an empty screen, with a freshness line in the header so you always know how old what you are reading is — “Last fetch: just now” when the refresh worked, and an amber “Couldn’t fetch latest — tap to refresh” when it did not.
  • An honest staleness warning. When a refresh fails, the app keeps showing the saved responses and flags them — “Couldn't fetch latest — tap to refresh” — instead of quietly presenting old data as current.
  • Event check-in at the door. The check-in scanner records who has arrived on the device itself, so once a form's responses are loaded you can keep scanning and marking attendees with no signal in the room.

What does not, and we would rather say so than imply otherwise:

  • Saving an edit. Forms+ writes through Google's Forms API. With no connection, saving a form stops with a plain “No Internet connection” message rather than losing your change silently.
  • Loading your form list for the first time. The list of forms comes from your Drive, so a cold start with no signal shows an offline message, not your forms.
  • Creating or importing a form, or fetching new responses. All are network calls.

In other words: a form you were already working with stays readable on the train; it does not become editable. Anyone promising more than that on top of Google Forms is either syncing into their own database or overselling.

The responses header in Forms+ on iPhone reading “22 responses” with a refresh glyph and the line “Last fetch: just now”, next to an Accepting responses toggle.
The line that matters offline is the small one: Last fetch. It tells you whether you are looking at live data or at a copy from the last time you had signal — a distinction Google’s own web form never makes.

What works without a connection

With no connectionGoogle Forms in a browserForms+ on iPhone
Open your list of formsNoNo — the list comes from Drive
Read responses you already loadedNoYes — the saved copy, with a “Last fetch” time
See new responsesNoNo — fetching is a network call
Create or edit a formNoNo — saving needs a connection
Submit a responseNoNo
Respondent progress autosavedNo — “If you're offline, autosave doesn't work.”Respondents fill in the browser, so the same applies
Mark attendees checked in at an eventNoYes, once that form's responses are loaded
Collect answers on paperYes — print the blank form first, while you still have a connection

Know how old your data is, even with no signal

Forms+ keeps the responses it has fetched on your device and tells you when it last reached Google — your account, your Drive, no migration.

Get Forms+ free on the App Store

Frequently asked questions

Can you use Google Forms without internet?

No. Google's offline mode covers Docs, Sheets and Slides only — Google's own help pages list those three and never mention Forms. Without a connection you cannot open the Forms editor, save an edit, or submit a response.

Does Google Drive offline mode work with Google Forms?

No. The Drive and Docs offline help pages say you can create, view and edit files on Google Docs, Google Sheets and Google Slides while disconnected. Forms is absent from that list, and turning on the Google Docs Offline extension does not make a form available offline.

What happens to my answers if I lose connection halfway through a form?

Google's autosave help page is explicit: “If you're offline, autosave doesn't work.” Progress is saved as a draft for 30 days only when you are filling in the form in your Google Account and still connected. Answers typed after the signal drops exist only in that browser tab, and submitting will fail until you are back online.

Can I edit a Google Form offline on my iPhone?

No. Google Forms has no offline editor on any platform, and native clients such as Forms+ write every change through Google's Forms API, so saving an edit requires a connection. Forms+ says so plainly rather than silently losing the change.

Can respondents fill in a Google Form offline and submit it later?

Not in Google Forms itself. There is no queue-and-send-later behaviour documented for Forms responses. If you need answers collected where there is no signal, the reliable route is a printed blank form filled in on paper and entered afterwards.

Can I read my Google Forms responses without a connection?

Not on the Google Forms website. A native client can keep a local copy: Forms+ stores the responses it has already fetched for a form and re-shows them with the time of the last fetch, so you can read them with no signal. New responses only appear once a refresh succeeds.