Best Offline Survey App for Field Data Collection

An offline survey app stores completed interviews on the device and uploads them later when a connection is available. The best option for field research is ODK Collect: it is free, works on any Android phone, holds submissions for weeks without a signal, and pairs with a server you control.

Google Forms cannot do this. Neither can Qualtrics, SurveyMonkey, Typeform or Jotform in any dependable way. They are browser tools that assume connectivity, which is why teams searching for "offline survey app" almost always end up outside the mainstream form-builder market.

Last reviewed: September 22, 2026.

What "offline" actually has to mean

Vendors use the word loosely. For real fieldwork, an offline survey app has to do all five of these:

1. Download the form once and keep it on the device, including choice lists and media.
2. Complete interviews with the radio off — no background calls, no silent failures at question 40.
3. Store many finished submissions locally, not just the one in progress.
4. Sync selectively, so an enumerator on a weak connection can upload 3 of 60 forms without losing the rest.
5. Survive a crash or a dead battery without losing the interview in progress.

Anything that only caches the current page in a browser tab will fail in the field. Test point 5 specifically before you commit — it is the one that gets skipped in demos.

Offline survey apps compared

App	Cost	Platform	Offline depth	Where data goes
ODK Collect	Free	Android	Full, weeks offline	Any ODK Central server you choose
KoboCollect	Free	Android	Full, weeks offline	KoboToolbox servers
Epicollect5	Free	Android + iOS	Full, simple forms	Epicollect5 servers
SurveyCTO Collect	Paid platform	Android	Full	SurveyCTO's infrastructure
CommCare	$100+/month	Android	Full	Dimagi's infrastructure
Google Forms	Free	Browser	None	Google

ODK Collect

The default choice for field research, and the one the others are mostly built from. It is free and open source, runs on low-end Android phones, and captures GPS, photos, audio, video and barcodes offline. Because it speaks the open XLSForm standard, the same form runs on several server platforms without rewriting.

The part people miss: ODK Collect is only the app. It needs a server to send data to. That is ODK Central, which you either run yourself or have hosted for you. See the offline collection workflow for how the full cycle runs in practice.

KoboCollect

A fork of ODK Collect that points at KoboToolbox servers. If you want free hosted infrastructure and can work inside the Community plan's limits, this is the fastest path to collecting data today. The trade-off is hosting control — see ODK vs KoboToolbox.

Epicollect5

Free, and the only mainstream option with a first-class iOS app. Good for simple instruments; the form builder is not XLSForm, so complex logic and repeat rosters get awkward. See Epicollect5 alternatives.

What about Google Forms offline?

It does not work for enumeration. A Google Form needs a live connection to load and submit; the offline support in Google Drive does not extend to reliable form submission from the field. Teams that try it end up with enumerators screenshotting questions and transcribing later, which defeats the point. See ODK vs Google Forms.

What breaks in the field, and how to prevent it

• Media-heavy forms fill the device. A form that captures three photos per household will exhaust a 32 GB phone faster than you expect. Set image size in the form and plan sync points.
• Enumerators never hit "send". Finalised-but-unsent submissions are the most common source of "missing" data. Brief the team that finalising and sending are two separate actions.
• Device clocks drift. Offline devices with wrong system time produce timestamps that corrupt your timing analysis. Check clocks at every sync point.
• Forms get updated mid-round. Pushing a new form version while enumerators hold unsent submissions on the old one causes real pain. Use the form release checklist.
• Nobody knows if it is working. Without an audit log, you cannot tell a slow enumerator from a fabricated interview until the data is in.

How to set up offline collection

1. Write the questionnaire as an XLSForm — or have LooprAI build it from a plain-English description or an existing Word document.
2. Validate the form before it goes anywhere near a device.
3. Deploy it to a server. Get an ODK Central server — managed, or self-hosted if you have the skills.
4. Install ODK Collect on each device and configure the server URL, ideally by QR code rather than by hand. See the ODK Collect setup guide.
5. Run a genuine offline test — aeroplane mode, ten interviews, reboot, then sync.
6. Brief enumerators on finalise vs send and agree a daily sync point.

If submissions do not arrive, the ODK Collect not sending guide covers the usual causes.

Which offline survey app should you choose?

• Field research with any real complexity → ODK Collect plus managed ODK hosting.
• No budget, simple needs, happy with hosted → KoboCollect.
• You need iOS devices → Epicollect5, accepting the logic limits.
• Regulated clinical work → see REDCap alternatives.
• Online respondents with connectivity → you do not need an offline app at all.

"Every offline failure I have seen in the field came down to one of two things: the team never tested with the radio actually off, or nobody explained that finalising a form is not the same as sending it."

— Mehrab Ali, SurveyLoopr

Explore ODK hosting

Next: The ODK Collect Offline Workflow →