WPML ACF Link Field Not Translatable: Fixes and Workarounds for Link and Image Fields

Your link field is visible in ACF, saved on the original page, and perhaps even sitting inside a carefully built Repeater layout—yet WPML’s Advanced Translation Editor acts as if it does not exist. Or worse, the field appears translated in the editor but the front end still serves the original URL, image, or label. If you are searching for wpml acf link field not translatable, the problem is usually not the link itself.

The frustrating part is that ACF Link and Image fields can fail for reasons that are easy to miss: a field group configured with the wrong translation preference, a return format WPML cannot handle as expected, or translation data created before the field was changed. Add Repeaters and Flexible Content into the mix, and a small setting can leave important content silently untranslated.

Before rebuilding a layout or manually editing every language version, it is worth pinpointing where the translation chain broke. The right adjustment can make those missing fields show up where they should—and keep them working when your content changes next.

Why Is My WPML ACF Link Field Not Translatable?

A link can look like one field in the WordPress editor, but WPML does not see it that way. An ACF Link field is a compound value: it stores a URL, a visible title, and often a target such as _blank. WPML handles ACF data as post meta, so a “wpml acf link field not translatable” issue is usually a configuration or field-registration problem—not a failure of the translation editor itself.

Check whether the problem affects the field, the repeater, or the translation editor

First, identify where the chain breaks. If the Link field is missing from WPML’s Advanced Translation Editor (ATE), WPML may not recognize the field or its ACF field group configuration. If it appears but is locked, it is probably set to be copied from the original language. If you translate the URL and label in ATE, save the job, and the front end still shows the source-language link, the issue is more likely in how the theme retrieves the field, how the repeater data was copied, or whether the translated post is actually being displayed.

These are three different problems with three different fixes. Changing translation preferences will not help a field that never reaches ATE; editing ATE will not help a field that the template hard-codes from the original post.

Understand Copy, Copy Once, Translate, and Don’t Translate settings

WPML custom-field preferences determine what happens to the meta value on translated posts. Copy permanently mirrors the original value, which is useful for shared IDs or layout controls but wrong for a language-specific destination URL or link title. Copy Once copies the initial value, then allows the translation to diverge. Translate sends the value into the translation workflow and is usually the right choice when both the link label and URL can vary by language. Don’t Translate excludes the field altogether.

For example, a French CTA may need “Voir les tarifs” and a /fr/pricing/ URL. A permanent Copy setting guarantees that it stays English.

Know the extra complications of Repeaters, Flexible Content, and cloned fields

Repeaters and Flexible Content layouts are not single values. ACF stores a parent count plus separate meta keys for every row and child field. WPML must recognize both the structure and the nested Link field before ATE can reliably expose the values.

Problems often appear after a field name is changed, a new repeater subfield is added, or a cloned field is reused under a different layout. Existing translation jobs may retain the old field map, while new child keys are not configured as translatable. Re-save the field group, confirm the relevant parent and child fields are registered in WPML, then update or recreate the translation job so ATE receives the current structure.

How to Fix an ACF Link or Image Field That WPML Will Not Translate

Update the ACF field group translation preferences

A field can appear perfectly in WordPress yet be invisible to WPML’s translation workflow. That is usually a configuration problem, not a broken link. In WPML’s Multilingual Content Setup, or the ACFML settings for the relevant field group, review the translation preference for every field involved.

Set a link label, external URL, or any destination that genuinely differs by language to Translate. Use Copy only when the value must stay identical, such as a shared tracking parameter or a universal PDF. For internal destinations, WPML needs enough information to resolve the translated page rather than blindly copying the original-language URL. The same principle applies to image fields: translate media-related values when each language needs its own attachment text or image selection.

Use a translation-friendly field structure when the Link field is unreliable

The wpml acf link field not translatable issue is especially common inside repeater rows, where one compound Link field contains a title, URL, and target setting. Splitting that field is often the cleaner fix.

• Link label: a text field set to Translate.
• Internal destination: a Page Link, Relationship, or Post Object field configured to connect to the translated post.
• External URL: a separate URL field set to Translate when needed.
• Open in new tab: a true/false field, usually Copy.

This structure is less elegant in the editor, but far more predictable. It is particularly useful when a repeater contains several calls to action that must point to different translated pages.

Re-save the original post and update the translation in ATE

Changing field preferences does not reliably rewrite an existing translation job. Save the original post again, then check whether WPML shows a translation update indicator. Open the translation in Advanced Translation Editor, confirm the newly available custom-field segments appear, and complete every segment before finishing the job.

Finally, verify that WPML marks the translated post as complete. Leaving one segment unfinished can make a field look untranslated even when the configuration is now correct.

Test the rendered link and image data on the translated page

Do not stop at the editor. On the translated front-end page, check the button label, final URL, target attribute, selected image attachment, alt text, caption, and responsive image output. Clear WordPress, plugin, CDN, and browser caches, then test once while logged in and once in a private logged-out window. If both views render the intended language-specific data, the fix has actually reached visitors.

What to Do When WPML Still Does Not Pick Up the Field

Review the ACF, WPML, and ACFML integration versions

A field can be configured perfectly and still fail because the translation stack is out of step. This is especially common with repeater subfields, nested link fields, and workflows that use WPML’s Advanced Translation Editor. WPML, Advanced Custom Fields, and the WPML ACF integration component all evolve independently; a compatibility fix in one release may not exist in an older installation.

Update the relevant plugins on a staging copy first, then confirm that the ACF Multilingual integration is installed, active, and compatible with your current WPML and ACF versions. Retest with one simple page after updating. Do not assume a single setting will resolve every wpml acf link field not translatable report: custom field structures and editor configurations can change the result.

Inspect custom template code and field return formats

Sometimes WPML has translated the value, but the theme is rendering the wrong one. A template may directly query the original post ID, hard-code a destination URL, or run get_field() outside the active language context. In each case, the translation editor can look correct while visitors still see the source-language link or image.

Check the template code that outputs the field, not just the field group settings. For an ACF Link field, verify its configured return format and what the template expects. A link configured to return a URL will not behave like an array containing url, title, and target. Likewise, a post ID return value requires code that resolves that post in the current language. Image fields have the same trap: URL, ID, and array returns are not interchangeable.

Create a minimal reproduction before contacting support

When normal configuration changes fail, reduce the problem until it is impossible to misread. A clean reproduction saves days of back-and-forth and gives WPML support something they can actually test. The WPML support discussion about a link inside an ACF repeater field illustrates why the exact field structure and editor behavior matter more than a broad description of “links not translating.”

• A fresh test page with one repeater row and one affected field
• A field-group export or clear screenshots of the ACF settings
• The expected translation and the actual front-end or editor output
• Your WPML custom-field translation settings
• Versions of WordPress, ACF, WPML, ACF Multilingual, and the active theme

Also state whether the issue occurs in the Advanced Translation Editor, on the front end, or both. That distinction quickly separates an integration problem from a rendering problem.

Get the field setup right before translating again

When a WPML ACF Link field is not translatable, the issue is usually structural rather than editorial: the field’s translation preference, its configuration inside a repeater or flexible layout, or an older translation job still carrying outdated field data. Correct those settings first, update the original content, and create or refresh the translation job so WPML can expose the link URL, label, target, and related image data as expected. Once the configuration is sound, translations become repeatable instead of a series of one-off fixes.

If you already use WPML and want to make that workflow faster after resolving the ACF setup, LATW AI Translator for WPML can add bring-your-own-key AI translation directly to WPML’s existing translation process at raw provider cost. It requires WPML, does not replace it, and cannot repair ACF field registration or translation preferences—but with those foundations in place, it can help you translate content more efficiently without relying on expensive credit-based automation. Fix the structure once, then let every future translation follow it.