Hi @Scott Haggar I believe you are correct that it should be able to determine the language of the respondent’s browser. However, as for setting the language, are you looking to have a different language than the one in your builder? For example, if the respondent speaks French, it would automatically show in French? If so, I don’t think this is possible but @mathio or @picsoung can confirm!

Yes, it seems to only respect the user’s browser settings.

Our website can be manually switched by the user and declares the language in the head. If a user’s browser default is English and they navigate to the French site, I would like the form to be in French. Additionally, even if a user’s browser is set to French and they are on the French site, the typeform starts in English and asks the user if they would like to switch.

Ideally, it would be an attribute in the embed that would determine if the form should display in French (no prompt).

Unfortunately I dont think it is possible to explicitly switch language of your tyepform.

@Liz I think this functionality is a good candidate for a feature request.

Thanks for the clairity @mathio. I whole heartly agree it would be a great feature! Attached is a mock of where I would have expected the option when creating the embed. 

Hello @Scott Haggar , I think this is the first time I see this setting. Is this something available on the share page or just a mock you created yourself?

Sorry to be unclear. I made this. I thought I would have an option like this once I upgraded my plan :D

I would like this feature as well - more generally, to be able to specify the language as a URL parameter. 

I’m sending surveys to my customers, they speak multiple languages and I know what language they have set their account to, it would be very simple for me to have a local=en-CA or local=fr-CA

Right now the form defaults to french and gives the option to switch language at the top, which is a good back up, but since I know the desired language, this URL parameters would be better. I’m already using other URL parameters (hidden fields).  

Hi ​@jgoldes Happy Tuesday! Thanks for stopping by and sharing more about your use case.  That makes total sense then to have it set a default if you already know their preferred language. I’ll share this with the product team so they have some context!

Typeform’s Multilingual Support is Misleading & Completely Broken

This is absolutely ridiculous. Here’s my experience attempting to utilize multilingual support as advertised by type-form:

1. I upgraded to Professional because Typeform advertises AI support for multilingual forms.
2. As soon as I upgraded and tried to use this feature, I was immediately hit with an error telling me that my form is too long and that I need to shorten it if I want AI translations. Nowhere was this limitation disclosed before upgrading.
3. Not willing to give up, I manually translated my form using DeepL, then followed Typeform’s own instructions to upload the translated content via the provided spreadsheet template.
4. After successfully uploading the translation, I realized that I have absolutely ZERO control over whether it actually gets displayed to users.
5. Instead, the only thing that determines which language my form shows in is the user’s browser settings—something I have no control over whatsoever.

Let me be clear: This is NOT how the internet works in 2025. Every modern platform allows creators to dictate how their content is displayed, except Typeform.

So here’s my question:

• How is this still a thing?
• How has this not been fixed despite clear demand?
• Why is this limitation hidden from paying users until after they upgrade and attempt to use the feature?

This is completely misleading, and honestly, it’s unacceptable for a premium service. Typeform needs to publicly clarify this limitation upfront so people don’t waste time and money expecting functionality that simply doesn’t exist.

Someone from Typeform, please explain how this hasn’t been addressed yet.