> For the complete documentation index, see [llms.txt](https://help.rechat.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rechat.com/guides/marketing/marketing-center/email-marketing/embedded-videos.md). # Embedded Videos Rechat's ability to embed videos within emails is a popular feature. \ However, there are some technical limitations in Emails. Most importantly is that Emails natively do not support video. In order for Rechat to embed a video in an email we convert them into a format called `GIF`. To email clients, `GIF`'s are basically animated images. This format comes with 2 severe limitations: 1. The output cannot have more than 256 colors. 2. The file size of the output will be extremely large. If the video is more than a few seconds long, most email clients will just refuse to render it. For the 2 reasons above, the embedded video will have lower quality and will be short. ### Why use videos? Given the limited quality of the videos, you may ask yourself why would you embed a video in your email if it cannot look good?\ The reason is, emails with such embedded videos usually have a very high click through rate and people seem to be very forgiving of the low quality nature of them. Different reports suggest up to 75% click through rate improvement on such emails. --- # 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://help.rechat.com/guides/marketing/marketing-center/email-marketing/embedded-videos.md?ask=&goal= ``` `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.