Ninja Forms Multilingual – Multilingual Multi-Step Forms, Layout & Styles, Email Actions, and Every Integration Action

Translate Every Ninja Forms Field Type

Ninja Forms’ 28+ field types translate through WPML’s Advanced Translation Editor: text, paragraph, name, email, address, phone, list (select, radio, checkbox, multiselect), number, date/time, file upload, submit. Repeater Fields translate row-level: add-row labels and per-row field labels stay multilingual.

Multi-Step Forms Translate, Step by Step

Multi-Step Forms split long forms into shorter pages. Ninja Forms Multilingual translates each step’s heading, navigation button labels (Previous, Next, Submit), and per-step Conditional Logic. The multi-step flow stays in the visitor’s language from the first step to the success screen.

Layout & Styles Survive Translation

Ninja’s visual Layout & Styles designer lets you build columns, grids, and styled sections inside the form. The design is preserved when the form translates – only the strings change. Visitors see the same layout in every language, just with translated labels.

Image Select Fields Translate the Label, Keep the Image

Image Select Fields pair a visual choice (a thumbnail) with a text label. Ninja Forms Multilingual translates the label per language while the image stays shared across languages. The visual selector works identically; the visitor reads the label in their own language.

Save Progress Prompts Translate

Ninja’s Save Progress feature lets visitors save a partial form and resume later. The visitor-side prompts (the Save Progress button, the resume email, the confirmation copy) all translate so visitors get the workflow in their own language.

Per-Field Validation Messages Translate

Every Ninja Forms field carries its own validation copy: required-field error, format error, custom validation message. Each one appears as a translatable row in the Advanced Translation Editor. Anti-Spam and Honeypot copy translates through WPML String Translation.

Success Messages and Submission Redirects Translate

Ninja Forms uses Actions to define what happens after submission. The Success Message Action displays an inline thank-you – translated per language. The Submission Redirect Action routes the visitor to a URL after submission; you set a per-language URL so each language version lands on its own thank-you page.

Email Action Copy Translates

Every Email Action on a form translates independently. To, From Name, Subject, and the Email Message template all sit in the translation job. Multiple Email Actions per form get separate translation rows. Admin notifications and visitor confirmations carry their own per-language copy.

Every Integration Action Translates

Ninja Forms’ Actions architecture turns every integration into a per-form workflow step. Ninja Forms Multilingual translates every Action’s visitor-facing copy. Webhook, Mailchimp, ActiveCampaign, HubSpot, Salesforce, ZohoCRM, Zapier, Slack, Trello, MailPoet, AWeber, Campaign Monitor, Constant Contact, EmailOctopus, Emma, Kit, and CleverReach all receive translated visitor input plus translated mapped-field copy. List, pipeline, channel, and tag labels translate too.

Payment Action Copy Translates

Ninja Forms’ payment Actions for Stripe, Authorize.net, Elavon, and PayPal translate the visitor-facing strings on the checkout flow (purchase descriptions, button labels, error states, success copy), so the payment step stays in the visitor’s language.

Forms Read Natively in Every Language With PTC

Translating a Ninja Forms form is genuinely difficult work. Ninja’s Actions architecture multiplies the problem. The same word can mean different things in different Actions on the same form. Submit. Send. Continue.

A typical Ninja Forms setup mixes:

• Email Action subject lines and body templates.
• Success Message Action text that appears inline after submission.
• Submission Redirect Action URLs that route to per-language thank-you pages.
• Integration Actions for Mailchimp, HubSpot, or Salesforce that push mapped values into pipelines.
• Per-field validation messages.
• Layout & Styles output.
• Multi-Step navigation labels.

Most strings are short. Classic machine translation looks at each one by itself. The form ends up reading as a collection of awkward fragments rather than one coherent form.

PTC – WPML’s AI translation works with the full context of your site. PTC knows whether Submit lives on the form’s main submit button or inside a Multi-Step Forms Next-step button. It knows whether Continue belongs on a Save Progress prompt or on a payment Action. It knows whether a Success Message follows a contact form or a registration form.

The result reads like the form was built natively in each language. Every Action’s copy in the right register. Validation messages that read clearly. Integration values that line up across languages so downstream automations don’t break.

Known Limitations

Two behaviors are worth knowing before you commit:

• Merge tags inside Email Action templates don’t translate per language. The merge-tag insertion uses the source-language template. Tracked on the errata page.
• The Ninja Forms PDF Form Submission add-on doesn’t generate PDFs when Ninja Forms Multilingual is active on forms with translations configured. Tracked on a recurring forum thread.

Built Alongside the Ninja Forms Team

Ninja Forms Multilingual ships with Ninja Forms compatibility confirmed on the joint Ninja Forms compatibility page. When Ninja Forms ships a release, Ninja Forms Multilingual keeps up.