> For the complete documentation index, see [llms.txt](https://docs.shortify.wtf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shortify.wtf/features-overview/image-overlays.md).

# Image Overlays

### Layer branding and visuals on your clip

Stack images beneath or alongside captions to brand clips for your project, token, or personal channel.

#### What's live

| Capability          | Detail                          |
| ------------------- | ------------------------------- |
| **Formats**         | JPG, PNG, GIF, WebP             |
| **Layering**        | Images sit under caption text   |
| **Opacity control** | Fine-tune visibility over video |

#### Use cases

* **Token logos:** Watermark clips with your project mark
* **Meme templates:** Layer reaction images over viral moments
* **CTA graphics:** "Buy $TOKEN" or "Join Discord" overlays on promo clips
* **Brand kits:** Consistent visual identity across a content series

#### Coming soon

* **Start/end timing:** Show overlays only during specific segments
* **Multiple overlay tracks:** Stack and sequence multiple images

***

##


---

# 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.shortify.wtf/features-overview/image-overlays.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.