> For the complete documentation index, see [llms.txt](https://docs.convai.com/api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.convai.com/api-docs/no-code-experiences/chat-experiences/share-files-with-the-room.md). # Share files with the room Understand what reaches the characters when you attach a file to a message in a chat experience room, and what the room keeps afterwards. A message you send in a [chat experience](/api-docs/no-code-experiences/chat-experiences.md) room can carry files. A file is never handed to the characters as a file: what reaches them is text—either the words the file already holds, or a description written for it. These pages cover what each kind of file becomes, what the room shows you about it, and what is kept once the conversation is over. ### What the characters receive A file goes to the characters that turn is addressed to. A character the message did not address is not given the file, and the replies that follow do not pass it on. If you want every character to have a file, address the message to everyone—tag `@everyone`, or set the respond chip to **Everyone must respond**—before you send it. See [Choose who replies](/api-docs/no-code-experiences/chat-experiences/running-the-room/choose-who-replies.md). Those characters receive text, and only text. A room carries writing, so every file you attach becomes writing before it travels. There are two ways that happens. A file that holds words is shared as its own words: a PDF, a Word file, and every plain-text format reach the characters as the text they contain. A file that holds a picture cannot be shared that way, so a description of the picture is written and the characters receive the description instead. The characters are told that the words describe a picture you attached, and that description is all they have to answer from. A file you share belongs to the conversation you shared it in. Every new conversation starts with nothing shared. ### What each kind of file becomes | What you attach | What reaches the characters | | --------------------------------------------------- | ----------------------------------------------------------------------------------- | | A plain-text file—`.txt`, `.md`, `.csv`, or `.json` | The file's own text | | A Word file—`.docx` | The text of the document | | A PDF carrying a body of prose | The text of the document | | A PDF carrying little text of its own | Whatever text it does hold, then a description of its first pages, written in words | | A picture—`.png`, `.jpg`, or `.jpeg` | A description of the picture, written in words | A PDF is the one format with two outcomes, and both are correct. [Share a document](/api-docs/no-code-experiences/chat-experiences/share-files-with-the-room/share-a-document.md) sets out which one you get and how the room tells you. ### When a file cannot be read A file the room could not read is still sent. Its name goes to the characters and nothing else, and the message is not held back. Nothing tells you in advance whether a file's contents can be shared. You find out afterwards. Every file you attach gets a chip above where you type, and the chip's second line settles once the file has been dealt with. A file whose contents were not shared says so on that line, and a file the room could not read—or a picture it could not describe—also raises a message naming the file. The paperclip that attaches a file is greyed out only while the message box is locked. No file makes it unavailable. See [You cannot send a message](/api-docs/no-code-experiences/chat-experiences/troubleshooting/composer-is-locked.md) for every reason the box locks. ### What the room keeps The room keeps file names, not file contents. Three places show a file after you send it: * **The thread.** The message you sent carries a chip for every file that went with it. * **The side panel.** Its **Shared in room** section lists the files sent so far in this conversation, each with its name, the same second line as the chip, and a note saying what the characters were given. [File limits reference](/api-docs/no-code-experiences/chat-experiences/share-files-with-the-room/file-limits-reference.md) sets out what each note means, and [Running the room](/api-docs/no-code-experiences/chat-experiences/running-the-room.md) covers the panel's other sections. * **A finished session's transcript.** It records the name of every file a turn carried, and a transcript you download lists those names under the turn they were sent with. See [Review a past session](/api-docs/no-code-experiences/chat-experiences/sessions-and-transcripts/review-a-past-session.md) and [Export a transcript](/api-docs/no-code-experiences/chat-experiences/sessions-and-transcripts/export-a-transcript.md). **Clear conversation** in the room's three-dots menu empties the **Shared in room** list along with the thread. See [Room controls reference](/api-docs/no-code-experiences/chat-experiences/running-the-room/room-controls-reference.md). Because only names are kept, every file in a past session's thread is shown as a name, whatever happened to it at the time. A transcript records that a file was shared, not what the characters were given from it. ### Which page answers which question
Share a document
Attach a PDF, a Word file, or a plain-text file, and read what the chip reports about it.		Share a document
Share an image
Attach a picture, and understand what the characters are told about it.		Share an image
File limits reference
The accepted file types, the size and text limits, and what happens at each one.		File limits reference
The message box, where a file is attached, is one of the room's three working parts. {% content-ref url="/pages/kSda6H5yqLJkFsnndHYK" %} [Running the room](/api-docs/no-code-experiences/chat-experiences/running-the-room.md) {% 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 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.convai.com/api-docs/no-code-experiences/chat-experiences/share-files-with-the-room.md?ask=&goal= ``` `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.