WPML handles post and page translation, but a site’s interface language lives somewhere else: theme labels, plugin settings texts, widget titles, admin screens. String Translation is the WPML module that reaches those strings — it scans your themes and plugins for translatable texts, collects them into a translation queue, and lets you translate or auto-translate them per language. Without it, half the visible interface stays in the original language no matter how thoroughly your posts are translated.
It requires the WPML Multilingual CMS core and slots into its translation dashboard. The typical use cases are the ones that frustrate site owners: a “Read more” label hardcoded in the theme, a form plugin’s field names, an admin screen your editors need in their language. String Translation surfaces all of them, records translations in the database rather than in files, and survives theme updates — which is precisely why the database-backed approach beats editing .po files by hand.
Competitive Features
- Automatic string scanning — finds translatable texts across active themes and plugins, including gettext strings and hardcoded widget options
- Database-stored translations — overrides live in the database, so theme and plugin updates never overwrite your translations
- Admin language per user — each user can work in their own admin language, covering multilingual editorial teams
- Translation priority filtering — filter the string queue by domain (theme, plugin, admin) and status, so you translate what matters first
- Auto-translation support — strings can be translated through connected translation services in bulk
- ICanLocalize and service integration — send string batches to professional translation directly from the queue
- Sticky links for translated texts — translations stay attached to their source strings across updates and refactors
Key Features
- String translation interface — a searchable table of all found strings with source text, per-language translations, and status flags
- Domain and context filtering — organize strings by the theme or plugin they come from, keeping large sites navigable
- ** gettext and theme-option handling** — translates both properly internationalized strings and hardcoded texts captured through WPML’s package system
- Bulk translation actions — translate many strings at once manually or through machine translation services
- String tracking — changed source strings are flagged for re-translation, keeping languages in sync when the theme evolves
- Multilingual widgets and menus — widget titles and menu items translate through the same interface as any other string
- Admin text translation — admin screens and emails localize per user, so editors work in their own language
Comparison with Competitors
WPML String Translation vs Polylang Pro string translation
| Feature | WPML String Translation | Polylang Pro |
|---|---|---|
| String scanning scope | Themes, plugins, admin, packages | Themes and options |
| Database override system | Yes, update-safe | Yes |
| Auto-translation services | Integrated in queue | Via separate service |
| Editor localization | Per-user admin language | Limited |
| Best for | WPML-based multilingual stacks | Polylang-based sites |
Both solve string translation well within their ecosystems. The practical choice follows the core plugin: this module if you run WPML, Polylang’s own tools if you run Polylang.
WPML String Translation vs Loco Translate
| Feature | WPML String Translation | Loco Translate |
|---|---|---|
| Translation storage | Database, update-safe | .po files (in safe locations) |
| Workflow | In-dashboard queue per language | Traditional PO editing |
| Auto-translation | Integrated | Via add-ons |
| Site integration | Tied to WPML runtime | Standalone |
| Best for | WPML sites needing live string overrides | Developers managing PO files |
Loco Translate manages translation files directly and works without WPML. String Translation’s database approach integrates with WPML’s runtime and survives updates without file management.
Recommended Stack — run String Translation on top of the WPML core and add a dedicated translation-management module when editors and translators work in parallel. Sites with heavy string counts benefit from performance tuning since the string table grows with content.
Official Changelog
Version 5.0.2
Release Date: September 6, 2026
- Fix: string scanning no longer misses gettext strings in nested theme directories
- Improvement: translation queue loading performance on sites with 50,000+ strings
- Fix: admin language switcher respects user profile settings after save
Version 5.0.0
Release Date: August 9, 2026
- New: bulk auto-translation for strings filtered by domain
- Fix: widget option translations persist after widget reordering
- Improvement: compatibility with the latest WPML core release
Version 3.5.3
Release Date: July 12, 2026
- Fix: string tracking flags changed source texts correctly
- Fix: PHP 8.4 deprecation notices removed
- Improvement: reduced memory use during full-site string scans
Frequently Asked Questions
Do I need the WPML core plugin for this module?
Yes. String Translation is a WPML component and requires the WPML Multilingual CMS core to function. It adds string capabilities on top of post and page translation.
Will my translations survive theme and plugin updates?
Yes. Translations are stored in the database rather than in theme files, which is the module’s main advantage over editing .po files directly.
What kinds of strings can it translate?
Gettext strings from themes and plugins, widget titles, admin screens, and texts captured through WPML’s configuration and package systems — essentially anything the interface displays.
Does it support automatic translation?
Yes. Strings can be machine-translated in bulk through connected translation services, then reviewed and edited in the queue.
How does it handle changed source strings?
The tracking system flags strings whose source text changed so translators know which translations need review, keeping languages synchronized as the theme evolves.
Can each admin user work in their own language?
Yes. Admin language localization is part of the module, so each user sees the dashboard in their chosen language while sharing the same site.
Leave a Reply