> For the complete documentation index, see [llms.txt](https://docs.subscripta.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.subscripta.app/builder/media-banners-and-qr-codes.md).

# Add logos, photos, banners, and QR codes

Media makes signatures more branded, but email clients are strict. Use public HTTPS images whenever possible.

## Profile Photos

1. Open **Builder**.
2. Add or upload the profile photo.
3. Enable profile photo display if the template supports it.
4. Save the signature.

## Company Logos

1. Add or upload the company logo.
2. Enable logo display if needed.
3. Review the preview.
4. Save the signature.

## Campaign Banners

1. Add the banner image URL or upload the banner.
2. Enable the banner.
3. Optionally enter a **Banner click URL**.
4. Save the signature.

Banner click tracking requires Pro or Business.

## QR vCards

1. Enable **Show QR**.
2. Make sure full name and email are filled in.
3. Save the signature.
4. Subscripta stores a permanent QR image URL when possible.

QR Code vCard requires Pro or Business.

## Clickable QR Links

Clickable QR links require Business. They let the QR image link to a URL and track QR clicks.


---

# 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.subscripta.app/builder/media-banners-and-qr-codes.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.