WhatsApp Web Translation Not Working? A Step-by-Step Fix

Missing sidebar, untranslated messages, replies that will not translate, or the wrong language? Identify the symptom, check the right setting and verify the result.

WATransTroubleshooting8 min

Start by identifying what is actually failing

If a foreign-language message has no translation, do not reinstall immediately. WhatsApp Web translation depends on the page, extension access, engine and chat settings working together. Change one thing at a time so you can tell which action helped.

  • No sidebar: check the browser profile, extension status and site access.
  • Sidebar visible, incoming messages unchanged: check incoming auto translation and your reading language.
  • Incoming works, replies do not: check outgoing translation and your send shortcut.
  • Only one conversation affected: check that conversation’s individual settings.
  • Every chat waits or shows an error: try a small engine test and inspect the actual error.

When the sidebar is missing

  1. Open web.whatsapp.com in desktop Chrome, sign in and wait for the chat list. The mobile app and standalone desktop app do not load this browser extension.
  2. Open Chrome’s extension manager and confirm WATrans is installed and enabled in the profile you are using. A work profile and a personal profile can have different extensions.
  3. Check the extension’s site access for WhatsApp Web. Pinning the toolbar icon makes it easier to find; it does not grant permission or determine whether translation runs.
  4. Save any unsent draft and refresh the page if it was already open during installation. Open a conversation again.

Expected result: the chat list loads and the translation settings panel is available. If WhatsApp itself is still connecting or asking you to sign in, resolve that before changing translation settings.

Run one small engine test

Note the current engine and language settings before changing them. Use a test chat and a harmless complete sentence rather than an emoji, number or name.

  1. Select an engine available to your account, such as Google Translate or Volcano. Follow any sign-in, activation or access prompt first.
  2. Keep one source sentence and one target language for the test. For example, use “Can we meet tomorrow?” with a target other than English.
  3. Let the request finish and note its result or error. Repeated clicks and refreshes make it harder to identify what worked.
  4. If the engine fails, keep the chat and language pair unchanged and try one other available engine.

If the second engine works, focus on the first engine or its access conditions. If neither works, check connectivity, account prompts and the relevant direction switch. This comparison does not by itself prove a provider outage.

If you are unsure which language belongs where, review the WhatsApp Web translation setup: the incoming target is the language you want to read; the outgoing target is the language your recipient needs.

Incoming messages stay untranslated

Open settings in the affected chat. Under Chat Trans, enable Auto Trans. Leave the source on Auto detect unless you know it is misidentifying short or mixed-language messages; in that case, select the known source language and retry.

Choose your reading language as the target. When source and target are the same, an unchanged result is not a reliable failure signal. Test with a complete new sentence in another language.

  • Ask a trusted contact to send a new test message, or use a conversation you control.
  • Look beside the original for the translation. Check text size and color if it is difficult to distinguish.
  • Do not judge recovery only from older messages. Whether existing bubbles are processed again depends on page behavior; a new message is a clearer check.
  • If text works but voice does not, check the separate voice switch and account access.

Expected result: a new incoming message has a translation in your chosen language, with the original available for comparison.

Outgoing replies do not translate or send

Enable Send Translation and check its target language. Successful incoming translation does not mean the outgoing switch is enabled.

Use a test conversation before trying a real order or customer commitment. The default shortcuts have different purposes:

  • Alt+T: translate without sending. Start here to inspect the result.
  • Enter: translate and send by default; after a translation-only action, use Enter to send the translation.
  • Control+G: send the original. Sending untranslated text with this shortcut is expected.

If you customized the keys, follow the current Shortcut settings. Finish composing any text with your input method before using a shortcut.

A translation exists, but sending is blocked

Check Ban Chinese. When enabled, it can block sending if Chinese characters remain after translation. Verify the target language and any retained names before changing this setting to suit your needs.

Expected result: first obtain the correct-language reply, then verify sending in the test chat. Review numbers, dates and negative statements before sending; an unsuitable translation and a failed send are different problems.

Only one chat uses the wrong language

Do not change every conversation’s defaults when only one contact is affected. Open that chat and check Individual settings. It may hold a language pair that overrides the global configuration.

  1. Note the chat’s incoming and outgoing targets.
  2. Keep Individual enabled if the contact needs a custom pair, and change that pair only.
  3. To use the global settings, turn Individual off and check the languages actually shown afterward.
  4. Verify both directions with new test messages.

For example, reading Spanish messages in English requires English as the incoming target, while replying in Spanish requires Spanish as the outgoing target.

Aggregator is a separate text translation workspace; AI optimization refines wording. Neither automatically corrects the target language configured for your chat. Fix the basic pair first.

Still stuck? Narrow the cause before reinstalling

Save your draft and note your configuration. After each step, return to the same test conversation instead of changing several conditions together.

  1. Refresh once and wait for the chat list before opening settings.
  2. Record the exact error or access prompt rather than only “nothing happened.”
  3. Check Chrome updates and extension status. If Chrome explicitly marks the extension as corrupted, use its repair option. Organization-managed restrictions may require your administrator.
  4. If other chat or translation extensions run on the same page, temporarily disable them one at a time for a comparison, then restore them. Do not switch off all browser protections.
  5. Consider reinstalling last. Record language pairs, individual settings and custom shortcuts first, and ensure you can access your account. Reinstallation may require configuration again.

If the problem persists, collect the extension and Chrome versions, engine, source and target languages, failing direction and one reproducible error. Use a sanitized sentence and screenshot if you contact support.

Verify that the fix lasts

Complete three checks in one test chat: receive a new foreign-language message, translate a draft without sending, and send it after review. Refresh and confirm the switches and languages still match your choices.

Restore temporary troubleshooting changes one at a time. Use the WhatsApp Web translation setup as a reference when assigning languages to another contact, and verify that conversation separately.

You do not need every feature enabled. Keep the directions and language pairs you actually use so the next unexpected result is easier to diagnose.

WATrans

WATrans is a WhatsApp Web translator for Chrome. Read messages in your language and reply in theirs with free translation engines after activating plugin access.

Copyright © 2026 WATrans. All rights reserved.

WATrans is an independent browser extension and is not affiliated with, endorsed by, or sponsored by WhatsApp LLC or Meta Platforms, Inc.