> For the complete documentation index, see [llms.txt](https://docs.feathery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feathery.io/platform/international-forms/translate-forms.md).

# Translate Forms

Feathery forms can be easily translated into different languages and conditionally served to your different audiences based on their region.

You create your Feathery form in a particular language, but you may need to serve the same form to international audiences of different languages. Rather than rely on Google Translate's default translation, it's easy to create and maintain your own custom translations that are automatically applied based on the user's preferred language.

## Adding a custom translation

1. Go to the `Custom Translations` section of your form `Settings` tab.
2. Download the `Default Translation` file, which will contain phrases from your existing form that should be translated to the new language you wish to add. If you don't wish to completely translate your form, you don't have to add a translation for every single phrase.
3. Once you've completed the translation file, click `Add New Translation`.
4. Choose the language that you've created a custom translation for.
5. Upload your file
6. Click `Add`
7. You're done! To view the new translation you've created for the form, you can click the preview icon on the language you've added.

## Viewing the custom translation

By default, your form will show up for users in their browser's preferred language. You can override this in a few ways.

* From your browser settings, you can adjust your personal user interface language. Your form will detect this adjustment and switch translations if one exists.
* To directly view the custom translation you've created, go to the `Custom Translations` section of your form settings. Find the language you want to view, and click the preview icon. This will open up the translated form in a new tab.
* If you have the URL of your Feathery form, you can add the `_locale` query parameter mapped to the [ISO 639-1](https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes) code corresponding to the translation you want to view it in. So if your URL is `https://form.feathery.io/to/abcdef`, to view the Spanish version you would change it to `https://form.feathery.io/to/abcdef?_locale=es`.
* If you embedded your Feathery form with our React or JS SDK, you can pass your desired language code in as an [initialization option](/develop/react/api-guide/init.md) using the **language** parameter.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.feathery.io/platform/international-forms/translate-forms.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.