How to Translate ACF Repeater and Flexible Content Fields in WPML

A repeater field can look perfectly organized in WordPress—until you translate it and discover missing rows, duplicated values, or layouts that refuse to appear in the secondary language. The problem is that wpml acf repeater translation is not like translating a single headline: every nested row, subfield, and Flexible Content layout has its own rules.

That complexity is easy to underestimate when the original page works flawlessly. A field-group setting that seems harmless can decide whether WPML copies a structure, translates its text, or leaves it empty altogether. Add existing content, changing layouts, and different translation preferences into the mix, and a small configuration mismatch can turn into hours of guessing.

The good news is that these issues are usually predictable once you know where the field structure and translation workflow meet. The fix is rarely “translate it again”—it is making sure WPML and ACF are interpreting the same content structure from the start.

Before You Start: What You Need for WPML ACF Repeater Translation

A repeater field may look like one editor block, but WPML treats its rows and subfields as separate translation decisions. Miss one setting and you can end up with blank cards, mixed-language sections, or layouts that no longer match.

Install and activate the required WPML components

For wpml acf repeater translation, install and activate WPML Multilingual CMS, Advanced Custom Fields, and WPML’s ACF Multilingual integration. ACF Multilingual is the bridge that lets WPML understand ACF field groups and their translation preferences. Add WPML String Translation only when you also need registered theme or plugin strings translated; it is not responsible for post-field values. Configure every target language in WPML before creating translations. Then back up the database and update WPML, ACF, and ACF Multilingual. These settings affect stored content, so production is not the place for casual experiments.

Understand what WPML translates in repeater and flexible content fields

Keep labels and values separate. A label such as Button text guides editors; a value such as Book a demo is visitor-facing content. In a repeater, every row and nested subfield needs the right preference: translate text, copy shared data, or copy once and then translate. Flexible Content layouts add another layer, often combining headings and rich text with IDs, toggles, images, and structural settings that should stay synchronized. Set preferences before translating the parent post, or WPML may copy a layout while leaving its meaningful text untranslated.

Step 1: Configure Translation Preferences in Your ACF Field Group

Set the repeater or flexible content parent field to Copy

The parent field is the blueprint, not the text visitors read. Set each ACF repeater or flexible content parent field to Copy so WPML carries its rows, layouts, and order into the translated post. Without that structure, the translation editor may have nothing useful to display—or worse, an editor may need to rebuild a 12-row page section by hand. This single setting is the foundation of reliable wpml acf repeater translation.

Choose Translate, Copy, or Copy Once for every subfield

Do not apply one rule to every nested field. The correct preference depends on what the field represents:

• Translate: headings, body copy, button labels, testimonials, and any text that should read naturally in the target language.
• Copy: CSS classes, layout choices, image IDs when the same asset is used, toggles, URLs that must remain universal, and other non-linguistic values.
• Copy Once: a useful starting duplicate for content that will later diverge by language, such as a local contact detail or market-specific call to action.

Save the field group and update an affected source post

Changing preferences does not always rewrite an existing translation job. Save the ACF field group, then update the source-language post to send WPML the revised configuration. Refresh the translation job; if the expected fields still do not appear, cancel and recreate it. Check this before translating dozens of posts—fixing the setup early is far cheaper than repairing incomplete translations later.

Step 2: Translate the Post and Its Nested ACF Content in WPML

Create a translation job from the original post

A correct field setup can still fail at the last mile: the translated post must be created through WPML, not as an unrelated draft. Open the original post, use the language panel to add or update the target language, and send the item to WPML’s Translation Editor. WPML then keeps the new version linked to its source through its standard multilingual content relationship, while passing the configured ACF values into the translation job.

Translate each text value without changing the layout structure

In a wpml acf repeater translation workflow, repeater rows and Flexible Content layouts usually appear as a sequence of translatable segments. Translate the copy inside each row, but do not try to rebuild, delete, or reorder the structure in the editor. Treat URLs, shortcodes, HTML tags, placeholders, and dynamic tokens such as %s as protected unless they genuinely need localization. A translated button label may change; its tracking URL usually should not.

Review the translated page for rows, layouts, and front-end output

• Confirm that every repeater row is present and that Flexible Content layouts remain in the original order.
• Check that translated text appears in the correct cards, accordions, tabs, or sections.
• Verify shared fields remain unchanged where the ACF configuration intended them to be copied.
• Test buttons and links in the target language, including mobile layouts and any conditional content.

Finally, view the page on the front end rather than trusting the editor alone. Nested ACF content can look complete in a translation job while a template condition, missing field value, or broken link reveals the real issue only after rendering.

Fix Common WPML ACF Repeater Translation Problems

Most wpml acf repeater translation failures are configuration mismatches, not corrupted content. The key is to diagnose the field structure before rebuilding rows by hand.

Why are repeater fields missing from the WPML translation editor?

A missing repeater usually means its parent field, or a nested child field, is set to Do not translate. Check the ACF Multilingual translation preferences, save the field group, then update the source post. Finally, refresh or recreate the translation job: an existing job may still reflect the old settings.

Why are rows missing, duplicated, or out of sync?

WPML needs to copy the repeater or flexible-content structure while translating only the child values that actually vary by language. Do not independently add, remove, or reorder rows in the translated post unless your selected workflow explicitly supports it. Otherwise, WPML can lose the connection between matching rows.

How should you handle images, links, and relationship fields?

Non-text fields need deliberate rules. Copy shared images when the same asset applies everywhere; use WPML Media Translation when an image needs localized alt text, captions, or a replacement. For relationship and post-object fields, confirm that the selected item has a valid translation and that the target-language link resolves correctly.

When should you update, test, or contact support?

First confirm that WPML, ACF, and ACF Multilingual are current and compatible. Reproduce the problem on staging with one small field group. If support is needed, provide the field-group export, screenshots of translation preferences, and a minimal example post. That evidence separates a plugin conflict from an outdated translation job quickly.

Speed Up WPML Content Translation With AI After Your Fields Are Configured

Use a WPML add-on for scalable, bring-your-own-key translation

Once your field groups, translation preferences, and layouts are working, the hard structural part of wpml acf repeater translation is behind you. The remaining problem is volume. A landing page with six reusable ACF sections may contain dozens of headings, descriptions, calls to action, and metadata fields—and translating each one manually quickly becomes repetitive.

For WPML users at that stage, LATW AI Translator for WPML is a practical add-on for speeding up the content workflow. It requires an active WPML installation and works inside WPML’s Translation Management process; it does not replace WPML or provide the multilingual framework, URL structure, or language switcher itself.

Instead, it translates page and post content, metadata, SEO fields, and configured ACF fields through the site owner’s chosen AI or machine-translation provider. Content goes directly from WordPress to that provider’s API, rather than through intermediary plugin servers. Bring-your-own-key billing also means you pay the provider’s underlying usage cost, not a separate translation-credit markup.

The useful controls are not just about speed. A glossary can keep a product name or CTA consistent across every repeated section, while website context helps the model distinguish a terse button label from a marketing headline. After confirming that WPML maps your repeater and Flexible Content fields correctly, you can translate at scale and reserve human review for the pages that genuinely need editorial judgment.

A Reliable Workflow for Complex ACF Layouts

For dependable WPML ACF repeater translation, treat the field group as the blueprint: copy the repeater or flexible-content structure, decide which nested fields need independent translation and which should stay synchronized, then update the original post before creating or refreshing its WPML translation. That order gives WPML a current translation package and prevents translators from working against an outdated field configuration.

When something appears missing, duplicated, or locked, look first at the field settings and the status of the translation job—not the content itself. Before applying the setup across a large site, test one representative layout on staging and translate it end to end. A small, verified configuration is far easier to scale than a site-wide repair.