> For the complete documentation index, see [llms.txt](https://docs.itranslator.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itranslator.app/amazing-features/automatic-translation/configure-style-and-format.md).

# Configure style & format

You can fully customize the style and formats of the translation, here is how!

<figure><img src="/files/ivgB9YYK4KkC6hhzM9Q9" alt=""><figcaption></figcaption></figure>

## 1. Configure Style

There are actually 3 styles available: `TEXT`, `EMBED`, `WEBHOOK`.

<details>

<summary>TEXT</summary>

<img src="/files/st01heKPdWxhcN3V2zer" alt="TEXT" data-size="original">

</details>

<details>

<summary>EMBED</summary>

<img src="/files/sRMqPkFHOSRQvcJEypTH" alt="EMBED" data-size="original">

</details>

<details>

<summary>WEBHOOK</summary>

<img src="/files/RW0chPcCx04bXNkmTpEE" alt="WEBHOOK" data-size="original">

</details>

*(Yes, these languages don't have the same source because these screens come from different times)*

#### How to change the style of my Auto-Translate configuration?

Just run the command: `/autotranslate config style`

<figure><img src="/files/AQpoAtQzax9VywnAEPjM" alt=""><figcaption><p>iTranslator Automatic-Translation Style</p></figcaption></figure>

## 2. Configure Format

{% hint style="info" %}
This feature requires [**Premium**](/overview/premium.md).
{% endhint %}

<figure><img src="/files/ss6oV70gJFqwwnhg3wb7" alt=""><figcaption></figcaption></figure>

Now that you've chosen your style, you'll probably want to change the format of that style - here's how!

Just run the command: `/autotranslate config format`

You will then be redirected to a Modal where you can configure the translation format in detail! Brilliant, isn't it?

We're going to set up an Auto-Translate with the EMBED style as a tutorial.

<details>

<summary>Tutorial with EMBED style as example</summary>

1\) We run the command

![](/files/3XZzNGMAUNNtvNQewb4F)

2\) It automatically open the configuration modal

3\) Fill the fields using variables explained at the end of the page

4\) Click 'Submit'

5\) Success!

</details>

{% hint style="success" %}
Now that you understand how styles and formats work, you need to use variables in your formats. Variables allow you to insert text dynamically into your formats in order to configure your messages as much as possible.
{% endhint %}

### Variables you can use everywhere in formats

| Variable                  | Description                                              |
| ------------------------- | -------------------------------------------------------- |
| {source\_language}        | Source language of the translation.                      |
| {language}                | Target language of the translation.                      |
| {translation}             | Translated text.                                         |
| {billed}                  | Cost of the translation (in billing).                    |
| {original\_message}       | Content of the original message.                         |
| {original\_message\_link} | Jump URL to the original message                         |
| {source\_channel}         | Mention of the source channel.                           |
| {source\_channel\_name}   | Name of the source channel.                              |
| {user}                    | Mention of the message author.                           |
| {user\_name}              | Effective name of the message author.                    |
| {user\_avatar}            | URL of the message author's avatar.                      |
| {member}                  | Mention of the server member (if available).             |
| {member\_name}            | Effective name of the server member (if available).      |
| {member\_avatar}          | URL of the server member's avatar (if available).        |
| {guild\_member\_count}    | Total number of members in the server.                   |
| {guild\_boost\_count}     | Number of server boosts.                                 |
| {guild\_boost\_tier}      | Server boost level.                                      |
| {guild\_icon}             | URL of the server icon.                                  |
| {guild\_banner}           | URL of the server banner.                                |
| {guild\_channel\_count}   | Total number of channels in the server.                  |
| {guild\_role\_count}      | Total number of roles in the server.                     |
| {guild\_owner}            | Mention of the server owner (if available).              |
| {source\_language\_flag}  | Flag emoji(s) of the source language of the translation. |
| {language\_flag}          | Flag emoji(s) of the target language of the translation. |
| {user\_role}              | Name of the highest role of the user.                    |
| {user\_role\_mention}     | Mention of the highest role of the user.                 |

{% hint style="info" %}
**Could a missing variable be useful?** Don't hesitate to ask us to add it to our [Discord Support](https://discord.itranslator.app)!
{% 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 dynamically by asking a question.

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

```
GET https://docs.itranslator.app/amazing-features/automatic-translation/configure-style-and-format.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.