> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/guides-and-best-practices/message/email/design-and-layout/how-to-add-a-background-to-your-email.md).

# How to add a background to your email?

Find out how to build consistency in your email design.

Backgrounds can be applied either to **individual containers or stripes**, or to the **entire email**, depending on your design objectives.&#x20;

When used on specific containers or stripes, backgrounds help draw recipients’ attention to particular sections and highlight key content. When applied to the full email, they contribute to a cohesive and polished design, ensuring **visual consistency** throughout the message.

## Add a background color

Each element of the structure of your email has its own background. It allows you to enlighten specific parts of your email.

{% hint style="warning" %}
If you want **one unique color**, you need to change the background **for all the elements.**
{% endhint %}

To add the background color, click on **the element of the structure** in your email, click the **Styles** button and on the options panel on the right, you'll find the **Content Background color** field. Choose a color among the proposition or type the color code of your choice:&#x20;

<figure><img src="https://509463063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfiAYaWDWqtFZeXxyg67F%2Fuploads%2FUe2labnhl6LAX7jlfKpF%2FCleanShot%202026-02-10%20at%2016.11.50.gif?alt=media&amp;token=ff142f1c-6353-4a90-a0c4-9963b4ffdcee" alt=""><figcaption></figcaption></figure>

## Add a background image <a href="#h_ade52cef08" id="h_ade52cef08"></a>

{% hint style="danger" %}
First, note that the background image will be visible on desktop, but **not on mobile devices**.
{% endhint %}

To add a background image, click on **the element of the structure** in your email, click the **Styles** button and enable the **Stripe Background image** toggle:&#x20;

<figure><img src="https://509463063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfiAYaWDWqtFZeXxyg67F%2Fuploads%2FziwHnnOhnvK5t9XKA9Zw%2FCleanShot%202026-02-10%20at%2016.21.58.gif?alt=media&amp;token=6ab7f531-4a01-4b32-915b-124c189381f1" alt=""><figcaption></figcaption></figure>

There, add your image by dropping one or with an external link. Check our documentation if you need help [handling the image and editing it](https://doc.batch.com/guides-and-best-practices/message/email/how-to-add-and-edit-images-in-your-email).

Once the chosen image is here, you can set it up! Define its position and click the **Background repeat** toggle if you want your image to be applied to the whole email, no matter how long it is:&#x20;

<figure><img src="https://509463063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfiAYaWDWqtFZeXxyg67F%2Fuploads%2FNfYDwAdN3erRN2UXUHHQ%2FCleanShot%202026-02-10%20at%2016.36.34%402x.png?alt=media&amp;token=99d81028-c574-4956-b9f5-f4cb9c35f392" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Note that some email providers, such as Outlook, may not display the background image. We recommend that you also define a background color, **similar to the background image**.
{% 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://doc.batch.com/guides-and-best-practices/message/email/design-and-layout/how-to-add-a-background-to-your-email.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.
