I get asked about TranslatePress a lot at Cool Plugins. Mostly some variation of "we like the visual editor, but how do we actually translate a full site without burning through their AI credits?" This guide is the answer I usually give. We will look at what TranslatePress gives you out of the box, where the built-in AI credits hit a wall and how to extend the setup with AutoTP for six AI providers (three of them completely free).
Why people pick TranslatePress in the first place
TranslatePress works differently from WPML and Polylang. Instead of treating each language as a copy of a post, it intercepts strings at render time and swaps them out. That sounds nerdy, but it has one big practical consequence. You click any element on your live site, you translate it inline and the visual editor shows you the real page with the real layout as you work.
For agencies handing translation off to a client who has never touched the WordPress admin, that workflow is a game changer. I have set this up on a handful of client sites and the learning curve for non-technical reviewers is basically zero. They open the page, click, type, save. That is the whole experience.
What TranslatePress includes for AI translation
The free version on WordPress.org is manual-only. To unlock AI, you need TranslatePress Pro. The Automatic Translation module supports two modes:
- TranslatePress AI credits: their hosted service. The Business plan is roughly €199/year and includes about 200K AI translated words per year. You do not need any API key. Translations run through TranslatePress's own infrastructure.
- Your own DeepL or Google Translate API key: bring-your-own-key mode for either DeepL or Google Cloud Translate. You pay the provider directly based on usage, which works out much cheaper than credits once you exceed the bundled allowance.
Both options live inside the same Automatic Translation panel in TranslatePress Pro. The credits route is genuinely easy to start with. The DeepL or Google route gives you better cost control. Either way, the visual editor is the QA layer you walk through afterwards to approve the AI output.
Where TranslatePress AI credits get expensive
200K words sounds like a lot until you start running real numbers. A typical 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 burn the same allowance before the site even launches.
When the bundled credits run out you can buy more, but the per-credit pricing is where this gets painful at scale. This is the same gap WPML users hit with their own credit system, and the same fix applies: use a third-party addon to bring your own AI key (or use a free provider) and pay the provider directly.
AutoTP: six AI providers for TranslatePress
AutoTP is our addon for TranslatePress. It sits next to TranslatePress and adds six AI options inside the same visual-editor workflow:
- OpenAI for marketing copy and editorial content where tone matters. GPT-4o is the recommended model.
- Gemini for high-volume work. Gemini Flash is roughly 10× cheaper than OpenAI for similar quality on most language pairs.
- Claude for long-form editorial and technical writing. Reads more naturally on tone-heavy content in many languages.
- Google Translate for free unlimited bulk translation. No API key needed inside AutoTP.
- Yandex Translate for Russian and Eastern European languages. Free, no API key.
- Chrome built-in AI for completely free in-browser translation. Nothing leaves your machine.
The first three (OpenAI, Gemini, Claude) need your own API key from the provider. You pay them at their raw API rate. The last three (Google Translate, Yandex, Chrome AI) run free inside AutoTP. No API key, no metering, no quota.
AutoTP also has a free version on WordPress.org with over 10,000 active installs. The free version 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, Google Translate and the bulk translation interface.
Real cost comparison: TranslatePress AI vs AutoTP options
Here is the cost picture for translating a 50,000-word site into one language. Numbers are approximate but they reflect the actual rates from each provider's public pricing as of 2026.
| Translation route | Cost for 50K words, one language | API key needed? | Notes |
|---|---|---|---|
| TranslatePress AI credits | About €50 (a quarter of the €199/year bucket) | No | Hosted by TranslatePress, simple but limited to the 200K-word annual bucket |
| TP + DeepL API (your own key) | About $5 to $10 | Yes (DeepL) | Best for European languages, you pay DeepL directly |
| TP + Google Translate API (your own key) | About $10 | Yes (Google Cloud) | Google Cloud Translate billing, separate from free options |
| AutoTP + OpenAI (GPT-4o) | About $5 | Yes (OpenAI) | Best quality for tone-heavy content |
| AutoTP + Gemini Flash | About $0.50 | Yes (Google AI Studio) | Best price-to-quality on bulk content |
| AutoTP + Google Translate | Free | No | Unlimited, no quota, no API key inside AutoTP |
| AutoTP + Yandex Translate | Free | No | Unlimited, especially good for Russian and Eastern European languages |
| AutoTP + Chrome built-in AI | Free | No | Runs in your browser, fully private, no quota |
The pattern is consistent. Hosted AI credits are convenient but expensive. Your own API key is much cheaper. Free providers inside AutoTP are unlimited, which is honestly the strongest argument for AutoTP if you are running a content blog or any site where the translation just needs to be readable, not award-winning.
Add OpenAI, Gemini and Claude with your own API key. Or translate unlimited with Google Translate, Yandex or Chrome AI at zero cost.
Step by step: bulk translate a TranslatePress site with AutoTP
First-time setup is about ten minutes. Every translation job after that is a few clicks from the WordPress Pages or Posts screen.
Step 1. Install TranslatePress and configure languages
Install TranslatePress (free or Pro) and add your target languages under Settings → TranslatePress → General. Free supports one extra language, Pro supports unlimited. Make sure the URL slug field is filled for each language before you start translating. That trips up more people than I would like.
Step 2. Install AutoTP alongside TranslatePress
Install AutoTP on the same site and activate it. AutoTP detects TranslatePress automatically and adds its own settings page plus a bulk action to your Pages and Posts screens. Both plugins are designed to coexist, so you can keep TranslatePress's own Automatic Translation enabled too if you want a fallback.
Step 3. Pick a provider and connect a key (if needed)
Open the AutoTP settings page. Pick your provider:
- Paid (your own API key): OpenAI, Gemini, Claude
- Free (no key required): Google Translate, Yandex Translate, Chrome built-in AI
For OpenAI, grab a key at platform.openai.com/api-keys. For Gemini, visit aistudio.google.com/apikey. For Claude, sign up at console.anthropic.com. Paste the key into AutoTP, save, the connection is tested automatically.
Step 4. Open Pages or Posts in your WordPress admin
Go to Pages or Posts. AutoTP adds translation status indicators next to each item so you can see at a glance which posts already have translations in each language.
Step 5. Select the items to translate
Tick the checkboxes next to the posts you want, or use the top "Select all" checkbox to grab everything on the screen. For large sites, filter by category or date first and translate in smaller batches.
Step 6. Pick a target language and click Bulk Translate
Choose one language or all configured languages from the bulk action dropdown, then click Bulk Translate. AutoTP queues the jobs and sends them to your AI provider in the background. You can close the tab and come back. Failed requests auto-retry. The TranslatePress bulk translation guide covers queue handling and rate limits in more depth.
Picking the right AutoTP provider
A short decision framework I use when consulting on TranslatePress setups:
- Marketing pages or brand-sensitive copy? OpenAI or Claude. Both read more naturally than the generic translation engines on tone-heavy content.
- Hundreds or thousands of items on a budget? Gemini Flash. Cost is roughly a tenth of OpenAI for comparable quality on bulk content.
- Translating into German, French, Spanish or Italian? If you want to stay with TranslatePress's own engine, use the built-in DeepL with your own DeepL API key. If you also need other providers, AutoTP fills in everywhere else.
- Russian or Eastern European languages? AutoTP + Yandex. Free, unlimited, often better than Google for those specific languages.
- Budget is zero? AutoTP + Google Translate or Chrome AI. Both unlimited and free, ideal for content sites and staging environments.
On real projects I usually end up using two providers. A free option (Google Translate or Yandex) for the first-pass bulk translation, then OpenAI on the homepage, key landing pages and top 10 product pages where quality really matters. That hybrid setup keeps the overall bill under $10 even for sites with 200,000+ words.
The visual editor is your QA tool
This is where TranslatePress really earns its place over Polylang and WPML for many teams. After a bulk run, you do not have to guess whether the AI translated everything correctly. You walk through the live site in the target language, every string that has not been reviewed shows a coloured indicator in the visual editor. Click any of them, edit if needed, save. Twenty to thirty minutes per site for a solid QA pass.
I usually walk the homepage, the top three blog posts (by traffic, ask your analytics), the pricing or services page plus the contact page. Anything else can be reviewed lazily as it comes up.
WooCommerce stores on TranslatePress
TranslatePress has the easiest WooCommerce setup of the three big multilingual plugins because WooCommerce strings get intercepted automatically. No extra add-on needed for products, attributes, variations or checkout strings. Both TranslatePress's own AI and AutoTP handle all of this.
One gotcha: product permalinks. TranslatePress translates URL slugs only on the Business plan and above. If you are on Personal and SEO-clean translated URLs matter to you, the upgrade is worth it.
Pro tips most people miss
- Mark non-translatable content with a CSS class. TranslatePress respects the standard
notranslateclass. Use it on code blocks, brand names, addresses and anything that should stay in the source language. - Watch your caching plugin. Clear cache after every big translation run or visitors might get the old single-language version. WP Rocket, W3 Total Cache and LiteSpeed all play nicely once cache is cleared.
- Use the language switcher widget. Do not roll your own. TranslatePress's switcher handles flag selection, URL preservation and fallback languages cleanly.
- Translate menus through the visual editor. Menu items sometimes do not show up cleanly in the bulk panel, but they always work in the visual editor. Browse to a page that uses the menu, translate the items in place.
What about SEO?
TranslatePress has a free SEO Pack add-on that handles hreflang, language-aware sitemaps and meta translation. Install it. Without it, search engines will not reliably index your translated pages. AutoTP also translates Yoast or Rank Math meta fields automatically as part of bulk translation, so SEO meta does not need a separate pass.
AutoTP, AutoPoly, AutoMLP and LocoAI together. One license covers every multilingual stack a client throws at you.
Wrapping up
TranslatePress is the right pick when a non-developer will own translation review. The visual editor workflow is genuinely unmatched. Pairing it with AutoTP gives you provider flexibility on top, with three free providers that take the cost question off the table for most projects.
For a deeper look at the TranslatePress AI ecosystem specifically, the TranslatePress AI addons roundup breaks down each option. For a side-by-side comparison with the other multilingual plugins, the WPML vs Polylang vs TranslatePress deep dive covers pricing and workflow trade-offs.
