Advanced Custom Fields Multilingual: worth it if WPML is already your stack
- ACF-heavy multilingual sites
- WordPress agencies managing client sites
- ACF Pro projects with repeaters
- Sites using PHP or JSON-registered fields
- You need a standalone translation plugin
- Your site has only simple post content
- You already use Polylang or TranslatePress
- You want to avoid WPML complexity
Advanced Custom Fields Multilingual is a compatibility add-on, not a complete multilingual plugin. It connects Advanced Custom Fields or ACF Pro to WPML so custom-field values, field labels, field groups, options pages, and structured content can be translated without building separate language-specific fields by hand.
That distinction matters. ACFML requires ACF, WPML, and WPML String Translation, and it is included with WPML’s Multilingual CMS and Agency plans rather than sold as a separate product. The current WPML Multilingual CMS plan costs €99 per year, covers three production sites, and includes ACFML alongside WPML’s broader translation tools. If you already have that plan, ACFML is effectively the missing integration layer. If you do not, the real purchase is WPML.
Where ACFML is genuinely strong
The main strength is that it understands ACF’s data model instead of treating custom fields as a pile of generic metadata. Text, WYSIWYG, image, file, gallery, link, relationship, post object, repeater, flexible content, clone, conditional logic, and ACF block fields can be assigned translation preferences. Repeater and flexible-content rows can remain aligned between languages, while the Copy Once option allows a translated version to diverge after the initial copy.
This is particularly useful for agencies building structured pages. A translator can work with the same field layout the editor uses, rather than receiving an opaque list of meta keys. Options pages and field labels are also covered, which helps when a theme stores global contact details, calls to action, or footer content in ACF.
Recent improvements make the developer workflow better. PHP-registered fields and ACF Local JSON fields can now carry a wpml_cf_preferences value, and the preferences can be synced from ACF Tools. A concrete limitation remains: the sync is not automatic in the way many developers expect. After changing local field definitions, you need to trigger the sync, and incorrectly named or duplicated fields may not appear for translation.
Where it is weak or annoying
ACFML inherits WPML’s complexity. You must decide whether each field should be translated, copied, copied once, or ignored, and those choices can be confusing in the WordPress editor. A support discussion specifically describes fields marked “Copy” still appearing as editable in translated screens even though saving them causes the default-language value to overwrite the change. That is a workflow problem, not merely a documentation gap.
Performance can also become an issue on badly optimized ACF builds. WPML support documented one case where translation logic ran more than 8,000 times because the theme made excessive ACF field calls. ACFML has added filters and newer releases improve local-field and frontend performance, but developers may still need to reduce repeated acf_get_field calls or bypass translation logic for fields that do not need it.
How it compares
Compared with Polylang, ACFML offers a more guided, officially documented ACF workflow, but Polylang can be a simpler choice for sites that need straightforward page and post translations. Compared with TranslatePress, ACFML is better suited to structured, developer-built content because it translates field data at the content-model level rather than primarily through a visual frontend interface. Weglot is easier for quickly translating conventional websites, but it is less attractive when custom-field structure, repeaters, and language-specific media need careful editorial control.
Verdict: buy or use ACFML when ACF is central to the site and WPML is already acceptable. Do not choose it as your first multilingual plugin for a simple brochure site; the dependency, configuration work, and occasional performance tuning outweigh the benefit.
Questions people ask
- Is Advanced Custom Fields Multilingual a standalone translation plugin?
- No. ACFML is an add-on for WPML and requires ACF, WPML, and WPML String Translation. It handles multilingual ACF data but does not provide the complete language-management system by itself.
- Does ACFML work with ACF Pro repeaters and flexible content?
- Yes. It supports ACF and ACF Pro field types, including repeaters, flexible content, clone fields, conditional logic, and ACF blocks. Repeater rows can be synchronized across languages or allowed to diverge with the appropriate translation setting.
- Can ACFML translate fields registered in PHP or Local JSON?
- Yes, but developers must define the translation preference with the wpml_cf_preferences setting and sync it through ACF Tools. The field definitions must also be maintained carefully so WPML can identify them consistently.
- Does ACFML slow down WordPress?
- It can on sites that make excessive ACF field calls or scan large sets of local fields repeatedly. Recent releases improve performance, but complex sites may still need code-level optimization and filters to skip translation processing for fields that do not need it.
Get Advanced Custom Fields Multilingual: worth it if WPML is already your stack 2.2.4
Complete package, ready to install, via WorldPressIT.