> For the complete documentation index, see [llms.txt](https://support.pipefile.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.pipefile.com/requests/translations.md).

# Send requests in another language

Send a request in Spanish, French, Portuguese, Russian or Chinese, with translated emails and upload page.

Each request has a language. Pipefile shows the recipient's upload page and sends its own emails and text messages in that language.

## Supported languages

English (the default), Spanish, French, Portuguese, Russian and Chinese.

## Choose a language

{% stepper %}
{% step %}

### Build your request

Create the request as usual. Write the subject, message, checklist item names and instructions in the recipient's language.
{% endstep %}

{% step %}

### Open the Advanced options

Click **Next**. In the **Send Request** dialog, click **Advanced**.
{% endstep %}

{% step %}

### Pick the language

Choose the language from the **Language** menu, then click **Send Request**.
{% endstep %}
{% endstepper %}

To change the language of a request you've already sent, open it, click the **Edit request** icon, click **Next**, and change it under **Advanced**. To make a language the default for a kind of request, set it under **Advanced** in a template. Every request sent from that template, including through [bulk send](/requests/bulk-send.md), uses it.

## What gets translated

| Translated by Pipefile                                                                                                 | Not translated                                                                                                                         |
| ---------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| The recipient's upload page: buttons, labels, status messages and help text                                            | Your subject and message                                                                                                               |
| Pipefile's standard emails to recipients, such as the new request, reminders, review results, completion and reopening | Checklist item names, instructions and section titles                                                                                  |
| Pipefile's standard text messages                                                                                      | Files you attach                                                                                                                       |
|                                                                                                                        | Emails and texts from a custom [notification sequence](/reminders-and-notifications/reminder-sequences.md), which use your own wording |

{% hint style="warning" %}
Pipefile doesn't translate what you write. Match your subject, message and checklist to the language you choose, or the recipient sees a mix of languages.
{% endhint %}

If you use a custom notification sequence, write a version in the recipient's language and choose it under **Advanced** > **Notification Sequence** along with the language.

## What you see

A request's language only affects what the recipient sees. It doesn't change your dashboard or the notification emails Pipefile sends to you and your team.

## Related

* [Create and send a request](/requests/create-and-send-a-request.md)
* [Create and edit templates](/templates/create-and-edit-templates.md)
* [Recipient FAQ](/for-your-clients/recipient-faq.md)


---

# 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://support.pipefile.com/requests/translations.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.