App comparison
📅 2026-11-13 ⏱️ 9 min read Dean Dean

Best Offline Voice Typing Apps for Android: FUTO, Sayboard, Gboard

Compare offline Android dictation by device support, language packs, keyboard integration and network exceptions before choosing FUTO, Sayboard or Gboard.

Android dictation workflow showing downloaded speech models, a microphone, and recognized text with connectivity disabled
📋 Key Takeaways
  • FUTO Voice Input and FUTO Keyboard have different installation and integration paths. Prepare the appropriate models, and distinguish established Keyboard-integrated Whisper from experimental separate-app engines.
  • Sayboard provides on-device voice typing through Vosk as an Android input method. Download or import a suitable language model, then enable and select the installed input method.
  • Gboard advanced voice typing requires an eligible Pixel 6 or later and supported language conditions. Basic on-device dictation does not make internet-dependent correction features work offline.
  • Verify fresh dictation with Wi-Fi and mobile data disabled, inspect the inserted text, and review reconnection behavior separately. FoneClaw is an optional downstream Android-action route, not an offline keyboard.

Choose How Speech Reaches Your Text Field

The best offline voice typing apps for Android depend on how you want recognized speech to reach the app you are using. FUTO offers distinct voice-input and keyboard integration paths. Sayboard works as a voice input method. Gboard's documented advanced route depends on eligible Pixel hardware and language conditions.

This shortlist compares documented fit, not measured accuracy or speed. Here, offline means the intended recognition works after preparation with connectivity disabled. It does not mean every correction, rewrite, synchronization feature, or subsequent phone action also works disconnected.

OptionIntegration decisionPrepare firstImportant boundary
FUTOChoose between FUTO Voice Input and FUTO Keyboard's integrated routeThe correct app integration and suitable model filesExperimental engines are not universal stable features
SayboardEnable and select a voice input methodA suitable Vosk language modelRecognition is not an AI rewriting or phone-action service
Gboard on eligible Pixel devicesUse supported advanced voice typing within GboardCompatible device and language settings, plus speech assetsSome correction and editing features require internet

An input method inserts text into an editable field. A companion speech app needs a supported integration to deliver that text. A recorder transcribes captured audio, while an AI assistant interprets requests and may take separate actions. Those are different jobs, even when each interface contains a microphone.

FUTO: Match the App, Integration, and Model

FUTO Voice Input provides on-device speech input, with model files that must be prepared before disconnected use. Start by deciding which distribution you need: FUTO Voice Input and FUTO Keyboard are separate installation and integration paths, not interchangeable names for one app.

If you use FUTO Keyboard's integrated voice input, inspect the recognition option actually available in that installation. If you choose the separate voice-input app, check how your intended keyboard or application invokes it. Installing a speech app does not establish that another keyboard's microphone automatically uses it.

Complete setup while connected. Select a suitable available model for your intended language, let its download finish, and confirm the chosen integration can insert a short phrase into your target field. Keep a normal typing route available for corrections. A microphone animation alone does not establish successful text insertion.

FUTO's September voice-input development notes distinguish existing Keyboard-integrated Whisper from newer separate-app work involving asr4all and Nemotron. The described improvements include nightly or experimental features; asr4all is English-only in that documented state.

That distinction should guide installation choices. Do not download a development build merely because a demonstration uses a newer engine, then assume the same controls or behavior exist in the stable keyboard. Check the distribution, engine, and model you actually selected. Likewise, an English-only experimental engine does not describe the language scope of every other FUTO model.

Choose FUTO when its available local model and integration match your daily text-entry workflow. The useful result is recognized text appearing where you intended, with a practical correction path, rather than simply having a newer engine installed.

Sayboard: Select a Vosk Voice Input Method

Sayboard takes a more direct input-method approach. Its official project documentation describes Android on-device voice input using Vosk. Prepare a suitable language model by downloading or importing it before relying on disconnected recognition.

After installing from the project's supported distribution route, follow the setup presented on your phone. Enable Sayboard through Android's input-method settings and select it when entering text. Manufacturers organize keyboard and input settings differently, so use the actual device interface rather than expecting one universal menu sequence.

Check the intended language before downloading a model. A model being available for one language does not establish support for another, and the interface language is not a substitute for the selected recognition model. Confirm that the model is ready, then grant the microphone access needed for the dictation you intend to perform.

For an initial check, place the cursor in a harmless editable field and dictate a short fictional sentence. Inspect whether text is inserted at the cursor, whether it replaces selected text, and how you will correct an unfamiliar name. These details matter if you regularly switch between speech and ordinary typing.

Sayboard's role is recognition and insertion. Do not assume that it will turn rough speech into a polished email, infer missing facts, or execute the meaning of a sentence. If you dictate Call the supplier, the expected typing outcome is those words in the field, not an automatically placed call. Review the result before saving or sending anything.

Gboard: Check Pixel and Language Eligibility

Gboard is a useful candidate when your phone already meets Google's documented conditions. Its advanced voice typing guidance identifies Pixel 6 and later, with supported English, French, German, Italian, Japanese, and Spanish language conditions. Primary device and Gboard language compatibility matters, as does preparing the required speech assets.

Having Gboard installed on another Android phone does not establish access to the Pixel advanced experience. Nor does selecting a language from Gboard's general keyboard list establish that the same language supports this voice-typing route.

Before going offline, inspect the voice-typing options offered in your installed Gboard setup. Check the device and keyboard language configuration, complete any required asset preparation, and confirm that the intended voice mode is active in an editable field. Follow the controls actually present rather than looking for an assumed universal toggle.

Separate recognition from correction. Basic supported dictation can run on-device, while features such as Fix it or detailed editing can require internet. You may therefore be able to dictate a sentence disconnected but not use the same workflow to rewrite or extensively revise it.

A useful comparison records those outcomes separately: speech inserted, punctuation handled, correction available, and rewriting unavailable or connected. Do not describe the whole keyboard as failing offline because a network-dependent editing feature is unavailable; equally, do not describe every feature as offline because ordinary dictation worked.

If the advanced option is missing, check hardware and language eligibility first. Granting unrelated permissions will not add unsupported device capabilities. Where your setup does not qualify, consider a prepared FUTO or Sayboard route rather than assuming all Gboard installations behave like a supported Pixel.

Check Fresh Dictation With Connectivity Disabled

Prepare this proposed comparison before a trip or other disconnected session. Use only eligible app, device, and language combinations. The observations will be yours; this is not a report of tests we performed.

  1. Finish preparation online: Install from official channels, download the required model or speech assets, complete setup, and select the intended input path. Confirm that downloads have finished rather than merely started.
  2. Choose a safe destination: Open a nonsensitive editable field that does not automatically send its contents. Place the cursor deliberately and remove any selection you do not want replaced.
  3. Disable connectivity: Turn off mobile data and Wi-Fi and inspect their actual state. Airplane mode alone is insufficient evidence because Wi-Fi can be reenabled while it remains active.
  4. Dictate fresh material: Use the same intended sentence for each eligible setup: Nora Patel needs 24 blue folders, not 42. Speak naturally and inspect the proper name, both numbers, and the negation.
  5. Inspect editing behavior: Check insertion position and punctuation. If spoken punctuation commands are supported, evaluate them separately; otherwise correct punctuation manually. Do not assume identical command vocabulary.
  6. Review before saving: Correct unintended text and confirm the destination. If you save it, reopen the actual record rather than relying only on what briefly appeared in the input field.

If no text appears, identify the failing layer: selected input method, microphone access, missing model, language mismatch, or an integration that was not invoked. Repeating the phrase will not download a missing model while disconnected.

Before reconnecting, discard unwanted drafts and review the destination app's sync settings and the speech app's privacy information. An offline recognition run establishes that the tested operation worked without a connection at that moment. It does not prove that no data was stored, that nothing will sync later, or that the app can never make a future network request.

What Google's Local-Speech Announcement Means

Google's November 10 local-speech announcement describes on-device speech-recognition and text-to-speech APIs demonstrated in Google AI Edge Gallery. It is relevant development context for local voice interfaces, not a fourth everyday keyboard recommendation.

Speech recognition turns audio into text. Text-to-speech turns text into spoken output. A demonstration offering both does not establish that it can replace an Android input method across your usual apps, and API availability does not mean every installed keyboard already integrates that implementation.

The same distinction applies to experimental engine announcements elsewhere. A development demonstration can show a possible interaction without establishing stable availability in the app and distribution you use.

For your next disconnected typing session, rely on the installed integration and downloaded resources you can verify. Check what is ready on your phone instead of treating local-speech news as proof that a missing keyboard feature has already arrived.

Keep Transcription Separate From the Next Action

If your goal is to type a note, stop after reviewing and saving the text. There is no need to add an AI-agent step merely because the words came from speech. For the differences between input methods, dictation, and recording transcription, read Android Voice Input vs Dictation vs AI Transcription: Four Outputs.

In FoneClaw, we provide an Android agent runtime for separately supported actions. We are not a system-wide input-method keyboard or a guaranteed offline speech recognizer. A configured model interprets the supplied request, while enabled tools act within actual permissions and approval settings. Our Features page explains that supported-action scope.

After reviewing your text, you could explicitly supply it and request a personal task such as Check the folder quantity with Nora Patel, without adding a date. Review any required approval and inspect the saved task. This is a separate proposed follow-up, not something the dictation app automatically performs.

An online model may need connectivity and may receive the context you supply. Successful local recognition therefore does not establish that model inference or a downstream action will work disconnected.

If your real goal is rewriting rough speech into polished prose, Rambler vs Wispr Flow vs Samsung Keyboard: Android AI Dictation covers that different choice. For offline typing, choose the supported input path, prepare its assets, and verify fresh text in the intended field.

Try FoneClaw