Mid-sentence, mid-password, mid-everything — the keyboard disappears and a little popup says "Gboard keeps stopping." Few Android errors are this disruptive, because when the keyboard dies you cannot type your way out of anything: not a search, not a reply, not even a fix that needs a password.
The good news: this is a software problem nearly every time. Corrupted cache, a bad update, a conflicting keyboard, or a settings tangle — all fixable, in the order below. One warning before you start: if your phone asks for a PIN or password after a restart, and Gboard is your only keyboard, you could get locked out of typing it. Install a backup keyboard first if that scenario applies to you.
Quick Answer
Gboard keeps stopping on Android? Force-stop Gboard (Settings → Apps → Gboard → Force stop) and restart the phone. Still crashing? Clear Gboard's cache (Storage & cache → Clear cache) — safe, keeps your settings. If that fails, update Gboard from the Play Store, or uninstall its updates if the crashes started right after an update. Make sure Gboard is set as the default keyboard, since conflicts with Samsung Keyboard or other keyboards trigger this error.
In This Guide
Fix 1 — Force-Stop Gboard and Restart
Start with the lightest touch: kill Gboard's stuck process and reboot. This clears the temporary glitches — a crashed render thread, a wedged background service — that produce the "keeps stopping" popup out of nowhere.
- Go to Settings → Apps → Gboard and tap Force stop.
- Do not restart yet if your phone requires a PIN/password at boot and Gboard is your only keyboard — install a second keyboard first (any simple one from the Play Store works as a backup).
- Hold the power button and tap Restart.
- After reboot, open any app with a text field and test the keyboard.
If Gboard survives a reboot and a few minutes of typing, the crash was transient. If the popup returns, the problem is in Gboard's data or its update — which is what the next fixes target.
Fix 2 — Clear Gboard's Cache
Gboard's cache holds temporary files for predictions, themes, and glide typing. When these corrupt, Gboard can crash the instant it tries to render the keyboard. Clearing the cache is completely safe: your words, settings, and themes stay exactly as they are.
- Open Settings → Apps → Gboard.
- Tap Storage & cache (Pixel), Storage (Samsung One UI), or on Xiaomi HyperOS: Apps → Manage apps → Gboard → Clear data → Clear cache.
- Tap Clear cache.
- Open a text field and check whether Gboard stays up.
This is the single highest-success fix for Gboard crashes, and it takes under a minute. Do not confuse it with "Clear data" — that one resets everything, covered in Fix 3.
Fix 3 — Clear Gboard's Data (Resets Settings)
If the cache clear did not help, the corruption is in Gboard's stored data — its settings files or learned dictionary. Clearing data returns Gboard to a fresh-install state. The trade-off: you lose your personal dictionary (custom words), learned typing patterns, and custom settings.
- Go to Settings → Apps → Gboard → Storage & cache.
- Tap Clear data (or "Clear storage") and confirm.
- Restart the phone.
- Open a text field — Gboard will launch like a fresh install. Re-enable your languages and themes in Gboard's settings.
If you rely on a large personal dictionary, export or note down critical custom words first — there is no undo for a data clear. That said, a clean slate fixes crashes that nothing else touches.
Fix 4 — Update Gboard, or Roll Back a Bad Update
Google updates Gboard through the Play Store independently of Android, and a buggy Gboard update is one of the most common causes of sudden, widespread "keeps stopping" crashes. The timing tells you which direction to go: crashes that started after an update point to the update itself.
- Open the Play Store, search Gboard, and tap Update if one is pending.
- If Gboard is already current — or the crashes started right after updating — roll back instead: Settings → Apps → Gboard → ⋮ (three dots) → Uninstall updates.
- Restart the phone after either change.
- Test the keyboard. If the rollback fixed it, leave auto-update off for Gboard for a few days until Google ships a corrected build.
On Pixel phones, Gboard is a system app, so "Uninstall updates" is the deepest removal available — you cannot fully uninstall it, and that is fine. The rollback returns it to the factory version that shipped with the phone.
Fix 5 — Set Gboard as the Default Keyboard
Keyboard conflicts are a quiet but real cause. On Samsung phones especially, Samsung Keyboard and Gboard can fight over input focus, and the loser crashes. Making Gboard the explicit default ends the tug-of-war.
- Go to Settings → System → Languages & input → On-screen keyboard (Pixel). On Samsung: Settings → General management → Keyboard list and default. On Xiaomi: Settings → Additional settings → Languages & input → Current keyboard.
- Select Gboard as the default keyboard.
- If you do not use Samsung Keyboard (or another third-party keyboard), consider disabling it to remove the conflict entirely.
- Restart the phone and test typing in two or three different apps.
Also check Gboard's own settings for anything unusual you enabled recently — an experimental feature, a new language pack, or a theme can occasionally destabilize it. Turning off the most recent change is a quick test.
Fix 6 — Reinstall Gboard and Free Up Storage
The last software-level options: a full reinstall (for phones where Gboard is not a system app) and making sure the phone is not starving for storage — Android kills background processes aggressively when storage runs critically low, and the keyboard is a frequent victim.
- If Gboard is not a system app on your phone: Settings → Apps → Gboard → Uninstall, restart, then reinstall Gboard from the Play Store.
- Open Settings → Storage and confirm at least 1–2 GB free. Delete unused apps, old downloads, and large videos if needed.
- Check for a system update: Settings → System → System update (Pixel), Settings → Software update (Samsung) — keyboard crashes sometimes trace back to an OS-level input bug.
- Restart once more and test.
If Gboard still crashes after all six fixes, run a Play Protect scan (Play Store → profile → Play Protect) to rule out a malicious app interfering with input, and consider resetting app preferences (Settings → Apps → ⋮ → Reset app preferences) — it restores defaults without deleting data. Covers Android 10 through 14.
Watch: Fix Gboard Not Working, Step by Step
Prefer a walkthrough? This video shows the main Gboard fixes step by step:
Video by gossipfunda — full credit to the creator.
Related Guides
Frequently Asked Questions
Will clearing Gboard's cache delete my saved words?
No. "Clear cache" only removes temporary files — your personal dictionary, settings, and themes are untouched. It is "Clear data" (Fix 3) that wipes your saved words and resets Gboard to defaults, so use that one deliberately.
What if Gboard crashes and I cannot type my lock-screen password?
This is the scenario to avoid: after a restart, Android asks for your PIN/password before any third-party keyboard loads. If Gboard is broken and it is your only keyboard, use a fingerprint or face unlock if enrolled. Otherwise, you may need to boot into Safe Mode or have a second keyboard installed beforehand — which is why Fix 1 warns about it.
Why does Gboard keep stopping only in one app?
When the crash is app-specific, the problem is usually that app's text field or its own cache, not Gboard. Clear that app's cache first (Settings → Apps → [the app] → Storage → Clear cache). If Gboard crashes everywhere, it is a Gboard problem — work through the fixes above.
Can a theme or language pack crash Gboard?
Yes, occasionally. A corrupted theme download or a freshly added language can destabilize the keyboard. If crashes started right after you changed Gboard's appearance or added a language, revert that change first — it is the fastest possible fix.
By Sameer Zehri | App Fix Guru Editor | Last updated: October 2026
