WPML Multilingual for CF7 – Multilingual Contact Form 7 Form-Tags, Messages, Mail Templates, and Integrations

Translate Every Contact Form 7 Form-Tag

Contact Form 7’s full form-tag catalogue translates through WPML’s Advanced Translation Editor: text, email, tel, url, textarea, number, range, date, checkbox, radio, select, file, quiz, acceptance, and submit, plus the required-variant * forms (text*, email*, and the rest). Labels, placeholders, dropdown options, button text, file-upload hints – all of it.

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

Contact Form 7’s selectable fields support pipe syntax ([select your-country "China" "India" "San Marino"]), where each value can also carry a different label using label|value. WPML Multilingual for CF7 translates the visitor-facing labels per language while the submitted value (and the mail-tag substitution) stays canonical. A French visitor sees Chine, Inde, Saint-Marin; the submission, the email body, and your CRM receive the original English values. Backend systems don’t break.

Acceptance Text and Quiz Tags Translate

The Acceptance checkbox (the consent control that often carries a long sentence with embedded privacy-policy and terms-of-service links) translates as a single row. The link targets translate per language too, so you can point French visitors to your French privacy page. Quiz tags translate both the question text and the accepted-answer values, so quiz challenges work in every language.

The Messages Tab Translates

Contact Form 7’s Messages tab carries the editable validation copy that runs the form. About 16 strings in total, every one of them translatable:

• 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 number is smaller than the minimum allowed.
• The date format is incorrect.
• The file is too big.

…and the rest. All of them appear in the translation job. No need to translate them by hand or rely on locale .mo files. Mail-tags embedded in confirmation messages (Thanks [your-name], your message has been sent!) resolve correctly after translation.

Both Mail and Mail (2) Templates Translate

Contact Form 7 supports two outgoing email templates per form: Mail (the admin notification) and Mail (2) (the optional reply or autoresponder to the visitor). WPML Multilingual for CF7 translates both independently per language. To, From, Subject, Additional headers, Message body, and the File attachments descriptions all come through. Mail-tags ([your-name], [your-message], …) inside the translated templates resolve correctly.

Submission Integrations Receive Translated Data

Contact Form 7 sites typically pair the form with one or more submission-handling tools. WPML Multilingual for CF7 keeps the visitor’s language flowing into all of them:

• Flamingo. The CF7 author’s submission-management add-on. Submissions land in Flamingo’s Inbound Messages with the translated subject and body intact.
• Constant Contact. CF7’s official integration. Visitor input flows through to your Constant Contact lists in the visitor’s language.
• Stripe. CF7’s Stripe form-tag fields and the receipt-message text both appear in the translation job.
• Akismet and reCAPTCHA. Anti-spam labels and any visitor-facing error messages translate through WPML’s string-translation path.

Forms Read Natively in Every Language With PTC

Translating a Contact Form 7 form is genuinely difficult work. CF7 is full of very short, decontextualised strings:

• A form-tag’s visitor-facing label might be a single word: Name, Email, Send.
• The Messages tab carries about 16 standalone validation strings like This field is required or The date format is incorrect, with no surrounding context.
• The Acceptance checkbox often holds a long sentence in legal register with embedded privacy-policy links.
• Mail and Mail (2) bodies interleave mail-tag placeholders like [your-name] and [your-message] with prose.

Classic machine translation looks at each string by itself and translates word-by-word. The form ends up with awkward labels, validation messages that read as broken English-translated-back, and emails that mix registers.

PTC – WPML’s AI translation works with the full context of your site. PTC knows that a one-word submit form-tag value is a button label and translates it as a button. It knows that the Messages tab strings are validation copy and translates them in that register. It knows that the Acceptance sentence is legal language. It knows that the Mail and Mail (2) bodies are emails to the form owner and to the visitor.

The result reads like the form was built natively in each language. Short labels read naturally. Validation messages stay terse and clear. Acceptance text preserves the legal register. The outgoing emails sound the way an in-house translator would write them.

Built Alongside the Contact Form 7 Team

WPML and Contact Form 7 share an active compatibility commitment, confirmed on the joint Contact Form 7 compatibility page. When Contact Form 7 ships a release, WPML Multilingual for CF7 keeps up.