GPLClub
🔌 Plugin · By Gravity Forms

Gravity Forms Multilingual

v5.2.0 · Updated 21 Oct 2026 · Official site

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
Gravity Forms Multilingual · Plugin for WordPress
Follow

About Gravity Forms Multilingual

A translated form has two readers

The first is the visitor, who wants to read "Quote" in their language. The second reads nothing, but depends on every option: the rule that sends the notice to the right department, the conditional logic that shows a field, the list in your CRM. If you duplicate the form for each language, the visitor is happy and those rules multiply by the number of languages, with each copy to maintain separately.

Translating a form is not about changing words, it is about keeping a single value beneath all the labels. Gravity Forms Multilingual, the WPML piece that joins the two products, keeps a map between source and translated options, which is why conditions and routing keep working with a single form.

What goes into the translation of each form

  • Fields: labels, placeholders, dropdown, radio and checkbox options, and HTML fields.
  • Special fields: pricing, lists, digital signature, file upload, multiple choice and image choice.
  • Paginated and conversational forms: page titles, prompts and transitions.
  • Confirmations: text ones, page ones, which follow that page's translation, and redirects, with one URL per language. Those with conditional logic work on translated forms.
  • Notifications: recipient, sender name, subject, body and merge tags.

You use the same Gravity Forms block or the same shortcode on each version of the page, translated with WPML, and the visitor gets the form in their language. You only need separate forms when the structure changes, not when the words do.

Integrations follow that logic: services such as Mailchimp, HubSpot, ActiveCampaign or Slack receive what the visitor types, already in their language, and mappings based on field values do not change across languages. If your process depends on Zapier, test it first, because there is an open issue about the translated data it receives.

The edit that breaks the map

The delicate point comes after translating. If you edit an option label in the source language, the map breaks and conditional logic stops working. The fix is to send the form to translation again, so it is worth doing that as part of every change.

Limits with builders, flows and polls

It does not work alone and does not translate by itself: WPML does the translating.

  • Page builders: Divi or Elementor may drop the shortcode during translation; if the form appears in the source language, insert it again.
  • Form block: its styling may look wrong on translated pages; meanwhile, use the shortcode.
  • Gravity Flow: steps and messages are translated and follow the entry's language, except the invalid approval link message and the custom cancellation message, which appear in the default language.
  • Polls: the Polls add-on does not show translations in results mode.

Three prior plugins and the first form

It needs Gravity Forms, WPML and WPML String Translation. To translate a form:

  1. Build the complete form in the source language.
  2. Go to WPML, Translations, Dashboard, and open the Gravity Forms section.
  3. Tick the form and choose the translation method.
  4. Translate the page that holds it and use the same block or shortcode there.
  5. Send a test in each language and review conditions, emails and confirmation.

The pieces around it in the catalog

To work it needs Gravity Forms, WPML and WPML String Translation. If your forms are built with Contact Form 7, Contact Form 7 Multilingual plays the same joining role: a single shortcode that serves the form in the visitor's language.

Before you translate your first form

Do I need one form per language?

Only if the structure changes. If the words change, one is enough.

Can I send people to a different page by language?

Yes: redirect confirmations accept a different URL per language.

In what language does the admin registration email arrive?

With Gravity Forms User Registration, the administrator gets it in their language and the registrant gets theirs in their own.

Version history

  • v
    5.2.0 Current 21 Oct 2026
  • v
    5.1.0 1 Oct 2026
  • v
    5.0.0 30 Sep 2026
  • v
    1.8.4 7 Apr 2026

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.