The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →To create a multilingual WordPress form, translate the form itself—not just the page around it. The reliable pattern is to build one complete source-language form, connect your form plugin to a multilingual plugin, translate labels and operational messages, and place the same form block or shortcode on each translated page. With WPForms and WPML, one form ID serves every language; the translated page determines which version visitors see.
What a multilingual form must translate
A page can be translated while its embedded form remains in the default language. Audit every customer-facing and operational string before publishing:
- Field labels, descriptions, placeholders and required-field indicators
- Dropdown, checkbox, radio and multi-select choices
- Validation and error messages
- Success confirmations or redirect destinations
- Notification recipients, subjects and email body text
- Acceptance, quiz and consent wording
- Conditional-logic choices and payment text
- User-registration confirmation emails and connected marketing or submission integrations
Legal, consent and transactional wording needs human review even when automatic translation is enabled.
Choose the language and URL structure first
Set the default language, add the languages you will publish, and decide how language-specific URLs should work. WPML documents 65 pre-configured languages and supports custom languages, language switchers, and three URL patterns:
#1 Best Overall
- Book - 1, 000 books to read before you die: a life-changing list (1000 before you die)
- Language: english
- Binding: hardcover
| URL pattern | Example | Operational consideration |
|---|---|---|
| Directories | example.com/fr/contact/ |
One domain with a clear language path. |
| Separate domains or subdomains | example.fr/contact/ or fr.example.com/contact/ |
Requires domain or DNS configuration for each language. |
| Language parameter | example.com/contact/?lang=fr |
Simple to deploy, but less readable for visitors and sharing. |
Place a language switcher where visitors can find it. Switching a page should take the visitor to that page’s translated version, with the correctly translated form rendered inside it.
WPForms and WPML: one form for every language
This is the most fully documented workflow for WPForms. WPML’s guidance, updated February 19, 2026, specifically says not to create a separate form for each language.
Install the required components
- Install and activate WPForms.
- Install and configure WPML, including the languages and URL format.
- Install WPML String Translation.
- Install the WPForms Multilingual add-on.
Build the complete source form
In WPForms, create the form in the site’s default language before sending it for translation. Finish the fields, multi-page sections, conditional logic, validation behavior, confirmation method, notification rules, payment add-ons and marketing integrations first. Changes made later must be sent through translation again.
Send the form to translation
- Go to WPML → Translations → Dashboard.
- Filter or select the form under WPForms.
- Send it to your translation workflow, or allow WPML’s automatic workflow to pick up a new or changed form.
- Translate each language’s form strings and complete the translation before publishing the page.
Translate operational messages, not only fields
In the translation job, review notification recipients and message content, confirmation text or redirect URLs, validation messages, and user-registration confirmation email text. Keep recipient addresses correct for every market; a translated subject does not automatically imply a different recipient.
Embed the same form on every translated page
Add the same WPForms block or [wpforms id="X"] shortcode to the source page and each translated page. Do not duplicate the form or create language-specific IDs. WPML resolves the translated page language and serves the corresponding translated form automatically while retaining the same form ID and shortcode.
Contact Form 7 workflow
For Contact Form 7, install Contact Form 7, WPML, WPML String Translation and WPML Multilingual for CF7. Create the source form, then use the connector to associate its translations.
Translate the form tags and all text in the Messages tab, mail templates, acceptance and quiz text, pipe-separated choices, and any supported submission integrations. Embed the translated form on the translated page; the connector uses that page’s language to resolve the correct version.
Other plugin choices
| Option | Strength | Check before production |
|---|---|---|
| WPML | Dedicated connectors documented for WPForms, Gravity Forms, Ninja Forms and Contact Form 7, plus control over language URLs and operational strings. | Install the connector that matches your exact form plugin and test every integration it touches. |
| TranslatePress | Front-end translation workflow and language controls under Settings → TranslatePress. | Confirm compatibility with your chosen form builder, especially validation, notifications, conditional fields and add-ons. Custom languages can define a language code, native name, automatic-translation code, flag URL and RTL setting. |
| Polylang | Basic setup is lightweight: activate it, create languages and add a language-switcher widget. | Verify the exact form-builder integration and translation coverage before relying on it for a production form. |
The connector matters more than the multilingual plugin’s general page-translation features. Without a form-specific integration, labels may translate while validation, email templates or submission data remain in the source language.
Recommended Free Tools
Quality-check every language before launch
- Open the translated URL directly and confirm the language switcher points to the matching page.
- Submit the form with each required field empty to check translated validation messages.
- Test every dropdown, checkbox, radio choice and conditional branch.
- Verify confirmation text and every redirect destination, including language-specific landing pages.
- Send a real test submission and confirm the correct recipient, subject, body, reply-to behavior and localized user email.
- Check consent, payment and marketing integrations for the translated field values they receive.
- Review date, phone and address instructions for local conventions.
- For right-to-left languages, inspect field order, alignment, multi-page navigation, error placement and confirmation layouts.
- Repeat the checks after changing the source form; changed strings require a new translation pass.
Common problems and fixes
The translated page still shows the default-language form
Confirm that the page is genuinely translated, the form connector is active, and the same source form block or shortcode is used. Clear page and object caches after completing a translation job.
Rank #4
- Guide students toward a healthy lifestyle, both physically and financially
- This revised and expanded edition adds much more information on work ethic, nutrition, and exercise; updates the sections on sexually transmitted diseases and drugs; and includes completely new sections on preparing financially for the future
- Graphic organizers, self inventories, puzzles, real-life situations, and cloze activities provide creative opportunities for students to assess their own lifestyles and make good choices for the future
- Prepare students for adulthood
- Practical lessons to help handle real life events
Labels are translated but emails are not
Notification subjects, bodies, recipients and user-registration messages are separate translatable content. Reopen the form’s translation job and translate those fields explicitly.
A conditional choice or error remains in the source language
Look for the string in the connector’s form translation screen or WPML String Translation. Choices, validation messages and conditional-logic text are not guaranteed to be included when only visible field labels are translated.
Automatic translation sounds wrong
Replace machine output for product names, industry terminology, legal consent, gendered or formal language, and instructions that affect a user’s submission. Have a native or qualified reviewer test the complete flow, not just isolated strings.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Best Value
- Features Over 160 Latin Songs
- Arranged for C Instruments
- Standard Notation
- 48 Pages
RTL layout is broken
Check the language’s RTL setting, then test the rendered form on desktop and mobile. Correct alignment and navigation in the form theme or builder after translation; do not assume translated text alone changes layout.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Recommended implementation decision
If you use WPForms, choose WPForms Multilingual with WPML and keep one source form across all translated pages. If you use Contact Form 7, use WPML Multilingual for CF7 and translate both the form and mail configuration. For TranslatePress or Polylang, select them only after confirming a connector or integration that covers your form builder’s operational strings. In every case, publish only after testing submissions, messages, redirects and integrations in each language.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
