> For the complete documentation index, see [llms.txt](https://powerfan-1.gitbook.io/redchat.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://powerfan-1.gitbook.io/redchat.app/faq/faq-story-chat-sharing.md).

# Sharing Stories & Chats

Want to share the stories you've created with a wider audience? On redchat, you can share individual chats one by one, or weave several chats together into a single **Story**. And when your shares bring in new friends, you can even earn rewards. Here's a quick rundown of the essentials.

***

## Q1. What's the difference between a Story and a Chat?

Here's the simple breakdown.

* **Chat** — A **single chat episode** with a character. Think of it as the most basic unit.
* **Story** — Several Chats bundled together into **one continuous narrative**. It's a collection that connects scattered episodes into a single thread.

> 💡 **Why bundle into a Story?** Stories get **better visibility** in Feed and Explore. Even for the same amount of content, organizing it into a Story gives it a better chance of reaching more people. Got a story you're proud of? Try bundling it into a Story!

***

## Q2. How do I share a chat?

Just three steps.

1. Open the chat you want to share.
2. Open the **chat side menu** and set it to **Public**.
3. A **share link** is generated automatically.

You can use this link freely outside of redchat. Just paste it anywhere — social media, messengers, communities — and you're done.

> Nervous because it's your first time? Even after switching to public, **only people who have the link** can view it, so there's no need to worry.

***

## Q3. How do I create a Story?

There are two ways. Go with whichever is easier for you.

**Option 1 — From the Create page**

1. Go to the **Create** page
2. Select **Story**
3. Choose a **title, category, and the chats to include** — done!

**Option 2 — Directly from within a chat**

* You can bundle a chat into a Story right from the chat screen you're in. It's perfect for organizing a story on the spot, the moment you fall in love with it.

> Want more detailed steps? Take a look at [Quick Creation](/redchat.app/guides/quick-creation.md) and [Advanced Creation](/redchat.app/guides/advanced-creation.md) as well.

***

## Q4. Can I actually make money from sharing?

Yes, you can! 🎉

When someone uses your share link to **newly sign up and make a purchase** on redchat, you earn **30% of their payments for a full year** as a reward. All you did was introduce a character or story you love — and the earnings follow.

> Curious about the full reward structure (including the family referral system)? Check out [Monetization & Visibility](/redchat.app/faq/faq-monetization-visibility.md) for all the details.

***

## Still have questions?

Couldn't find your answer here? Reach out anytime via our support chat (bottom-right of your screen) — we'll help you out fast. 💬


---

# 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://powerfan-1.gitbook.io/redchat.app/faq/faq-story-chat-sharing.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.