WPForms Multilingual – Multilingual Form Templates, Form Pages, Confirmations, Notifications, and Payment Add-Ons

Translate Any of WPForms’ 2,100+ Form Templates Once

WPForms ships with one of the largest template libraries in the WordPress form ecosystem: 2,100+ pre-built forms across contact, marketing, surveys, payments, registration, and request flows. Translate the template once and every form you build from it inherits the translated wiring. Multi-Page Forms translate page by page. Each page heading, intro paragraph, and Next / Previous / Submit button label appears in the translation job. Smart Conditional Logic survives translation: choice values stay aligned across languages so show/hide rules keep firing on the same data.

Form Pages Translate Alongside the Form

The Form Pages Addon turns a WPForms form into a full landing page. No theme, no header, no footer, just the form against the layout you pick. WPForms Multilingual translates the page-level strings too: headline, intro copy, footer message, and the post-submission success state. The landing page lands in the visitor’s language, not just the fields inside it.

Validation Messages Translate per Field

WPForms’ Validation Messages (required field, email format, URL format, number range, file extension, file size, and the rest) translate per language. Visitors get errors in their own language instead of fallback English. Per-field overrides (the Validation setting on individual fields) translate the same way.

All Three Confirmation Types Translate

WPForms Multilingual covers WPForms’ three Confirmation types: Message (inline thank-you text), Show Page (redirect to a translated WordPress page), and Go to URL (Redirect) (per-language redirect URLs for off-site thank-you pages). Conditional Confirmations (the rules that show different confirmations based on field values) translate alongside.

Form Notifications Translate – Owner-Side and Visitor-Side

WPForms Form Notifications translate independently per language. Send To Email, Email Subject Line, From Name, Reply-To, and Message all sit in the translation job. Conditional Notifications (rules that route emails by field value) survive translation. User Registration confirmation emails translate to the visitor’s language too (improved in 0.5.0).

Payment Add-On Copy Translates

The payment add-on family (Stripe Pro, PayPal Commerce, Square Pro, and Authorize.Net) has visitor-facing strings on the form (button labels like Pay $50 with PayPal, validation messages on card fields) and after submission (success messages, receipt summaries, error states). All of it translates per language, so the checkout flow stays in the visitor’s language end-to-end.

Marketing and CRM Integrations Receive Translated Submissions

When a visitor submits a form in their language, the WPForms add-on that pushes the submission into Mailchimp, AWeber, Constant Contact, Drip, GetResponse, HubSpot, Salesforce, Klaviyo, ActiveCampaign, or Zapier receives the translated visitor input – name and message in the visitor’s language. Field mappings translate too, so list segments and pipeline stages key off the right strings.

Forms Read Natively in Every Language With PTC

Translating a WPForms form is genuinely difficult work. A typical WPForms setup mixes many different registers and string types:

• Short Form Template labels like Name, Email, Phone.
• Form Pages landing-page copy that sells.
• Payment add-on checkout strings like Pay $50 with PayPal.
• Smart Conditional Logic choice values.
• Form Notification subject lines.
• User Registration emails.
• Per-field validation messages.

The registers are very different. Landing-page selling. Transactional checkout. Operational email. Terse error message. Most strings are short and decontextualised. Classic machine translation looks at each one by itself. The form ends up inconsistent across registers and quietly wrong on the short labels.

PTC – WPML’s AI translation works with the full context of your site. PTC knows that a Form Pages headline has to convert. It knows that a Stripe checkout button has to fit the payment register. It knows that a User Registration email has to read warmly. It knows that a validation message has to be terse and clear.

The result reads like the form was built natively in each language. Form Templates match the source’s tone. Payment copy fits the visitor’s purchasing language. Marketing-integration values line up across languages.

A Note on the Calculations Addon

The Calculations Addon is currently incompatible with WPForms Multilingual. Calculation logic doesn’t run when both are active. The errata page tracks the issue. If your site relies on Calculations, plan around this until the compatibility is resolved.

Built Alongside the WPForms Team

WPForms Multilingual ships with WPForms compatibility confirmed on the joint WPForms compatibility page. When WPForms ships a release, WPForms Multilingual keeps up. The 0.4.1 fixes for form-saving interference (Dec 2024) and the 0.5.0 user-registration improvements (Apr 2026) are recent examples.