WPForms Multilingual
Antivirus scan
Powered by ClamAV
✅ Verified clean
This product file has passed our security filters.
Want to run a fresh ClamAV scan right now? Takes a few seconds and shows scanner version, signature DB and live result.
This can take 5 to 30 seconds.
Clean file Threat detected
No threats detected in this file.
- File
- Size
- Scanned
- ClamAV
- Signature database
⚡ Powered by ClamAV
Scan could not be completed
Report product
If you detected an issue (broken file, malware, inappropriate content, etc.) let us know and we'll review it ASAP.
Sign in to report
About WPForms Multilingual
You have a contact form that works in Spanish, and now visitors arrive in other languages. Duplicating the form per language seems logical, but it ends up as a pile of forms to maintain at once, with email alerts nobody is sure which language they go out in. WPForms Multilingual avoids that path: a single form, translated inside WPML, shown in each visitor's language.
One form, one shortcode, every language with WPForms Multilingual
First, understand what it is: an add-on that connects WPForms with WPML. It doesn't work alone. You need WPForms (Lite or Pro), WPML and WPML String Translation, plus this plugin.
Step 1: build the form in your original language
Set up fields, pages, conditional logic, validation messages, confirmations and notifications before translating. If you change something later, you can send it again and translate only the differences.
Step 2: send it for translation from WPML
From the WPML translations panel you pick the form and the method: WPML's automatic translation, a translator, or yourself. Fields, options, confirmations, notifications and validation messages all come into the same translation job. If your site has automatic translation of all content turned on, WPML does this step on its own.
Step 3: insert the form in the page and translate the page
You place the WPForms block or the shortcode on the original page and translate the page like any other. The translated version keeps the same form: you don't need another ID or a different shortcode per language. The plugin serves the right version at render time.
There is only one reasonable exception: if you want different forms per language (other fields or other logic, not just other copy), you create separate forms and put each shortcode on its translated page.
If you use Divi or Elementor, check the translated page
When the shortcode sits inside a text module of a page builder such as Divi or Elementor, it sometimes doesn't survive translation well and the translated page shows the form in the original language. The fix is to open that page in the builder and re-insert the block or shortcode. With the WordPress block editor or the classic editor this doesn't happen.
What gets translated beyond the labels
- Multi-page forms: each page title, intro text and button (Next, Previous, Submit) is a translatable row, and the progress indicator text too. Walk through them in each language to check the labels sound natural.
- Conditional logic: a map is kept between the original and translated options, so the rule keeps working. If you change a label in the original language after translating, send the form again to update that map.
- Confirmations: the on-screen message, the destination page (translated like any page) and the redirect to a URL, which you can set differently per language.
- Notifications: recipient, subject, sender name, reply-to and body. Smart Tags such as {name} or {email} keep working after translation.
Form pages, payments and integrations
If you use the Form Pages addon, translate the form and also the page: headline, intro, success message and footer come in the same job, but visit the page in each language to confirm everything is translated.
The texts of the payment add-ons (Stripe Pro, PayPal Commerce, Square Pro, Authorize.Net) are also translated: buttons, card errors and the post-payment message. Run a test payment in each language using the gateway's test mode. Integrations with Mailchimp, HubSpot, Salesforce, ActiveCampaign, Zapier and others receive what the visitor typed in their language; mapped values stay as they are so the matching doesn't break.
Calculations doesn't work with this plugin
The WPForms Calculations addon is incompatible with WPForms Multilingual: the calculation logic doesn't run if both are active. If your form is a price or quote calculator, you'll need to rethink it before buying.
Frequently asked questions
Do I need WPML?
Yes, along with WPML String Translation. This plugin only links WPForms with WPML.
Is the user registration email translated?
Yes, the registration confirmation email goes out in the visitor's language. Test it by registering a test user from a translated page.
Topics
Version history
-
v
5.2.0 Current 24 Oct 2026
-
v
5.1.0 2 Oct 2026
-
v
0.5.1 7 Sep 2026
-
v
0.3.4 16 May 2024
Customer reviews
Sign in to leave a review. Only people who have the product can review it.
No reviews for this product yet.
Frequently asked questions
-
GPL (General Public License) is the license under which WordPress and most premium plugins/themes are distributed. It grants you the right to use, modify and redistribute the software in as many projects as you want, with no domain restrictions.
-
Yes. With membership you get automatic updates via our GPLClub Updater plugin (installed on your WP, detects new versions and applies them). With individual purchase, you get one year of manual updates from your account.
-
Depends on the plan. Monthly: 3 domains. Semi-annual: 7. Annual and Lifetime: 15. Individual purchase: 1 domain.
-
GPLClub offers its own support for installation, configuration and compatibility. For direct support from the original author (feature requests, product-specific bugs), a license purchased from the author is required.
