WPML Advanced Custom Fields Multilingual Addon
Antivirus scan
Powered by ClamAV
✅ Verified clean
This product file has passed our security filters.
Want to run a fresh ClamAV scan right now? Takes a few seconds and shows scanner version, signature DB and live result.
This can take 5 to 30 seconds.
Clean file Threat detected
No threats detected in this file.
- File
- Size
- Scanned
- ClamAV
- Signature database
⚡ Powered by ClamAV
Scan could not be completed
Report product
If you detected an issue (broken file, malware, inappropriate content, etc.) let us know and we'll review it ASAP.
Sign in to report
About WPML Advanced Custom Fields Multilingual Addon
On a site built with ACF, translating starts by deciding what not to translate
A property, product or professional listing built with Advanced Custom Fields has twenty fields. The title and the description have to be translated. But the price, the reference, the phone number, the photo gallery or the map coordinates are the same in every language, and if every translator touches them, they end up being different.
On an ACF site, most fields are not translated: they are copied. And choosing wrongly which is which is what makes the version in another language show an old price or a photo that is no longer there. ACF Multilingual, the WPML add-on known as ACFML, is there precisely to make that decision once: by field type in the recommended modes, or field by field in Expert mode.
Three ways to handle a field group
- Same content in every language, translated: the text is translated and the layout and settings stay the same. It is the usual setting and supports automatic translation.
- Each language with its own content: fields start as a copy of the original and then each language goes its own way. They are not synced or translated automatically.
- Expert: you set each field's preference by hand. It is not recommended for new groups.
Translate, copy, copy once or start blank
Every field that stores a value has one of four preferences:
- Translate: each visitor sees the value in their own language.
- Copy: every language shows the same as the original and the field is locked in translations. For prices, references or phone numbers.
- Copy once: the value starts as a copy and is then edited in each language.
- Don't translate: the translation starts without that value and is filled in by hand.
Tabs, accordions, messages and separators store no value, so they have no preference.
Relationships, options pages and ACF blocks
ACFML covers text, image, gallery, choice, map and date fields, containers such as Repeater, Flexible Content and Clone, and relational fields. Since ACF 6.2 relationships can be bidirectional, and ACFML keeps each pair correct in every language.
Options pages are translated as their own object, separate from posts. And ACF blocks store their values inside the post content, so only the fields set to translate are sent for translation.
Labels, fields in code and repeaters: where ACFML needs attention
Field labels do not travel with the post. A post's translation does not include the labels or the choice values, which are translated separately. If they are forgotten, the visitor sees the form in the original language.
Fields registered in PHP or local JSON ignore the panel: the preference is written in the field definition with the wpml_cf_preferences key.
In expert mode, repeater rows can fall out of order between languages, and there is a box to sync them. And if the field that controls a conditional logic rule is copied or not translated, the condition follows the original language value.
The four plugins required, and the alternative without WPML
ACFML does not translate anything on its own. It needs Advanced Custom Fields or ACF Pro, WPML and WPML String Translation, plus ACFML itself.
- Install and activate all four.
- Go through each field group and choose one of the three modes.
- If a text field holds data that must be the same in every language, such as a reference or a phone number, switch that group to Expert and set it to copy.
- Translate the field labels separately and check one post in each language.
If you would rather not use WPML, Polylang Pro integrates ACF Pro with its own set of per field options, including one that syncs the value across all languages, and creates one post per language paired with the original.
Modes, labels, options and automatic translation
Does it work with free ACF?
Yes, with Advanced Custom Fields or with ACF Pro.
Can fields be translated with automatic translation?
Yes with the same content translated mode. With the own content per language mode, no.
Why are the labels still in the original language?
Because they are not part of the post's translation: they are translated separately.
Does it translate options pages?
Yes, as their own object, separate from posts.
Does it work for fields defined in code?
Yes, but the preference goes in the definition with wpml_cf_preferences.
Topics
Version history
-
v
5.2.0 Current 21 Oct 2026
-
v
5.1.0 1 Oct 2026
-
v
5.0.0 23 Sep 2026
-
v
2.2.4 22 Apr 2026
Customer reviews
Sign in to leave a review. Only people who have the product can review it.
No reviews for this product yet.
Frequently asked questions
-
GPL (General Public License) is the license under which WordPress and most premium plugins/themes are distributed. It grants you the right to use, modify and redistribute the software in as many projects as you want, with no domain restrictions.
-
Yes. With membership you get automatic updates via our GPLClub Updater plugin (installed on your WP, detects new versions and applies them). With individual purchase, you get one year of manual updates from your account.
-
Depends on the plan. Monthly: 3 domains. Semi-annual: 7. Annual and Lifetime: 15. Individual purchase: 1 domain.
-
GPLClub offers its own support for installation, configuration and compatibility. For direct support from the original author (feature requests, product-specific bugs), a license purchased from the author is required.
