WPML

Before You Start

Install and activate these plugins:

Build the form in Contact Form 7 in your site’s source language (every form-tag, the Mail and Mail (2) templates, every entry on the Messages tab, and any Additional Settings) before sending the form for translation. You can edit the form later and re-send it for translation if anything changes.

Translate Everything Automatically Handles This for You

If your site has Translate Everything Automatically turned on, you don’t need to send the form for translation manually. WPML picks up new and updated forms alongside the rest of your content and translates them in the background. The page-insertion step below still applies, but the send the form for translation step is automatic. The rest of this page describes the manual path for sites on Translate Some: You Choose What to Translate (or for forms you want to translate ahead of the automatic queue).

Send the Form for Translation

  1. Open WPMLTranslationsDashboard.
  2. Expand the Contact Forms section.
  3. Tick the form you want to translate.
  4. Choose a translation method: PTC (recommended), your translator, or Translate myself.
  5. Click Translate.

The form template, the subject and body of Mail and Mail (2), and the Messages tab all come into the same translation job. Translators see them as labelled rows in the Advanced Translation Editor.

For form-tags with quoted texts, like choices, placeholders, and button labels, the job contains only the quoted texts. The form-tag type, name, and options stay out of the job. So a translation can’t break these form-tags.

You can edit the source form while its translation is in progress. Each translated text stays on its own form-tag.

Insert the Form Into Your Translated Pages

Contact Form 7 sits inside a page or post through the [contact-form-7] shortcode, usually generated by the Contact admin screen as [contact-form-7 id="123" title="My Form"]. The multilingual insertion rule:

Use the same shortcode on every language version of the page. Don’t create a separate form per language.

The flow:

  1. Build the form once in your source language.
  2. Send the form for translation (or let Translate Everything Automatically pick it up).
  3. Insert the shortcode on the source-language page.
  4. Translate the page through WPMLTranslationsDashboard the same way you’d translate any other page. The shortcode is preserved on the translated page.
  5. When a visitor opens the translated page, WPML Multilingual for CF7 serves the form in the visitor’s language automatically – same shortcode, translated content.

You don’t need a different form ID per language. The translation is linked to the source form; the glue plugin resolves the right-language version at render time based on the page’s language.

ID-based, hash-based, and title-based shortcodes all work. [contact-form-7 id="123" title="Contact form 1"] works multilingually out of the box. So does the hash ID that Contact Form 7 5.8 and later puts in the shortcode, like [contact-form-7 id="1a2b3c4" title="Contact form 1"]. [contact-form-7 title="Contact form 1"] (title only, no ID) also resolves to the right language.

The form also shows in the page’s language when a theme or a page builder loads it with AJAX.

The exception – when you genuinely want different forms per language. If you need structurally different forms per language (different form-tags, different Mail templates, different Messages tab content), build separate Contact Form 7 forms and insert each one’s shortcode on the matching language version of the page using the WordPress editor for that translation. That’s the only situation where shortcodes diverge across languages.

Page-Builder Gotcha

If your page is built in Divi, Elementor, or another page builder whose text module wraps the shortcode, the shortcode may not always survive translation cleanly. If the translated page shows the source-language form, open the translated page in the page builder and re-insert the [contact-form-7] shortcode there. Native WordPress block editor and classic editor don’t have this issue.

If you use the Divi 5 Contact Form 7 module, you do not need this step. The module shows the translated form automatically.

Form-Tag Labels and Visitor-Facing Strings

Every form-tag’s visitor-facing content translates: labels (the text outside the bracketed tag), button labels (the value in [submit "Send"]), placeholders set via the placeholder option, and the option values inside [checkbox], [radio], and [select] tags.

The form-tag type and name don’t translate. They’re identifiers. The form-tag values (the visitor-facing choices) do translate. Example:

[select your-country "China" "India" "San Marino"]

In the French translation, "China" becomes "Chine" while your-country (the form-tag name) and select (the type) stay identical. Mail-tag substitution still works because the translation preserves the position of each value.

Pipe-Separated Values – Translate the Label, Keep the Value Stable

Pipe syntax lets you decouple the visitor-facing label from the value sent in the email:

[select your-country
  "Chinese|CN"
  "Indian|IN"
  "Sammarinese|SM"]

When you translate this form, only the labels (Chinese, Indian, Sammarinese) go to the translation job. The values (CN, IN, SM) stay out of the job, and the translated form takes them from the source form. A French visitor sees Chinois, Indien, Saint-Marinais; the email body and any backend handler still receive CN, IN, SM. Use pipe syntax when the submitted value must be the same in every language. Examples are CRM mappings, payment SKUs, and geographic codes. It also works for the email address that a [select] choice sends the message to. Hidden field values also stay as they are in the source form.

Acceptance and Quiz Tags

The Acceptance checkbox carries the consent text and usually one or more embedded links to privacy and terms pages. Translate the text as a single row in the translation job; for the link targets, edit the translated row to point to per-language privacy and terms pages.

Quiz tags use the pipe syntax. The question comes before the pipe and the answer comes after it. The question goes to the translation job. The answer stays as it is in the source form, so use answers that work in every language, like numbers:

[quiz captcha
  "1+1=?|2"
  "2+3=?|5"]

The Messages Tab

Contact Form 7’s Messages tab carries ~16 editable validation strings – the ones visitors see on submission and on error. Every one translates in the same job:

  • Thank you for your message. It has been sent.
  • One or more fields have an error. Please check and try again.
  • There was an error trying to send your message. Please try again later.
  • This field is required.
  • This e-mail address is invalid.
  • The telephone number is invalid.
  • The URL is invalid.
  • The number is smaller than the minimum allowed.
  • The number is larger than the maximum allowed.
  • The date format is incorrect.
  • The file is too big.
  • The file is not supported.
  • The Acceptance checkbox is required.
  • The answer to the quiz is incorrect.
  • (plus the remaining default messages CF7 ships).

A message that you customized goes to the translation job as it is. A message that still has the Contact Form 7 default text gets the translation that Contact Form 7 ships for that language.

If your Messages tab uses mail-tags to interpolate input (Thanks [your-name], your message has been sent!), the mail-tag still resolves correctly after translation.

Mail and Mail (2)

Contact Form 7’s two outgoing email templates, Mail (admin notification) and Mail (2) (optional reply or autoresponder to the visitor), translate independently. The Subject and the Message body of each template sit in the translation job. Mail-tags inside the translated bodies ([your-name], [your-message], [your-email]) resolve correctly.

The To, From, Additional headers, and File attachments settings are not in the translation job. They follow the source form: when you change them in the source form, WPML copies the change to the translated forms. This change doesn’t mark the translations as needing an update. To use a different value in one language, edit that language’s form in Contact Form 7. WPML keeps a value that you set in a translated form.

Each language version of the form sends its emails in its own language. A visitor who submits the French form sends the French Mail, and gets the French Mail (2).

For Mail (2), the visitor-facing autoresponder body is where translation matters most. That’s the message that lands in the visitor’s inbox. Send a test submission from a translated page and confirm the autoresponder arrives in the visitor’s language.

Submission Integrations

Contact Form 7 has a small but important set of integrations. Each one preserves the visitor’s language when translation is configured:

  • Flamingo. The Contact Form 7 author’s submission-management add-on. Submissions land in ContactInbound Messages with the translated subject and body intact.
  • Stripe. Contact Form 7’s [stripe] form-tag fields and the receipt-message text both appear in the translation job.
  • Akismet. Spam-protection messaging translates through WPML String Translation (not the form-translation job).
  • reCAPTCHA. The visitor-facing error message translates through WPML String Translation.
  • Cloudflare Turnstile. If the [turnstile] tag has a language: option, each translated form shows the Turnstile widget in the form’s language.

Common Pitfalls

  • Acceptance with embedded link points to the wrong language’s privacy page. Edit the Acceptance translation in the Advanced Translation Editor and set per-language link targets.
  • The Messages tab translations don’t appear. Confirm WPML String Translation is active and that the form was re-sent for translation after editing the Messages tab.
  • Mail-tags inside translations resolve to empty strings. Check that the form-tag name in the mail-tag (e.g., [your-name]) matches a form-tag in the form. The translation never breaks mail-tag resolution, but renaming a form-tag after translation will.
  • Your JavaScript reads the form ID from a DOM event. The contactFormId of the wpcf7submit and wpcf7mailsent events is the ID of the form in the page’s language. Each language has its own form ID, so check for the ID of every language.

Written byAmir