Skip to content
AI Translate for WPML Get the plugin

Built for WPML + ACF

Translate your entire WordPress site for less than 1 €*

Your posts, your custom post types and — the part everyone else skips — every ACF field inside them, repeaters and flexible content included. You bring your own OpenAI key, so you pay cents instead of translation credits.

Start translating free See how it works

* About 500,000 words for 1 € with gpt-4o-mini at OpenAI’s current rates. A typical corporate site runs 15,000–40,000 words.

How it connects

Your fields leave as text and come back as a WPML translation

Nothing is duplicated and nothing is guessed. The plugin reads the structure you already have, sends only the text, and writes the answer back where WPML expects to find it.

  1. 1

    Your originals

    Every post and custom post type WPML marks as translatable, with the fields that actually hold text — walking ACF to any depth, repeaters and flexible content included.

    • Title
    • Slug
    • Content
    • ACF fields
    • Taxonomy terms Pro
    • ACF options Pro
    • Strings Pro
  2. 2

    The plugin

    Only text leaves your site. Images, URLs, numbers and dates are copied exactly as they are. Every field is hashed, so editing one paragraph re-sends one paragraph.

  3. 3

    OpenAI, with your key

    One batched request using structured outputs: the model can only return the same keys it received, so it cannot reshape your field structure or invent new fields.

And back into WPML. The translation is created in the same translation group as the original, with the right language and marked as complete — not a duplicate sitting outside WPML.

The difference

The fields nobody else translates

On a site built with ACF, the real content is not in the editor. It is in repeaters, flexible content and nested groups. Most WPML automation copies those across verbatim and leaves them in the original language.

About us page

  • hero_title text Translated
  • hero_image image Copied
  • credits repeater
  • credits_0_role text Translated
  • credits_0_name text Excluded
  • credits_1_role text Translated
  • cta_link link Copied

The plugin walks that structure to any depth. Proper names stay put because you excluded them by pattern — here, credits_*_name.

Scope

What it touches, and what it deliberately doesn’t

Translated

  • Title, slug, content and excerpt
  • ACF text, textarea and wysiwyg fields, at any depth
  • Visible text inside HTML, plus alt and title
  • Taxonomy terms, ACF options and WPML strings Pro

Copied, never touched

  • Images, galleries, files and relational fields
  • URLs, emails, numbers, dates and booleans
  • Shortcodes and placeholders like {{name}}
  • Translations you made by hand — shown as External and skipped

It does not reach inside the block JSON of Gutenberg or Elementor. This is a plugin for content that lives in fields, which is where ACF sites keep it.

The maths

You already pay for WPML. This is about who does the translating.

WPML is required either way and this plugin does not replace it. What changes is where the automatic translation comes from — and what that part costs.

WPML’s own AI credits

22,500 words included

That is what the Multilingual CMS plan (99 €/year) includes. The Agency plan (199 €/year) includes 45,000. Past that you buy more.

A typical corporate site is 15,000–40,000 words — per language.

Your own OpenAI key

~3 cents for the same 22,500

You pay OpenAI directly for what you translate. No credits, no monthly allowance to run out of, no per-word fee to anyone.

Measured, not estimated: translating this site into three languages cost $0.02 — roughly 500,000 words per euro with gpt-4o-mini.

To be fair about it: WPML’s credits come with their own translation editor, glossary and review workflow, and you may well want those. The figures above are from WPML’s pricing page and are about volume, not about which tool you prefer.

Pricing

Free for the part that matters most

Free

0 €

  • Posts and custom post types

  • Title, slug, content and excerpt

  • Every ACF text field, at any depth

  • No limit on languages — as many as WPML has

  • No limit on how much you translate

Get it from WordPress.org

Pro

from 49,99 € per year

  • Everything in Free

  • Taxonomy terms, with their own ACF fields

  • ACF options pages, one set per language

  • WPML String Translation strings

  • Translate from a language other than the WPML default

  • Fix an item written in the wrong language

Secure checkout by Freemius. 14-day refund policy. The free version stays free — you only need this for taxonomies, ACF options and strings.

Requires WPML Multilingual CMS. ACF is optional — without it the plugin still translates titles, slugs, content and excerpts. You need an OpenAI API key, which you pay for directly.

Questions

Before you install it

Is there a limit on how many languages I can translate into?

No, and not in the free version either. You translate into as many languages as WPML has set up, as many times as you like. What you pay is what OpenAI charges you for the text.

Do I need ACF?

No. WPML is the only hard requirement. Without ACF the plugin translates titles, slugs, content and excerpts. ACF is where it goes further than other tools, not a condition for it to work.

Will it overwrite translations I made by hand?

No. Anything the plugin did not create is shown as External and skipped. You have to force it explicitly, one by one.

Does it re-translate everything when I edit a page?

No. It stores a hash per field and only sends the ones that actually changed, so fixing one paragraph costs one paragraph.

Where does my content go?

To OpenAI, with your own API key, and nowhere else. Only text fields are sent — images, URLs and numbers never leave your site. The plugin author receives no data.

The documentation covers the rest: statuses, batches, exclusion patterns and what each Pro tab does.