Formbricks supports multi-language surveys, allowing you to reach a global audience by translating your surveys into multiple languages. Respondents can view surveys in their preferred language, with optional language switching.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/formbricks/formbricks/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Multi-language support includes:- Default Language: Primary language for your survey
- Secondary Languages: Additional languages enabled for translation
- Language Switch: Optional toggle for respondents to change language
- Per-Field Translations: Each text field can have language-specific content
Multi-language surveys require an Enterprise license. See your billing settings to enable this feature.
Setting Up Multi-Language Surveys
Enable Multi-Language
In the survey editor, open the “Multiple Languages” card (marked with the Languages icon).
Configure Workspace Languages
Navigate to Workspace Settings > Languages to add languages to your workspace. You need at least 2 languages configured.
Select Default Language
Choose your primary language from the dropdown. This is the fallback if translations are missing.
Survey Language Configuration
Languages are configured in thelanguages array on the survey object:
Field-Level Translations
Each translatable field uses a record structure with language codes as keys:Configuration Examples
Example 1: Welcome Card Translation
Example 2: Multi-Language Rating Question
Example 3: Multi-Language Open Text
Example 4: Thank You Message Translation
Language Switch Feature
Enable respondents to change languages during the survey:The language switch toggle appears only when 2 or more languages are enabled.
Practical Use Cases
Global Customer Feedback
- Support customers in their native language
- Increase response rates with localized surveys
- Collect feedback from international markets
Employee Engagement
- Survey distributed teams across countries
- Ensure all employees understand questions clearly
- Demonstrate inclusivity and cultural awareness
Product Research
- Test product concepts in different markets
- Gather region-specific insights
- Validate translations before product launch
Educational Assessments
- Support multilingual student populations
- Provide accessibility for language learners
- Comply with educational standards requiring multiple languages
Best Practices
- Consistent Terminology: Use the same translations across all surveys for consistency
- Test in Each Language: Preview the survey in every language to check formatting
- Consider Text Expansion: Some languages require more space (German often needs 30% more)
- Right-to-Left Support: Test RTL languages (Arabic, Hebrew) for proper display
- Cultural Adaptation: Adapt examples and references to be culturally appropriate
- Default Language: Always provide complete content in the default language as fallback
Implementation Reference
The multi-language implementation can be found in:- UI component:
apps/web/modules/ee/multi-language-surveys/components/multi-language-card.tsx:45 - Language utilities:
apps/web/lib/i18n/utils - Language types: Database schema and
packages/database/zod/surveys.ts:68-70
Limitations
- Multi-language is an Enterprise feature
- Workspace must have at least 2 languages configured
- Each field must be translated manually (no automatic translation)
- Language switch requires at least 2 enabled languages
Related Features
- Custom Styling - Style surveys for different cultural preferences
- Conditional Logic - Combine with branching for region-specific flows
- Hidden Fields - Pass user language preference as hidden field