> 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/exports/which-export-should-i-use.md).

# Which export should I use?

Different email apps accept and rewrite signatures differently. Pick the export based on where you install the signature, not only where recipients read it.

| Export          | Best For                                                                 | Tradeoff                                                |
| --------------- | ------------------------------------------------------------------------ | ------------------------------------------------------- |
| Gmail / Outlook | Pasting directly into compose windows or signature editors.              | Rich clipboard support depends on the browser.          |
| Copy HTML       | Webmail and source-based installs. Keeps Gmail iOS dark-mode protection. | Some desktop clients may rewrite advanced CSS.          |
| Email Clients   | Desktop apps like eM Client that break advanced CSS.                     | Gmail iPhone may still gray forced white identity text. |
| PNG / JPG       | Exact visual appearance.                                                 | Links are not clickable and text is not selectable.     |
| Apple Mail      | macOS Apple Mail setup.                                                  | Requires using the guided install flow.                 |
| Plain Text      | Fallback signatures or systems that reject HTML.                         | No images, styling, tracking icons, or layout.          |

## Recommended default

Use Gmail / Outlook or Copy HTML first. Use Email Clients only when a desktop app breaks the standard HTML. Use PNG only when exact appearance matters more than links.

## Quick Rules

* Use **Gmail / Outlook** when pasting into Gmail, Outlook, or a rich signature editor.
* Use **Copy HTML** when a webmail client lets you paste or edit HTML source.
* Use **Email Clients** when a desktop email app rewrites the standard HTML or creates visual artifacts.
* Use **PNG / JPG** only when the visual result matters more than clickable links.
* Use **Plain Text** when a system rejects HTML.


---

# 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://docs.subscripta.app/exports/which-export-should-i-use.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.