> For the complete documentation index, see [llms.txt](https://docs.bird.com/taxi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bird.com/taxi/email-design-systems/custom-email-design-systems/uploading-a-custom-email-design-system-to-taxi.md).

# Uploading a custom Email Design System to Taxi

To build an email in Taxi, you can either use one of the [built-in ](/taxi/email-design-systems/built-in-taxi-email-design-systems.md)Email Design Systems, or a custom one. First, you'll need to build the email in your usual code editor, including the [Taxi Syntax](http://taxiforemail.com/code) to make it work with the Taxi Editor. Once you've done this, you'll need to upload it to your Taxi account.

To upload a custom Email Design System:

1. Click on the 'Email Design System' tab in your account
2. Click 'Add New'
3. Complete the 'Name' and 'Description' fields
4. Select how you'd like to upload your code\
   You can either upload the file, paste in your HTML, or create a Brand

![](https://2516523503-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMq0EQG9Ff46ZMsrIBcVn%2Fuploads%2Fgit-blob-0cdc6dc7214d967183aaf7bfefb35c581d96e933%2Fcreatenewbrand.png?alt=media)

5\. Select 'Create Email Design System'

6\. The next step is a 'Code Check' if you have any errors in your template they will show here.\
You can find out more about errors [here](https://docs.messagebird.com/taxi/Email%20Design%20Systems/Custom%20Email%20Design%20Systems/understanding-email-design-systems-uploader-error-messages).

7\. Click 'Continue' at the bottom of the page

![](https://2516523503-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMq0EQG9Ff46ZMsrIBcVn%2Fuploads%2Fgit-blob-7355cd22ea425927c2a63817a5e6de0ebdd9a278%2FScreenshot%2B2020-09-08%2Bat%2B12.10.24.png?alt=media)

8\. On the Image Assets page, you need to select where your images will be hosted from the dropdown

* Leave on remote host: is selected when you want to leave the images where they are hosted. In the HTML you'd have image URLs that have already been hosted and they stay hosted in this way
* Download from remote host: images would be downloaded and used on the Taxi CDN for Taxi to host. This is also selected if you want images to be added to a zip file on export.
* Copy images from zip file. If you upload your HTML in a zip file along with the images for your Email Design System then choose this option. On future uploads of the EDS Taxi will remember the images from the zip file so you don't have to include it each time.

9\. Select 'Set Email Design System Owner and Guide'\
You can read more on Email Design System owners [here](http://get.taxi.support/en/collections/93646-email-design-systems#email-design-system-owners)

10\. Select Save & Finish.

11\. You can see a preview of what your Email Design System looks like on the Settings page.

Click on Preview and it will show your Email Design System

![](https://2516523503-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMq0EQG9Ff46ZMsrIBcVn%2Fuploads%2Fgit-blob-8d5dda870175ccca2ad6f72bd2d630a518d4a6b3%2FScreenshot%2B2020-10-13%2Bat%2B12.11.01.png?alt=media)


---

# 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.bird.com/taxi/email-design-systems/custom-email-design-systems/uploading-a-custom-email-design-system-to-taxi.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.