> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/form-management/form-designer/multi-language-forms.md).

# Multi-Language Forms

For surveys that targets a worldwide audience of respondents who don't speak the same language you may create a multi-language based survey that will adapt its content based on the respondent language. 

Using the multi-language features of ngSurvey we can translate a single survey into multiple languages and let the respondent choose in which language he wants to take the survey.

At the end of the survey you can use the [reporting ](/form-management/reports.md)tools either have a global look at your results or a using a more granular approach a filter the responses based on their languages.

{% hint style="info" %}
You may also follow our quick walkthrough on [how to create a multi-language survey](/walkthroughs/translate-a-survey.md).
{% endhint %}


---

# 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.ngsurvey.com/form-management/form-designer/multi-language-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.