Description
LATW AI Translation for Polylang adds automatic AI translation to the Polylang site you already have. Polylang keeps your languages, URLs, language switcher and translation groups. This plugin fills in the translations.
Pick a post, tick the languages and click Translate. The job runs on your server, in the background, so you can close the tab and move on. The finished translation lands in Polylang as an ordinary post, linked to the original, exactly as if you had written it yourself.
Why LATW for Polylang
- Translates in the background, not in your browser. Jobs are queued and finished on the server. Close the tab, and long pages still translate without timing out.
- One screen for your whole site. Posts, pages, custom post types, categories, tags, Polylang strings and SEO titles all have their own translation screens, with the status of every language at a glance.
- Your engine, your API key. OpenAI, Google Gemini, Google Translate, the free MyMemory, or LATW Cloud with no API key at all. Pro adds Claude, DeepL and your own model. The provider bills you directly, at their price, and we add nothing on top.
- You see what every translation cost. The History screen records the model, the tokens and the actual cost of each job.
- Works with Polylang free and Polylang Pro. No need to buy Polylang Pro to get automatic translation.
- Your translations stay yours. They are ordinary Polylang posts, terms and strings. Delete this plugin, and every translation stays on your site.
- The free version is not a trial. Unlimited translations into every language set up in Polylang, 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.
- 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, bulk translation, automatic translation of new posts, a glossary, and translation straight from your Claude or ChatGPT chat.
How it plugs into Polylang
Polylang has no translation pipeline of its own to plug into: a translation is just another post, linked to the original through Polylang’s translation groups. So this plugin does the whole job itself. It reads the content, sends only the text to your engine, and writes the translation back as a linked Polylang post, term or string.
On Polylang Pro it reuses Polylang’s own export and import machinery, so what counts as translatable always matches what Polylang understands. On Polylang free it uses its own content walker, built to follow the same rules.
Who it is for
- Site owners on Polylang who want their content translated without copying it into a chatbot page by page
- Agencies running client sites on Polylang that want translation cost on a metered API key instead of a subscription
- Elementor sites, where only the text should travel to the model and the layout should stay untouched
- 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 Polylang is set to translate
- Gutenberg blocks, including Spectra blocks, with their attributes preserved
- Elementor layouts: only the text inside known widgets is sent to the model, never the layout, styling or IDs
- Categories, tags and custom taxonomies, on a dedicated screen with per-term status
- Strings registered with Polylang, in batches
- SEO titles and descriptions from Yoast SEO, Rank Math, SEOPress and All in One SEO
- Advanced Custom Fields (ACF), image alt texts and any custom field you choose
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: a model on your own server, OpenRouter, Groq (Pro)
- LATW Cloud: no API key, pay per word
Workflow
- Translate a post into several languages in one click, in the background
- Processing modes: Synchronous, Background and Batch at roughly half the price (OpenAI)
- Choose the status of new translations, and which parts of a post are translated
- A manual “Check Responses” button for hosts where WP-Cron does not run
- Pages built with Bricks, Divi, Beaver Builder, Oxygen or WPBakery are detected and skipped with the reason shown, instead of producing a broken translation
- 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)
- Custom field control: translate extra meta keys, or exclude ones you do not want touched
- 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 you have set up in Polylang, permanently.
Free
- Unlimited translations, every Polylang language
- Posts, pages and custom post types
- Gutenberg, Spectra and Elementor
- Taxonomy translation and Polylang string translation
- ACF fields, custom fields and SEO metadata
- Translation history and per-job cost tracking
- All processing modes, including Batch at roughly half price (OpenAI)
- 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
- Bulk translation
- Automatic translation of new content
- Re-translate only changes
- Editable translation prompt and glossary
- 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 Translation → 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.
Page builders
Elementor is supported. Only the text inside known widget fields is extracted and sent to the model, as a flat list of strings. The widget tree itself — layout, styling, IDs, responsive settings — never leaves your site, and the translation is written back into a copy of the original tree, so nothing the model never saw can be damaged by it.
Spectra blocks are supported. Pages built with Spectra — the block library Astra’s starter templates install — are translated like any other block editor content: headings, paragraphs, buttons, tabs, accordions and their labels.
Other builders are refused rather than mangled. Bricks, Divi, Beaver Builder, Oxygen and WPBakery keep their content in their own storage format instead of the post content. Translating such a post would either produce an empty page or copy the original layout across untouched — both of which look like a broken plugin. Posts built with them are detected and blocked in the interface, with the reason shown, and refused server-side as well.
Polylang and Polylang Pro
Both editions work. With Polylang Pro the plugin delegates string extraction and reassembly to Polylang’s own export machinery, so block parsing stays in step with whatever Polylang supports. On Polylang free it uses its own content walker instead. Elementor always goes through the plugin’s own extractor, on both editions.
Requirements
- WordPress 6.2 or higher
- PHP 7.4 or higher
- Polylang 3.2 or higher, with at least two languages configured — this is an add-on for Polylang, not a standalone translation plugin
- An API key for the engine you choose. MyMemory needs none, and LATW Cloud needs a LATW account instead.
- Working WP-Cron, or a real server cron job calling wp-cron.php. If neither is available, the plugin offers a manual “Check Responses” button instead. LATW Cloud needs neither, but your site must be reachable from the internet so LATW Cloud can read and write through the WordPress REST API.
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
- 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
LATW Cloud
- Service URL: https://app.latw.ai/
- Privacy Policy: https://latw.ai/privacy-policy/
- Terms of Use: https://latw.ai/terms-of-service/
Installation
Quick start
- Install and activate Polylang, and set up at least two languages.
- Install and activate LATW AI Translation for Polylang.
- Go to AI Translation > Settings, choose an engine and paste its API key. Starting with MyMemory needs no key at all.
- Optionally write a short website description, so the language model knows what kind of site it is translating.
- Open AI Translation > Translations, pick your content and target languages, and start.
Translations arrive in the background. Check History to see what was sent, what came back, and what each job 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. Bulk translation, the glossary, the editable prompt, the extra engines, the custom endpoint and MCP 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:
- 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
- MyMemory — no key required
- Custom endpoint (Pro) — whatever your provider issues, for example openrouter.ai/keys or console.groq.com/keys; a model on your own server usually needs no key
FAQ
Do I need Polylang?
Yes. This is an add-on for Polylang, not a standalone translation plugin. It needs Polylang active with at least two languages, and does nothing without it.
Does it work with Polylang free, or only Polylang Pro?
Both. Polylang Pro lets the plugin reuse Polylang’s own export and reassembly machinery; on Polylang free the plugin uses its own content walker. The screens and the results are the same either way.
What can I do with the free version?
Translate unlimited content into every language configured in Polylang, using MyMemory, Google Translate, selected low-cost OpenAI and Gemini models, or LATW Cloud. Posts, custom post types, taxonomies, strings, ACF, Elementor, SEO metadata and custom fields 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 — you pay the provider directly, at their rates. Language models bill per token, Google Translate bills per character, MyMemory is free within its quota. As a rough guide, a single 1,000-word page through GPT-6 Luna or Gemini 3.5 Flash Lite costs well under one cent. Every completed job records what it actually cost, so the History screen shows real figures for your own content rather than an estimate.
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 — unless you connect the optional LATW Cloud engine, which translates on LATW’s servers and deletes your text 7 days after each job (see Third-Party Services).
Which engine should I choose?
If quality on nuanced content matters most, use a language model — OpenAI or Gemini. It reads 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 is 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. A site connected to LATW Cloud has to be disconnected first; it then goes back to the engine it used before.
Do Google Translate and MyMemory use the prompt?
No. They ignore the translation prompt and the website description. They are machine translation engines rather than language models, so there is nothing to prompt.
Can I customise the translation prompt?
This plugin ships one prompt, and the Settings page prints it in full so you can see exactly what is sent. You can still add a website description, which is passed to the model with every translation. Writing a prompt of your own, and a glossary for locking specific terms, come with Pro.
Which languages are supported?
Every language you have configured in Polylang. There is no per-language limit in the free version.
What are the processing modes?
Synchronous waits for the provider and fills in the translation in the same run.
Background is OpenAI-only. It finishes without holding a long request open, and is the default where available.
Batch is OpenAI-only too. It sends the job to OpenAI’s Batch API for roughly half the price and collects it when ready, usually within the hour, though OpenAI only guarantees a 24-hour window.
Gemini, Google Translate and MyMemory run synchronously only.
Does it work with page builders?
Elementor is supported. Bricks, Divi, Beaver Builder, Oxygen and WPBakery are deliberately refused: their content lives in their own storage format, and translating it would produce an empty page or an untranslated copy. Those posts are marked in the list with the reason, rather than silently producing a broken translation.
Does it work with WooCommerce?
Products are ordinary posts as far as Polylang is concerned, so the plugin translates whatever Polylang hands over. There is no shop-specific handling — product attribute taxonomies and variations are not covered.
Can I stop it translating certain fields?
Yes. Settings > Custom Fields takes a list of meta keys to translate in addition to the defaults, and a list to exclude. The exclusion list wins.
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 term. It runs inside the subscription you already have, so there is no API key and no per-token charge, and publishes the result as a Polylang-linked translation. The free version does not include MCP.
Can I see what was translated?
Yes. The History screen shows every past translation, what was sent, what came back, the status of each job and what it cost. The Logs screen carries the technical detail.
How are translations queued?
Jobs go to your chosen engine and are collected by WP-Cron in the background, so long pages do not time out. Cron health is shown on the dashboard. If your host blocks WP-Cron, enable Manual Check Responses in Settings > Advanced to get a button that collects finished jobs on demand. With LATW Cloud no cron is involved: LATW Cloud reads the content and writes the translation back itself.
What happens to my translations if I delete the plugin?
They stay. Translated posts, terms and strings are ordinary Polylang content and belong to your site. Deleting the plugin removes its own queue table, settings and logs, and nothing else.
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 licence at all.
Screenshots







Changelog
1.1.3
- Improvement: with the LATW Cloud engine, AI Translation → 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.
1.1.2
- Fix: pages built with Spectra blocks kept their original text. Pages made with Spectra, the block library Astra’s starter templates install, were translated with every heading, paragraph and button still in the original language. Their text is now translated on both Polylang free and Polylang Pro; translate those pages again to replace translations made earlier.
1.1.0
- New: LATW Cloud engine. Connect the site to your LATW account under AI Translation → Settings → General and translate on LATW’s servers with LATW Credits or your own API key, with no WP-Cron needed.
1.0.1
- New: GPT-6 Luna. OpenAI’s new low-cost model is now available to pick under AI Translation → Settings → General → Model.
1.0.0
- First release.
