WPML Translation Credits vs. AI API Keys:
The Brutal Truth About Your Monthly Bill
One of these scales with you. The other one bleeds you quietly.
If you’ve been using WPML’s built-in translation credits to keep your multilingual site up to date, you’ve probably noticed the bill doesn’t stay flat. Every new product, every updated post, every added language — it all goes on the per-word tab. This article lays out exactly what that costs over time, what the alternative looks like, and why most site owners don’t make the switch until they’ve already spent more than they needed to.
How WPML translation credits actually work
WPML’s translation credits system is straightforward on the surface: you buy credits, each credit translates a certain number of words, and WPML’s infrastructure routes your content through an AI engine on your behalf. You don’t choose the engine, you don’t control the model, and you pay their rate — not the AI provider’s rate.
That gap between what the AI provider charges and what WPML charges you is the core of the problem. You’re paying a margin on top of the actual cost of the translation, every single time, for every single word. On a small static site that barely changes, this is manageable. On any site that publishes regularly or maintains a growing product catalog, the math turns against you fast.
You pay a markup
WPML purchases AI translation wholesale and resells it to you per word. The actual token cost from providers like OpenAI is significantly lower than what credits translate to in practice.
No model choice
WPML decides which AI engine processes your content. You can’t pick GPT-4 for nuanced blog posts and a cheaper model for short product titles. One rate, one quality level, no flexibility.
Costs grow forever
Every product you add, every post you update, every new language you enable — it all generates new translation demand. With per-word billing, a growing site pays a growing bill with no ceiling in sight.
The numbers side by side
Let’s make this concrete. Here’s what translating a typical 50,000-word WooCommerce store into 3 languages looks like under each model — and what happens when you update 20% of your content each month.
| Scenario | WPML Credits | AI API (NEXU Addon) |
|---|---|---|
| Initial bulk: 50,000 words × 3 languages | ~$75–120 | ~$10–18 |
| Monthly update: 10,000 words × 3 languages | ~$15–24 / month | ~$2–4 / month |
| Year 1 total (initial + 12 months updates) | ~$255–408 | ~$34–66 |
| You save in Year 1 | — | ~$220–342 |
| NEXU Addon plugin cost (one-time) | N/A | Pays itself back in month 1 |
These are conservative estimates based on typical AI API token pricing. Actual savings depend on your content volume and language count — but the direction of the difference doesn’t change regardless of scale.
What “bring your own API key” actually means
When you connect your own AI API key through the NEXU AI Translation Addon for WPML, you’re removing the middleman entirely. You create an account directly with OpenAI, Anthropic, Mistral, or xAI, get an API key, and paste it into the addon settings. From that point, your translations go directly to that provider at their published token rates — with no markup, no per-word padding, and no dependency on WPML’s infrastructure for the actual translation work.
WPML still does its job — managing the multilingual structure of your site, the language switcher, the URL routing. But the translation layer is now yours to control. You choose which AI model processes each job, you see your usage in the addon’s statistics panel, and you pay the AI provider directly at rates that are a fraction of what credits cost.
NEXU AI Translation Addon — routes your WPML translation jobs through your own AI API key, bypassing the per-word credit system entirely.
The hidden costs people miss
The per-word rate isn’t the only thing that adds up with WPML credits. There are a few other cost factors that don’t show up obviously until you’re already deep into the system.
Re-translating updates
Every time you edit a page or update a product description, WPML marks it as needing re-translation. That’s more credits spent on content you’ve already paid to translate once. If you refine your copy regularly, this compounds fast.
Adding a new language
Every language you add requires translating your entire existing content from scratch. With the credits model, that’s a large one-time spend every time you expand to a new market. With API pricing, it’s a fraction of the cost.
WooCommerce catalog growth
Each new product you add has a title, description, short description, attributes, and metadata — all of which need translating. A store that adds 50 products per month is generating a steady translation bill that never plateaus under the credits model.
Setup takes minutes. Savings start immediately.
Switching from WPML credits to your own AI API doesn’t require rebuilding anything. The NEXU addon installs like any WordPress plugin, registers itself as a translator inside WPML, and from that point forward new translation jobs are routed through your API key — not through WPML’s credit system.
Bulk translate your entire existing content in one go — no credit drain.
Real-time queue dashboard — watch translations process, retry if needed.
Your existing WPML setup stays completely intact. Content already translated stays translated. The only thing that changes is where new translation jobs get sent — and what you pay for them.
“But I don’t want to manage an API account”
This is the most common reason people stay on WPML credits longer than they should. It’s worth addressing honestly.
Setting up takes 5 minutes
Creating an OpenAI or Anthropic account, generating an API key, and pasting it into the NEXU addon settings is genuinely a 5-minute task. There’s nothing to configure beyond choosing your preferred model.
Billing is completely transparent
AI providers show you exactly what each request cost in their dashboard. OpenAI, Anthropic, and Mistral all have clear usage pages. You always know what you’ve spent — there are no surprise credit top-ups.
You can set spending limits
Every major AI provider lets you set monthly spending caps and alert thresholds on your API account. You’ll never accidentally run up a huge bill — something that’s actually harder to control with pre-purchased WPML credit bundles.
Is the translation quality better, worse, or the same?
WPML’s credit system uses a fixed AI engine — you don’t know which one, and you can’t change it. When you use your own API key through the NEXU addon, you choose. That means you can use GPT-4o for your most important product pages and a more cost-efficient model for routine content. In practice, you’re not accepting lower quality — you’re gaining the ability to apply higher quality where it actually matters.
For most content types, modern AI models like Claude, GPT-4, and Mistral produce translations that are genuinely better than what WPML’s fixed engine outputs — particularly for nuanced language, technical product terminology, and long-form blog content. The quality argument for credits doesn’t hold up once you’ve actually compared outputs side by side.
WPML credits — fixed model
One engine for everything. No visibility into which model, no option to upgrade for important content, no way to use a cheaper model for simple strings to save cost.
AI API — your choice
OpenAI, Claude, Mistral, or Grok — switch between them from the same settings panel. Use GPT-4 for high-value pages, Mistral for bulk catalog updates. Quality where it matters, efficiency where it doesn’t.
Credits made sense when there was no alternative.
There’s now an alternative.
WPML’s translation credits weren’t a bad idea — they were a convenient way to access AI translation without managing external API accounts. In 2024, that convenience premium was hard to avoid. In 2026, with the NEXU AI Translation Addon making the API connection a 5-minute setup, paying that premium is just paying more for the same result.
The math doesn’t change regardless of your site size. The quality argument doesn’t hold. And the “complexity” of managing an API key is genuinely overstated. If you’re still on credits, the only question worth asking is how much you’ve already overspent — and when you’re going to stop.
Stop paying per word. Switch to your own API key.
The NEXU AI Translation Addon connects directly into WPML’s job system — no rebuild required. Install it, paste your API key, and from that point your translation costs drop to AI provider token rates. Your existing setup stays exactly as it is.
Get the NEXU AI Translation Addon
Works with WPML · OpenAI · Claude · Mistral · Grok · WooCommerce · Elementor
This article really got me thinking I'm setting up a multilingual WooCommerce store, and that "bleeds you quietly" line hit hard. How do you even catch those sneaky cost increases before they spiral? Is there a way to set up alerts before credits run out, or does WPML just keep charging until you manually notice?
Finally, real cost transparency. Worth the read.
Hey, this broke down the WPML credit costs clearly
I've been running a small blog alongside my taxi work, and this breakdown really got me thinking. if I'm tweaking posts often to keep them fresh, does that mean WPML will keep charging me for full re translations every single time? Even if I just fix a typo or update a date? That could add up fast