How to Fix Gemini Error 13 (Text Input Not Working on Google Account)

If Google Gemini shows “Something went wrong, please try again (13)“, the problem is usually not your device. In most cases, Gemini fails to process text input due to an account-level issue, even while voice continues to work normally.

This error often appears across multiple devices and networks, which makes it confusing. But once you understand the cause, you can stop wasting time on the wrong fixes. This guide shows you exactly how to fix Gemini Error 13 step by step.

Quick Fixes for Gemini Error 13

• Toggle Gemini Memory OFF and ON (highest success rate from community reports)
• Start a new chat if the current session is stuck or loading indefinitely
• Clear the Gemini app cache and the AI Core app cache on Android
• Disable VPN, ad blocker, or private DNS settings
• Sign out of all devices and sign back in on one device only
• Wait 24 hours if the error followed a large image or file upload
• Upload images one at a time instead of in batches
• Report via Send Feedback if the error persists beyond 48 hours

What Is Gemini Error 13?

Gemini Error 13 appears when the system fails to process your text request. You will notice that text input fails every time, while voice interaction continues to work normally. The error shows up instantly after you send a message and often occurs across multiple devices. This clearly indicates that Gemini cannot process text requests for your account.

This issue does not come from your internet connection. Gemini uses separate processing paths for voice and text. When your account data goes out of sync, text requests fail while voice requests continue to work without problems. As a result, Gemini keeps showing Error 13 repeatedly.

In simple terms, your account becomes partially stuck on Google’s backend, which prevents text processing from working correctly.

Common Signs of Gemini Error 13

• Text input fails every time while voice works normally
• Error appears instantly after sending a message
• The same error shows up across multiple devices and browsers
• Prompts return “Something went wrong (13)” with no response
• Chats remain stuck loading indefinitely
• Custom Gems fail to share or respond
• Mobile app behavior differs from desktop behavior

What Causes Gemini Error 13?

Gemini Error 13 rarely appears out of nowhere. It is usually triggered by one of the following scenarios.

Account Data Out of Sync: When your Google account data falls out of sync with Gemini’s backend, the text processing pipeline breaks. Voice requests use a separate path and continue working, which is why only text input fails. This is the most common root cause behind Error 13 appearing across all your devices simultaneously.

Mass Image or File Uploads: Uploading a large batch of images or files (30 or more in a short span) for analysis triggers a temporary system conflict. This restricts your account from processing multiple files and can break the chat entirely. Uploading in small groups of one to three files at a time avoids this trigger.

Context Limit Overload: Gemini retains your entire conversation history to provide coherent responses. If you have been chatting in the same window for hours, the volume of data overwhelms the session’s memory limit, causing it to freeze or brick. Starting a new chat clears this immediately.

Non-English Text Encoding: Many users report Error 13 specifically when inputting pure non-English text or mixed languages. This points to an AI processing failure related to character encoding. A community workaround is to start the conversation with an English prompt before switching to non-English text, which helps Gemini correctly route the language input.

Cross-Device Session Conflicts: Sometimes the error is localized. A PC browser might process prompts smoothly while the Gemini mobile app throws the Error 13 message, or vice versa. This typically happens when session tokens conflict across devices after a sign-in on a new device.

Sharing or Using Custom Gems: Users frequently report Error 13 specifically when attempting to share custom Gems, even without attached files. This indicates a server-side permission conflict that prevents the sharing operation from completing. Switching between desktop and mobile to attempt the share often works around this.

How to Fix Gemini Error 13 (Step-by-Step Solutions)

Follow these fixes in order. Start with quick fixes before moving to advanced solutions.

Fix 1: Toggle Gemini Memory Off and On

This is the most effective fix reported by users and has resolved the error even after days of persistence. Users describe it as the fix that works when everything else fails.

1. Open Google Gemini on desktop
2. Click your profile picture or the Settings icon
3. Go to Personalization
4. Toggle Memory to OFF
5. Toggle Memory immediately back to ON

This forces a session data refresh on Google’s backend without deleting your saved context or preferences. The text processing pipeline reconnects after the toggle.

Fix 2: Start a New Chat Session

If your current chat is frozen due to context limit overload, click New Chat (the + icon). Starting a fresh conversation drops the accumulated session data and gives Gemini a clean slate. This fixes chats that are stuck loading indefinitely.

If the new chat works, your previous conversation thread is corrupted. Leave that thread and continue using a new one.

Fix 3: Test on Another Google Account

Switch to a different Google account and open Gemini. Send a simple message.

• If it works on the other account, the issue is tied to your specific account
• If it fails on the other account too, the problem is on your device or network

This diagnostic step tells you exactly where the fix needs to happen before you waste time on the wrong solutions.

Fix 4: Disable VPN, Ad Blocker, or Private DNS

Security filters and VPNs can silently block Gemini’s text processing requests. Turn off the following one at a time and test after each:

• VPN services
• Browser extensions, especially ad blockers
• Private DNS settings on your phone or router

Re-enable them after testing to isolate which one is causing the conflict.

Fix 5: Clear App Cache (Gemini and AI Core)

Corrupted cache data breaks the request connection between your device and Google’s servers.

For Desktop: Sign out of your Google account, clear browser cookies and cache fully, then sign back in.

For Android:

1. Go to Settings > Apps > Gemini (or Google App) > Storage > Clear Cache
2. Go to Settings > Apps > Show System > AI Core > Storage > Clear Cache
3. Restart your device after clearing both caches. Do not skip the restart.

Fix 6: Update Gemini and the Google App

Open the Play Store or App Store and update both the Gemini app and the Google app. Outdated versions frequently cause backend handshake failures that trigger Error 13.

Fix 7: Sign Out of All Devices, Then Sign Back In

1. Go to Google Account > Security > Your Devices
2. Sign out of every device listed
3. Sign back in on one device only
4. Test Gemini before logging in on any other device

Active sessions on multiple devices can create token conflicts that block text processing for your account.

Fix 8: Clear Gemini Activity (Optional)

Warning: This step permanently deletes your Gemini conversation history. Only proceed if you are comfortable losing your chat records.

1. Go to myactivity.google.com/product/gemini
2. Delete recent Gemini activity
3. Restart the app and test

Clearing activity resolves sync issues between your account data and Gemini’s backend in some cases.

Fix 9: Wait Out the 24-Hour Restriction

If you triggered the error after mass image uploads or long file processing sessions, your account may have hit a temporary rate limit. This restriction usually clears itself within a few hours to a full 24-hour cycle without any action needed on your end.

For Developers Using the Gemini API

If you encounter Error 13 inside Google AI Studio rather than the regular Gemini interface, the cause is likely API permissions or service configuration rather than a chat session conflict.

Check the following in your Google Cloud Console:

• Confirm the Gemini API is still active under APIs and Services
• Check that billing is active and not flagged
• Review IAM permissions to ensure your service account has the correct roles assigned

If you work inside a Google Workspace environment, contact your Workspace Administrator. Policy updates or security rule changes can silently block API access at the organizational level without showing a clear error message.

Still Not Fixed After 48 Hours?

At this point, the issue is on Google’s backend. No local fix will fully resolve it.

Report the Issue to Google

1. Open Google Gemini
2. Click Settings > Send Feedback
3. Include the following in your report:
   • Error code: 13
   • Text input not working
   • Voice working normally
   • Issue appearing across multiple devices
   • Other Google accounts working fine

This gives Google’s engineers enough information to investigate and fix your specific account.

If you use Gemini Advanced (paid plan), you can reach a live support agent through Google’s Gemini support page, which is significantly faster than waiting in the standard feedback queue.

Frequently Asked Questions

Gemini Error 13 is almost always a temporary, account-level issue rather than a permanent problem. Whether the trigger is an overloaded context window, a mass file upload restriction, a session conflict across devices, or a backend sync failure, the fixes in this guide cover every confirmed scenario. Start with the Memory toggle and a fresh chat, then work through the remaining steps if needed. If nothing works after 48 hours, report through Send Feedback or contact Gemini support directly if you are on the Advanced plan.

For similar errors, see how to fix Gemini Error 1076, Gemini Error 1099, Gemini Error 1096, and Gemini Error 1152.

Related Error Fixes

• How to Fix Gemini Error 1076 (Something Went Wrong)
• How to Fix Gemini Error 1099 (Something Went Wrong During Analysis)
• How to Fix Gemini Error 1152 (Something Went Wrong)