Back to blog

How to Translate ACF Options Pages With WPML: A Step-by-Step Guide

7 min read
How to Translate ACF Options Pages With WPML: A Step-by-Step Guide

Your footer says “Free shipping over $50”—but only in English. The contact number, site-wide announcement, and call to action sitting in your ACF Options Page can quietly remain untranslated even when every post and page looks perfect. That is where WPML ACF Options Page translation becomes less intuitive than translating ordinary custom fields.

An Options Page does not belong to a single post, so it cannot follow the usual post-by-post translation workflow. Its fields power global details visitors encounter everywhere: header contacts, footer copy, legal notices, banners, and reusable CTAs. A small configuration gap can turn a polished multilingual site into one with mixed-language interface content.

The good news is that these fields can be translated reliably once WPML and ACF are set up to treat them as the site-wide content they are. The key is knowing which settings control the fields, where their translations appear, and why the familiar workflow for post-level ACF data is not enough here.

Before You Start: What You Need to Translate ACF Options Pages

An ACF Options Page can hold the details visitors see everywhere: a footer message, contact link, promotional banner, or site-wide call to action. That is exactly why a missed translation here is so visible. Before configuring wpml acf options page translation, make sure the underlying ACF, WPML, and field setup is sound.

Configure WPML and ACFML for Options Page Translation

Install and activate the required plugins

You need three working components. First, install Advanced Custom Fields or ACF Pro. In most cases, Options Pages are an ACF Pro feature; developers can also register one with custom code. Next, install and activate WPML’s core multilingual components, including WPML Multilingual CMS and String Translation where your setup requires it. Finally, install ACF Multilingual (ACFML), WPML’s companion add-on for handling ACF field translation preferences.

WPML provides the multilingual framework, while ACFML tells it how individual custom fields should behave. Neither replaces the other.

Confirm that your Options Page is registered correctly

In the WordPress admin, confirm that the Options Page appears as its own menu item, often under Settings, Theme Settings, or a custom top-level menu. Open it and verify that its intended field group is visible and editable.

Then check the field group’s location rules. A default ACF Options Page may use a rule such as “Options Page equals Options.” A developer-registered page can have a custom slug, such as theme-settings; the location rule must target that specific page. If the fields do not appear on the correct admin screen, translation settings will not fix the problem.

Decide which global fields should vary by language

Not every global value needs translating. Text fields, WYSIWYG content, button labels, links, image alt text, and language-specific banner images usually need separate values. By contrast, analytics IDs, social profile URLs, legal identifiers, or a universal logo may remain identical.

Make this decision field by field before enabling translation preferences in ACFML. It prevents duplicated maintenance and avoids the common mistake of translating technical settings that should stay consistent across every language.

Configure WPML and ACFML for Options Page Translation

An ACF options page looks global in WordPress, but its content should not be treated as one shared value across every language. The crucial step in wpml acf options page translation is setting a translation preference for each field before translators begin editing.

Set ACF field translation preferences

Open the relevant ACF field group and use ACFML’s translation controls, or review the rules in WPML → Settings → Custom Fields Translation. Assign a behavior deliberately: Translate creates a separate value per language; Copy keeps the source value synchronized; Copy once copies the initial value but permits later edits; and Don’t translate excludes the field from WPML’s workflow. Avoid leaving important fields on an inherited default—especially when an options page mixes editorial text with technical settings.

Use the right translation preference for each field type

  • Set headings, button labels, notices, and WYSIWYG content to Translate.
  • Set true/false toggles, color choices, spacing values, and layout controls to Copy; a translated footer should not unexpectedly lose its CTA because one locale changed a switch.
  • For URLs, use Translate when each market has its own landing page or legal document. Use Copy for a universal external destination.
  • For media, decide whether locales need different assets or only translated attachment metadata. Language-specific banners need translation; a single logo usually needs copying.

Make the options page appear in WPML’s translation workflow

Save the field group, then save the options page with source-language values populated. ACFML can only register fields that WordPress has actually stored. In WPML, look in String Translation for the options-page or admin_texts entries, then search for the field label or saved value. If a newly added field is missing, save the field group and options page again, refresh the String Translation screen, and rescan or reload the relevant strings. This small refresh step prevents a common mistake: assuming WPML is sharing values when it simply has not detected the new field yet.

Translate the Content on Your ACF Options Page

Add the source-language values first

An Options Page is often where a site’s most visible details live: the phone number in the header, a footer disclaimer, a promotional banner, or a global call to action. Complete and save these fields in WPML’s default language before creating translations. A finished source gives WPML and ACF Multilingual a reliable record to send into the translation editor, rather than leaving translators to interpret empty or partial fields.

Open and complete each language translation

Open the target language from WPML’s Translation Management screen or the relevant ACFML translation controls. Translate fields configured for translation, then mark the job complete only after reviewing every value. Do not overwrite fields set to Copy or Copy once; those settings exist to preserve a shared value, such as a tracking ID, layout choice, or non-localized configuration. If you use LATW AI Translator for WPML, remember that it works inside an active WPML installation and can accelerate the translation workflow, but field translation preferences still determine what should change.

Handle links, media, and reusable global content

Check every link manually. A translated button should point to the matching translated page, not back to the default-language URL. Select translated images where the creative contains text or is culturally specific, and confirm alt text is localized. For repeated footer text, cookie notices, and banners, keep terminology consistent; “Contact us” should not become three different phrases across the same site.

Test the translated options on the front end

Finish wpml acf options page translation with a browser-level review. Switch languages and inspect every template that retrieves option values: headers, footers, pop-ups, custom Gutenberg blocks, WooCommerce notices, and mobile menus. Test links, images, and dynamic labels in each language. One correct translation record is not enough if a template still loads the default value.

Fix Common WPML ACF Options Page Translation Problems

The translated field is missing from the translation editor

A missing field is usually a configuration issue, not a failed translation. In ACFML, check that the field’s translation preference is set to Translate rather than Copy, Copy once, or Don’t translate. Then save the source-language options page again; WPML often needs that save event to detect newly eligible values. Also update WPML, ACF, and ACFML, since older combinations can miss newer field types. Finally, confirm the field group’s location rule targets the intended Options Page. A field group assigned to a different admin page cannot appear in this page’s translation job.

The front end still shows the default-language value

When the editor contains the translation but the site does not, inspect the template call. get_field() and get_sub_field() must request the same options-page context used to store the value, such as the correct options-page slug rather than a generic or outdated option reference. Test while viewing the target language, then clear page cache, object cache, and any CDN cache. This is a common wpml acf options page translation trap: the translated value exists, but cached markup keeps serving yesterday’s default-language output.

A field should be shared, but WPML creates separate values

Not every option needs localization. Sitewide IDs, tracking codes, shared phone numbers, and reusable configuration values generally belong on Copy; values that should initially match but may later diverge fit Copy once. Use Translate only where each language genuinely needs its own text or selection. Be careful changing this on a live, already translated site: switching preferences can overwrite, expose, or stop synchronizing existing values. Review the current source and translated data before saving the new rule.

Speed up large-scale WPML translations with AI

For established WPML sites, LATW AI Translator for WPML can translate ACF fields within WPML’s existing content workflow. It is an add-on, not a standalone multilingual plugin, and requires WPML. Its bring-your-own-key model sends content directly from WordPress to your chosen AI or machine-translation provider, with glossary support for consistent terminology. Automate the repetitive work, but always review global options-page copy before publishing: one incorrect label can appear across every page of a site.

Make Global Content Multilingual Without Making It Fragile

A reliable WPML ACF Options Page translation workflow comes down to discipline: register and populate the options page correctly, choose field translation preferences deliberately, create each language version in WPML, and test every template where those global values appear. The field settings are especially important—they determine which values remain shared and stable across the site and which ones adapt for each visitor’s language.

Before publishing, review the site as each target-language visitor would: headers, footers, contact details, calls to action, and any reusable blocks powered by ACF. Once those global elements are verified, you can localize confidently without turning a single options page into a source of inconsistent sitewide content. Translate what the visitor should experience; protect what the site must keep consistent.