Troubleshooting
WPML String Translation Not Working: Causes and How to Fix It

Short answer
WPML String Translation usually fails because the string was never scanned or registered, the translation is not marked complete, the string language is wrong, or the text is hard-coded without translation functions. Scan the theme or plugin, check the string settings, then clear every cache.
Key takeaways
- String Translation is a separate WPML add-on that must be active.
- Scan themes and plugins so their strings appear in the list.
- Text typed into settings screens must be registered as admin texts.
- Translations only show once they are marked complete.
- Hard-coded text without translation functions cannot be translated.
Why is WPML String Translation not working?
WPML String Translation usually fails because the string was never registered, the translation is not marked complete, the string language does not match your site settings, the text is hard-coded, or a cache is serving old pages.
String Translation handles text that does not live in posts and pages. That includes theme and plugin text, widget titles, the site tagline, and options saved in the admin area.
Because these strings come from many places, there are many ways for one to slip through. The checks below follow the order that solves most cases fastest.
If whole pages or posts are not translating, the issue is different. See our guide on WPML translation not working instead.
Is the String Translation add-on installed and active?
String Translation is a separate WPML add-on, so check that it is installed, active and included in your WPML plan.
Go to Plugins and look for WPML String Translation. It must be active alongside the core WPML plugin.
If you do not see it, check your plan on the WPML site. Not every plan includes String Translation. Our guide on how to install the WPML plugin shows how to add components from your account.
Also keep all WPML components on matching, current versions. Mixing old and new versions often causes strange string behaviour.
Can you find the string in WPML at all?
If the string does not appear under WPML > String Translation, it has not been registered yet, so scan the theme or plugin that outputs it.
Strings from themes and plugins need to be scanned before WPML knows they exist.
- Go to WPML > Theme and plugins localization.
- Find the theme or plugin that contains the text.
- Select it and click the scan button.
- Go back to WPML > String Translation and search again.
Search using a short, distinctive part of the text. Long searches often miss because of extra spaces or formatting.
The WPML guide to String Translation explains scanning and searching in detail.
Is the text an admin string or option?
Text saved in settings screens, such as a plugin's button label or a theme option, is an admin string, and you need to register it from the admin texts screen first.
At the bottom of the String Translation page, look for the link to translate texts in admin screens. It opens a list of saved options grouped by plugin and theme.
Tick the options you want to translate and save. They then appear in the main String Translation list.
This catches many people out. The text looks like plugin text, but because you typed it into a settings box, a scan of the plugin's files will never find it.
Is the translation marked as complete?
WPML only uses string translations that are marked complete, so a translation saved without that checkbox will not appear on the front end.
Open the string in WPML > String Translation and click the translation link for the language. Make sure the Translation is complete box is ticked, then save.
The status column should show a completed state for each language. A partly finished translation may look saved but still be ignored.
Translations done through the translation editor or by a translator also need to finish their workflow before they go live.
Does the string language match your site setup?
If WPML thinks a string is written in a different language than it really is, it will not swap it out, so check the string language and source language settings.
Each string has a language. If your site's default language is German but a plugin's strings are in English, WPML needs to know the strings are English.
In WPML > String Translation, you can change the language of selected strings or whole text domains. Set it to the language the text is actually written in.
Also check that you are translating into the right language. It is easy to add a translation for one language and then check the page in another.
Is the text hard-coded in the theme or plugin?
Text that is not wrapped in WordPress translation functions cannot be translated by WPML, no matter what settings you change.
Developers make text translatable by wrapping it in functions like __() or _e() with a text domain. The WordPress internationalization guide explains how this works.
If a theme prints plain text without those functions, WPML has nothing to hook into. Ask the developer to fix it, or move the text into a setting or template part you control.
If you maintain the code, our guide on how to translate a WordPress plugin covers text domains and translation files.
Are .mo files or file permissions the problem?
WPML can store string translations in translation files, so if WordPress cannot write those files, new translations may not show until permissions are fixed.
Recent WPML versions write translation files into a folder inside wp-content/languages. If that folder is not writable, WPML may show a notice in the admin.
These are the same compiled .mo files that the gettext system uses. The PHP gettext manual describes how they are read, if you want the background.
Check for any WPML warning about file permissions on the dashboard or String Translation screen. Fix permissions so the web server can write to the languages folder.
Our guide on setting correct file permissions in WordPress explains safe values for folders and files.
Is caching hiding your translations?
Page caches, object caches and CDN caches can keep showing the old text after you save a translation, so clear every layer before testing.
| Cache layer | How to clear it |
|---|---|
| Page cache plugin | Use its purge all option |
| Object cache, such as Redis | Flush it from the plugin or host panel |
| Server cache | Use your host's clear cache button |
| CDN | Purge from the CDN dashboard |
| Browser | Test in a private window |
Make sure your cache plugin creates separate caches per language. Most do this automatically with WPML, but a misconfigured cache can serve one language to everyone.
If you use Cloudflare, its guide on purging cache explains how to clear single URLs or the whole zone after saving translations.
Our guide to clearing cache in WordPress covers the most common plugins.
Is the text from a page builder, widget or menu?
Page builder text, menus and some widgets are not translated through String Translation, so you may be looking in the wrong place.
Text inside Elementor, WPBakery or block layouts is usually part of the page content. Translate it by translating the page itself. If that fails, see our guide on WPML with Elementor not working.
Menus are translated through WPML > WP Menus Sync or by creating a menu for each language. Widgets may need the block editor or String Translation, depending on type.
What should you check before contacting WPML support?
Note the exact text, where it appears, which plugin or theme outputs it, and what you see in String Translation, then contact WPML support with your debug information.
WPML has a FAQ on why translated strings do not show on the front end that covers more edge cases.
WPML's debug information page, found under WPML > Support, collects your versions and settings. Include it with your ticket to save time.
For a refresher on how strings fit into the wider setup, see our guide on how to use the WPML plugin.
Frequently asked questions
Why can't I find a string in WPML String Translation?
The string has probably not been registered. Scan the theme or plugin from the Theme and plugins localization screen. If the text was typed into a settings page, register it through the admin texts screen at the bottom of the String Translation page.
Why does my WPML string translation not show on the front end?
Check that the translation is marked complete, that the string language is correct, and that caches are cleared. Also confirm the text is actually that string, since similar text may come from a different plugin, widget or page content.
Can WPML translate hard-coded theme text?
No. WPML can only translate text that developers wrap in WordPress translation functions with a text domain. Hard-coded text needs a code change by the theme developer, or you can replace it with a setting or template you control.
Is String Translation included in every WPML plan?
No. Check your plan on the WPML website. Lower-tier plans may not include String Translation. If you need to translate theme, plugin and widget text, choose a plan that includes the add-on.
Do I translate Elementor text with WPML String Translation?
Usually not. Text inside Elementor layouts is part of the page content, so you translate it by translating the page with the WPML translation editor. String Translation is for text from themes, plugins, widgets and settings.
Sources
- String Translation WPML Documentation
- Why aren't my translated strings showing up on the front end of my site? WPML
- Internationalization WordPress Developer Resources
- Download and install WPML WPML Documentation
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


