5 Proven Ways to Translate ACF Custom Fields with Polylang

Learn how to translate ACF custom fields with Polylang in WordPress. Follow five practical steps to handle multilingual field values, preserve structured data and troubleshoot common issues.
Dragwyb Dragwyb 8 min read
Translate ACF custom fields with Polylang in WordPress, including text, repeater and flexible content fields.
Learn how to translate ACF text, repeater and flexible content fields across languages with Polylang in WordPress.

To translate ACF custom fields with Polylang, first decide which values should be translated and which should be shared across languages. Advanced Custom Fields (ACF) stores structured data separately from the main post content, so a translated post can still display source-language field values unless your workflow handles them. In this guide, you will learn how to translate ACF custom fields with Polylang, preserve structured values and verify the translated content on your WordPress site.

If your website uses Polylang, the right approach depends on the purpose of each field and how your translated posts are connected. This guide explains how to plan and check an ACF translation workflow without assuming that every field should be translated in the same way.

Why translate ACF custom fields with Polylang?

ACF saves extra information separately from the main post title and content. For example, a product detail, team bio, location description or button label may be stored in a custom field. When you translate a post, these field values may not change with it. That is why you should check your ACF fields when making a page in another language.

For example, imagine a service page with these fields:

  • Service title and short description
  • Benefits displayed in a repeater
  • A button label and destination URL
  • An internal reference or numeric setting
  • An image used in the page layout

Text that visitors can read may need translation. A number, image or internal reference may need to stay the same. Before you translate ACF custom fields with Polylang, check what each field does so you do not change something the website needs.

Know which ACF fields to translate and which to copy

Not every ACF field needs translation. Some fields contain words that change by language, while others hold data that should stay the same. Use this simple guide to decide what to do:

Field purposeTypical handlingExample
Visitor-facing textTranslate the valueHeading, description, button label
Structured text collectionsTranslate each text value while preserving the structureRepeater labels or feature descriptions
Shared media or referencesUsually copy or keep the reference, depending on the siteImage, relationship or post reference
Numeric or technical settingsUsually preserve the valueSort order, quantity or internal flag
Language-specific URLs or labelsReview and set per languageButton destination or localized resource link

These are common examples, not fixed rules. Your theme or plugin may use a field in a different way. Check the field settings and view the page on your website before translating all your content.

Set up ACF and Polylang before you start

Before you translate ACF custom fields with Polylang, check these basic settings. This quick check can help you avoid missing values and broken layouts:

  • Install and configure Polylang, then add the languages your site needs.
  • Confirm that the source post has the correct language assigned.
  • Create or connect the corresponding translated post using your normal Polylang workflow.
  • Review the ACF field groups attached to the post type.
  • Identify which fields contain visitor-facing text and which contain shared data.
  • Take a backup or test on a staging copy before processing many posts.

If you use custom post types, make sure they are enabled for translation in Polylang. Also check that the right field group is shown on the translated post. If a field is missing on the page, check the post, field group and page template.

How to Translate ACF Custom Fields with Polylang: 5 Practical Steps

1. Identify the fields that contain text

Open the ACF field group and look at the fields used on your page. Note each field name and type, and check whether visitors can see its value. If you use repeater or flexible content fields, make sure their rows and layouts stay in place when you translate them. This is an important first step when you translate ACF custom fields with Polylang.

2. Decide how each field should behave

For each field, decide whether to translate it, copy it from the original language or set a different value for each language. Do not translate every value just because it appears next to text. A post ID or number may be needed by your website, and changing it could cause a link or page feature to stop working. These choices help you translate ACF custom fields with Polylang without changing data your site depends on.

3. Create or open the translated post

Use Polylang to create or open the translated post. Check that it has the right language and is linked to the correct original post. Once this is set, you can work on the ACF fields for that language.

4. Translate the appropriate field values

Translate the text that people see on the page. Keep any needed HTML, shortcodes, links and placeholders in place. If a field contains HTML, check it in the editor and on the live page to make sure the layout still looks right. When you translate ACF custom fields with Polylang, keeping this structure in place helps your page work as expected.

5. Check the translated page on the frontend

Open the translated page and check the parts that use ACF fields. Make sure headings and descriptions use the right language, images appear, links go to the right place, and repeater rows are still in the right order. This final check helps confirm that your ACF fields were translated correctly with Polylang.

Common ACF translation problems and simple fixes

A custom field is empty on the translated page

Open the translated post and see if the field has a value. Check that the field group is used for that post type and that your page template reads the correct field name. Also make sure the two posts are linked in Polylang.

The field value is copied but not translated

Some tools copy ACF values when they create a translated post. This is useful for values that should stay the same, but text shown to visitors may still need translation. Check how your tool handles each field type.

A repeater or flexible layout looks different

Make sure the translated field still has the same rows, subfields and layout. Do not translate the whole field as one block of text if that could change how your page displays it.

The translated page displays the wrong link or image

Check whether the field should use the same image, a different image for each language or a link to a translated post. Then test the page to make sure it shows the right image or opens the right link.

Can AI help translate ACF fields?

AI translation can save time when you have lots of ACF fields to translate. But it should only translate text that people read. Numbers, post IDs, URLs and image references may need to stay as they are. When you translate ACF custom fields with Polylang, check what each field contains before sending it for translation.

AI can help translate ACF custom fields with Polylang, but the tool must support the ACF field types used on your website. TranslateSense is an AI translation addon for Polylang. Before using it, check the latest documentation to see which ACF fields are supported. Try a few fields first, keep numbers and links safe, and check the translated page before translating more posts.

For plugin-specific setup, visit the TranslateSense for Polylang product page and the TranslateSense getting started guide. For the underlying tools, refer to the official Advanced Custom Fields documentation and Polylang documentation.

ACF and Polylang translation checklist

  • Source and translated posts have the correct language assignments.
  • Each translated post is connected to its source-language post.
  • Visitor-facing text fields contain the intended translated values.
  • Technical values and references have not been changed accidentally.
  • Repeater and flexible content structures remain valid.
  • Images, relationships and links point to the intended resources.
  • The translated page has been checked on desktop and mobile.
  • A backup and review process is in place before bulk translation.

Frequently asked questions

Does Polylang automatically translate ACF fields?

Polylang manages multilingual content and language relationships. The way ACF field values are copied or translated depends on your field setup and the translation workflow you use. Check the behavior of your installed plugins and test the fields used by your templates.

Should every ACF field be translated?

No. Translate visitor-facing text where appropriate. Numeric settings, identifiers, shared media references and technical values may need to remain unchanged or be managed separately for each language.

Can you translate ACF repeater fields with Polylang?

They can be part of a multilingual workflow, but the translated data must preserve the repeater’s rows and subfield structure. Test the specific field configuration and translation tool you use.

Can AI translate ACF custom fields with Polylang?

AI can translate text stored in custom fields when the translation workflow supports those fields. Always verify which field types are supported and exclude values that should not be translated.

Final thoughts

Good ACF translation starts with knowing what each field does. Use Polylang to connect your posts in different languages, translate the text that visitors read and keep shared values unchanged. If you use AI, test a few fields first and check the results before translating the rest of your website. With a clear process, you can translate ACF custom fields with Polylang and keep your pages working well.

Dragwyb
Written by

Dragwyb

More practical WordPress tutorials and product guides from the Dragwyb team.