Before You Start
Install and activate these plugins:
- Gravity Forms.
- WPML and WPML String Translation.
- GFML – Gravity Forms Multilingual (the add-on this page covers).
Build the form in Gravity Forms in your site’s source language. Add every field you want (Pricing Fields, paginated structure, Conditional Logic, Notifications, and Confirmations) before sending the form for translation. You can always change the form later and re-translate the differences.
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
- Open WPMLTranslationsDashboard.
- Expand the Gravity Forms section.
- Tick the form you want to translate.
- Choose a translation method: PTC (recommended), your translator, or Translate myself.
- Click Translate.
The form, its fields, options, Notifications, Confirmations, per-field validation messages and form messages all come into the same translation job. The form messages are the entry limit, schedule and require login messages, and the post title and content templates. Translators see them as labelled rows in the Advanced Translation Editor.
The editor groups the rows of each field under Field: <field label>, for example Field: Email. Conditional logic rules show as Conditional Logic Rule rows, under the field, Notification, Confirmation, page or submit button they belong to. Each form message has its own label, for example Entry Limit Reached Message, Form Expired Message or Require Login Message.
Insert the Form Into Your Translated Pages
Gravity Forms sits inside a page or post, usually through the Gravity Forms block or the [gravityform id="X" title="false"] shortcode. The way you handle multilingual insertion is the bit that surprises clients most, so here’s the rule:
Use the same block or shortcode on every language version of the page. Don’t create a separate form per language.
The flow:
- Build the form once in your source language.
- Send the form for translation (or let Translate Everything Automatically pick it up).
- Insert the form on the source-language page using the Gravity Forms block or the
[gravityform]shortcode. - Translate the page through WPMLTranslationsDashboard the same way you’d translate any other page. The form embed is preserved in the translated page.
- When a visitor lands on the translated page, GFML serves the form in the visitor’s language automatically – same form ID, same shortcode, translated content.
You don’t need a different form ID per language. You don’t need to swap shortcodes 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.
The exception – when you genuinely want different forms per language. Some sites need structurally different forms per language (different fields, different logic, not just different copy). In that case, build separate Gravity Forms (one per language) 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 that wraps shortcodes in its own text module, 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 form’s block or shortcode there. Native WordPress block editor and classic editor don’t have this issue.
Field Labels and Options Translate Alongside Pricing and Product Fields
Every field label, placeholder, dropdown option, radio choice, checkbox label, and HTML field content appears in the translation job. For Gravity Forms’ distinctive Pricing Fields (Product, Quantity, Total, Shipping), the labels translate too – “Quantity” becomes “Quantité” – while the underlying numeric handling stays untouched. List fields, Digital Signatures, and File Uploads translate the same way. Multiple Choice and Image Choice fields translate the same way. The country and number sub-labels of a Phone field in the International format are in the job too. From Gravity Forms Multilingual 5.4.0, the default sub-labels of Name, Address and Password fields are in the job too. So are the sub-labels of an Email field with confirmation. Examples are “First”, “City” and “Confirm Email”. Before, you translated them in WPML String Translation, after a plugin scan. The State and ZIP sub-labels of an Address field come from the address type, so they are not in the job. A form created before this version gets these strings the next time you save it. A sub-label with no translation keeps the text from the Gravity Forms language files.
Paginated Forms and Conversational Forms
For paginated forms, every page heading and page-break title sits in the translation job. Conditional Logic that branches across pages survives translation. Choice values stay aligned across languages, so the show/hide rules keep firing on the same data. Conversational forms (the one-question-at-a-time mode of the Gravity Forms Conversational Forms add-on) put their own texts in the translation job, next to the form fields: the Continue button, the welcome screen title, message, button and image alt text, and the conversational page title. On a translated conversational page, the browser tab shows the translated page title, and when the logo links to a page of your site, the link opens that page in the visitor’s language. A link to another site stays as it is. The Previous and Next buttons, the “%s Completed!” progress label, and the “Use Shift + Enter to add line breaks” hint come from the add-on’s own language files, not from the form. Translate them in WPML String Translation (text domain gravityformsconversationalforms), or add a .mo file for your language. Pick one language version, walk through the conversational flow, and confirm each step reads naturally before publishing.
Per-Field Validation Messages
Each field in Gravity Forms has its own Validation Message setting in the field’s Advanced tab – the text shown when validation fails. Each one appears as a row in the Advanced Translation Editor.
If you don’t see a per-field validation message in the translation job, the field is probably using Gravity Forms’ default message (set in FormsSettingsForm Settings) rather than a per-field override. Either set a custom per-field message and re-send the form for translation, or translate the global default via WPML String Translation.
Confirmations – Text, Redirect, and Page
Gravity Forms supports three Confirmation types and all three work multilingually:
- Text confirmations translate inline. Edit the source-language confirmation in Gravity Forms > re-send the form for translation > translated text appears for each language.
- Page confirmations point to a WordPress page. Translate that page through WPML’s normal page-translation workflow; the visitor sees the language version that matches their context.
- Redirect confirmations send the visitor to a URL after submission. The URL itself is translatable per language. Set a different thank-you URL for each language in the Advanced Translation Editor. When the redirect URL points to a page of your site and you do not translate it, WPML sends the visitor to the translation of that page.
Notifications and Notification Routing
The Subject and the Message of every Gravity Forms Notification are in the translation job. The From Name is in the job too. The email addresses (Send To, From Email, Reply To, BCC) are not in the job: they are the same in every language. The Notification body uses Gravity Forms merge tags ({Name}, {Email}, {All Fields}) and these resolve correctly after translation. Notification routing rules send different submissions to different recipients based on field values. They survive translation because the underlying choice values stay aligned across languages.
After translation, send a test submission in each language and confirm the notification arrives in the visitor’s language with the right merge-tag substitutions.
Conditional Logic on Translated Choice Values
Conditional Logic on text-based choices (Radio Buttons, Checkboxes, Dropdowns) keeps working across translations because GFML maintains a value map between source and translated labels. The visitor sees “Pas encore” in French; the underlying value stays “Not yet”; the conditional rule keeps firing on “Not yet”.
The one thing that breaks Conditional Logic: changing the source-language choice label after translation without re-sending the form for translation. The mapping goes stale. Fix it by re-sending the form – GFML updates the value map.
You can also translate the values you type in conditions. This applies to Notifications, Confirmations, the Submit button and the Next buttons of a paginated form. An example is “send this notification when field A contains Yes”. The value “Yes” appears in the translation job, and the translated form uses the translated value. If a condition is not in the job, save the form once in Gravity Forms. Then send it for translation again.
Integration Add-Ons – Mailchimp, ActiveCampaign, HubSpot, Zapier, Slack, Webhooks
Gravity Forms add-ons that push submissions to third-party services (Mailchimp, ActiveCampaign, HubSpot, Zapier, Slack, Webhooks, and the rest) receive the entry as Gravity Forms saves it. GFML does not translate or change this data. A French visitor’s name and message arrive at the destination as the visitor typed them.
The settings of these add-on feeds are not in the translation job. This includes the mapped list names, pipeline stages, channel names and fixed values. They are the same for every language. Gravity Flow is the exception: its step texts are in the job (see below).
If your integration maps a choice to something in the other service, for example a dropdown choice to a Mailchimp list, submit the form once in each language. Then check that the data arrives as you expect. For Zapier, read the known issue with translated forms.
Gravity Flow – Workflow Emails and Step Messages
If you use Gravity Flow to add approval steps and other workflow steps to a form, the texts of the steps come into the form’s translation job. Translate them together with the rest of the form:
- The name, description and Instructions of each step.
- The subject and message of the step emails: Assignee Email, Approval Email, Rejection Email, Revert Email, In Progress Email, Complete Email, and the email of a Notification step.
- The Confirmation Message of a step.
- The custom messages of an Approval step: Approval Confirmation, Rejection Confirmation and Reverted Confirmation.
WPML uses these translations in the language of the entry. This is the language of the page where the visitor submitted the form. The entry language applies in every part of the workflow: when the visitor submits the form, when a later step starts, and when an assignee approves or rejects the entry. The admin language of the assignee does not change it. For example, an entry submitted on your French page sends the step emails in French and shows the French Approval Confirmation.
Limitation: the Invalid Approval Link Message of an Approval step and the Custom Cancellation Message of the Workflow Complete step are in the translation job too, but they still show in your site’s default language. The first message shows when someone clicks an approve or reject link after the step is processed. The second one shows when someone cancels the workflow, and when anyone opens the entry after that.
Common Pitfalls
- Choice labels don’t translate in notification emails. Re-send the form for translation after changing the source-language labels. If the problem persists, check that GFML is up to date. This was a recurring issue on older versions and is tracked on the forum threads.
- Form shows “There is nothing to translate” when there obviously is. Usually a Dashboard cache issue. Refresh the page, or re-send the form for translation from the post that embeds it.
- Conditional Logic stops firing in translated forms. A choice label was edited in the source language after translation. Re-send the form for translation to refresh the value map.