الوصف
LATW AI Translation for WPML adds an AI translator to the WPML Translation Management workflow you already use.
WPML keeps doing what it does today: language switching, translation jobs, string translation, the whole multilingual structure of your site. This plugin registers one additional translator inside that pipeline and lets it do the actual translating, using the AI model or translation engine you pick.
You bring your own API key
WPML’s built-in automatic translation is billed in WPML credits. This plugin works differently. You connect your own provider key, and every request goes straight from your WordPress server to OpenAI, Google, Anthropic or DeepL, at their published rates, with nothing added on top by us.
A real example. Translating 30 articles into 3 languages costs €386.00 in WPML Automatic Translation credits. The same job, through this plugin with GPT-5.4 nano, costs $0.45. Same content, same WPML workflow, over 99% off the bill.
Nothing passes through our servers, and no content is stored outside your site and your chosen provider. You are responsible for your own provider billing and usage limits.
How it plugs into WPML
On activation the plugin creates a dedicated virtual translator user, latwaitr_ai_bot, shown in WPML as “LATW AI Translator”, and registers it with WPML as a local translator for your active language pairs.
Assign content to that translator on WPML’s Translation Management screen and the plugin picks the job up automatically, translates it with your chosen engine, and hands the result back through WPML’s own pipeline.
The practical consequence: if WPML can send it for translation, this plugin can translate it. Posts, pages, custom post types, taxonomies, strings, page-builder layouts, third-party integrations. The plugin does not reinvent translation routing, it rides WPML’s.
Who it is for
- Agencies running client sites on WPML that want translation cost moved off the invoice and onto a metered API key
- Site owners with a few hundred pages, where credit-based pricing stops making sense
- Anyone who needs translated content to travel between their own server and one named provider, with no intermediary in between
Features
- Deep WPML integration — runs entirely through WPML’s Translation Management pipeline via a dedicated AI translator user
- Six engines, your choice — MyMemory, Google Translate, OpenAI, Gemini, and in Pro also Claude and DeepL
- String Translation — batch-translate interface, theme and plugin strings from WPML String Translation
- Page builder support — full support for Elementor and Bricks Builder; other WPML-compatible builders should work but are not officially tested
- ACF support — translates Advanced Custom Fields content
- Taxonomy translation — a dedicated screen for categories, tags and custom taxonomies, with per-term status
- SEO metadata — Yoast SEO, Rank Math, SEOPress and All in One SEO titles and descriptions
- Website context — describe your site once and every LLM translation is done with that context in mind
- Cost tracking — every completed job records what it actually cost, priced against the engine that produced it
- Translation history — review any past translation, inspect what was sent and what came back, track status over time
- Custom prompt and glossary — control tone, register and terminology, and lock specific terms to specific translations (Pro)
- Processing modes — translate synchronously for immediate results, or send jobs to the provider’s Batch API for roughly half the price
- Re-translate only changes — edit one paragraph, pay for one paragraph instead of the whole page (Pro)
- Bulk translation — queue dozens of posts for translation in a single action instead of one at a time (Pro)
- WooCommerce — product attribute taxonomies, variations and shop-specific data (Pro)
Free vs Pro
The free version is not a trial. It translates unlimited content into every language configured in WPML, permanently.
Free
- Unlimited translations, all WPML languages
- Posts, pages and custom post types
- Elementor, Bricks and ACF
- WPML String Translation
- Taxonomy translation
- SEO metadata
- Translation history and cost tracking
- All processing modes, including Batch at roughly half price
- Engines: MyMemory, Google Translate, OpenAI GPT-5.6 luna and GPT-5.4 nano, Gemini 3.5 Flash Lite
Pro
Everything in free, plus:
- Bulk translation — queue many posts at once
- Re-translate only changes
- Custom translation prompt
- Glossary
- WooCommerce support
- Engines: Claude Opus 5, Sonnet 5 and Haiku 4.5; DeepL; OpenAI GPT-5.6 Sol, GPT-5.6 Terra, GPT-5.5 and more; Gemini 3.7 Flash, 3.6 Flash and more
- Premium support
Supported content
- Post titles, content and excerpts
- Custom post types
- Elementor and Bricks Builder widgets and modules
- ACF fields
- WPML String Translation strings
- Yoast SEO, Rank Math, SEOPress and All in One SEO metadata
- Categories and custom taxonomies
- WooCommerce products, attributes and variations (Pro)
- Anything else WPML is able to send for translation
Translation engines
Six engines, split into two kinds. Language models read the whole page, follow your prompt and your website description, and handle nuance. Machine translation engines are faster and cheaper per word but take no instructions, because there is nothing to instruct.
Language models
- OpenAI — GPT-5.6 luna and GPT-5.4 nano in free; GPT-5.6 Sol, GPT-5.6 Terra, GPT-5.5 and more in Pro
- Google Gemini — Gemini 3.5 Flash Lite in free; Gemini 3.7 Flash, 3.6 Flash and more in Pro
- Anthropic Claude — Opus 5, Sonnet 5 and Haiku 4.5 (Pro)
Machine translation
- Google Translate — Neural Machine Translation, billed per character
- DeepL — billed per character (Pro)
- MyMemory — translation memory with machine translation fallback, free within a daily quota
Each engine stores its own API key and model separately, so switching between them, and back again, costs you nothing in reconfiguration.
Requirements
- WordPress 6.2 or higher
- PHP 7.4 or higher
- WPML — required, this is an add-on and not a standalone translation plugin
- An API key for the engine you choose. MyMemory needs none.
Third-Party Services
Content is sent only to the engine you selected in the plugin settings, and only when you start a translation. Nothing is sent without your action, and every request goes directly from your WordPress server to that provider.
OpenAI API
- Service URL: https://api.openai.com/
- Privacy Policy: https://openai.com/privacy/
- Terms of Use: https://openai.com/terms/
Google Gemini API
- Service URL: https://generativelanguage.googleapis.com/
- Privacy Policy: https://policies.google.com/privacy
- Terms of Use: https://ai.google.dev/gemini-api/terms
Google Cloud Translation API
- Service URL: https://translation.googleapis.com/
- Privacy Policy: https://policies.google.com/privacy
- Terms of Use: https://cloud.google.com/terms
MyMemory (Translated S.r.l.)
- Service URL: https://api.mymemory.translated.net/
- Privacy Policy and Terms of Use: https://mymemory.translated.net/terms-and-conditions
- Usage limits: https://mymemory.translated.net/doc/usagelimits.php
لقطات الشاشة
التنصيب
Quick start
- Install and activate LATW AI Translation for WPML
- Go to AI Translator > Settings, choose an engine and paste its API key. Starting with MyMemory needs no key at all. 2.5. Optionally write a short website description, so the language model knows what kind of site it is translating
- Open Translations page, select your content, and translate it.
The plugin picks the job up from there and returns the finished translation through WPML. Check Translation History to see what was sent, what came back, and what it cost.
Where to get an API key
The settings screen links straight to the right page for each engine, with step-by-step instructions:
- OpenAI — platform.openai.com/api-keys
- Google Gemini — aistudio.google.com/apikey
- Google Translate — a Google Cloud API key with the Cloud Translation API enabled
- Anthropic Claude (Pro) — console.anthropic.com
- DeepL (Pro) — deepl.com/pro-api
- MyMemory — no key required
الأسئلة المتكررّة
-
Do I need WPML?
-
Yes. This is an add-on for WPML, not a standalone translation plugin. It extends WPML with AI-powered automatic translation and does nothing without it.
-
How is this different from WPML’s own automatic translation?
-
WPML bills automatic translation in WPML credits, purchased from WPML. This plugin bills nothing at all: you connect your own provider key and the provider charges you directly at their list price. There is no markup and no intermediary. In exchange you manage your own API account and your own spending limits.
-
What can I do with the free version?
-
Translate unlimited content into every language configured in WPML, using MyMemory, Google Translate, OpenAI GPT-5.6 luna, GPT-5.4 nano or Gemini 3.5 Flash Lite. Posts, custom post types, taxonomies, ACF, Elementor, Bricks, SEO metadata and WPML strings are all included. It is not a trial and it does not expire.
-
How much does translation actually cost?
-
It depends on the engine and the volume. Language models bill per token, Google Translate and DeepL bill per character, MyMemory is free within its quota.
Rough guide for a single 1,000-word page:
- OpenAI GPT-5.4 nano — under $0.01
- Gemini 3.5 Flash Lite — under $0.01
- Google Translate — $20 per million characters
- MyMemory — free, within its daily quota
- Batch mode — roughly half the synchronous price
For a full project: 30 articles into 3 languages runs to €386.00 in WPML Automatic Translation credits, against $0.45 with GPT-5.4 nano through this plugin.
-
Which engine should I choose?
-
If quality on nuanced content matters most, use a language model. It sees the whole page, follows the translation prompt and your website description, and keeps tone consistent. If you are pushing large volumes of straightforward text and cost is the priority, Google Translate and DeepL are cheaper and faster, and MyMemory is free within its daily quota.
-
Can I switch engines later?
-
Yes, at any time. Each engine keeps its own key and model setting, so switching back does not mean re-entering anything.
-
Do Google Translate, DeepL and MyMemory use the prompt?
-
No. They ignore the translation prompt, the website description and the reasoning effort setting. They are translation engines rather than language models, so there is nothing to prompt.
-
Can I customise the translation prompt?
-
In the free version the prompt is fixed and shown read-only on the Settings page, but you can add a website description that is passed to the model with every translation. A fully editable prompt, along with a glossary for locking specific terms, is a Pro feature.
-
What are the processing modes?
-
Synchronous waits for the provider and fills in the translation in the same run. Fastest feedback, full price.
Background is OpenAI-only. It finishes in minutes without holding a long request open, and is the default where available.
Batch sends the job to the provider’s Batch API for roughly half the price and collects it when ready, usually within the hour, though providers only guarantee a 24-hour window.
All three modes are available in the free version. Google Translate, DeepL and MyMemory run synchronously only, because they have no Batch API. That is safe even for long posts, since their content is split into many small requests.
-
What is bulk translation, and how is it different from Batch mode?
-
They solve different problems and the names are easy to confuse.
Batch mode is about price: a single job is sent to the provider’s Batch API instead of being translated immediately, and comes back at roughly half the cost. Available to everyone.
Bulk translation (Pro) is about volume: you select dozens of posts and queue them all for translation in one action, rather than assigning them one at a time. It works with any processing mode.
-
Does it work with WooCommerce?
-
WooCommerce support is a Pro feature. Products are ordinary posts as far as WPML is concerned, so the free version translates whatever WPML hands over, but it has no shop-specific handling: no product attribute taxonomies (
pa_*), no variations, no other WooCommerce data. Pro adds that handling and supports it. -
Does it work with page builders?
-
Elementor and Bricks Builder are fully supported. Other builders compatible with WPML should work, but have not been officially tested.
-
Can I translate WPML strings?
-
Yes. The plugin integrates with WPML String Translation, so interface strings, theme strings and plugin strings can be batch-translated through your chosen engine directly from the plugin.
-
Can I see what was translated?
-
Yes. The Translation History page shows every past translation, what was sent, what came back, the status of each job and what it cost.
-
How are translations queued?
-
Through WordPress Cron, in the background, so long jobs do not time out. You can check cron status from the admin UI.
-
What happens when my Pro license expires?
-
The version you have keeps working, but you stop receiving updates until you renew. The free version continues working regardless, with no license at all.
المراجعات
المساهمون والمطوّرون
“LATW AI Translation for WPML” هو برنامج مفتوح المصدر. وقد ساهم هؤلاء الأشخاص بالأسفل في هذه الإضافة.
المساهمون
ترجمة ”LATW AI Translation for WPML“ إلى لغتك.
مُهتم بالتطوير؟
تصفّح الشفرة، تحقق من مستودع SVN، أو الاشتراك في سجل التطوير بواسطة RSS.
سجل التغييرات
2.2.0
- All languages in the free version. Every language configured in WPML can now be translated, with no per-language limit.
- New: MyMemory engine. A free translation memory and machine translation engine that needs no API key, available in the free version.
2.1.0
- New: additional translation engines. Alongside OpenAI you can now use Anthropic (Claude), Google Gemini, DeepL and Google Translate. Each engine keeps its own API key and model, so switching back and forth costs you nothing.
- New: DeepL and Google Translate support. Dedicated machine-translation engines, billed per character instead of per token.
- New: processing modes. Choose Synchronous, Batch or Background. Modes an engine cannot serve fall back to Synchronous instead of failing.
- New: current models. GPT-5.6 luna, terra and sol, Claude Opus 5, Sonnet 5 and Haiku 4.5, Gemini 3.7, 3.6 and 3.5 Flash, and Gemini 3.5 Flash Lite.
2.0.9
- Fix: Astra Site Builder layouts not showing after translation.
- Fix: corrected the database join used to read untranslated posts.
- Fix: translated products kept appearing as needing translation.
- Fix: fatal error when saving translations of WooCommerce products, caused by the downloadable-files field type not being passed to WPML/WCML.
2.0.0
- Translations now ride WPML’s Translation Service pipeline. The plugin no longer writes translated posts directly. Jobs are pushed through WPML’s queue, so they appear in WPML’s Translation Management UI, respect WPML job statuses and stay consistent with manual edits.
- New: Taxonomy Translation page. A dedicated tab for categories, tags and custom taxonomies, with its own term browser and per-term status.
- Database and options upgrade. The queue table stores WPML job IDs, and the dedicated translator user is created on activation and removed on deactivation.