Skip to main content
Localization lets you create multiple language versions of your funnel that automatically display based on your visitors’ location and browser language. Studies show conversion rates improve by up to 70% when users see content in their native language.
Language switcher in Visual Editor

How localization works

FunnelFox automatically detects the best locale for each visitor using the following priority order:
  1. URL Parameters: locale is determined by ?lang=xx and ?country=xx parameters
  2. IP and browser language: locale is determined if geographic location (IP-based country detection) and browser language match the same locale
  3. Default locale: fallback to your default locale if no matches with locales above.
FunnelFox checks URL parameters first, then tries to match IP location and browser language to the same locale, otherwise uses the default locale. You can expand this logic by using the catch-all feature. Learn more about catch-all locale matching.
Important: Localized content is part of your funnel’s static build. You must republish after making localization changes for them to go live.

Manage locales

To manage locales, open a funnel, hover over the 🌐︎ globe icon at the top and click Manage locales.
Locales management page

Add new locale

  1. Click Add locale
  2. Select Country
  3. Select Language
  4. Optionally enable catch-all for broader matching
  5. Choose whether to Translate with AI for instant translation
Use “Europe” as a country to target all 27 EU countries with one locale: AT, BE, BG, HR, CY, CZ, DK, EE, FI, FR, DE, GR, HU, IE, IT, LV, LT, LU, MT, NL, PL, PT, RO, SK, SI, ES, SE.
Creating a new locale

Catch-all locale matching

When you enable catch-all, FunnelFox matches visitors to locales in this order:
  1. Exact match: Country + Language (e.g., Germany + German)
  2. Country with any language: Country match + catch-all language
  3. Language in any country: Catch-all country + language match
  4. Broad catch-all: Both country and language set to catch-all
  5. Default locale: Used when no other rules match

Edit localization

Changes to the default locale’s structure automatically apply to all other locales. Be careful when adding or removing elements in the default locale.
To edit a funnel’s content in a specific locale, switch between locales using the 🌐︎ globe icon in the editor toolbar:
Language switcher in Visual Editor
You can change:
  • All text content (headlines, paragraphs, buttons)
  • Images and media files
  • Input placeholders and labels
  • Option lists in dropdowns/radio buttons
  • Error messages
  • Meta tags and SEO content
You cannot change:
  • Screen structure or flow
  • Number of elements
  • Element types or positions
  • Actions and triggers
  • Form field requirements

AI translation

FunnelFox includes built-in AI translation for quick localization:
  • During locale creation: Enable Translate with AI when creating a new locale for instant translation of all content.
Translate with AI
  • From the Locales page: Click Translate with AI on any existing locale to retranslate all content.
AI translation takes 1-2 minutes depending on funnel size. The page shows “Processing translation with AI…” during this time. You can navigate away and return later.
Review AI translations before publishing. Pay special attention to:
  • Brand names and product titles
  • Technical terms and acronyms
  • Calls-to-action (cultural adaptation needed)
  • Legal disclaimers and compliance text
  • Pricing and currency symbols

Pricing localization

To localize prices in FunnelFox, first create prices for each currency you need in Stripe. Learn more about prices in Stripe.
To show relevant currencies for each user and improve conversions, you can set up different local currencies for any locale using the Checkout element with Stripe:
  1. Open the locale in the Editor.
  2. In the Element tab of the Plan picker, update the currency and prices.
Plan picker prices
  1. Go to the Actions section in the Element tab of Checkout.
  2. From the Subscription dropdown, select the Stripe price in the relevant currency.
Local prices
  1. Save and republish to go live.

Override locale via URL

You can override the automatic locale detection by passing an ff-locale parameter in the URL query string. This is useful for:
  • Testing different language versions without VPN
  • Sharing direct links to specific language versions
  • Quality assurance and review workflows
  • Customer support scenarios
To do so, add ?ff-locale= followed by the locale code to any funnel URL:
https://example.fnlfx.com/welcome?ff-locale=de-DE
https://example.fnlfx.com/welcome?ff-locale=es-ES
https://example.fnlfx.com/welcome?ff-locale=fr-FR
The ff-locale parameter accepts standard ISO language codes in the format:
  • language-COUNTRY (e.g., en-US, de-DE, fr-FR)
  • language only (e.g., en, de, fr)
The ff-locale parameter must match one of your configured locales. If an invalid or non-existent locale is provided, FunnelFox falls back to automatic detection.

How override works

When a locale is set via URL parameter:
  • It overrides geographic and browser language detection
  • The preference persists throughout the funnel session
  • Subsequent page navigations maintain the selected locale
  • The parameter doesn’t need to be included on every page

Examples

Direct link to German version:
https://your-project.fnlfx.com/signup?ff-locale=de-DE
Append to existing parameters:
https://your-project.fnlfx.com/offer?utm_source=email&ff-locale=fr-FR
Testing multiple locales quickly:
# Open multiple browser tabs with different locales
open https://example.fnlfx.com/?ff-locale=en-US
open https://example.fnlfx.com/?ff-locale=de-DE
open https://example.fnlfx.com/?ff-locale=es-ES

Import/export translations

For professional translations or bulk editing, use the import/export feature:

Export

  1. Click Export from the Locales page
  2. Receive a TSV (Tab-Separated Values) file
Now you can share it with translators or translation services. The TSV file has the following structure:
Key                                             🌐 Default         🇩🇪 Germany • DE
screens.welcome.elements.heading.props.content  Welcome!          Willkommen!
screens.welcome.elements.button.props.text      Get Started       Loslegen
Each row contains:
  • Key: Unique identifier (don’t modify it)
  • Default column: Original text
  • Locale columns: Translated text for each locale

Import

  1. Ensure TSV maintains the exact structure
  2. Click Import and select your file
  3. Review changes in the editor
  4. Republish to make changes live
Import overwrites all existing translations for included locales. Always backup by exporting first.

Test locales

With the locale URL parameter and other methods, you have multiple ways to test:

Test different locales

  1. URL Parameter: Add ?ff-locale=xx-XX to force a specific locale
  2. Use VPN: Connect from different countries to trigger geo-detection
  3. Change browser language: Modify browser’s language preferences
  4. Use different devices: Test with colleagues in other locations
  5. Browser extensions: Use header modification tools to change Accept-Language

Preview mode test

Preview mode uses the same locale detection as production, including support for the locale URL parameter. Your detected locale in preview helps verify the experience visitors will see.

Locale identifiers

Your webhooks and API responses include:
  • locale: Full locale name (e.g., “Germany • DE”)
  • locale_code: ISO format (e.g., “de-DE”)

Troubleshooting

Ensure you republished the funnel after making localization changes. Check that your test location/language matches your locale rules.
Review your locale priority rules. More specific rules (exact country + language) take precedence over catch-all rules.
I