If you run a TranslatePress site and you want AI translation on top of it, there are three real options worth comparing in 2026. Quick disclosure before the list: I work at Cool Plugins, which makes AutoTP, the first one on this list. The other two (TranslatePress's own built-in AI and TranslateX from GTranslate) are independent products. I will keep that honest as we go through each one.
How AI translation works on TranslatePress
TranslatePress handles the multilingual side: languages, hreflang, language URLs and the visual translation editor. To get AI translation on top of that, you add an AI layer. The three real options for that layer in 2026 are:
- AutoTP for bring-your-own-key translation with six providers
- TranslatePress's own Automatic Translation module with AI credits or your own DeepL or Google Translate key
- TranslateX for TranslatePress, a hosted translation engine added to TranslatePress through a single platform API
Before the list, one thing worth understanding upfront: TranslatePress's hosted AI credits are convenient but priced higher per word than running your own API key. We will cover the actual numbers in the second section. That cost gap is the main reason most TranslatePress users eventually move to a bring-your-own-key addon for bigger projects.
1. AutoTP: six AI providers (three of them free)
AutoTP is our addon for TranslatePress. It sits next to TranslatePress and adds bring-your-own-key AI translation plus three completely free providers that need no API key. Instead of paying for TranslatePress AI credits, you connect your own API key from OpenAI, Gemini or Claude and pay the provider directly at their raw API rate. Or you skip the key entirely and use Google Translate, Yandex or Chrome built-in AI for unlimited free translation.
The full provider list:
- OpenAI for marketing copy and editorial content where tone matters (GPT-4o recommended)
- Gemini for cost-efficient bulk translation
- Claude for long-form editorial and technical writing
- Google Translate, free unlimited with no API key inside AutoTP
- Yandex Translate, free unlimited, strong on Russian and Eastern European languages
- Chrome built-in AI, free in-browser translation with no API key and no quota
AutoTP also adds a proper bulk translation panel to the WordPress Pages and Posts screens. Pick the items, choose a target language, click Bulk Translate. The queue runs in the background and retries failed requests automatically. TranslatePress's own engine works string by string lazily as visitors hit pages, which is fine for small sites but painful when you want to translate 200 posts before a launch.
There is a free version on WordPress.org with over 10,000 active installs. The free build ships with Yandex and Chrome AI built in, so you can translate at zero cost from day one. The premium version unlocks OpenAI, Gemini, Claude and Google Translate plus the full bulk translation interface. The TranslatePress AI translation guide covers the full step-by-step setup if you want the deep walkthrough.
Bring your own OpenAI, Gemini or Claude key. Or translate unlimited with Google Translate, Yandex or Chrome AI at zero cost.
2. TranslatePress Automatic Translation (built-in)
TranslatePress Pro ships with an Automatic Translation module inside the standard settings panel. It is the path of least resistance because you already own TranslatePress Pro and the AI option is right there. Two modes are available:
- TranslatePress AI credits: their hosted AI service. The Business plan is around €199/year and includes about 200K AI translated words per year. You do not need a separate API key. Translations run through TranslatePress's own infrastructure.
- Bring your own DeepL or Google Translate API key: you connect a DeepL or Google Cloud Translate key and pay the provider directly based on usage. Cheaper than credits at scale but limited to those two engines.
The honest math on TranslatePress AI credits
200K bundled words per year sounds like a lot until you start running real projects. A single 1,500-word blog post translated into 3 languages eats 4,500 credits per post. Translate 50 posts and the yearly bucket is gone. A WooCommerce store with 300 products plus variations and category descriptions can exhaust the same allowance before launch.
When the bundled credits run out you can buy more, but the per-credit cost is where this gets expensive at scale. The effective rate works out to roughly €1 per 1,000 words after the bundle. Compared to running your own AI key through AutoTP:
- TranslatePress AI credits: ~€1 per 1,000 words
- AutoTP + OpenAI (GPT-4o): ~$0.10 per 1,000 words (about 10× cheaper)
- AutoTP + Gemini Flash: ~$0.01 per 1,000 words (about 100× cheaper)
- AutoTP + Google Translate, Yandex or Chrome AI: free (unlimited)
For a small marketing site translating one or two languages, the TranslatePress credit bundle is genuinely convenient and the math is fine. For anything bigger, this is the point where most teams switch to AutoTP and bring their own AI key. The two can also run side by side without conflict, so a common workflow is using TranslatePress's own DeepL for one language and AutoTP's OpenAI for another.
3. TranslateX for TranslatePress
TranslateX for TranslatePress is a third-party plugin by GTranslate that adds the TranslateX hosted translation engine as a new option inside TranslatePress's Automatic Translation module. You enter a TranslateX API key, pick TranslateX as the engine and translations are routed through api.translatex.com, with servers in the US and EU.
Where TranslateX fits:
- Hosted neural machine translation through a single platform API
- Free plan for personal or non-commercial sites, paid Pro plan for commercial projects
- Around 50 supported languages including the common European, Asian and Middle Eastern ones
- Works with both free and paid TranslatePress, version 2.9.16 and above
- Installs cleanly as an extra engine inside TranslatePress's own Automatic Translation settings
Worth knowing if you want a hosted alternative to DeepL or Google Translate with a free starter plan. The trade-off is similar to any single-engine hosted service. There is one provider, you depend on their pricing and uptime, plus the daily translation limits from TranslatePress's own settings still apply unless you raise them manually. It is a fair starting point for personal projects, but most growing sites end up wanting either the direct DeepL or Google Translate path inside TranslatePress or the wider provider stack in AutoTP. Take a look at the TranslateX plugin page if you want to try it.
Quick comparison: how the three stack up
| Feature | AutoTP | TranslatePress Automatic Translation | TranslateX for TranslatePress |
|---|---|---|---|
| Free version on WordPress.org | Yes (Yandex, Chrome AI) | Pro-only feature | Yes (free plan, registration required) |
| OpenAI (GPT-4o) | Yes | No | No |
| Gemini | Yes | No | No |
| Claude | Yes | No | No |
| DeepL | No (use TP built-in for DeepL) | Yes (your own DeepL API key) | No |
| Google Translate | Yes (free, no key) | Yes (your own Google Cloud API key) | No |
| Yandex Translate (free) | Yes | No | No |
| Chrome built-in AI (free) | Yes | No | No |
| Hosted AI credits | No (BYOK) | Yes (~€199/year for 200K words) | Yes (TranslateX free + Pro plans) |
| Bulk translation panel | Yes (WP Pages and Posts screens) | String-by-string as visitors browse | String-by-string via TranslatePress |
| Best for | BYOK savings + free unlimited options + bulk | Small sites that want one-click setup | Personal projects that want a hosted alternative to DeepL or Google |
Quick recommendations
- Want a free starting point with free unlimited providers built in: AutoTP free on WordPress.org with Yandex or Chrome AI.
- Bigger site, you have ever used TranslatePress AI credits: AutoTP with OpenAI or Gemini. Cost savings on the next bulk run usually pay for the license on day one.
- Translating mostly into European languages with TranslatePress Pro already: TranslatePress's built-in DeepL is the simplest path. Add AutoTP when you want OpenAI quality or free providers for the bulk pass.
- Want a hosted alternative to DeepL with a free plan: TranslateX for TranslatePress is a reasonable starting point for personal projects.
- Running multiple multilingual stacks across clients: the TranslateXYZ bundle covers AutoTP, AutoPoly, AutoMLP and LocoAI together.
Workflows that work well on TranslatePress
Workflow 1: TranslatePress AI credits for daily edits, AutoTP for bulk runs
Many users keep TranslatePress's built-in AI on for one-off translations during regular editorial work, then fire up AutoTP only for big bulk operations (new language launch, WooCommerce catalog migration, blog backlog catch-up). Both can run side by side without conflict.
Workflow 2: Hybrid premium and free providers inside AutoTP
Use OpenAI or Claude through AutoTP for high-value content (homepage, key landing pages, top product pages). Use Google Translate, Yandex or Chrome AI for everything else. Total spend usually stays under $10 even on big sites.
Workflow 3: Privacy-first translation
Legal, medical or internal documentation sites that cannot send content to cloud AI APIs. AutoTP with Chrome built-in AI translates entirely in the browser. Nothing leaves the machine.
Pitfalls regardless of which option you pick
- Install the SEO Pack add-on. Free TranslatePress add-on, handles hreflang and language-aware sitemaps. Without it, search engines may not index translated pages reliably.
- Mark non-translatable content with the no-translate class. TranslatePress respects the standard
notranslateCSS class. Use it on code blocks, brand names and anything that should stay in the source language. - Walk the visual editor as your QA pass. Whatever AI engine you use, walk the homepage and top landing pages in the target language before going live. The visual editor is TranslatePress's biggest advantage for QA.
- Clear cache after bulk runs. WP Rocket, W3 Total Cache and LiteSpeed all play nicely with TranslatePress once cache is cleared after a translation pass.
The bundle covers AutoTP, AutoPoly, AutoMLP and LocoAI together. Practical for agencies and freelancers running different multilingual plugins per client.
Wrapping up
TranslatePress's built-in Automatic Translation is the path of least resistance for small sites. AutoTP is the cost-effective path on everything bigger, especially WooCommerce stores and multi-language setups. The free AutoTP build with Yandex and Chrome AI covers the zero-budget scenario. TranslateX is a third hosted option worth knowing if you want a free plan and an alternative to DeepL or Google Translate inside TranslatePress's own settings.
For the full step-by-step setup, the TranslatePress AI translation guide walks through everything. For broader context comparing TranslatePress to the other multilingual plugins, the three-way comparison covers pricing and workflow side by side.
