Description
LATW AI Translation for TranslatePress adds automatic AI translation to the TranslatePress site you already have. TranslatePress keeps your languages, the language switcher, the visual translation editor and your multilingual URLs. This plugin fills in the translations.
Use it in two ways, or both. Pick it as the engine under TranslatePress > Settings > Automatic Translation, and pages are translated as visitors open them. Or open the plugin’s Pages screen, tick the languages and translate whole pages in the background, before anyone visits them.
Translations are written into TranslatePress’s own tables, so they show up in its visual editor and can be corrected there like any other translation.
Why LATW for TranslatePress
- Your own API key, no word quota. 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. We add no credits, no word packs and nothing on top.
- Whole pages, translated in the background. The Pages screen shows how many strings each page still has untranslated in every language. One click queues the page, and the job finishes on your server even after you close the tab.
- Built into TranslatePress itself. It appears as an engine in TranslatePress’s own Automatic Translation settings, and adds a Translate with AI button to the TranslatePress visual editor.
- Your hand corrections are safe. A normal translation only fills in strings that have no translation yet. A string you corrected in the TranslatePress editor is never sent to the model and never overwritten, unless you ask for a page to be translated again from scratch.
- You see what every translation cost. The History screen records the model, the tokens and the actual cost of each job.
- Works with the free TranslatePress. No paid TranslatePress add-on is needed for AI translation.
- The free version is not a trial. Unlimited translations into every language set up in TranslatePress, 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 content, a glossary, and translation straight from your Claude or ChatGPT chat.
How it plugs into TranslatePress
TranslatePress does not translate posts. It renders the page, collects the text from the finished HTML and stores every string in its own tables, one per language. This plugin works on those same strings:
- As a TranslatePress translation engine. Pages are translated by your chosen AI model as visitors open them, exactly like TranslatePress’s built-in engines, with its character counter, its daily limit and its translation log still in charge.
- As a batch queue. The Pages screen groups TranslatePress’s strings by page and translates them ahead of time, in the background. Theme and plugin interface strings (gettext) are translated the same way from the String Translation screen.
Because TranslatePress reads the finished page rather than the editor’s storage format, page builders need no special handling. Elementor, Bricks, Divi, the block editor and the rest are translated from what they render.
Who it is for
- Site owners on TranslatePress who want the whole site translated by AI without buying word packs
- Agencies running client sites on TranslatePress that want translation cost on a metered API key instead of a subscription
- Sites built with Elementor, Bricks, Divi or any other builder, since TranslatePress translates what the page renders
- Anyone who wants their content to travel only between their own server and one named provider
Features
What it translates
Whatever TranslatePress itself collects and lets you translate:
- Page content: text, headings, buttons, image alt texts and titles, whichever theme or page builder rendered them
- Interface strings of your theme and plugins (gettext), by text domain
- Page titles and meta descriptions, as TranslatePress collects them
- URL slugs, when TranslatePress’s SEO Pack add-on is active and its automatic slug translation is switched on
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
- TranslatePress translation engine: translate new text on the fly as pages are opened
- Pages screen: untranslated strings per page and per language, one-click translation into several languages
- Translate Again: translate a finished page again from scratch, replacing every translation it has
- String Translation screen: page strings and theme and plugin strings, translated in batches
- Translate with AI in the TranslatePress visual editor: fill a single translation, check it, then save
- Processing modes: Synchronous, Background and Batch at roughly half the price (OpenAI)
- A manual “Check Responses” button for hosts where WP-Cron does not run
- Bulk translation: queue many pages in one action (Pro)
- Automatic translation: new posts translated after publishing, and new text as TranslatePress collects it, within a daily limit you set (Pro)
- Translate from your Claude or ChatGPT chat: no API key and no per-token cost (Pro)
Control and cost
- Hand corrections are kept: a normal translation only fills in strings with no translation. Only Translate Again replaces them, and it says so before it starts
- 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 you have set up in TranslatePress, permanently.
Free
- Unlimited translations, every TranslatePress language
- The TranslatePress translation engine, for on-the-fly translation
- Page-by-page translation in the background
- Page strings and theme and plugin (gettext) strings
- Translate with AI in the TranslatePress visual editor
- 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
- 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 into TranslatePress, 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.
What it translates. The pages you translate from the Pages screen, the strings you send from the String Translation screen, and, started from LATW Cloud itself, whole pages and the theme and plugin strings of any text domain. The model, LATW Credits or your own API key, the prompt, the glossary, the website description and the target languages are set per site in LATW Cloud. As with every engine, a normal translation never overwrites a string you corrected by hand. “Translate again” in LATW Cloud translates the whole page or text domain from scratch, the same as Translate Again on the Pages screen, and replaces your hand corrections too.
What changes while connected. LATW Cloud works in jobs rather than while a page loads. Translating new text as visitors open pages (this plugin as TranslatePress’s automatic translation engine) and the Translate with AI button in the TranslatePress editor are therefore paused. New text on a page stays untranslated until you translate the page from the Pages screen or from LATW Cloud. Everything comes back as it was when you disconnect.
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.
Cost. 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. Translations made by LATW Cloud show as “LATW Cloud” in this plugin’s History.
Requirements
- WordPress 6.2 or higher
- PHP 7.4 or higher
- TranslatePress 3.0 or higher, with at least two languages configured. This is an add-on for TranslatePress, 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, for background translation. If neither is available, the plugin offers a manual “Check Responses” button instead. LATW Cloud does not need WP-Cron.
Third-Party Services
Content is sent only to the engine you selected in the plugin settings. For batch translation, that happens only when you start a translation. When you select this plugin as TranslatePress’s automatic translation engine, TranslatePress sends the untranslated strings of a page through it when that page is opened in another language — the same as with TranslatePress’s built-in engines. 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
Only when you connect the site to it. LATW’s servers then read the text of the items you translate from your site through the WordPress REST API, have it translated by the AI model chosen for the site, and write the translation back (see LATW Cloud above).
- Service URL: https://app.latw.ai/
- Privacy Policy: https://latw.ai/privacy-policy/
- Terms of Use: https://latw.ai/terms-of-service/
Screenshots








Installation
Quick start
- Install and activate TranslatePress, and add at least one language besides your default one.
- Install and activate LATW AI Translation for TranslatePress.
- 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.
- Either select LATW AI Translation as the engine under TranslatePress > Settings > Automatic Translation, or open AI Translation > Pages, pick a page and its target languages, and click Translate.
Background translations arrive on their own. 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, automatic 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 TranslatePress?
-
Yes. This is an add-on for TranslatePress, not a standalone translation plugin. It needs TranslatePress active with at least two languages, and does nothing without it.
-
Does it work with the free TranslatePress, or only the paid versions?
-
Both. Everything works with the free TranslatePress. The only thing that needs a paid TranslatePress add-on is slug translation, which TranslatePress itself offers only with its SEO Pack.
-
Should I use it as a TranslatePress engine, or translate in the background?
-
Either, or both. As a TranslatePress engine, a page is translated when a visitor first opens it in another language. It is simple, but the first visitor waits while the model answers. The Pages screen does the same work ahead of time, in the background, and can use OpenAI’s Batch API for roughly half the price. Many sites translate their existing pages from the Pages screen and leave the engine on for whatever appears later. A site connected to LATW Cloud translates from the Pages screen only: the engine is paused while it is connected.
-
Why is a page missing from the Pages screen, or showing fewer strings than I expected?
-
TranslatePress learns a page’s text when that page is rendered in a translated language. Until then there is nothing for the plugin to translate. Open the page once in any of your translated languages, and it appears on the Pages screen with its string counts. Text that only shows up for some visitors, or only after an interaction, is collected when TranslatePress first sees it.
-
Will it overwrite translations I corrected by hand?
-
Not unless you ask it to. A normal translation only fills in strings TranslatePress has no translation for. A string you edited in the TranslatePress editor, and a theme string translated by its own language file, are never sent to the engine and never written over.
The one exception is Translate Again, on the Pages screen and as “Translate again” in LATW Cloud. It translates the whole page from scratch in the languages you pick and replaces every translation the page has, including the ones you corrected by hand. The confirmation says so before anything is sent. To add only the missing translations, use Translate on the Pages list instead.
-
What can I do with the free version?
-
Translate unlimited content into every language configured in TranslatePress, using MyMemory, Google Translate, selected low-cost OpenAI and Gemini models, or LATW Cloud. Use it as TranslatePress’s engine, page by page from the Pages screen, string by string, or from the TranslatePress editor. 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, on our test site a short blog post cost about $0.0002 and an Elementor home page about $0.0003 per language with GPT-6 Luna. Every completed job records what it actually cost, so the History screen shows real figures for your own content rather than an estimate. Translation done through the TranslatePress engine is counted by TranslatePress’s own character counter and daily limit.
-
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).
-
Which engine should I choose?
-
If quality on nuanced content matters most, use a language model: OpenAI or Gemini. It 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.
-
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 TranslatePress. There is no per-language limit in the free version.
-
What are the processing modes?
-
These apply to translation from the Pages and String Translation screens. 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. Translation through the TranslatePress engine is always synchronous, because the visitor is waiting for the page.
-
Does it work with page builders?
-
Yes. TranslatePress collects text from the page as it is rendered, so it does not matter which builder produced it: Elementor, Bricks, Divi, Beaver Builder, Oxygen, WPBakery or the block editor.
-
Can I translate URL slugs?
-
Only with TranslatePress’s SEO Pack add-on, which is what lets TranslatePress translate slugs at all. With SEO Pack active and its automatic slug translation switched on, slugs are translated by this plugin’s engine like everything else.
-
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 your strings. It runs inside the subscription you already have, so there is no API key and no per-token charge, and the result is saved into TranslatePress. The free version does not include MCP.
-
Can I see what was translated?
-
Yes. The History screen shows every past translation from the Pages and String Translation screens: what was sent, what came back, the status of each job and what it cost. The Logs screen carries the technical detail. Translations made through the TranslatePress engine also appear in TranslatePress’s own machine translation log.
-
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.
-
What happens to my translations if I delete the plugin?
-
They stay. Translations are stored in TranslatePress’s own tables and belong to your site. Deleting the plugin removes its own queue table, settings and logs, and never touches TranslatePress’s data.
-
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.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“LATW AI Translation for TranslatePress – Automatic Translation with OpenAI & Gemini” is open source software. The following people have contributed to this plugin.
ContributorsInterested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.0.1
- New: Translate Again. The Pages screen’s “Update Translations” button is now “Translate Again”: it translates a finished page again from scratch in the languages you pick and replaces every translation it has, including the ones you corrected by hand. Translate on the list still fills in only what is missing.
- Fix: “Translate again” in LATW Cloud estimated 0 words for a page that was already translated and translated nothing. It now translates the whole page or text domain from scratch
1.0.0
- First release.
