LATW AI Translation for WPML – Automatic Translation Without WPML Credits

By szymon0zawadzki

★ 5.0/5 (5 ratings)100+ active installationsVersion 3.1.5

Automatic AI translation inside WPML with your own OpenAI, Gemini, Claude or DeepL key, or LATW Cloud. No WPML credits. Unlimited free version.

Description

LATW AI Translation for WPML replaces WPML’s credit-based automatic translation with the AI you choose. It adds an AI translator to WPML, so your languages, URLs, translation jobs and editors stay exactly as they are. Only the translating changes, and so does the bill.

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-6 Luna costs $0.19. Same content, same WPML workflow, over 99% less on the bill. Your own cost depends on the model and the content.

Why LATW for WPML

  • Over 99% cheaper than WPML credits. Use your own API key and pay OpenAI, Google, Anthropic or DeepL their list price. We add nothing on top. Batch mode cuts that price roughly in half again.
  • Works inside WPML, not next to it. The plugin adds a translator called “LATW AI Translator” to WPML. If WPML can send it for translation, this plugin can translate it: posts, pages, custom post types, taxonomies, strings, page builder layouts and SEO fields.
  • Runs in the background. Translations are queued and finished on the server. You can close the browser while dozens of pages translate.
  • Your engine, your choice. OpenAI, Google Gemini, Anthropic Claude, DeepL, Google Translate, the free MyMemory, any OpenAI-compatible API, or LATW Cloud with no API key at all. Switch at any time.
  • The free version is not a trial. Unlimited translations into every language configured in WPML, with no expiry.

Three ways to translate

  • With your own API key (free). Paste an OpenAI, Gemini or Google Translate key, or start with MyMemory, which needs no key. The provider bills you directly, at their price.
  • With LATW Cloud (free plugin, pay per word). Click Connect with LATW and AI translates on LATW’s servers. You don’t need an API key, a Pro licence or a working WP-Cron. Your first connected site gets 10,000 free words to try it. LATW Cloud is an optional paid service (see Third-Party Services below).
  • With Pro. Every current model from OpenAI, Anthropic and Google, plus DeepL, automatic translation of new posts, a glossary, WooCommerce support, and translation straight from your Claude or ChatGPT chat.

How it plugs into WPML

On activation the plugin creates a translator user, LATW AI Translator (latwaitr_ai_bot), and registers it in WPML as a local translator for your active language pairs.

Pick content on the plugin’s Translations screen and click Translate. The plugin sends the job through WPML, translates it with your engine and hands the result back through WPML’s own pipeline. The translation then behaves like any other WPML translation: it opens in WPML’s Translation Editor, and WPML marks it as needing an update when the original changes.

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 off the invoice and onto a metered API key
  • Site owners with a few hundred pages, where credit-based pricing stops making sense
  • WooCommerce shops on WPML with large catalogs (WooCommerce support is in Pro)
  • Anyone who wants their content to travel only between their own server and one named provider

Features

What it translates

  • Post titles, content and excerpts, pages and custom post types
  • Elementor and Bricks Builder layouts. Other WPML-compatible builders should work, but are not officially tested.
  • Advanced Custom Fields (ACF)
  • Categories, tags and custom taxonomies, on a dedicated screen with per-term status
  • Theme, plugin and interface strings from WPML String Translation, in batches
  • SEO titles and descriptions from Yoast SEO, Rank Math, SEOPress and All in One SEO
  • WooCommerce products, attributes and variations (Pro)
  • Anything else WPML is able to send for translation

Engines

  • Language models: OpenAI and Google Gemini (selected low-cost models in free), Anthropic Claude and every current model (Pro)
  • Machine translation: Google Translate, MyMemory (free, no key), DeepL (Pro)
  • Your own model or any OpenAI-compatible API: Ollama, vLLM, LM Studio, OpenRouter, Groq (Pro)
  • LATW Cloud: no API key, pay per word

Workflow

  • Translations queued in the background, with a WP-CLI command (wp latwaitr run) for hosts where WP-Cron is unreliable
  • Processing modes: Synchronous, Background (OpenAI) and Batch at roughly half the price
  • Choose the status of new translations: same as the original, published, draft, pending or private
  • Review translations in WPML’s Translation Editor or the native WordPress editor
  • Failed requests are retried automatically, and provider errors are shown with the reason
  • Bulk translation: queue dozens of posts in one action (Pro)
  • Automatic translation of new posts of selected types, with daily limits (Pro)
  • Re-translate only what changed: edit one paragraph, pay for one paragraph (Pro)
  • Translate from your Claude or ChatGPT chat: no API key and no per-token cost (Pro)

Control and cost

  • Website description: tell the model once what your site is about, and every translation uses it
  • Custom prompt and glossary to control tone and lock terminology (Pro)
  • The cost of every job is recorded, priced against the engine and model that produced it
  • Translation history: what was sent, what came back, status and errors

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 and taxonomy translation
  • SEO metadata
  • Translation history and cost tracking
  • All processing modes, including Batch at roughly half price
  • Engines: MyMemory, Google Translate, selected OpenAI and Gemini models
  • LATW Cloud

Pro

Everything in free, plus:

  • Every current model from OpenAI, Anthropic (Claude) and Google (Gemini)
  • DeepL
  • Your own model, or any OpenAI-compatible API: a model on your own server, OpenRouter, Groq
  • Translate from your Claude or ChatGPT chat, with no API key and no extra token cost
  • Automatic translation of new content
  • Bulk translation
  • Re-translate only changes
  • Custom translation prompt and glossary
  • WooCommerce support
  • Premium support

Pro is an add-on: it installs next to this plugin and adds its features to the screens you already know. Get Pro

LATW Cloud

With LATW Cloud, your server doesn’t call an AI provider or wait for WP-Cron to collect the answer. LATW’s servers read the text from your site, translate it and write the translation back, so long pages and large batches no longer depend on your host’s timeouts.

LATW Cloud is a good fit if:

  • you don’t want to create an account with an AI provider or generate your own API key (pay with LATW Credits instead),
  • WP-Cron doesn’t run reliably on your site,
  • your server is small and you don’t want translations to load it,
  • you want to manage translations for several sites from one dashboard.

Connecting. Under AI Translator → Settings → General, pick LATW Cloud as the engine and click Connect with LATW. A window opens where you sign in to your LATW account and authorize the site. The plugin does the rest and checks that LATW Cloud can reach your site. No Pro licence is needed.

Requirements. The site must be reachable from the internet. If a security plugin, firewall or password protection blocks access, LATW Cloud tells you when you connect or click Test connection.

Your data. LATW Cloud does not store your source texts. They are processed only while a translation is running. Finished translations are written straight back to your site. A translation is stored on LATW’s servers only when your site can’t be reached at that moment. In that case it is kept for up to 7 days until it can be delivered, and then deleted.

Requirements

  • WordPress 6.2 or higher
  • PHP 7.4 or higher
  • WPML. This is an add-on, not a standalone translation plugin.
  • An API key for the engine you choose. MyMemory needs none, and neither does a model you host yourself. LATW Cloud needs a LATW account instead.

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 — except with LATW Cloud, described last, where LATW’s servers do the translating.

OpenAI API

Google Gemini API

Google Cloud Translation API

MyMemory (Translated S.r.l.)

LATW Cloud

Installation

Quick start

  1. Install and activate LATW AI Translation for WPML
  2. 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
  3. 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.

Adding Pro

Pro is a separate add-on plugin that runs alongside this one. Install this plugin first, then upload the Pro .zip under Plugins > Add New > Upload Plugin and activate it. The extra engines, the glossary and automatic translation appear on the screens you already know — there is no second settings page and nothing to migrate.

Where to get an API key

The settings screen links straight to the right page for each engine, with step-by-step instructions:

FAQ

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.

The one exception is LATW Cloud, if you choose to connect it. Then you pay for translation in LATW Credits instead of keeping your own provider account, or you use your own API key in LATW Cloud.

Is my content sent anywhere else?

No. Content goes from your server to the engine you selected and back. It does not pass through our servers, and we neither see nor store it. The exception is the optional LATW Cloud engine, if you connect it: LATW’s servers then read the text from your site, have it translated by the AI model chosen for the site and write the translation back. Source texts are not stored. A translation is kept on LATW’s servers only while your site can’t be reached to receive it, for up to 7 days (see LATW Cloud above).

What can I do with the free version?

Translate unlimited content into every language configured in WPML, using MyMemory, Google Translate, selected low-cost OpenAI and Gemini models, or LATW Cloud. 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-6 Luna — 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.19 with GPT-6 Luna through this plugin.

LATW Cloud prices each job by the number of words and charges it in LATW Credits, or your provider bills you directly if you use your own API key in LATW Cloud. Current prices are at latw.ai/cloud.

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. If you don’t want to manage an API key, WP-Cron is unreliable on your host or your server is small, choose LATW Cloud.

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.

While the site is connected to LATW Cloud, the Engine setting is locked to it. To use another engine, click Disconnect under AI Translator → Settings → General (or disconnect the site in LATW Cloud). The engine you used before connecting comes back, with its key and settings unchanged.

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.

With LATW Cloud, the prompt, the glossary and the website description are set for the site in LATW Cloud instead, and their fields here link there.

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.

With LATW Cloud there is no processing mode to choose: LATW’s servers run the translation, so the setting is hidden.

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.

Can I translate from a chat with Claude or ChatGPT?

Yes, with Pro. Pro includes an MCP server: connect your site once to Claude or ChatGPT, then ask the assistant to translate a post, page or product. It reads the content through WPML, translates it inside the subscription you already have, so there is no API key and no per-token charge, and publishes the result as a WPML-linked translation with blocks and internal links intact. The free version does not include MCP.

While the site is connected to LATW Cloud, the MCP server and Pro’s automatic translation are switched off. Their settings are kept, and they work again after you disconnect.

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.

For translations done by LATW Cloud, the Cost column says “LATW Cloud”, because LATW Cloud bills them. You can see what they cost in your LATW account.

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.

With LATW Cloud, WordPress Cron is not used. Translations show as “In LATW Cloud” in the queue, and LATW’s servers write each one back to your site as soon as it is ready. You can cancel a translation from the queue until LATW Cloud starts translating it.

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.

Screenshots

Changelog

3.1.5

  • Improvement: with the LATW Cloud engine, AI Translator → Settings → General shows your balance in LATW Credits (for example “Solo · 61.7 Credits”) and the plan without a subscription as Free, matching the new LATW Cloud plans.
  • Improvement: confirmations and messages now appear in the plugin’s own dialog and as notices at the top of the page, instead of the browser’s pop-up boxes.

3.1.4

  • Fix: the notice “LATW AI Translator requires WPML plugin to be installed and activated.” could show up even though WPML was installed and active. It happened when WordPress loaded this plugin before WPML. The notice now shows only when WPML is really missing.

3.1.3

  • Fix: clicking Save Changes on AI Translator → Settings → General sometimes did nothing — no message, no reload, and the API key was not saved. It happened when the browser or a password manager filled in a field of another engine that was hidden at the time, such as the MyMemory contact email. The settings now save.

3.1.2

  • Improvement: the AI now gets only the text of each field instead of its full HTML, with short placeholders where tags sit inside the text, the way WPML’s Advanced Translation Editor shows it. Parts of a page that have no text at all are not sent. The HTML is put back unchanged before the translation is saved. Pages built with blocks and page builders cost much less to translate. This works with every AI engine and with LATW Cloud. It is on by default, and you can turn it off under AI Translator → Settings → Advanced → Send Only Text.

3.1.1

  • Fix: new Gemini API keys from Google AI Studio (the ones starting with “AQ.”) were rejected as invalid. The dot in the key was removed when saving it. Paste your Gemini key again under AI Translator → Settings → General after updating.

3.1.0

  • New: LATW Cloud engine. Connect the site to your LATW account under AI Translator → Settings → General and translate on LATW’s servers with LATW Credits or your own API key, with no WP-Cron needed.

3.0.6

  • Fix: translating categories, tags or other taxonomies could change the language of an original term, leave the new translation without a language, or link it to the wrong original. It happened on sites where a term’s ID and its taxonomy ID differ, which is common on WooCommerce shops. Translations are now linked to the right term.
  • Fix: the “Translate Again” list for taxonomies showed the wrong term names on those sites, and translating a term from it could translate a different term. It now lists and translates the right ones.
  • Fix: a term whose name stays the same in the target language, such as a brand, could take over the original term as its own translation. It now gets a term of its own.
  • Fix: a child term whose parent could not be translated was moved to the top level of the tree. It now fails with a message asking you to translate the parent first, and the tree stays as it is.
  • Fix: translating a term again replaced the slug and the parent you had set by hand. Only a slug the plugin generated follows the new name now, and the parent is changed only to match the original term’s parent.

3.0.5

  • Fix: with the Pro add-on installed, translations ignored the OpenAI or Gemini model chosen under AI Translator → Settings → General → Model and were always sent to the default model (GPT-5.4 nano or Gemini 3.5 Flash Lite). The model you select is now the one that translates.

3.0.4

  • New: Translated Post Status. Choose the status a newly created translation gets — the same as the original post (default), Published, Draft, Pending Review or Private. Find it under AI Translator → Settings → Translation. Existing translations keep their current status when they are translated again.
  • Fix: private, pending and scheduled posts were missing from the AI Translator → Translations list, so they could not be translated. They are listed now, and the Status filter covers them too.

3.0.3

  • Fix: the upgrade banner and the review request could not be dismissed for good. Closing them, or choosing “Maybe later” or “Don’t show again”, hid them only until the next page load.

3.0.2

  • New: GPT-6 Luna. OpenAI’s new low-cost model is now available to pick under AI Translator → Settings → General → Model.

3.0.1

  • Improvement: a translation that the AI provider refuses now fails immediately, with the reason. When the provider rejects the request itself — a model it does not know, a setting it does not accept, a key it does not like — the same request is no longer sent two more times before giving up. You see what the provider said on the first attempt, on the Translations and History screens. Timeouts, rate limits and provider outages are still retried.

3.0.0

  • The Pro version is now an add-on. It installs alongside this plugin instead of replacing it, so this plugin holds the translation engine, the screens and the history for both. If you only use the free version, nothing changes.
  • New: a translation that fails is retried instead of giving up. A request the AI engine rejects or drops is sent again up to three times before the translation is marked as failed, so a passing glitch at the provider no longer costs you a translation.
  • New: wp latwaitr run processes the queue from WP-CLI, for sites where WP-Cron is unreliable.
  • New: a translation can now be checked, corrected or rejected by your own code before it is saved into WPML.
  • Improvement: Target Languages now starts with every language WPML is set up for ticked, instead of nothing, so the plugin is ready to translate straight away. Untick the ones you do not want; an empty list is filled in again, as it would leave the plugin translating nothing.
  • Improvement: switching translation engine no longer disturbs translations already in progress — each one is finished by the engine it was sent to.
  • Fix: after sending content for translation the page did not refresh, so the Active Translation Queue stayed hidden until you reloaded it by hand. The confirmation pop-up is gone with it — the message now appears on the refreshed page.
  • Fix: the plugin could take over translation jobs assigned to a different translator in WPML.

2.2.4

  • Improvement: Check Response button on History page

2.2.3

  • New: reasoning effort for Gemini. The Reasoning Effort setting now applies to Gemini as well as OpenAI, and is sent as the model’s thinking level.
  • Fix: Gemini translations were priced without their thinking tokens, which Gemini reports separately from the answer tokens. Cost history was under-reporting them.

2.2.2

  • Fix: translation category – always use the source language, not the one currently set in the admin panel.

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.