> 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/whats-new/view-email-in-browser.md).

# View Email in Browser

Give your recipients a seamless backup way to view your emails—perfect for sharing, texting, and ensuring nothing gets missed. Instantly turn any email into a shareable web link.

<figure><img src="https://1031368632-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MJZySovZjoLVT1XAonI%2Fuploads%2FwS3NgBM1Kwmh7eY4B5Us%2FView%20in%20Browser.png?alt=media&amp;token=f204a912-b3a3-44e1-9c30-3f2f9ae4b8e3" alt=""><figcaption></figcaption></figure>

Ever sent an email that didn’t display quite right, or wished you could quickly share it via text or social?

**Now you can.**

With **View Email in Browser**, you can add a button to your email that allows recipients to open a fully formatted web version of your message in their browser.

#### Why This Matters

This isn’t just a “nice to have”, it unlocks entirely new ways to use your email content:

* **📱 Text your email as a link** Send your newsletter or listing email via text message by sharing the browser link.
* **🏡 Share listings more easily** Include the link in conversations, DMs, or follow-ups when a client prefers not to dig through email.
* **🖥️ Ensure perfect formatting** If an email client cuts off images or formatting, recipients can view the full experience in their browser.
* **🔁 Reuse your content anywhere** Drop the link into social media, CRM notes, or follow-up messages.

{% content-ref url="/pages/zhEjuMTeJnSPTI48U4T5" %}
[Broken mention](broken://pages/zhEjuMTeJnSPTI48U4T5)
{% endcontent-ref %}


---

# 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://help.rechat.com/whats-new/view-email-in-browser.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.