# Translation files

**Translation Files** simplify the localisation of templates by allowing you to manage multilingual content in a single, centralised system. With Translation Files, you can dynamically serve the correct language version of text in your templates based on your recipients’ locale, reducing the need for multiple templates and improving campaign efficiency.

### Key Features

#### Centralised Management

* Upload translation files in the Bird CRM interface.
* Store translations for multiple locales in a single file, reducing duplication and streamlining updates.

#### Dynamic Translation Rendering

* Automatically fetch the correct translation for a recipient’s locale using Liquid syntax.
* Include fallback logic to ensure messages always render, even if a translation is missing.

#### Flexible Format

* Use CSV files with row keys for locales (e.g., `en-EN`, `fr-FR`) and column keys for translation content (e.g., `header`, `body`).
* Example file structure:

| locale | header               | body                                             |
| ------ | -------------------- | ------------------------------------------------ |
| EN     | Welcome to Bird!     | We can’t wait for you to get started with Inbox. |
| FR     | Bienvenue chez Bird! | Nous avons hâte que vous commenciez avec Inbox.  |
| ES     | ¡Bienvenido a Bird!  | Estamos ansiosos por que empieces con Inbox.     |

#### Multi-Channel Support

* Use translation files across supported channels including email and also SMS and push notifications if enabled.

#### Locale-Based Personalisation

* Dynamically select translations based on the recipient’s locale attribute (e.g., `contact.attribute.locale`) or other custom attributes.
* Ensure consistent messaging for global audiences.


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bird.com/applications/content/translation-files.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.